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?

Thanks.
>>>>Hi,
>>>>
>>>>I posted two days ago about this subject and it seems nobody has experience in dealing with this problem.

>>>>
>>>>The problem was loading MS DOS environment such as mode comX in windows XP.
>>>>
I added on the last line of autoexec.nt the code MODE COM4:4800,n,8,1 and launching the legacy application still fails. Basically the application will check if can communicate with the encryption card, this encryption card uses com port but it doesn't work.
>>>>

>>>>Running an instance of command.com within windows, will give me an error "Bad command or file name". This means that the mode command on autoexec.nt is not working even though the path is correct. I even go to the extent of debugging this mode.com and I found that the said version will not run in dos mode.

>>>
>>>If you go into the Windows Device Manager, you can set the port's values to what you need, without having to run a MODE command. That way the port should be ready to go each time the computer starts.
>>>
>>>While you're in there, check the port settings. While Windows can assign a COM port to a wide range of addresses, DOS apps typically expect the ports to be in a fixed place. On the Resources page it should be set to 02E8-02EF and IRQ3.
>>>
>>>Of course, all this assumes COM4 is visible to Windows. If it doesn't show in the Device Manager you'll need to check that it's set properly (typically in the PC BIOS), then re-start Windows and let it install the new port for you.
>>>
>>>If you have another serial device on COM2 this is likely to conflict with your card, as it would be trying to share IRQ3.
>>>
>>>Some security devices require a low-level DOS driver to be loaded in the apppropriate AUTOEXEC or CONFIG file.
>>>
>>>Finally, have you tried running your Clipper app from a .BAT/.CMD file with the MODE commands there:

REM Batch file to run Clipper App
>>>MODE COM4 < parameters >
>>>Drive:\Path\MyClipperApp.EXE
>>>MODE COM4 < parameters to set it back to default >

>>
>>
>>Thanks AL,
>>
>>In device manager, I have com1, com2, com3 & com4, but I had disabled com1 & com2. The strange thing is this, when I look at the com3 & com4 settings, its the same as the one I set on the autoexec.nt, its getting its baud setting from from it.

>>
>>I had tried also running a batch file invoking mode com4:4800,n,8,1, then the executable file, but still it doesn't communicate with the encryption device.
>
>Did you check that the resources (address range & IRQ) are as I specified above for COM4?
>Does the encryption device require a device driver that must be loaded in CONFIG.NT?