Missing O.S

November 11, 2009 at 14:21:04
Specs: Windows 3.1, 256/256
Missing Operating system

Earlier today, I loaded up an old hard drive and Windows 3.1 took off a going like it had for years. Did some stuff there then quit. Turned off the computer and found did a batch of bad work so came back to add and correct.

Now, am getting the error message of Missing Operating System smack after completing the boot process.

How could DOS go bad so fast then? Anyone got an idea as to what should do to reinstall an operating system? Using another computer and connection, I can find the Autoexec.bat file and it looks normal. I ran Scandisk there too, and it said all was OK and normal with the old hard drive. I got the old DOS disks, but do not want to load them up for after that it will be Windows 3.1 time again, and will loose every single file and program then.

Wm.


See More: Missing O.S

Report •


#1
November 11, 2009 at 14:52:27
booting a dos 6.22 diskette containing fdisk and sys

Go into fdisk and make sure the partition is marked active.
After exiting and rebooting [if you made a change] then run
fdisk /mbr then
sys c:

The first makes sure the partition is active
The second makes sure it has a mbr
The third copies the boot files to their correct locations.


Report •

#2
November 11, 2009 at 16:40:39
Well, don't SYS it with 6.22 unless that's the dos version you're running on the 3.1 dirve.

Is the drive in the same computer in which it was previously working. If not, what was it in before and what is it in now?

Is the drive properly identified in cmos/bios setup?

Help me Jebus!


Report •

#3
November 11, 2009 at 17:10:22
Dave...

The computer has been around the block a few times now, new printer, but same ol' same old. That same computer has had a few Win 95 hard drives, but only one Win 3.1 in it.

It was way beck when set up to run programs in DOS 6.2 which I still got the original disks here, as mentioned. Never had 6.22 on it.

Which is the odd point, It fired right off this morning, and is dead now.


Wm.


Report •

Related Solutions

#4
November 11, 2009 at 19:27:53
Make sure it's seen right in cmos/bios setup and that the drive's data and power connections are tight and in good condition. Maybe that's all it is.

You can SYS it with the first 6.2 disk. Just boot from it and exit the installation process. That should leave you at a:\>. Then you can sys it and run fdisk as wanderer mentioned.

Help me Jebus!


Report •

#5
November 13, 2009 at 14:11:15
Got yet another loaned out computer back home late night. A third one.

Well, plugged that probem hard drive in to it, and whammo, it took off running like normal.

Am wondering if the problem could not have been a slowly pooping out power supply now.


Wm.


Report •

#6
November 13, 2009 at 14:23:51
I'd still bet on the BIOS setup for the hdd Dave spoke of in response #4. Write down the cylinders/heads/sectors the current install sees in BIOS; they're obviously correct.

Reinstall the drive in the problem machine and check to see if they match. A BIOS can see more than one configuration and they're not all correct.

Skip


Report •


Ask Question