Lets make sure msdos.sys is ok. Type the following (including the 'type': type msdos.sys You should see a lot of stuff displaying, including a whole bunch of XXXXXXXs. If you see just a line or two, msdos.sys is bad and needs to be replaced. Do yourself a favor BACKUP!!!

0

Sure - and if that is the case (MSDOS.SYS only contains a line or so) then you can copy and use this one, once you fill in the angle bracket parts: WinDir=<Windows> WinBootDir=<Windows> (usually C:\Windows) We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

0

when i type in "type msdos.sys" this is what i get ";SYS" what does this mean and then the C:\> prompt andreyus

0

That means msdos.sys is corrupted. See Jboy's post #8 above. Go to that Microsoft page and it will show you how to create a msdos.sys file. Note the: WinDir=<Windows> WinBootDir=<Windows> (usually C:\Windows) Lets hope that's the last problem. Do yourself a favor BACKUP!!!

0

ok i got to the MS-DOS Editor i kind of dont understand what am i supposed to type am i supposed type [Paths] WinDir=<windows> WinBootDir=<windows> HostWinBootDrv=C [Options] BootGUI=1 ; ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx something like that and how do i know if its bigger than 1024 bytes and do i have to change the name of it or just keep it as untitled sorry for being so anoying but i like dont know anything about programming andreyus

0

Yes, you seem to have it right. Just copy exactly (except for the example below) what it shows on that web page. If you do that it will be over 1024 bytes. this will be the only difference: WinDir=<c:\windows> WinBootDir=<c:\windows> The name should be msdos.sys Don't hesitate to ask any questions. Do yourself a favor BACKUP!!!

0

Assuming your Windows is in the standard location, yes - but lose the angle brackets: WinDir=c:\windows WinBootDir=c:\windows MSDOS.SYS was a DOS system file, but its original function has been incorporated into IO.SYS - the version found on most bootdisks is a placeholder, the 'full version' is created upon installation, on the hard drive, and contains the location of Windows (among other things) We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

0

OOOps, thanks jboy. Do yourself a favor BACKUP!!!

0

okay i did all of that now when i try to save it it says this "Path/File access error" i hit "help" and it said this "make sure the file specification you entered in the text box id formatted correctly. Any filename can contain a drive name and a full or partial path. This error can also occur when you try to sav file which would re place an existing read-only file." (thats what i think i did) what do i do now andreyus

0

The 'bad' copy of MSDOS.SYS on your C: drive is likely a protected file - as per the instructions from the given link, you will need to remove that protection from DOS: At a command prompt, type the following: attrib -s -h -r c:\msdos.sys We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

0

Did you type the following before loading and editting the file? attrib -s -h -r c:\msdos.sys If not change the name of the file you made to msdos.tmp and save it. Then type in: attrib -s -h -r c:\msdos.sys and then: del c:\msdos.sys ren msdos.tmp msdos.sys attrib +s +h +r c:\msdos.sys Did you see Jboy's correction to my post? It should be: WinDir=c:\windows WinBootDir=c:\windows not WinDir=<c:\windows> WinBootDir=<c:\windows> Do yourself a favor BACKUP!!!

0

I'm gonna back out of here and let Jboy handle it. It's getting late and my mind isn't working that well. Do yourself a favor BACKUP!!!

0

That should work - although once the protected attributes are removed from C:\msdos.sys, you can just overwrite it using 'save as' More than one way to do things In the past, we used to email the file, or else paste a copy here in the forum, but the link works just about as well, since it is only a text file. The location of Windows is the most important bit of data in the file, but it can be used to control other aspects of the OS We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

0

I can email you a 95 msdos.sys if you can't get it figured out.

0

ok i got it but then when i try to load it up it say the windows doesnt run on Msdos 7.00 or earlier what am i supposd to do now get a newer msdos andreyus

0

You probably sys'd the drive with the wrong OS version. Boot up the computer, either from the c: drive or a bootdisk. Then at the dos prompt type dir c:\command.com and post back exactly what it says. Then type dir c:\windows\command.com and post back what that says. The first will tell us what version you sys'd the drive with and the second will tell what version of windows you have.

0

dir c:\command.com says: Volume in drive C is AP Volume Serial Number is 0765-17f8 Directory of C:\ COMMAND COM 92870 07-11-95 9:50a 1 file(s) 92870 bytes 573800448 bytes free dir c:\windows\command.com says: Volume in drive C is AP Volume Serial Number is 0765-17f8 Directory of C:\WINDOWS COMMAND COM 93974 02-19-99 10:55a 1 file(s) 93974 bytes 573800448 bytes free andreyus

0

OK, that threw me for loop for a bit. Normally they should match but the second one is the result of a 95 Y2K update so I guess it's OK. Go to a prompt again and type dir c:\windows\win.com and enter. Post back what it says.

0

it says: Volume in drive C is AP Volume Serial Number is 0765-17F8 Directory of C:\WINDOWS WIN COM 24503 08-24-96 11:11a 1 file(s) 24503 bytes 573800448 bytes free andreyus

0

Seems to be a version mismatch - are most of the other files in the Windows folder also timestamped 08-24-96 11:11a? We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

0

no i dont think so andreyus

0

Well then - either you've somehow gotten the wrong version of win.com, or else you'd used the wrong version of Win95 bootdisk when you sys'd the drive We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

0

ok can you tell me how to reboot my laptop totally so i can start over andreyus

0

'Reboot'? Possibly you mean repair? Depends on which version of Win95 was originally installed If it's a case of the wrong version of command.com, you would replace it with the correct one, either by copying from another source (such as a bootdisk) or do another 'sys c:' with the correct bootdisk version If it's the wrong version of win.com, then you would replace that with the correct version, either by copying from another source, or by extracting win.cnf from your Windows CD and rename to win.com At a guess (based on the info provided) seems like your version of win.com is the wrong one We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

0

ok first of all i cant access the desktop and when i try i type in c:\windows\win i get an: "VFAT Device or resource required by VFAT is not present or is unavailable. VFAT cannot continue loading." "System halted" andreyus

0

I'm going to put together a bootdisk that'll replace your existing 95a system files with 95b system files. Give me a few minutes and I'll email it.

0

OK, I sent it. Create the bootdisk, boot up the computer with it and it will automatically change the files. When it's done, reboot without the bootdisk and see what happens. If you continue having problems then it's likely you've deleted other necessary files.

0

Ok - well, I'm not sure why you'd be doing that (#31) but at any rate, go with DAVE's fix and replace the system files (the 'other' possibility) the moral here is: don't delete files just to be 'tidy' - it seldom ends well We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

0

HEY THANKS A BUNCH ITS WORKING PERFECTLY THANKS EVERYBODY AND A SPECIAL THANKS TO DAVEINCAPS andreyus

0

You're welcome. We're glad you got it fixed.

0