I hope someone out there can help me out with this problem.
Here is the situation:
Windows NT 4.0 workstation (Service Pack 3)
DOS terminal emulation program that uses COM port to connect to our old
Now for the most part this all runs fine, the terminal emulation itself
even KERMIT file transfers. However, I run into a problem when I send
escape sequences to the emulation program from the host. The escape
sequence tells the emulation program to shell out to DOS and run a batch
file. This part works fine. My problem is when the batch file finishes
and hands control back over to the emulation program the emulation's screen
stops updating. The emulation itself is still working, ie. it lets the
host know that the DOS command has finished and the host continues its job.
This procedure worked fine in Win95. The only thing I can think of is that
it is a problem with the shell to DOS that somehow relates to the Video
Mode that the emulation program is in. But the emulation program is a text
mode program and the batch file that I run simply using FTP to connect to
our new system and pulls a file back using the /s switch on the FTP command
with output redirected to a log file that I can check for errors using the
What is the difference between CMD.EXE and COMMAND.COM, the way I
understand it is that CMD.EXE is 32-bit, and COMMAND.COM is 16-bit. Do all
DOS apps use COMMAND.COM? Can you use CMD.EXE? If I start CMD.EXE via the
'RUN' command on the start menu, and go into my DOS app from the resulting
command prompt. What is my DOS app using CMD.EXE or COMMAND.COM? How does
all this relate to the ntcmdprompt command in the config.nt file?
What PIF properties have an effect on the VIDEO emulation of the DOS apps?
What effect does the 'Compatible Timer Hardware Emulation' switch have?
Any other ideas on what I should try?
Sorry this is so long, but any help would be greatly appreciated!
Thanks in advance
Miami Luken, Inc.
Springboro, OH. 45066
--remove the .no.spam