.exe files don't open

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

No problems until 05/23. Now I get the message "The system cannot execute
the specified program" I was hacked on that day and have removed the startup
files and other remnants but can't find how to fix the command prompt.
NTVDM.exe , autoexec.nt, and config.nt are ok. UsrClass.dat was modified and
I renamed it. I could use a little help--still going around in circles.
Thanks, anyone?



Scott
 
These may help.

How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/default.aspx?kbid=292175

What an In-Place Windows 2000 Upgrade Changes and What It Does Not Change
http://support.microsoft.com/default.aspx?kbid=306952

Be sure to apply these to your repair install before connecting to any
network.

http://download.microsoft.com/download/E/6/A/E6A04295-D2A8-40D0-A0C5-241BFECD095E/W2KSP4_EN.EXE
http://www.microsoft.com/technet/security/bulletin/MS03-043.mspx
http://www.microsoft.com/technet/security/bulletin/MS03-049.mspx

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| No problems until 05/23. Now I get the message "The system cannot execute
| the specified program" I was hacked on that day and have removed the
startup
| files and other remnants but can't find how to fix the command prompt.
| NTVDM.exe , autoexec.nt, and config.nt are ok. UsrClass.dat was modified
and
| I renamed it. I could use a little help--still going around in circles.
| Thanks, anyone?
|
|
|
| Scott
 
No problems until 05/23. Now I get the message "The system cannot execute
the specified program" I was hacked on that day and have removed the startup
files and other remnants but can't find how to fix the command prompt.
NTVDM.exe , autoexec.nt, and config.nt are ok. UsrClass.dat was modified and
I renamed it. I could use a little help--still going around in circles.
Thanks, anyone?



Scott
Click to expand...
See tips 271 and 1605 in the 'Tips & Tricks' at http://www.jsifaq.com
 
Thanks Jerold,

Turns out regedit.exe does work and the association with .exe in the
registry is ok. The problem is within the command prompt (ie: edit.exe
fails; but dir and cd work). Run "command.com" also fails but clicking on
the command prompt opens the window.
 
Control Panel|System|Advanced|Environment Variables|System Variables and
make sure that "PathExt" has at least;
..COM;.EXE;.BAT;.CMD



--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Thanks Jerold,
|
| Turns out regedit.exe does work and the association with .exe in the
| registry is ok. The problem is within the command prompt (ie: edit.exe
| fails; but dir and cd work). Run "command.com" also fails but clicking on
| the command prompt opens the window.
|
|
|
| --
| Scott
|
|
| "Jerold Schulman" wrote:
|
| > On Wed, 8 Jun 2005 14:40:01 -0700, "Scott"
| >
| > >No problems until 05/23. Now I get the message "The system cannot
execute
| > >the specified program" I was hacked on that day and have removed the
startup
| > >files and other remnants but can't find how to fix the command prompt.
| > >NTVDM.exe , autoexec.nt, and config.nt are ok. UsrClass.dat was
modified and
| > >I renamed it. I could use a little help--still going around in
circles.
| > >Thanks, anyone?
| > >
| > >
| > >
| > >Scott
| > See tips 271 and 1605 in the 'Tips & Tricks' at http://www.jsifaq.com
| >
| >
 
In microsoft.public.win2000.cmdprompt.admin =?Utf-8?B?U2NvdHQ=?=
wrote:
Thanks Jerold,

Turns out regedit.exe does work and the association with .exe in
the registry is ok. The problem is within the command prompt
(ie: edit.exe fails; but dir and cd work). Run "command.com"
also fails but clicking on the command prompt opens the window.
Click to expand...

This sounds much like a problem in the 16-bit sub-system. Does
executing sysedit.exe do the same thing?
What OS are you running?

Are you getting errors or event log entries similar to,

16 bit MS-DOS Subsystem
drive:\program path
XXXX. An installable Virtual Device Driver failed DLL
initialization. Choose 'Close' to terminate the
application.
OR
16 bit MS-DOS Subsystem
drive:\program path
SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers. VDD.
Virtual Device Driver format in the registry
is invalid. Choose 'Close'



From Jerold's Tip #
2328 » Windows 2000 Virtual Device Driver error in 16-bit MS-DOS
subsystem?
 
Environment variables are ok. Event log does not show any events as result
of attempting to run dos.

Seems like this is a path issue, but they are all there. Could this be a
long file name issue or a path greater than 64 characters issue? One path
is long:
APPDATA=C:\Documents and Settings\Jeff Radcliffe\Application Data.
 
You're right. The clicked command prompt is cmd.exe. and it opens. But
neither cmd.exe or command.com will open from the run window.
 
In microsoft.public.win2000.cmdprompt.admin =?Utf-8?B?U2NvdHQ=?=
wrote:
You're right. The clicked command prompt is cmd.exe. and it
opens. But neither cmd.exe or command.com will open from the
run window.
Click to expand...

I'm out of this because (and IMO) you keep dribbling out different
symptoms and "facts" about your situation. Some of your problems
would appear to be very different post to post. Some helpful
responders have posted suggestions or links which you have never
even acknowledged or insufficiently addressed. Some symptoms tend
to look variously like
.exe exefile associations
16-bit sub-system
System PATH problem (current problem perhaps)
...

It's very confusing and difficult too. <G>

And your News Reader keeps Top Posting (not easy to follow) and not
stripping signatures (which is worse, for the responder).

You may wish to consider assembling everything observed, tested,
investigated and so on into a single comprehensive post with all
available data, and post it directly under your original post.

Just IMHO and FWIW Scott.
 
Mark V,

Sorry I pissed you off. I certainly didn't intend to. I'm new to the
newsgroup and navigated these posts as best I knew how. As to the symtoms
and replies to others sugestions: I thought I had responded to the
suggestions and offered footnotes to those suggestions. If I knew how or
what was important or not in the original post, I probably would not had to
make the post in the first place. Incidentally, I spent days querying the
KnowledgeBase before posting here--virtually going in circles.

Again sorry.
 
In microsoft.public.win2000.cmdprompt.admin =?Utf-8?B?U2NvdHQ=?=
wrote:
Mark V,

Sorry I pissed you off.
Click to expand...

You didn't. I was just a little frustrated. :-)
I certainly didn't intend to. I'm new
to the newsgroup and navigated these posts as best I knew how.
As to the symtoms and replies to others sugestions: I thought I
had responded to the suggestions and offered footnotes to those
suggestions. If I knew how or what was important or not in the
original post, I probably would not had to make the post in the
first place. Incidentally, I spent days querying the
KnowledgeBase before posting here--virtually going in circles.
Click to expand...

Yep, KB research can be dizzying.
Again sorry.
Click to expand...

No need to be. Only trying to get you some focused brain power on
the actual problems.
Cheers
 
Back
Top