Output path?

All other questions regarding DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
new2009
Posts: 14
Joined: Tue, 2009-06-02, 10:04

Output path?

#1 Post by new2009 »

Hi,

Is there any way to specify output path or output file for DCMODIFY?

I found dcmodify will create the output file in the same folder as the input file.

Thanks.

Michael Onken
DCMTK Developer
Posts: 2052
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

#2 Post by Michael Onken »

Hi,

no, so far there is no such option in dcmodify, sorry. However, I like the idea so I added this to our internal list of feature requests (with low priority, though).

Best regards,
Michael

new2009
Posts: 14
Joined: Tue, 2009-06-02, 10:04

#3 Post by new2009 »

Hi Michael,

Thanks for that. The reason for this feature is problem on Windows 2008 Server.

As part of our application, the dcmodify.exe is located under "Program Files" folder.

And because the dcmodify creates output to the same folder, the user must have administrative account to run it :(

Michael Onken
DCMTK Developer
Posts: 2052
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

#4 Post by Michael Onken »

Good point!

J. Riesmeier
DCMTK Developer
Posts: 2506
Joined: Tue, 2011-05-03, 14:38
Location: Oldenburg, Germany
Contact:

#5 Post by J. Riesmeier »

I guess you can change the current working directory before running dcmodify (and dcmodify is then using this directory for output, right?).

new2009
Posts: 14
Joined: Tue, 2009-06-02, 10:04

#6 Post by new2009 »

Hi J,

You are right.

I am able to workaround this by using that technique. Basically, I moved the dcminput file (only) to a user writable folder outside the Program Files.

I am using CSIDL_COMMON_APPDATA for now, but this has non-ideal situation because the folder is "hidden" by default.

Not a big deal, but less desirable (having to explain the user how to find the data, dcminput file!).

Post Reply

Who is online

Users browsing this forum: Ahrefs [Bot], Baidu [Spider], Bing [Bot], Google [Bot] and 1 guest