<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> norman wrote: <blockquote cite="mid:1196283342.5683.147.camel@localhost" type="cite"> <blockquote type="cite"> <pre wrap="">If I'm following correctly, the Ubuntu drive is SATA. Therefore it doesn't come into master/slave debate. </pre> </blockquote> <pre wrap=""> That is correct and interesting. Does that mean I could just plug in another SATA drive without having to worry about setting jumpers etc? </pre> </blockquote> I don't have much experience with SATA drives so my help is limited. I believe you can have one SATA drive per header/connector meaning no need for jumpers. Some controllers are hot swappable so you can plug drives in and out without turning off your machine (except for the drive you are booting from of course). <blockquote cite="mid:1196283342.5683.147.camel@localhost" type="cite"> <blockquote type="cite"> <pre wrap="">Assuming the Ubuntu drive is fully working and Grub is installed to the MBR, can you post the menu.lst and device.map files the from /boot/grub/ directory to the pastebin (or to this list)? Then we can see the current configuration and maybe make suggestions about what needs to be changed. </pre> </blockquote> <pre wrap="">Please explain to this ignorant one what is the MBR and how do things get installed there? There have been no changes made to menu.lst other than the few lines right at the end which I was advised to put there, these are:- title Windows map (hd0) (hd1) map (hd1) (hd0) rootnoverify (hd1,0) chainloader +1 device.map is simply:- (hd0) /dev/sda I would have thought there should be some reference to hd1. </pre> </blockquote> Grub doesn't update the device.map unless you ask it to, so new drives don't get immediately recognised. You can run the 'update-grub' script from a terminal on the live CD to have Ubuntu rewrite the file, although I don't think there's any harm in editing it yourself. In any case you'll need an extra line in device.map for your second drive: <tt>(hd0) /dev/hda</tt> Not sure if your other drive will be /dev/hda, it could also be hdb, hdc or hdd, depending on which controller it's connected to and whether it's the master or slave to your optical drive. Tom </body> </html>