DICOM @ OFFIS

The dcmprscu tool has nothing to do with DCMPRINT, I will, therefore, move this discussion to the DCMTK folder. The "index.dat" file is created or updated, for example, when you use the dcmpsprt tool to prepare a print job. The location of this file is defined in the configuration file tha...

There is no tool called "printscu.exe", neither in DCMPRINT nor in the public DICOM toolkit (DCMTK). The public toolkit contains a print client named "dcmprscu" and the DCMPRINT module has a totally different print client named "tcpprt". Both print clients require a con...

If you have created your own private dictionary, you can load that in addition to the other dictionary file(s) the DCMTK tools load. On Posix platforms, by default, /usr/local/dicom/lib/dicom.dic is loaded and private.dic is not. This behaviour can be modified through the DCMDICTPATH environment var...

Your life would probably be easier if you would read the installation instructions, and these are present in a text file named "INSTALL" in the DCMTK source code package.

There is no C-GET client in DCMTK, and actually I have never seen any other C-GET client. This is still a very rare thing. The imagectn application provides experimental support for C-GET, but since there is no client to test with, it is quite likely that there are still problems. The problem you re...

The missing functions here are Winsock functions - they should be in the wsock32 library. Maybe you are not linking the libraries in the right order?

In order to use C-GET, your client needs to negotiate C-GET as an SCU and in the same association all of the Storage SOP Classes that might be needed to retrieve the requested images, in this case with the SCP role using SCP/SCU role negotiation. This seems not to have taken place.

zlib compression can be used both for network transmission and for file storage, but both functions are independent of each other. The "zlib transfer syntax" indeed applies zlib compression to all of the dataset, including the image pixel data. Also thanks for the comment on the movescu ma...

If it's a CAT5 cable then it probably does not go to the PACS, but to a network switch or hub. In principle what you want is possible if you can unhook the imaging modality from the network. Create a direct connection to your laptop (will need a cross-link cable), configure your laptop to use the IP...

In principle, yes, but this may require modifications to the system configuration at the modality or PACS system, or both, depending on what exactly you want to test.

By default all libraries except libxml are configured as "on" in the CMake project files, and you would indeed need to have all external libraries compiled for /MD and /MDd if you wanted to use them with a DCMTK version compiled with this setting. Unfortunately, we do not have pre-compiled...

The error message "movescu: cannot create network" indeed indicates that something has gone wrong during the initialization of the application. Most likely, the creation of the listen socket (function "initializeNetworkTCP" in dcmnet/libsrc/dimse.cc) has failed for some reason I ...

Warnings about duplicate elements and elements sent out of order are indicating severe violations of the DICOM encoding rules. First of all you should report this to the manufacturer of the device that has produced the images - duplicate "versions" of attributes such as columns, rows etc. ...

Your questions are not really related to DCMTK, this rather sounds like a general DICOM question that should be posted to the DICOM discussion forum at comp.protocols.dicom . To give you a short reply here, in the normal CT/MR SOP class, each slice is a separate DICOM object and stored in a separate...

We have never observed such behaviour indeed - and to my knowledge nobody has reported this type of behaviour either by e-mail or in this forum before. That of course does not mean that there is nothing wrong with our code, but at least it seems to be a rather rare problem. For your information, the...