Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rphroy!caen!hellgate.utah.edu!csn!ncar!unmvax!uokmax!occrsh!fang!tarpit!bilver!bill
From: bill@bilver.uucp (Bill Vermillion)
Newsgroups: comp.unix.sysv386
Subject: Re: ISC dual boot
Message-ID: <1991Mar5.142716.10448@bilver.uucp>
Date: 5 Mar 91 14:27:16 GMT
References: <1991Feb25.210428.4566@world.std.com> <995@redford.UUCP> <1991Mar4.141901.4772@ux1.cso.uiuc.edu>
Organization: W. J. Vermillion - Winter Park, FL
Lines: 24

In article <1991Mar4.141901.4772@ux1.cso.uiuc.edu> brando@uicsl.csl.uiuc.edu (Brandon Brown) writes:
>bill@polygen.uucp (Bill Poitras) writes:
 
(prior comments on vp.ix drive access deleted)

 
>Well as far as on power-up I believe someone posted a small little "boot menu"
>for ISC to boot either to DOS or Unix on the initial boot, but I wouldn't
>recommend it, unless you really switch between the two alot. I would use the`
>"fdisk" commands on both Unix and DOS to switch between the two.

Well I would surely recommend >AGAINST< fooling with the fdisk.  I have
seen systems get wiped out with this.  Some systems furnish a dual boot, if
not get the one posted here, or do the following (which I recommend to all
those I work for who don't want/have the  dual boot option.

Make a bootable DOS disk, with a switch to C: drive, and be sure to include
the comspec option to specify command.com on C:.

I have never had problem with the dual boot.

-- 
Bill Vermillion - UUCP: uunet!tarpit!bilver!bill
                      : bill@bilver.UUCP