Has anyone done it? Any problems?
Has anyone done it? Any problems?
The only problem I can foresee is it’s possible that windows service packs may not install because of grub. I have seen this in Vista and I have done trial installs of W7 RC with OS11.1
If this does become an issue at any time, the solution is easy. Restore the Windows boot code, install the service pack, re-install grub.
All About Grub - openSUSE
I currently have a Win7/openSUSE 11.2 setup, and there were no problems with it at all. As with previous releases, it is better to install Windows first and then install openSUSE so grub detects it.
A note on Win7 is by default it creates a 100MB boot partition and a main system partition. When grub is setup, it needs to point to the Windows boot partition in order to chainload because the system partition cannot boot on its own. Other than that, the two coexist swimmingly.
Didn´t use GAG with Windows 7, though I always had good results with GAG for Windows 2000, XP and Vista.
When you use GAG it does not matter in which order you install the OS´s. Make sure that for Linux and BSD you install the boot loader in the root partition.
GAG you will find here: GAG, the Graphical Boot Manager
Very interesting. I’ve installed a few of windows 7 and not once did I get a 100mb boot partition. I wonder what you and I are doing differently.
Perhaps some version difference, I do have a 100MB NTFS partition labeled “System Reserved”. Seems like openSUSE mounted it under /media/System_Reserved… and it does indeed contain bootfiles.
Using Win7 professional.
I have no problems running the two operating system alongside. Installed the servicepacks under vista just fine as well… although SP1 took like 5 tries of doing the same thing before it installed… and it took longer than it takes to install the OS itself.
I agree with you John. I didn’t get this either. Mind I’m talking the RC. Didn’t buy the **** (*= use imagination )
All mine have been so-called “windows 7 professional upgrades” of xp which requires a clean install onto an existing NTFS partition at location sda1.
The upgrades were performed by running “windows easy transfer” to take the data off, archive the whole old xp filesystem/tree in a folder named “windows.old” on sda1, and install win7 fresh and clean onto the old NTFS partition at sda1.
I wonder if this:
I do have a 100MB NTFS partition labeled “System Reserved”
is really a proprietary OEM reserved partition like notebook vendors commonly put on their notebook drives, where the bootloader files so often end up because it’s a windows-readable partition at sda1?
On my Vista/Win7/Linux box, there’s a small partion with diagnostic stuff in it. When I booted it out of curiosity, it actually copied Disk 1’s partition table to Disk 2, which lead to some fun with gpart & sfdisk patching the table back up, as the dumped partition table, was sitting on the disk in a “lost” partition rather than copied safe to central storage.
Oh the unpredictability & excitement of Windows Update, I had problems with their last mega-fix pack, causing an infinite loop of reboots! Doing a de-frag after doing all other updates first, before going for the biggies seems to improve things.
Win 7 installed into a partition I set aside for it, integrating itself with Vista boot loader, so no change to GRUB entries, just normal chain.
i have open suse, and one free partition…so i installed win 7 in it…but now only win 7 is loading…how do dual boot?
If you have a Linux Live CD, boot from it and log in. Then open a console window and enter su and you will be at the command prompt with root powers and ready to proceed. If on the other hand you have the openSUSE install DVD, boot from it and on the first menu of options select the Rescue System option. That will start an elementary Linux Live operating system and bring you to the login prompt. Enter the username root and you will be at the command prompt with root powers and ready to proceed. Whichever way you started (the openSUSE install DVD or a Linux Live CD) when you are at the root command prompt, first you find the partition containing openSUSE’s bootloader. Then you reinstall Grub with a pointer to that partition. First find the openSUSE installation:
You enter this ---------------- grub
Computer returns like this ---- grub>
You enter this ---------------- find /boot/grub/menu.lst
Computer returns like this ---- (hd0,5)
Here, (hd0,5) is Grub’s pointer to my openSUSE installation. Your pointer will be different from my example (hd0,5). Substitute your values for my example (hd0,5). Now that you have the pointer, proceed like this:
You enter this ---------------- root (hd0,5)
Computer returns like this ---- Filesystem type is ext2fs, partition type 0x83
You enter this ---------------- setup (hd0)
You see several lines like this — Checking if /boot/grub/stage1 exists … yes Computer finally returns this-- Succeeded…Done
You enter this ---------------- quit
You enter this ---------------- reboot
I had the same problem of update when dual booting. Also the Windows vista/7 won’t hibernate if grub is the bootloader. So I had to make windows bootloader to load both the Linux and windows 7.
I used EasyBCD to do the work. You may find this webpage useful.
How to dual-boot Vista with Linux (Vista installed first) – the step-by-step guide with screenshots
That looks interesting, thanks for the tip. Quite similar in operation to Neowin’s EasyBCD.
Regarding the 100mb being set aside by Windows 7.
I’ve seen it do it and not do it. From what I can see, if you have a clean disk with no partitions, Win7 creates a 100MB partition for system files when you create your first partition on the disk. The installer tells you it’s going to do it but doesn’t give you a chance to say no.
If you have a partitioned disk and simply want to format and install Windows 7 on one of the partitions, the 100mb partition isn’t created.
My Win7 creates that 100MB partition too, and if you remember, XP did this, but it was an 8MB partition. SUSE sees it as C: and the Windows C: is seen in SUSE as D: