Re: Run line problems

Well, I looked and did not find any viruses. But I did find the .com files
mentioned. Apparently at one time, they got left by a previous virus that I
had destroyed. Deleting the .coms re-enabled my commands. They were small
files with RW and nothing else in them. Thanks for the assistance. Now I
know for next time.

"Wesley Vogel" wrote:

Read my other post. You probably have a trojan/virus/worm.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:CC60FD79-7339-4AD8-A5C6-F1F0EA89C439@xxxxxxxxxxxxx,
Darkdrew <Darkdrew@xxxxxxxxxxxxxxxxxxxxxxxxx> hunted and pecked:
I will try these tonight and post results tomorrow. I'm using my sister's
computer since I don't have internet access.

"Wesley Vogel" wrote:

Sounds like your PATHEXT environment variable is messed up.

The environmental variable Pathext shows a list of file extensions that
are considered to be executable and regulates which extensions do not
need to be typed in a Command or Run window.

Open a command prompt, for you...
Start | Run | Type: cmd.exe | Click OK |
Type: set in the prompt and hit your Enter key |
Scroll down to PATHEXT

Should look something like this...

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

This registry key is what holds the environment variables...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
Session Manager\Environment
Value Name: PATHEXT should show the same thing.

I do not know if the fixpath2.zip (first link) fixes the PATHEXT problem.

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

See this...
Why do I have to type filename.bat, filename doesn't work
http://www.jsifaq.com/SUBD/TIP1700/rh1706.htm

And possibly this one...
You can't run anything from a CMD prompt
http://www.jsifaq.com/subd/tip1900/rh1918.htm

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:FE77AA40-4718-403C-8CB3-208DE1B97940@xxxxxxxxxxxxx,
Darkdrew <Darkdrew@xxxxxxxxxxxxxxxxxxxxxxxxx> hunted and pecked:
For reasons I cannot fathom, some RUN commands crash unless I add .exe
to the end. Example: CMD does not work but CMD.EXE does. Why is this?


.

Relevant Pages

  • Re: Run line problems
    ... MS-MVP Windows Shell/User ... Darkdrew hunted and pecked: ... Open a command prompt, for you... ... Scroll down to PATHEXT ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Run line problems
    ... Glad you got rid of the virus and the .com files. ... MS-MVP Windows Shell/User ... Deleting the .coms re-enabled my commands. ... Scroll down to PATHEXT ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: CMD
    ... Or there could be something wrong with PATHEXT. ... Do other commands work from Start | Run without typing the Extensions? ... If those commands did not work without typing the .exe part then something ... If you installed the Windows Scripting Host PATHEXT should look something ...
    (microsoft.public.windowsxp.configuration_manage)
  • Re: SOLVED start..run.. <-- how to run that exe automatically
    ... MS-MVP Windows Shell/User ... [[The PATH environment variable defines the Windows NT search path. ... The PATHEXT environment variable defines the list of file extensions ...
    (microsoft.public.windowsxp.general)
  • Re: CMD
    ... Or there could be something wrong with PATHEXT. ... If those commands work without typing the .exe part then something may be ... System File Checker replaces screwed up system files. ... System File Checker tool in Windows XP Home Edition ...
    (microsoft.public.windowsxp.configuration_manage)