Link to home
Start Free TrialLog in
Avatar of thartin
thartin

asked on

Can't get HD to boot

I'm trying to setup an old computer for a friend.  It's an AST Advantage 486 SX/25 with a Quantum ELS 170 MB HD.  I got it to boot fine from the floppy, then I FDISK'ed it as the primary DOS partition (active) and formatted the drive. I then copied over the system using the SYS command, but then when I try to let it boot up from the HD it just writes "LI" on the screen after the initial system check.  It then freezes and won't respond to the keyboard.

When I boot from the floppy I seem to have full access to the HD, so why won't it boot from the HD?  
Avatar of jrhelgeson
jrhelgeson
Flag of United States of America image

What Version of dos are you using?
Try typing fdisk /mbr at the dos prompt, then sys-ing the drive.
If it still does not work, try re-creating the partition and formatting with the /s option. -- I know, it's the "same" as sys-ing the drive, but sometimes just doing that will work.

I would also check your bios settings, try auto-config w/bios defalts, or w/setup defaults.

Some simple steps to start with.

Joel
ASKER CERTIFIED SOLUTION
Avatar of adamgg
adamgg

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
There are "leftovers" of a linux installation on the disk, run
"fdisk /mbr".
Avatar of arlenes
arlenes

when you format try format /s to install the system files
Nope.. /S does NOT remove the LiLo, but /MBR does.
Avatar of thartin

ASKER

j2 was right, this computer used to be Linux box.  The FDISK /mbr command did the trick.  Question: why doesn't FDISK and FORMAT completely clean off the disk, and what does the /mbr switch do?
Well, even tho i didnt get the points, ill explain :)

/mbr is a undocumented feature that reinstalls the "master boot record" (the very first piece of info on the disk) Linux entire bootstraploader lives in this area. MSDOS doesnt have a bootloader in the same fashion, and /S only replaces the system files, not the MBR, because it would be a shame to delete a custom bootloader everytime the systemfiles was tranferred :)