M
Merlin Ran
If I run cmd.exe, or telnet.exe, the command window appears, but if I don't
operate in the window for minutes and the input "exit<cr>", or telnet
session is timed out by peer, the command windows hangs. I can minimize or
maxmize it, but cannot close it, or set it's properties. There's no cmd.exe
or telnet.exe in the process list then, means that the process has exit, but
why command window remains?
Has anyone encounter the same problem? How can it be solved? Is it a bug
of Windows 2000 and Windows 98? I haven't found the case in Windows XP.
operate in the window for minutes and the input "exit<cr>", or telnet
session is timed out by peer, the command windows hangs. I can minimize or
maxmize it, but cannot close it, or set it's properties. There's no cmd.exe
or telnet.exe in the process list then, means that the process has exit, but
why command window remains?
Has anyone encounter the same problem? How can it be solved? Is it a bug
of Windows 2000 and Windows 98? I haven't found the case in Windows XP.