>>Al,
>>
>>I'm wrong, its not a path problem or whatever. The mode command actually is being executed, but it just dont run it on autoexec.nt because its a 32 Bit application, and its actually accessing the Windows API.
>>
>>I tried to replace a
windows98 version of mode.com and I go to RUN -> COMMAND->Press Enter, it tells me at the command prompt error "Incorect MS DOS version".
>>
>>Now, I wonder if I can nail down this fellow, unless I can force command.com to run 32 bit app or mode.com doesn't really work in autoexec.nt
>>
>>I'm already run out of ideas. Any more ideas?
>
>In XP you can force the COM port at 2E8 to be COM4. Go into the Device Manager, go to the properties of the COM port in question, go to Port Settings...Advanced and select COM4 from the dropdown list. Make sure the port is configured to be COM4.
Thanks, I haven't gone unto this advanced options.>Are you positive the encryption device doesn't need a driver? Look in CONFIG.SYS on the W98 machine (the one that works). If there's one there you will have to put the same call in CONFIG.NT on the XP box. You may also need an updated driver for XP.
I'm going to double check on that.>Also, are you actually using COMMAND.COM on XP instead of CMD.EXE? You could try the latter if so.
Even though, my COMSPEC is CMD.EXE, it still using command.com when I click a dos executable within explorer, otherwise I go to RUN --> CMD --> ENTERThanks.
