I'm starting to use a product that has one step of its installation/setup that
is a cmd script that calls a Java application that ends up using command.com to
call another Java application. The last Java application needs to references
environment variables set in the cmd script.
In Windows 2000, this process works fine. The last Java application sees the
environment variables fine. In Windows XP, however, the last Java application
seems to have no environment variables (I've only tried several, but I haven't
checked to see if there are any at all).
I wish they had written this process better (as the second Java application has
a relatively easy-to-use API that they could have just called directly from the
first Java application), but they didn't. I don't expect them to re-architect
this any time soon.
The question I have is, is there something that changed between Win2k and WinXP
in the area of calling other applications through command.com, such that a
downstream called application wouldn't be able to get any environment
Is there something they're supposed to use instead of "command.com" for this
sort of thing? I know there's "cmd" and "command", and "cmd" appears to be
much more functional, but I don't know a lot about the differences between
David M. Karr ; Java/J2EE/XML/Unix/C++