Solaris

Saloman,
What we are seeing from the strings and "od -bc" of the files is that the patient and other information is embedded into the same file as the actual image data, presumably if you run "strings <file> | more" and keep looking you will see something to indicate the start of the actual image data after the end of the patient related data? It looks like with a "strings <file> | head -10" we have got up to the time when the image was taken in the data, we need to see what comes after that...

Found this document that talks about JETConnect and DICOM images:
http://incenter.medical.philips.com/...986%26vernum=1 in relation to adac01 (mentioned as the header to the img file.

The DICOM image format is mentioned at:
http://en.wikipedia.org/wiki/Digital...ns_in_Medicine

Thanks for the assistance. I've learned that this nuclear machine (Philips) interfaces with this application (Pegasys) on SunOS 5.8 which produces image files. I also learned that this Pegasys application can save this data onto a mounted optical disc. Then it can upload the data to recreate the patient images - heart - cardiology. So it makes sense to me that I need to be able to read this optical disc so I can further trace this problem - need. I would like to be able to use a Windows Explorer like tool so I can read this optical disc on SunOS 5.8. A korn or C shell? Any ideas?

Your assistance is greatly appreciated!
~Salomon

Don't know about reading the optical disc but this site is an introduction to DICOM images and includes links to free DICOM image viewers including on Windows:
http://www.sph.sc.edu/comd/rorden/dicom.html#links

The simplest method of getting the files off the Solaris machine and onto a Windows machine is either using ftp/sftp/scp or by using a USB memory stick to transfer the images from the Solaris machine to your Windows machine.

The optical disc reader on the Solaris 8 machine is probably SCSI attached, you can get Adaptec SCSI cards for desktop PC's if the optical disc is not a normal CDROM/DVDROM.