Date: Fri, 12 Jan 1996 17:19:01 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: hlew@genome.Stanford.EDU (Howard Lew) Cc: terry@lambert.org, questions@FreeBSD.org Subject: Re: Ontrack DM & FreeBSD 2.1R Message-ID: <199601130019.RAA21110@phaeton.artisoft.com> In-Reply-To: <Pine.SUN.3.91.960112145400.4393A-100000@vegemite.Stanford.EDU> from "Howard Lew" at Jan 12, 96 03:06:02 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > The workaround is to use the DOS version of the OS-BS install from
> > a DOS prompt after booting DOS from wd0 (if you are booting Windows95,
> > you will need to pick the "reboot to DOS prompt" option from the
> > "Shutdown" on the Windows95 "Start" menu or the install will be
> > prevented, since they guard their boot track as a virus safeguard).
>
> For some reason, this OS-BS never did work with booting on the second
> drive if the first had Ontrack DM. I've tried this with 2.05 and the
> snaps before it.
Ugh. THis is part of the one drive/both drive assumptions that are
made. When you boot one with ontrack, it expects the other to
behave similarly. This might be classed as an OS-BS bug, or an
install bug (from you not putting OnTrack on both disks.
Putting it on both disks would probably fix the boot sector damage
on wd0 coincidently.
> Hmmm... maybe if just before installing the boot selector, the
> installation program could check if Ontrack DM is there.
That would fix the wd0 problem, but not the OS-BS problem.
Terry Lambert
terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601130019.RAA21110>