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.

"Merlin Ran" <(E-Mail Removed)> wrote in message
news:ehOEf5%(E-Mail Removed)...
> 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.

I have never heard of the problem in any O/S. If you are having a problem
running CMD.EXE in Windows 98, you should be aware that the two are not
compatible.

/Al

Hello, Al:
On Tue, 11 Jan 2005 19:40:33 -0700: you wrote...

ADM>
ADM> I have never heard of the problem in any O/S. If you are having a
ADM> problem running CMD.EXE in Windows 98, you should be aware that the
ADM> two are not compatible.

I had a similar sounding problem way back in the W9x series. If I clicked on
the close button the DOS prompt would hang. Haven't seen it in any of the
NT+ based OS'es. I always assumed it was some driver or something, perhaps
Anarkey which I used back then, causing it. Never fixed it, just moved on.

Regards, Paul R. Sadowski [MVP].

I wasn't able to get any program like anakey to work reliabily on 9x (except doskey but that didn't do what I needed). I went through a lot, but all would eventually hang. Though all this was on one production machine (where command line completion was needed like cmd).

--
----------------------------------------------------------
http://www.uscricket.com
"Paul R. Sadowski [MVP]" <(E-Mail Removed)> wrote in message news:ul8lmWG%(E-Mail Removed)...
> Hello, Al:
> On Tue, 11 Jan 2005 19:40:33 -0700: you wrote...
>
> ADM>
> ADM> I have never heard of the problem in any O/S. If you are having a
> ADM> problem running CMD.EXE in Windows 98, you should be aware that the
> ADM> two are not compatible.
>
> I had a similar sounding problem way back in the W9x series. If I clicked on
> the close button the DOS prompt would hang. Haven't seen it in any of the
> NT+ based OS'es. I always assumed it was some driver or something, perhaps
> Anarkey which I used back then, causing it. Never fixed it, just moved on.
>
> Regards, Paul R. Sadowski [MVP].
>
>

MS makes cmd for 95. A NT4 and a NT5 version. It's in unsupported tools of the platform sdk.
Win95Cmd.exe is it's name (win95cmdnt4 and win95cmd2k). I send it to people who mail (E-Mail Removed) and ask as the PSDK is 100s of MB for a 2 x 120K files.
--
----------------------------------------------------------
http://www.uscricket.com
"Al Dunbar [MS-MVP]" <alan-no-drub-(E-Mail Removed)> wrote in message news:%23RfqZAF%(E-Mail Removed)...
>
> "Merlin Ran" <(E-Mail Removed)> wrote in message
> news:ehOEf5%(E-Mail Removed)...
>> 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.
>
> I have never heard of the problem in any O/S. If you are having a problem
> running CMD.EXE in Windows 98, you should be aware that the two are not
> compatible.
>
> /Al
>
>