Need to delete Windows XP after Dual-Boot Vista Install.

[Xtreme2damax]

As the title states.

I had windows XP installed first, but then installed Vista in a Dual boot with XP. Both Vista and XP are using the Vista Bootloader right now.

I've been having some problems with XP and having my run in with Microsoft trying to get it solved.

So now I want to uninstall Windows XP and replace it with Ubuntu 7.04 (Feisty Fawn) instead while dual booting Ubuntu with Vista so I can still play all my games I currently own.

How would I go about uninstalling and deleting My XP Partition without it affecting my Vista install?

I don't want to mess anything up since I got a lot of data stored on my PC with no means to back it all up, so I need to do this right the first time without error.

Can someone tell me how to go about this without messing anything up?

Thank You, I would really appreciate it if someone can help me.

[Hard core Rikki]

Losing the bootloader located in C will make no data disappear, just rest assured. You might want to keep a live linux cd or usb handy just in case you cant access your data temporarily (puppy linux would suffice for this).


I believe you would be able to safely format XP's partition (after duly saving/moving its data to a safe place/Vista's partition). One it's formatted, consider unformatting it (RAW unused space, not ntfs or fat32)


After that, if XP's bootlader entry didnt disappear, edit it out. Once only vista's partition and unused space exist, Feisty should install without problem, with grub entering a line for vista:other OSes.

If grub didnt add one, some manual editing will be needed, nothing too stressful though. Quoting a premade solution. As usual, ask for more inputs before such operations.

Configure GRUB

If you want to modify how GRUB handles the new dualbooting environment, you need to edit the boot menu. Boot into Ubuntu and open up a Terminal window (Applications, Accessories, Terminal), and type in:

sudo cp /boot/grub/menu.lst /boot/grub/menu.lst_bak

and enter your root password when asked - this makes a backup of the GRUB menu file just in case things go wrong.

Next, type in:

sudo gedit /boot/grub/menu.lst

Dualboot - Configure Boot MenuDualboot - Configure Boot Menu



This opens up the boot menu as a text file in gedit.

Dualboot - Boot OptionsDualboot - Boot Options



There are loads of options you can change, but only a couple that you’re likely to be interested in. The default boot entry is defined by the “default” value.

The default value is 0, which means that the first entry in the list (which is Ubuntu) always gets loaded.

If you want to make it so that Windows Vista loads by default, change the value to 4, as Vista is the fifth item in the list (the numbering system starts at 0 and "Other operating systems" counts as a line).

The other way to load Windows Vista by default is to change the value for “default” from a numerical value to “saved”. Then, GRUB will load whichever boot entry has been marked with “savedefault”.

If you scroll down the list and have a look at the entries, you’ll notice that both the main Ubuntu entry and Windows Vista have been marked with “savedefault”. Remove the value for Ubuntu and Windows Vista will launch by default.

It's also worthwhile changing the description of the Vista entry from "Windows Vista/Longhorn (loader" to just "Windows Vista".

You can also increase the boot menu timeout – just change the value for “timeout”. You can also hide the GRUB boot menu by removing the hash in front of “hiddenmenu”. Save and exit gedit to keep any changes.

If instead of GRUB you want Vista's bootloader to be in charge, load up the Vista installation and install EasyBCD. Go to “Manage Bootloader”, then “Reinstall the Vista Bootloader”, an GRUB is overwritten. You can then configure the Vista bootloader to add Linux to the boot menu.

[Xtreme2damax]

Thank You HCR I really appreciate it. I have another quick question or to if not too much trouble. My machine is capable of running a 64-bit OS, is there any 32-bit programs that won't work in Feisty 64-bit?

Will I still be able to use Arnieboy's Automatix Automated install Program, Install Wine or Cedega (When I Subscribe for Cedega), run ID games like Doom 3, Quake 4 and others and use emulators in the 64-bit version of Feisty Fawn?

Also the last time I had Feisty installed, my Wireless Network Connection dropped out and the wireless Networking Icon would disappear from the top right hand corner of the screen, making me unable to re-connect forcing me to reinstall Ubuntu Feisty.

Has that issue been acknowledged and a fix issued yet for Ubuntu Feisty?

[Hard core Rikki]

Actually I'd advise sticking with 32bits Feisty if possible. Most if not nearly all synaptics packages should work fine anyway on 64bits feisty (32bits-only ones can be made to work anyway), using Kilz script (one single line and 2 or 3 choices... as easy as that)

- There will be issues with Wine barely working (you might considere cedega then)

[KillerShots]

Issues with 64-bit linux (in general):

Flash - won't work with 64-bit browsers. Either make sure you have a 32-bit browser as well, or do without flash. Note that the same problem exists in XP / Vista. Flash just doesn't support 64-bit. Period.

Cedega - Never did get this working right under 64-bit. If you really really want cedega, I'd recommend stearing clear of 64 bit.

Movies - anything that needs win32 codecs or similar won't work without a 32-bit player. Either make sure you have one lying around somewhere or don't use 64-bit.

[Hard core Rikki]

Myths.

Flash works properly now, one can always use Kilz script for anything still troublesome.

Multimedia is where it shines right now (with ocasional hiccups, nothing critical, use Kilz script again), especially transcoding and ripping.

[KillerShots]

Oh really... I haven't had flash working properly in konqueror as of yet, and the reasoning I've been able to dig up is that 64-bit binaries have not been released (flash is not open source, so you cannot compile it yourself in 64-bit mode).

Not familiar with the "Kilz" script - care to shed some light on this thing?

Anything that kills my system capability I don't tend to consider a "myth"

[Hard core Rikki]

The Kilz script is discussed in the ubuntu forums, mostly here.