What is in the "printer files" directory?

  • Hi LJJ,


    Printer_files is used for printing, but also for temporary files passed to the decompressor and for conversion to GIF that should have been deleted after use. So yes you can delete any files in there.


    But I do not understand why they are there. Are they dicom files, gif images for the web viewer or text files?


    Maybe the server can create the images there but not delete them due to insufficient rights?


    What version and OS do you use?


    Marcel

  • hmm.
    All dicom files.
    I am trying to regen the database and clean it up via drag and drop, the printer_files directory immediately starts filling up with duplicates ( at least I think they are duplicates).
    I think this may be a permission problem but cannot pin it down yet. I did change dgate logon as local administrator rather than system account to fix the write to mirror problem. Could this be the problem? I did confirm that the directory has proper permissions for local administrator to write to the Printer_files directory. No change in the duplicates appearing.
    I am using XP sp2. Conquest latest beta version.


    This is unusual. I run three conquest servers on this machine, all mysql native. Two share a single database and file directory, the third has it's own database and different directory. All three are otherwise set up similarly. MySql native, mirror drive, log in service as local administrator. The problem is seen in my larger shared database, not the smaller solo database.
    So, now I can't even regen my database because printer_files quickly grows to gigantic (double) size.
    Anyone have this problem too? Or able to replicate it?
    Thanks, LJJ

  • Well, I just made a new data directory, pointed conquest to it and drop/dragged the old one and things seem to be going ok. The printer_files directory is being used correctly.
    Initially, my data directory was "Fairlight conquest" with a space. That seems to cause difficulties occasionally, so the new data directory is without a space in the name... I wonder if that was part of the problem?
    Anyhow, things seem to be ok now. No buildup of files in the printer_files directory and I am mirroring to a NAS drive succesfully.
    Good deal.
    Thanks for a great product, LJJ

  • Marcel, what is happening here?


    [FAIRLIGHT] ***[CompressJPEGImage]: Error on load after: dcmcjpeg +el +un +sr F:\fairdicom\printer_files\1.2.826.0.1.3680043.2.135.732936.34336296.6.1193697443.625.46.dcm out.dcm)
    [FAIRLIGHT] Added file: F:\fairdicom\SHC32732\1.3.12.2.1107.5.2.2.9934.20050112082909000002_0002_000138_11930002311285.v2
    [FAIRLIGHT] Mirror copy: \\N5200\usbhdd\FAIRDICOM\SHC32732\1.3.12.2.1107.5.2.2.9934.20050112082909000002_0002_000138_11930002311285.v2
    [FAIRLIGHT] 0000,0002 18 UI AffectedSOPClassUID "1.2.840.10008.1.1"
    [FAIRLIGHT] 0000,0100 2 US CommandField 48
    [FAIRLIGHT] 0000,0110 2 US MessageID 7
    [FAIRLIGHT] 0000,0800 2 US DataSetType 257
    [FAIRLIGHT] 9999,0400 88 UN "addimagefile:F:\\temp2\\1.2.826.0.1.3680043.2.135.732936.34336296.6.1193000231.890.74.dcm"


    Is the system leaving files in the printer_files secondary to a jpeg error? I have conquest set to jpeg lossless storage on Mag0.
    Thanks,
    Leszek

  • Indeed,


    after a jpeg error th file is left. You can try out the command line as shown in the error log to see the error message:


    dcmcjpeg +el +un +sr F:\fairdicom\printer_files\1.2.826.0.1.3680043.2.135.732936.34336296.6.1193697443.625.46.dcm out.dcm


    The problem with spaces is solved: I added quotes around the file name.


    Marcel

  • I had this error myself recently, the "error on load after dcmcjpeg"... etc. error. I am using lossless JPEG.


    Is this still a known issue? Is it just erroring out on trying to compress, and then storing the image uncompressed instead?

  • Hi,


    indeed this is the case. dcmcjpeg cannot compress the image. The uncompressed image is then left in the printer_files directory and can be inspected to see what goes wrong, for instance by giving the dcmcjpeg command (as show in the log) yourself. The code is such that failure of dcmdjpeg or dcmcjpeg will not lead to data loss: the original image is kept when that fails.


    Marcel

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!