BIG question about dual boots
Ok, here is the beef
I had an already installed system. Windows 2000 pro on a 80 Gig drive. I decided to install suse 9.3 pro..onto a 20 gig that was not being used.. Well low and behold, guess what I cannot boot to windows as I presumed and read. Well, now I am stuck... How do I modify my menu.lst and device.lst to enable that.... Here is the info from the mapping of the drives Hda and hda1 are the mounted drive that windows exists on...why it separated the partition, I do not know... hdb, hdb1 and hdb2 is the 20 gig where linux exists, swap area etc etc all on it... Can any well versed linux guru help me out as to what to put into the list and menu file to get windows into the menu so I may duel boot with windows again. Yes I can fully see all of the windows partition and access it. Just need to have the old system back up to switch to. |
hi,
you can start your configuration on your linux ? if($response eq "yes"){ Code:
vi /boot/grub/menu.lst else{ Boot on a livecd or floppy disk and edit them. } excuse for my geek attitude..i'm tired :D |
Hey GaMeS (hd0,1) actually refers to partition /dev/hda2. won't he want (hd0,0) instead?
[edit] also i thought makeactive had to be on the line before chainloader? so i would like this right? I don't use grub so I could be way off here but this is what it looks like after my editing.... Code:
title Windows |
excuse me :x
yes try (hd0,0) he can edit line on the grub menu ... press 'e' key and add line on config grub..but the add is not permanent(i think) |
Hmmmm
Quote:
In looking at me path folders.....it is really confusing....I understand what HD is...but the 0,0 and 0,1....I am lost on this.. |
Going from the top of my head, so I could be wrong in some details. The difference is in how the Linux kernel sees devices the /dev/hda1 one part and how Windows or more correctly the PC's bios sees the partitions the (hd0,0) part. So depending on where the information is being sent, to either the bios or to the OS depends upon which notation must be used.
Also in your bios you can likely change the boot sequence of your hard-drives. On my system I have my Win2K Pro on my D:/ drive (mainly for historical reasons - originally had W9x on C:/) and my Linux is on a later partition. I will post a copy of my menu.lst file. It won't be exactly what you need, you will likely need to change some of the 1's and 0's, but it will give you a good starting point. Code:
# grub.conf generated by anaconda |
Let's try this Saspen, post the contents of the file /boot/grub/menu.lst for us. That way we can build the new menu for you and help you understand each point your configuration.
|
Ok
I tried by what was posted earlier and put it into the menu list....as you will see.... What is there now...did in fact start to boot the windows OS...but I got the dreaded blue screen with a "INACCESSIBLE BOOT DEVICE" now remember.... The YAST partition is showing the 75 gig (Windowss) drive as two (2) different drives...one HDA and the HDA1...both have the same sector start 0 and end 9727 etc sumtin.... What yast is reporting, first two entries... DEV/HDA 74.5 gig, and ST380031 Drive start sector 0 end 9728 Just below it is DEV/HDA1 74.5 gig unknown, ntfs start 0 end 9227 Below that is the listing for the 20 gig where Linux resides Menu.lst # Modified by YaST2. Last modification on Thu Oct 13 17:43:09 UTC 2005 color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd1,1)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE LINUX 9.3 kernel (hd1,1)/boot/vmlinuz root=/dev/hdb2 vga=0x31a selinux=0 splash=silent apm=off acpi=off mce=off barrier=off ide=nodma idewait=50 i8042.nomux psmouse.proto=bare resume=/dev/hdb1 showopts initrd (hd1,1)/boot/initrd ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy root (fd0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- SUSE LINUX 9.3 kernel (hd1,1)/boot/vmlinuz root=/dev/hdb2 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off nosmp noapic maxcpus=0 3 initrd (hd1,1)/boot/initrd ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows root (hd0,0) makeactive chainloader +1 |
Just quickly the HDA and HDA1 is quite simple.
HDA is a description of the first hardrive in your machine. Included in that drive are the partitions starting at HDA1. If you have only one partition that completely fills the drive like a default Windows install does then you would still have hda and hda1. I personally don't think you need the makeactive command for windows. |
Quote:
Damm I am a noob about this! grrrrrrrrrrrrrrrr lol |
I got on a friends laptop that is dual booting windows xp and linux.
this is the code that boots windows xp Code:
title Microsoft Windows XP Professional |
I think you mentioned Win2K.
For windows you need to have rootnoverify not just root. |
Yeah I started googling around incase my last post didn't get it for him. but plain old root is working for my friend.
well if my last post doesn't work i guess try rootnoverify instead of root. |
It might be that XP is not as finicky as Win2K. I have Win2K dual booted and I had to have rootnoverify. I will see if I can find the documentation I used.
|
OK, I found this;
"rootnoverify is just like a standard grub root command except that it doesn't attempt to mount /dev/hda1, which would cause all sorts of havoc in Windows." Once the chainloader line executes it hands off to the windows boot sequence. Do you still have boot.ini in the root of your C:\ drive? |
All times are GMT -5. The time now is 06:39 AM. |