Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Not certain on this one, but Ghost may check for whether the partition on which Windows is installed is flagged as "active". It's a flag you can set in GNU fdisk, and might be an option on MS fdisk. I remember something about old versions of Windows on certain hardware required the active flag to be set to boot properly. Maybe Ghost is checking that and giving up the ghost. <har har> -- David Backeberg (dave at math.mit.edu) On Tue, 26 Sep 2006, Scott R Ehrlich wrote: > Symantec's web site states that Ghost 2003 (what I have) will NOT work with > Grub. > > I have RHEL4 installed on a dual-boot machine I want to image. I have a > bootable DOS disk and performed an fdisk /mbr, but Ghost still complained. > The machine did boot into Windows, though, so Grub apparently had been removed. > > Not knowing what else to do, I'm re-imaging the machine with the XP image I > preserved, and am reinstalling RHEL4 but with no boot loader. > > What else could I be missing to fully remove Grub and permit Ghost to work? > > It would be most helpful to at least have Grub working during the install, then > have a proven way to remove it, image the system, then I can reinstall Grub > after the image. > > Any help/insights appreciated. > > Scott > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |