Run:cmd gets error msg "Not a Win32 app." ... Weird!

[Richard]

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

 

[Guest]

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...

 

[McFly]

Richard,

Have you tried System Restore? Restore to an earlier date, say a week
ago, and try to invoke the cmd command again...

-fly-

 

[CreateWindow]

Hi Richard,

Type path in a command prompt. Check for files called cmd.exe cmd.cmd
cmd.bat in your path etc. Make sure there are no bogus ones. Even just do a
search for cmd*

I know you mentioned the path I'm just trying to help.

CreateWindow

 

[HeyBub]

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?

The CMD.EXE found by the system is not a viable program. That the system
found it is implicit in the error message; that is, if CMD.EXE could not be
found, you'd get a different error message.

What happened is that the system found a DIFFERENT CMD.EXE than the one you
know to be the proper program.

Search for CMD.EXE and dislodge the alias. If all else fails, you can use
"COMMAND" (yes you can).

 

[Wesley Vogel]

You very likely have a trojan/virus/worm that created a cmd.com file.
NETSTAT, PING, REGEDIT, TASKKILL, TASKLIST or TRACERT may not work either.

UPDATE your antivirus software and run a full system scan.

UPDATE whatever anti-spyware applications that you have and run a full
system scan with each one.

You might want to start in Safe Mode to run your antivirus and anti-spyware
software.

Running a full system antivirus scan or anti-spyware scan in Safe Mode can
be a good idea. Some viruses and other malware like to conceal themselves
in areas Windows protects while using them. Safe mode can prevent those
applications access and therefore unprotect the viruses or other malware
allowing for easier removal.

''In safe mode, you have access to only basic files and drivers
(mouse, monitor, keyboard, mass storage, base video, default system
services), just the minimum device drivers required to start Windows.''

Because of that some malware does not load in Safe Mode and is easier to get
rid of.

How to start Windows in Safe Mode Windows XP
http://www.bleepingcomputer.com/forums/index.php?showtutorial=61#winxo

Also Known As: W32.Alcan.A, Win32.Alcan.A [Computer Associates],
P2P-Worm.Win32.Alcan.a [Kaspersky Lab], W32/Alcan.worm!p2p [McAfee],
W32/Alcra-A [Sophos], WORM_ALCAN.A [Trend Micro]

[[This worm drops the legitimate file compression DLL, BSZIP.DLL in the
Windows system folder. It does this so it can compress itself. It also drops
the following files in the Windows system folder:

CMD.COM
NETSTAT.COM
PING.COM
REGEDIT.COM
TASKKILL.COM
TASKLIST.COM
TRACERT.COM

These files contain the string MZ so that this worm can disable the
following Windows tool applications:

CMD.EXE
NETSTAT.EXE
PING.EXE
REGEDIT.EXE
TASKKILL.EXE
TASKLIST.EXE
TRACERT.EXE ]]
From...
WORM_ALCAN.A - Technical details
http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_ALCAN.A&VSect=T

Symantec Security Response - W32.Alcra.A
http://securityresponse.symantec.com/avcenter/venc/data/w32.alcra.a.html

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Richard]

Hi y'all,

Thanks for the (great) replies.

So far:

There are no apparently related errors in Event Viewer

I'm writing a Ruby script to search the top-level entries in each dir
on the path for cmd.[bat,com,exe], case ignored. I already discovered
3 no-longer-valid directories so far, and excised them.

I'll report back in a day or two with new discoveries or questions.
I've got to go play with my grand-children now. That takes
precedence

Best wishes,
Richard

 

[Wesley Vogel]

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi y'all,

Thanks for the (great) replies.

So far:

There are no apparently related errors in Event Viewer

I'm writing a Ruby script to search the top-level entries in each dir
on the path for cmd.[bat,com,exe], case ignored. I already discovered
3 no-longer-valid directories so far, and excised them.

I'll report back in a day or two with new discoveries or questions.
I've got to go play with my grand-children now. That takes
precedence

Best wishes,
Richard

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

 

[Richard]

Hi Wes,

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

Here's mine:
..COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.RB;.RBW

I merely added on two extensions for Ruby some time ago.

UPDATE your antivirus software and run a full system scan.

Did that with AVG-Free; it found and disabled Trojan horse Downloader-
Agent.KNW

I didn't notice your protected-mode suggestion; I'll rerun in P.M.
tonight.

I'm still working on the other suggestions.

Thanks for your guidance, Wes. It's much appreciated.

Best wishes,
Richard

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi y'all,

Thanks for the (great) replies.

So far:

There are no apparently related errors in Event Viewer

I'm writing a Ruby script to search the top-level entries in each dir
on the path for cmd.[bat,com,exe], case ignored. I already discovered
3 no-longer-valid directories so far, and excised them.

I'll report back in a day or two with new discoveries or questions.
I've got to go play with my grand-children now. That takes
precedence

Best wishes,
Richard

 

[Wesley Vogel]

Richard,

Not a valid win32 application
http://www.computerhope.com/issues/ch000726.htm

Did you do an Advanced Search for cmd.* to find every possible file? The
PATHEXT variable is the order that extensions are searched when you do not
type one, .com comes before .exe.

There should be two cmd.exes on your machine and not any other cmd.* files
with any other extension.

%systemroot%\system32\cmd.exe, the one that gets used.

%systemroot%\system32\dllcache\cmd.exe, backup for Windows File Protection.

%systemroot%\ServicePackFiles\i386\cmd.exe, if a ServicePackFiles folder
exists the i386 folder is used for WFP instead of the dllcache folder. Not
all XP installations even have a ServicePackFiles folder, neither of mine
do.

What does Start | Run | cmd.com produce? Windows cannot find 'cmd.com'
would be a good result.

You stated that: %SystemRoot%\system32\cmd.exe works fine.

Does %SystemRoot% = F:\WINXPPRO?

Does %SystemRoot% typed into Start | Run open F:\WINXPPRO?

Does F:\WINXPPRO\system32\cmd.exe typed into Start | Run work?

I just created a bogus cmd.exe in C:\WINDOWS. I created a 0 byte .txt file
and renamed it to cmd.exe. Start | Run | cmd still works OK because
system32 is in the path before the WINDOWS folder is. That is, the system32
folder is searched before the WINDOWS folder.

However, C:\WINDOWS\cmd.exe in the Run command gets this error:

---------------------------
C:\WINDOWS\cmd.exe
---------------------------
C:\WINDOWS\cmd.exe is not a valid Win32 application.
---------------------------
OK
---------------------------

Your PATH may still somehow be messed up.

Why don't my commands work?
http://internet.cybermesa.com/~bstewart/cmdprompt.html#6

Run the System File Checker. System File Checker (sfc.exe) replaces screwed
up system files.

Load your XP CD in your CD drive.

Start | Run | Type or paste: sfc /scannow | Click OK

sfc /scannow scans all protected system files immediately and replaces
incorrect versions with correct Microsoft versions.

System File Checker takes a while to run.

If you have XP Home and it asks for your XP Pro CD, see this KB article...

You may be prompted to insert a Windows XP Professional CD when you run the
System File Checker tool in Windows XP Home Edition
http://support.microsoft.com/kb/897128

If SFC.EXE did anything it will be listed in the Event Viewer.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK | Click System |

Windows File Protection will be listed under the Source column. Look at any
Windows File Protection entries.

Explains a whole bunch about sfc.exe.
scannow sfc (sfc.exe)
http://www.updatexp.com/scannow-sfc.html

Description of Windows XP and Windows Server 2003 System File Checker
(Sfc.exe)
http://support.microsoft.com/kb/310747

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi Wes,

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

Here's mine:
.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.RB;.RBW

I merely added on two extensions for Ruby some time ago.

UPDATE your antivirus software and run a full system scan.

Did that with AVG-Free; it found and disabled Trojan horse Downloader-
Agent.KNW

I didn't notice your protected-mode suggestion; I'll rerun in P.M.
tonight.

I'm still working on the other suggestions.

Thanks for your guidance, Wes. It's much appreciated.

Best wishes,
Richard

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi y'all,

Thanks for the (great) replies.

So far:

There are no apparently related errors in Event Viewer

I'm writing a Ruby script to search the top-level entries in each dir
on the path for cmd.[bat,com,exe], case ignored. I already discovered
3 no-longer-valid directories so far, and excised them.

I'll report back in a day or two with new discoveries or questions.
I've got to go play with my grand-children now. That takes
precedence

Best wishes,
Richard

On May 4, 11:49 pm, Richard
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

 

[Richard]

Hi Wes,

I'm going to follow all your suggestions, but slowly because I'm a
retired software developer. I don't (can't ?) work as fast as I did
when I had a client expecting me to meet deadlines.

I completed the AVG-Free global search after rebooting in Safe Mode.
No additional viruses were identified. For kicks, I'm going to do
the search for cmd.whatever with a Ruby script. This script will be
an expansion of my current script to process the PATH for various
purposes.

I'll post back when I have more news. This is an interesting
exercise!!

Best wishes,
Richard

Richard,

Not a valid win32 applicationhttp://www.computerhope.com/issues/ch000726.htm

Did you do an Advanced Search for cmd.* to find every possible file? The
PATHEXT variable is the order that extensions are searched when you do not
type one, .com comes before .exe.

There should be two cmd.exes on your machine and not any other cmd.* files
with any other extension.

%systemroot%\system32\cmd.exe, the one that gets used.

%systemroot%\system32\dllcache\cmd.exe, backup for Windows File Protection.

%systemroot%\ServicePackFiles\i386\cmd.exe, if a ServicePackFiles folder
exists the i386 folder is used for WFP instead of the dllcache folder. Not
all XP installations even have a ServicePackFiles folder, neither of mine
do.

What does Start | Run | cmd.com produce? Windows cannot find 'cmd.com'
would be a good result.

You stated that: %SystemRoot%\system32\cmd.exe works fine.

Does %SystemRoot% = F:\WINXPPRO?

Does %SystemRoot% typed into Start | Run open F:\WINXPPRO?

Does F:\WINXPPRO\system32\cmd.exe typed into Start | Run work?

I just created a bogus cmd.exe in C:\WINDOWS. I created a 0 byte .txt file
and renamed it to cmd.exe. Start | Run | cmd still works OK because
system32 is in the path before the WINDOWS folder is. That is, the system32
folder is searched before the WINDOWS folder.

However, C:\WINDOWS\cmd.exe in the Run command gets this error:

---------------------------
C:\WINDOWS\cmd.exe
---------------------------
C:\WINDOWS\cmd.exe is not a valid Win32 application.
---------------------------
OK
---------------------------

Your PATH may still somehow be messed up.

Why don't my commands work?http://internet.cybermesa.com/~bstewart/cmdprompt.html#6

Run the System File Checker. System File Checker (sfc.exe) replaces screwed
up system files.

Load your XP CD in your CD drive.

Start | Run | Type or paste: sfc /scannow | Click OK

sfc /scannow scans all protected system files immediately and replaces
incorrect versions with correct Microsoft versions.

System File Checker takes a while to run.

If you have XP Home and it asks for your XP Pro CD, see this KB article...

You may be prompted to insert a Windows XP Professional CD when you run the
System File Checker tool in Windows XP Home Editionhttp://support.microsoft.com/kb/897128

If SFC.EXE did anything it will be listed in the Event Viewer.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK | Click System |

Windows File Protection will be listed under the Source column. Look at any
Windows File Protection entries.

Explains a whole bunch about sfc.exe.
scannow sfc (sfc.exe)http://www.updatexp.com/scannow-sfc.html

Description of Windows XP and Windows Server 2003 System File Checker
(Sfc.exe)http://support.microsoft.com/kb/310747

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi Wes,

Here's mine:
.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.RB;.RBW

I merely added on two extensions for Ruby some time ago.

Did that with AVG-Free; it found and disabled Trojan horse Downloader-
Agent.KNW

I didn't notice your protected-mode suggestion; I'll rerun in P.M.
tonight.

I'm still working on the other suggestions.

Thanks for your guidance, Wes. It's much appreciated.

Best wishes,
Richard

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
InRichard <[email protected]> hunted and pecked:
Hi y'all,
Thanks for the (great) replies.
So far:
There are no apparently related errors in Event Viewer
I'm writing a Ruby script to search the top-level entries in each dir
on the path for cmd.[bat,com,exe], case ignored. I already discovered
3 no-longer-valid directories so far, and excised them.
I'll report back in a day or two with new discoveries or questions.
I've got to go play with my grand-children now. That takes
precedence
Best wishes,
Richard
On May 4, 11:49 pm, Richard
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

 

[Wesley Vogel]

Remember the KISS principle. You don't need a script to search for files.
But knock yourself out. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi Wes,

I'm going to follow all your suggestions, but slowly because I'm a
retired software developer. I don't (can't ?) work as fast as I did
when I had a client expecting me to meet deadlines.

I completed the AVG-Free global search after rebooting in Safe Mode.
No additional viruses were identified. For kicks, I'm going to do
the search for cmd.whatever with a Ruby script. This script will be
an expansion of my current script to process the PATH for various
purposes.

I'll post back when I have more news. This is an interesting
exercise!!

Best wishes,
Richard

Richard,

Not a valid win32
applicationhttp://www.computerhope.com/issues/ch000726.htm

Did you do an Advanced Search for cmd.* to find every possible file? The
PATHEXT variable is the order that extensions are searched when you do
not
type one, .com comes before .exe.

There should be two cmd.exes on your machine and not any other cmd.*
files
with any other extension.

%systemroot%\system32\cmd.exe, the one that gets used.

%systemroot%\system32\dllcache\cmd.exe, backup for Windows File
Protection.

%systemroot%\ServicePackFiles\i386\cmd.exe, if a ServicePackFiles folder
exists the i386 folder is used for WFP instead of the dllcache folder.
Not
all XP installations even have a ServicePackFiles folder, neither of mine
do.

What does Start | Run | cmd.com produce? Windows cannot find 'cmd.com'
would be a good result.

You stated that: %SystemRoot%\system32\cmd.exe works fine.

Does %SystemRoot% = F:\WINXPPRO?

Does %SystemRoot% typed into Start | Run open F:\WINXPPRO?

Does F:\WINXPPRO\system32\cmd.exe typed into Start | Run work?

I just created a bogus cmd.exe in C:\WINDOWS. I created a 0 byte .txt
file
and renamed it to cmd.exe. Start | Run | cmd still works OK because
system32 is in the path before the WINDOWS folder is. That is, the
system32
folder is searched before the WINDOWS folder.

However, C:\WINDOWS\cmd.exe in the Run command gets this error:

---------------------------
C:\WINDOWS\cmd.exe
---------------------------
C:\WINDOWS\cmd.exe is not a valid Win32 application.
---------------------------
OK
---------------------------

Your PATH may still somehow be messed up.

Why don't my commands
work?http://internet.cybermesa.com/~bstewart/cmdprompt.html#6

Run the System File Checker. System File Checker (sfc.exe) replaces
screwed
up system files.

Load your XP CD in your CD drive.

Start | Run | Type or paste: sfc /scannow | Click OK

sfc /scannow scans all protected system files immediately and replaces
incorrect versions with correct Microsoft versions.

System File Checker takes a while to run.

If you have XP Home and it asks for your XP Pro CD, see this KB
article...

You may be prompted to insert a Windows XP Professional CD when you run
the
System File Checker tool in Windows XP Home
Editionhttp://support.microsoft.com/kb/897128

If SFC.EXE did anything it will be listed in the Event Viewer.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK | Click System |

Windows File Protection will be listed under the Source column. Look at
any
Windows File Protection entries.

Explains a whole bunch about sfc.exe.
scannow sfc (sfc.exe)http://www.updatexp.com/scannow-sfc.html

Description of Windows XP and Windows Server 2003 System File Checker
(Sfc.exe)http://support.microsoft.com/kb/310747

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi Wes,

Here's mine:
.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.RB;.RBW

I merely added on two extensions for Ruby some time ago.

UPDATE your antivirus software and run a full system scan.

Did that with AVG-Free; it found and disabled Trojan horse Downloader-
Agent.KNW

I didn't notice your protected-mode suggestion; I'll rerun in P.M.
tonight.

I'm still working on the other suggestions.

Thanks for your guidance, Wes. It's much appreciated.

Best wishes,
Richard

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

Wes
MS-MVP Windows Shell/User

InRichard <[email protected]> hunted and
pecked:

Hi y'all,

Thanks for the (great) replies.

So far:

There are no apparently related errors in Event Viewer

I'm writing a Ruby script to search the top-level entries in each dir
on the path for cmd.[bat,com,exe], case ignored. I already discovered
3 no-longer-valid directories so far, and excised them.

I'll report back in a day or two with new discoveries or questions.
I've got to go play with my grand-children now. That takes
precedence

Best wishes,
Richard

On May 4, 11:49 pm, Richard
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

 

[Richard]

Hi Wes,

Thanks for recommending KISS. I acknowledge the wisdom of that
guidance but this situation parallels Polonius' analysis of Hamlet:
"There's a method to his madness."

My method is to:
- improve my fluency in Ruby programming
- have a tool for similar analysis in the future

While working on my Ruby tool, I found a few other problematic things
on my machine:
- a "file watch" program from Roxio was slowing Word's performance
when using the clipboard; I uninstalled it with good effect.
- I had a few directory addresses on my path that were longer valid; I
deleted them but with no observable effect.

I'll post back with more results in a few more days.

Best wishes,
Richard

Best wishes,
Richard

Remember the KISS principle. You don't need a script to search for files.
But knock yourself out. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi Wes,

I'm going to follow all your suggestions, but slowly because I'm a
retired software developer. I don't (can't ?) work as fast as I did
when I had a client expecting me to meet deadlines.

I completed the AVG-Free global search after rebooting in Safe Mode.
No additional viruses were identified. For kicks, I'm going to do
the search for cmd.whatever with a Ruby script. This script will be
an expansion of my current script to process the PATH for various
purposes.

I'll post back when I have more news. This is an interesting
exercise!!

Best wishes,
Richard

Richard,
Not a valid win32
applicationhttp://www.computerhope.com/issues/ch000726.htm
Did you do an Advanced Search for cmd.* to find every possible file? The
PATHEXT variable is the order that extensions are searched when you do
not
type one, .com comes before .exe.
There should be two cmd.exes on your machine and not any other cmd.*
files
with any other extension.
%systemroot%\system32\cmd.exe, the one that gets used.
%systemroot%\system32\dllcache\cmd.exe, backup for Windows File
Protection.
%systemroot%\ServicePackFiles\i386\cmd.exe, if a ServicePackFiles folder
exists the i386 folder is used for WFP instead of the dllcache folder.
Not
all XP installations even have a ServicePackFiles folder, neither of mine
do.
What does Start | Run | cmd.com produce? Windows cannot find 'cmd.com'
would be a good result.
You stated that: %SystemRoot%\system32\cmd.exe works fine.
Does %SystemRoot% = F:\WINXPPRO?
Does %SystemRoot% typed into Start | Run open F:\WINXPPRO?
Does F:\WINXPPRO\system32\cmd.exe typed into Start | Run work?
I just created a bogus cmd.exe in C:\WINDOWS. I created a 0 byte .txt
file
and renamed it to cmd.exe. Start | Run | cmd still works OK because
system32 is in the path before the WINDOWS folder is. That is, the
system32
folder is searched before the WINDOWS folder.
However, C:\WINDOWS\cmd.exe in the Run command gets this error:
---------------------------
C:\WINDOWS\cmd.exe
---------------------------
C:\WINDOWS\cmd.exe is not a valid Win32 application.
---------------------------
OK
---------------------------
Your PATH may still somehow be messed up.
Why don't my commands
work?http://internet.cybermesa.com/~bstewart/cmdprompt.html#6
Run the System File Checker. System File Checker (sfc.exe) replaces
screwed
up system files.
Load your XP CD in your CD drive.
Start | Run | Type or paste: sfc /scannow | Click OK
sfc /scannow scans all protected system files immediately and replaces
incorrect versions with correct Microsoft versions.
System File Checker takes a while to run.
If you have XP Home and it asks for your XP Pro CD, see this KB
article...
You may be prompted to insert a Windows XP Professional CD when you run
the
System File Checker tool in Windows XP Home
Editionhttp://support.microsoft.com/kb/897128
If SFC.EXE did anything it will be listed in the Event Viewer.
Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK | Click System |
Windows File Protection will be listed under the Source column. Look at
any
Windows File Protection entries.
Explains a whole bunch about sfc.exe.
scannow sfc (sfc.exe)http://www.updatexp.com/scannow-sfc.html
Description of Windows XP and Windows Server 2003 System File Checker
(Sfc.exe)http://support.microsoft.com/kb/310747
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
InRichard <[email protected]> hunted and pecked:
Hi Wes,
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
Here's mine:
.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.RB;.RBW
I merely added on two extensions for Ruby some time ago.
UPDATE your antivirus software and run a full system scan.
Did that with AVG-Free; it found and disabled Trojan horse Downloader-
Agent.KNW
I didn't notice your protected-mode suggestion; I'll rerun in P.M.
tonight.
I'm still working on the other suggestions.
Thanks for your guidance, Wes. It's much appreciated.
Best wishes,
Richard
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
InRichard <[email protected]> hunted and
pecked:
Hi y'all,
Thanks for the (great) replies.
So far:
There are no apparently related errors in Event Viewer
I'm writing a Ruby script to search the top-level entries in each dir
on the path for cmd.[bat,com,exe], case ignored. I already discovered
3 no-longer-valid directories so far, and excised them.
I'll report back in a day or two with new discoveries or questions.
I've got to go play with my grand-children now. That takes
precedence
Best wishes,
Richard
On May 4, 11:49 pm, Richard
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