While, as Paul describes, runnin Windoze on the slave is 
possible, I'd strongly suggest keeping the Windoze HDD as master and 
runnin Linux on the new drive added as slave.  I just believe it's 
easier and more foolproof. Linux doesn't care, it'll run just as 
well on the slave.  Winblows prob'ly won't.  If you haven't bought 
that new drive yet, I'd suggest a 7200 rpm with a 2mb cache (I like 
IBM's right now).
-- 
Tom Brinkman        [EMAIL PROTECTED]         Galveston Bay

On Saturday 04 November 2000 07:26 am, Paul wrote:
> It was Nov 4, 2000, 19:46, when Abraham E Mandac Jr keyboarded:
> >Pentium II 300 MHz, 64 MB RAM on an ASUS P2E-M motherboard
> >2 GB IDE HDD [the master HDD -- my only HDD at that]
> >
> >This is what I intend to do:
> >
> >1. Buy a new IDE disk and mount it as the new master drive [to
> > replace the old two-gig hard disk]
> >
> >2. Reconnect the old 2 GB drive, this time as the slave drive
> > [with Windows and everything else on it still intact]
>
> This should work well if you do not create any DOS-partition on
> your new harddisk. Add 1 DOS-like partition and the drive letters
> will get messed up, leaving your Windoze stuff dangling on the
> wrong drive. MS really did the world a favor with that technique.
>
> >Would the installer be able to 'detect' Windows on the slave slot
> > so I could still boot to Windows as it always was?
>
> I don't know this. It would not be a problem though, to add this
> to lilo.conf:
>
> other=/dev/hdb1
>       label=dos
>       table=/dev/hdb1
>
> Or its equivalent in grub:
>
> title dos
> root (hd0,0)
> makeactive
> chainloader +1
>
> Paul

Reply via email to