As I have only a nondirect access to the computer (I must ask a person
which
is given the permission to access it) I did not get all the information I
asked for.
Nethertheless I have got some more information.
1. Running command.com /c dir just opened the window, listed the filenames
quickly and closed it.
2. Running command.com opened the usual window (Microsoft (R) Windows
DOS).
3. When the user tried to change the catalogue (in command.com window,
using
cd command) to the one where the program resided, he couldn't do it - he
got
the message that the catalogue did not existed, although he used the
proper
short name for it.
4. When the user tried to change the catalogue (using cd command) to the
one
where the program resided, but in cmd session, he was able to do it.
5. When the new catalogue was created and the program was copied into that
catalogue, the problem disappeared.
I am perplexed - it is as if the catalogue was damaged. But why the 32-bit
program ran without any problem?
Anyway now the program seems to run just as it should.
Thank you,
JC
>> What is the value of "comspec" when the application is run?
> I will check it up and write the result here.
>
>> What happens if you run this from the command line:
> run command.com /c dir
> I will check it up and write the result here.
>
>> Does the application get started from a command line, and desktop
> shortcut, a batch file, or what?
>
> Normally the application is started from desktop shortcup. To notice the
> message the user had to run cmd and tried to start the application from
a
> command line.
>
> Perhaps it is a command.com problem... I hope so :)
>
> JC
>
>
> David A. Smith
>
|
