>>On my system, I've noticed that DOS applications which try to use
>>the COM ports will fail if I run them from a DOS subwindow, but
>>will work properly if I fire them up directly from Windows (via
>>an icon or by double-clicking on the .exe file in File Manager).
>Do you have any windows apps running that might have taken over control
>of the com port in question?
Quote:>Are you using a serial mouse that's
>connected to the com port your communications program is using?
Quote:>Try changing the com port settings of the DOS app. You SHOULD be able to
>run a DOS comm program Windowed; I did it just last night to connect to a
>local BBS with Kermit 3.13.
I think you've misread my post. It's not that I can't run it in a window,
it's that I can't run it when it's launched from a DOS shell window.
I *can* run it when I launch it directly from Windows without using the
DOS shell (e.g. I launch it from File Manager).
Quote:>It could also be that your DOS app simply refuses to run from a window.
>Can you run other DOS apps windowed successfully? If so, then you'll
>probably have to run the comm program full screen.
Again, that's not the problem. If I launch it from File Manager, I
can run it successfully either as a subwindow or full screen. When I
launch it from a DOS shell window, it won't run successfully either as
a subwindow or full screen.
"Don't tread on me"