Run:cmd gets error msg "Not a Win32 app." ... Weird!
Hi All,
I'm having trouble connecting to my ISP's home page on my WinXP-Pro/
SP2 system using both IE7 and Firefox. Both of them go into infinite
loops trying to bring up the home page.
BTW, my Win2003/SP1 server display the ISP's home page perfectly
(while connected to the same router and ultimately the same cable
modem as the workstation.)
I had ISP's tech support trying to resolve the problem. In the course
of doing that, he asked me to bring up a Command window by entering
CMD in the Start | Run textbox and press Enter. XP reported "cmd is
not a valid Win32 application".
I want to find out why this error is raised because it may provide a
clue as to the problem I described at the top of this msg. Here's
what I know:
Start | Run for
-- cmd.exe (i.e., with the .exe extension) fails in the same way.
-- %SystemRoot%\system32\cmd.exe works fine.
That made me think the Path was at fault. But ...
--- the path contains the string ;F:\WINXPPRO\system32; in the middle,
which looks right
--- the commands cmd and chkdsk work fine in a Command window, even
when the CWD is focused on a drive other than %HOMEDRIVE%
Does anyone have any idea what I do to identify what prevent cmd.exe
from being executed from Start | Run?
Try opening event viewer,locate the event/warning for the cmd,in the event/
warning,click on the url enclosed,this opens kb help/support in xp,usually
with
a fix...
"Richard" wrote:
> Hi All,
>
> I'm having trouble connecting to my ISP's home page on my WinXP-Pro/
> SP2 system using both IE7 and Firefox. Both of them go into infinite
> loops trying to bring up the home page.
>
> BTW, my Win2003/SP1 server display the ISP's home page perfectly
> (while connected to the same router and ultimately the same cable
> modem as the workstation.)
>
> I had ISP's tech support trying to resolve the problem. In the course
> of doing that, he asked me to bring up a Command window by entering
> CMD in the Start | Run textbox and press Enter. XP reported "cmd is
> not a valid Win32 application".
>
> I want to find out why this error is raised because it may provide a
> clue as to the problem I described at the top of this msg. Here's
> what I know:
>
> Start | Run for
> -- cmd.exe (i.e., with the .exe extension) fails in the same way.
> -- %SystemRoot%\system32\cmd.exe works fine.
>
> That made me think the Path was at fault. But ...
> --- the path contains the string ;F:\WINXPPRO\system32; in the middle,
> which looks right
> --- the commands cmd and chkdsk work fine in a Command window, even
> when the CWD is focused on a drive other than %HOMEDRIVE%
>
> Does anyone have any idea what I do to identify what prevent cmd.exe
> from being executed from Start | Run?
>
> TIA,
> Richard
>
>
Have you tried System Restore? Restore to an earlier date, say a week
ago, and try to invoke the cmd command again...
-fly-
On May 4, 10:49 pm, Richard
<RichardDummyMailbox58...@USComputerGurus.com> wrote:
> Hi All,
>
> I'm having trouble connecting to my ISP's home page on my WinXP-Pro/
> SP2 system using both IE7 and Firefox. Both of them go into infinite
> loops trying to bring up the home page.
>
> BTW, my Win2003/SP1 server display the ISP's home page perfectly
> (while connected to the same router and ultimately the same cable
> modem as the workstation.)
>
> I had ISP's tech support trying to resolve the problem. In the course
> of doing that, he asked me to bring up a Command window by entering
> CMD in the Start | Run textbox and press Enter. XP reported "cmd is
> not a valid Win32 application".
>
> I want to find out why this error is raised because it may provide a
> clue as to the problem I described at the top of this msg. Here's
> what I know:
>
> Start | Run for
> -- cmd.exe (i.e., with the .exe extension) fails in the same way.
> -- %SystemRoot%\system32\cmd.exe works fine.
>
> That made me think the Path was at fault. But ...
> --- the path contains the string ;F:\WINXPPRO\system32; in the middle,
> which looks right
> --- the commands cmd and chkdsk work fine in a Command window, even
> when the CWD is focused on a drive other than %HOMEDRIVE%
>
> Does anyone have any idea what I do to identify what prevent cmd.exe
> from being executed from Start | Run?
>
> TIA,
> Richard