Hello, please, see the attachments and config below. Could Conquest 1.4.16 possibly damage images like that?
Code
Hello, please, see the attachments and config below. Could Conquest 1.4.16 possibly damage images like that?
Hi,
seem very unlikely. I would guess this could be a disk or other hardware error. Is there any specific situation where this occured. When did it start happening?
Marcel
The images have a mixture of file blocks (like other dicom images, some even not from conquest) which suggest there is something wrong with the drive hardware.
Marcel
Marcel, thank you for your help.
As far as I know, disk was fine, and I think corrupted images actually could be a result of eFilm and Conquest interference.
I don't know how exactly it happened, but I heard, that some doubtful experiements could have take place.
Hi,
maybe conquest and efilm were somehow writing to the same files at the same time?
regards,
Marcel
Hi Marcel,
Yes, it seems that's what happend, I don't have any other explanations.
I suppose someone tried to make Conquest and eFilm share DICOM folder.
Don’t have an account yet? Register yourself now and be a part of our community!