Latest DNG converter not working in command-line mode

I have another issue that has been asked previously but not addressed. I'm trying to use the -d switch to specify that files should be saved in C:\RAW_Destination. I have used the following command variations:

1. C:\[path to DNG exe]\Adobe DNG Converter.exe -d c:\RAW_Destination c:\RAW_Source

2. C:\[path to DNG exe]\Adobe DNG Converter.exe -dc:\RAW_Destination c:\RAW_Source

3. C:\[path to DNG exe]\Adobe DNG Converter.exe dc:\RAW_Destination c:\RAW_Source

4. C:\[path to DNG exe]\Adobe DNG Converter.exe d c:\RAW_Destination c:\RAW_Source

Variation 1: does not run
Variation 2: runs without the correct destination directory, but with the correct source directory
Variation 3: runs without the correct destination directory, but with the correct source directory
Variation 4: thinks the destination I've specified is actually another input parameter

What is the correct syntax for the -d parameter? Is there a dash before, and a space after? Do I need to separate the parameters from the input files with some character?

Thanks very much for your help.

> Recent version of the DNG Converter for Windows have required full path names in command line mode (rather than allowing paths relative to the working directory). I have just fixed this in the code and the fix will appear in the next release (5.2).

That's good to hear. I'll look forward to it, and in the meantime will use the workaround with the fully qualified path name.

(Feature request for some future version: the ability to specify multiple files via wildcard in command-line mode. This doesn't seem to be supported yet...)

Thanks.

Recent version of the DNG Converter for Windows have required full path names in command line mode (rather than allowing paths relative to the working directory). I have just fixed this in the code and the fix will appear in the next release (5.2).

Try typing a full path to the file and see what happens.

> Macintosh or Windows? What command line shell are you using?

I'm running the converter under Windows XP service pack 2.

After seeing your reply I realized I had not tried running the program in a cmd.exe console window -- I'd been using only the 4NT version 5 command shell (meaning JP Software's command shell product 4nt.exe). For this latest attempt, I used both shells. The arguments/switches were:

-u -e -p1 -o _MG_0972.CR2 _MG_0972.dng

This time I added an explicit switch/arg for the output file to see if that would make any difference.

Result in both the cmd.exe shell and the 4NT shell:

I got output with the DNG converter that was released at about the time Photoshop CS2 was released, but no output with the one I downloaded most recently from Adobe's web site.

Variations: 1) omitted "-o filename" -- same results. 2) omitted "-o" and used "*.cr2" for the input filename; in that case neither converter version produced output; 3) omitted "-o" and used ".\" for the input file, in case the converter would accept that for "all raw files in the current directory" -- again neither converter version produced any output.

Macintosh or Windows? What command line shell are you using?

Is there anyone from Adobe who might have the time to respond to this question? Given the command-line switches and arguments shown in the previous message, does it look as if I am giving the commands incorrectly?