Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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
root (hd0,0)
makeactive
chainloader +1
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
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd1,5)
# kernel /boot/vmlinuz-version ro root=/dev/hda6
# initrd /boot/initrd-version.img
#boot=/dev/hdb
color white/black white/red
default=1
timeout=15
#splashimage=(hd1,5)/boot/grub/splash.xpm.gz
password --md5 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
title Fedora Core (2.6.12-1.1372_FC3)
root (hd1,5)
kernel /boot/vmlinuz-2.6.12-1.1372_FC3 ro root=LABEL=/ rhgb quiet vga=788 selinux=0
initrd /boot/initrd-2.6.12-1.1372_FC3.img
title Fedora Core (2.6.11.2)
root (hd1,5)
kernel /boot/vmlinuz-2.6.11.2 ro root=LABEL=/ rhgb quiet vga=788 selinux=0
initrd /boot/initrd-2.6.11.2.img
title Fedora Core (2.6.10-1.766_FC3)
root (hd1,5)
kernel /boot/vmlinuz-2.6.10-1.766_FC3 ro root=LABEL=/ quiet vga=788
initrd /boot/initrd-2.6.10-1.766_FC3.img
title Fedora Core (2.6.9-1.667)
root (hd1,5)
kernel /boot/vmlinuz-2.6.9-1.667 ro root=LABEL=/ rhgb quiet vga=788
initrd /boot/initrd-2.6.9-1.667.img
title Windows 2000
rootnoverify (hd0,0)
chainloader +1
Don't worry about the extra Fedora Cores, I like to have a couple of other working boots incase I stuff up my main one, especially when installing a new kernel. Mostly I will use just the 2nd Fedora and the Windows 2000.
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.
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.
Originally posted by Kerrysl 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.
Then what casued the blue screen and the "INACCESSABLE BOOT DEVICE ISSUE?"
Damm I am a noob about this! grrrrrrrrrrrrrrrr lol
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?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.