A friend is running Win 95. He went to start it this am when he got disk error message, I went over tried his boot up disk, got this error message C:\windows.command.com is infected or missing. I have gotten a new boot disk from www.bootdisk.com. Can anyone else think of something. Just don't remember that much about 95. Thanks

Kinda hard to decode what you did. The Windows 95 startup floppy should not be looking for command.com on the HDD. It runs all by itself, it has it's own command.com on the floppy. If you are "positive" you have the same version of command.com on your boot floppy as the installed windows version then boot with the floppy and key in: SYS C: It might be safer to download a boot floppy from: http://www.allbootdisks.com/ These disks are identical (w ramdrive for 95osr2) with the MS disks. Win95a is 7/11/95 9:50 AM Win95b is 8/24/96 11:11 AM (i think) Best ******************************************************

"C:\windows.command.com is infected or missing." Bizarre on several counts - are you sure it didn't say 'missing or corrupted'?? Very likely you are not even booting from the floppy if you're receiving C: drive errors - check the boot sequence in the BIOS and ensure that the floppy is first. Wouldn't hurt to check that the HDD is identified correctly there as well. What, exactly, was the 'disk error message' that started this in the first place? Click

bizzare, indeed; not every day you see a file named windows.command.com ! M2

MikeD - Is there an autoexec.bat on the bootdisk you used? If so, is the path statement mis-written to look for "C:\windows.command.com"? If the latter is the case, perhaps the autoexec.bat should be looking on a:\ for the command file, or should be re-written to look for c:\windows\command\command.com You don't have to be realistic to be cynical, but you DO have to be cynical to be realistic!

Not really. Autoexec.bat isn't even required. Location of command.com is *not* determined by the path - although it can be reset from the default by using the 'set comspec' statement. Command.com normally resides in the root of C: and in C:\windows - not in the command subfolder - take a look. Regardless of all that, when booting from a bootdisk, the only copy of command.com that's relevant would be the one on the a: drive Until we get some feedback, it's just guesswork (good or bad) Click