<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.0.9"> </HEAD> <BODY> <BLOCKQUOTE TYPE=CITE> <PRE> If Windows overwrites your MBR you can fix it fairly easily. Boot from the FC1 CD in rescue mode. This mounts your root partition at /mnt/sysimage, so run # chroot /mnt/sysimage to make it the root filesystem. Then run # grub-install /dev/hda (this assumes that GRUB is to be installed in the MBR of the primary master disk, if not you'll need a different command).</PRE> </BLOCKQUOTE> Fixing XP wasn't my primary worry. It was the Grub situation that had me in "newbie terror" mode. <IMG SRC="cid:1082718017.7646.6.camel@localhost.localdomain" ALIGN="middle" ALT=":-)" BORDER="0"> I suspected XP would crash on me. I can't say I've ever made any radical hardware changes on any NT-based windows machines without there being a crash. If it wasn't for the fact that my daughter uses XP for games, I more than likely would not repair it at all. The few windows apps I do use still run perfectly from wine. Thanks for the help! <BLOCKQUOTE TYPE=CITE> <PRE> As to fixing XP, that's another issue and one which doesn't really belong here. The only advice which should appear in this list for fixing XP is to run mke2fs /dev/hda1 which will cure all problems with XP (but I won't because that wouldn't be nice). Basically, you need to boot into safe mode and delete all devices related to the changed hardware - graphics card, IDE, USB etc. Then reboot and let XP detect the new hardware. Make sure you backup any XP files you need to keep as this process doesn't always work, changing the MB sometimes requires a re-installation of XP.</PRE> </BLOCKQUOTE> <PRE><TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> </TD> </TR> </TABLE> </PRE> </BODY> </HTML>