Date: Sat, 8 Jul 1995 00:35:19 -0700 (PDT) From: Howard Lew <hlew@genome.Stanford.EDU> To: adrian@virginia.edu Cc: questions@freebsd.org, bugs@freebsd.org Subject: Re: booteasy broken??? Message-ID: <Pine.SUN.3.91.950708002922.6124A-100000@vegemite.Stanford.EDU> In-Reply-To: <Pine.SUN.3.90.950707201304.12442A-100000@stretch.cs.Virginia.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 7 Jul 1995, Adrian T. Filipi-Martin wrote: > Hi, > > I had a similar problem, but fixed it. In my case, the boot > record on my second disk had been erroneously written. I do not know > which OS was the culprit, so I chose to blame MS-DOS. ;-) > > The error is that the physical disk number was wrong. Even though > it is the first disk as far as DOS is concearned, its number is 0x81 and > not 0x80! I didnt' spot this error until running fips, which does a > thourough job at checking for irregularities. All that is necessary is to > use your favorite disk editor and change the value. After this one bit > change, my second disk booted DOS w/o difficulty. I suggest Norton > DiskEdit if you can have it, but you can also do this with DOS's debug if > you are brave enough. Yep, you're right and it works... I also have a 386-40 system configured the other way DOS on wd0 (which boots okay) and FreeBSD on (wd1 which doesn't boot). And the Disk Editor trick doesn't work (and it doesn't say 128). Now to think about it, I'm not sure if it was 0x81 or 0x80.... PC Tools Disk Editor said 128 originally, but when I used the view info, it say it already was 0x81. I entered 129 (decimal) and wrote it to the hard disk. The reboot works great. Now I just have that one other problem with the 386-40 mentioned above. Thanks for the help.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.950708002922.6124A-100000>