Command all screwed up?
Started by
ktownkatman
, Aug 29 2005 02:09 PM
#16
Posted 04 September 2005 - 10:55 AM
#17
Posted 04 September 2005 - 10:56 AM
it says the same thing with cmd and command
#18
Posted 04 September 2005 - 11:14 AM
let's look for every file named cmd.xxx and command.xxx where .xxx can be anything.
right click start>search
All or part of file name - enter cmd
Look in - select your hard drive from the drop down menu
left click Search
repeat the search for command
please post the results of each search listing only those files that start with cmd and command.
why are we doing this? to find ALL copies of cmd and command. once found we will test each one.
right click start>search
All or part of file name - enter cmd
Look in - select your hard drive from the drop down menu
left click Search
repeat the search for command
please post the results of each search listing only those files that start with cmd and command.
why are we doing this? to find ALL copies of cmd and command. once found we will test each one.
#19
Posted 04 September 2005 - 12:03 PM
ok. for cmd i got:cmd.exe in C:\WINDOWS\$NtServicePackUninstall$, cmd.exe in C:\WINDOWS\system32, cmd.exe in C:\WINDOWS\ServicePackFiles\i386, and cmd.exe in C:\WINDOWS\system32\dllcache. Thoes where the only ones that said cmd. now for command:command prompt shortcut in C:\Documents and Settings\XXXXX\Start Menu\Programs\Accessories, where XXXXX is the username. Command.exe in C:\WINDOWS\system32\command.com, command shortcut in C:\WINDOWS\system32\command.com, and a command prompt shortcut in C:\WINDOWS\system32\config\systemprofile\Start Menu\Programs\Accessories.
That's all I found.
That's all I found.
#20
Posted 04 September 2005 - 01:00 PM
here's the next step - double click on each cmd.exe and command.com. at least one of those will fail. identify the good ones - then you might want to save them to floppy in case this happens again. double click on the newly copied floppy versions to make sure they are good files.
make copies of all cmd.exe and command.com and name them something clever like cmd.exe.good or cmd.exe.bad.
now you can delete the any bad files and replace them with a good file. please make copies of the files before deleting anything.
make copies of all cmd.exe and command.com and name them something clever like cmd.exe.good or cmd.exe.bad.
now you can delete the any bad files and replace them with a good file. please make copies of the files before deleting anything.
#21
Posted 04 September 2005 - 01:04 PM
bad being nothing comes up?
#22
Posted 04 September 2005 - 01:09 PM
either the cmd or command window opens or it doesn't. I had a similar problem recently. one version would open the window, then it would immediately close. your failure symptoms may vary slightly.
#23
Posted 04 September 2005 - 01:10 PM
ahh
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users