Date: Fri, 7 Jul 1995 20:21:09 -0400 (EDT) From: "Adrian T. Filipi-Martin" <atf3r@server.cs.virginia.edu> To: Howard Lew <hlew@genome.stanford.edu> Cc: questions@freebsd.org, bugs@freebsd.org Subject: Re: booteasy broken??? Message-ID: <Pine.SUN.3.90.950707201304.12442A-100000@stretch.cs.Virginia.edu> In-Reply-To: <Pine.SUN.3.91.950707132425.13488B-100000@marmite.Stanford.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
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. good luck, Adrian adrian@virginia.edu ---->>>>| Support your local programmer, http://www.cs.virginia.edu/~atf3r/ --->>>| STOP Software Patent Abuses NOW! Member: The League for -->>| info at ftp.uu.net:/doc/lpf, print Programming Freedom ->| "join.ps.Z" for an application
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.90.950707201304.12442A-100000>