Click to See Complete Forum and Search --> : win 98 doesnd boot :(
sjoerdmin
08-13-2003, 01:23 PM
Hey,
i know, there many posts about this subject but it just confuses:confused: me more and more...
I have installed rh9 om my primery drive and win98 on my secundary.
I've installed win98 first and rh second.
When i come in the boot menu form grub and i select 'Windows 98' than there is this message:
Booting 'Windows 98'
rootnoverify (hd1,0)
chainloader +1
and my pc just freez
I hope anyone can or will help me
and yes, i'm a newbie to Linux
grtzz, Sjoerd
graydon
08-13-2003, 01:49 PM
Can u post your relevant windows 98 section from your grub.conf
sjoerdmin
08-13-2003, 02:27 PM
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-
root (hd0,0)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ hdd=ide-scsi
initrd /initrd-2.4.20-8.img
title Windows 98
rootnoverify (hd1,0)
chainloader +1
grtzz, Sjoerd
mdwatts
08-13-2003, 04:18 PM
Here are the JL forum search results for 'grub windows second drive' (http://justlinux.com/forum/search.php?s=&action=showresults&searchid=710059&sortby=lastpost&sortorder=descending) of which many of them will suggest you add the required 'map' commands
title Windows 98
map (hd0, hd1)
map (hd1, hd0)
rootnoverify (hd1,0)
chainloader +1
So you Grub config should be
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-
root (hd0,0)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ hdd=ide-scsi
initrd /initrd-2.4.20-8.img
title Windows 98
map (hd0, hd1)
map (hd1, hd0)
rootnoverify (hd1,0)
chainloader +1
win 98 doesnd boot :( And you find this to be a bad thing? :confused:
:p
mdwatts is right- Windows can be picky about where it is installed. The "map" directive fools it into thinking it's on the Primary Master (C: ) drive.
mdwatts
08-13-2003, 05:09 PM
Originally posted by DMR
And you find this to be a bad thing? :confused:
:eek: :eek: :eek:
Blasphemy !!!
We'll have to take that Window Security Course diploma back I'm afraid David. :(
:D
Think of all the *cough* beer you could have bought instead of wasting the money on a MS related course. :rolleyes:
plainzwalker
08-13-2003, 05:34 PM
okay..im having the same problems, but with RH8 and XP... i tried the one above but it gave me a bad device error... here is what my grub.conf says:
default=0
timeout=10
splashimage=(hd0,6)/grub/splash.xpm.gz
title red hat linux (2.4.18-14)
root (hd0,6)
kernal .vmlinuz-2.4.18-14 ro root=LABEL=/ hdb=ide-scsi
initrd /initrd-2.4.18-14.img
title Dos
rootnoverify (hd0,4)
chainload +1
I tried adding the map (hd0, hd1) tags but it didnt work..any help would be greatly appreciated.. I'm trying to learn linux, but I still need windows for the time being to do projects for work..
Thanks
plainzwalker,
Your drive/partition configuration differs from that of the original poster, so the hd0/hd1 mappings won't work for your setup.
1. Please post the specifics of your drive setup, including an exact description of your partition setup.
2. Tell us exactly what the errors you're getting are.
Also, that "chainload +1" entry should be "chainloader +1" instead.
hard candy
08-13-2003, 05:46 PM
I think you need to point the chainloader in the right direction:
Try this:
title=Win98
root (hd1,0)
chainloader (hd1,0)+1
It works on my system.
plainzwalker
08-14-2003, 02:50 AM
okay, i hope this will make sense...but I have 2 hard drives.
The first one (/dev/hda) is broken into 6 partions.
hda5 and hda6 are ntfs
hda7, hda8 and hda9 are ext3
hda10 is linux swap
second (/dev/hdc) has two partitions
hdc1 is fat
hdc2 is extended/ntfs
i hope that is what you need...im thinking its a lil wierd to be seeing them out of order, but i guess its how i did the partitions with partition magic.
thank you again.
jeff
sjoerdmin
08-14-2003, 03:31 AM
the map thing, doesn'd work here, but when i tried to point the chainloader he says this:
Booting 'Windows 98'
root (hd1,0)
Filesystem is fat, partition type is 0xc
chainloader (hd1,0)+1
whan can be the problem, the patition:confused:
grtzz, Sjoerd
hard candy
08-14-2003, 06:07 AM
Is it just sitting there with a dark screen?
sjoerdmin
08-14-2003, 07:03 AM
yes
grtzz, Sjoerd
hard candy
08-14-2003, 07:12 AM
I believe the partition is messed up. Mine shows a Win98 splash screen then the same message and then boots into windows. Try a repair install with the win98 cd.
mdwatts
08-14-2003, 08:57 AM
Originally posted by sjoerdmin
the map thing, doesn'd work here, but when i tried to point the chainloader he says this:
Booting 'Windows 98'
root (hd1,0)
Filesystem is fat, partition type is 0xc
chainloader (hd1,0)+1
whan can be the problem, the patition:confused:
grtzz, Sjoerd
Did you make the changes exactly as I specified?
title Windows 98
map (hd0, hd1)
map (hd1, hd0)
rootnoverify (hd1,0)
chainloader +1
and you have
(hd0) /dev/hda
(hd1) /dev/hdb
in /boot/grub/device.map?
If that doesn't work, then I would suspect there is a problem with the fat32 partition as hard candy posted.
sjoerdmin
08-14-2003, 09:19 AM
i redid the patitions on my second (windows) drive, and i've re-installed windows.
When i tried the map thing again hes says:
Booting 'Windows 98'
map (hd0,hd1)
Error 11: Unrecognized device string
Press any key to continue...
and when i tried this:
title Windows 98
root (hd1,0)
chainloader (hd1,0)+1
he says:
Booting 'Windows 98'
root (hd1,0)
Filesystem type is fat, partition type 0xc
chainloader (hd1,0)+1
and he freez
is maybe a combination of those 2 posseble?
And i've checked device.map and it says:
(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/hdb
grtzz, Sjoerd
mdwatts
08-14-2003, 10:47 AM
Try exactly as I posted including the spaces.
title Windows 98
map (hd0, hd1)
map (hd1, hd0)
rootnoverify (hd1,0)
chainloader +1
If Win98 is on the first primary partition of the second (hdb) drive and that still does not work, there must be something wrong with the Win98 bootloader (installed in the Win98 partition).
hard candy
08-14-2003, 11:05 AM
I was reading and ran across an idea- try re-installing grub, then:
#grub
grub> root (hd0,0) (your boot partition)
grub> setup (hd0) (where the MBR is located)
grub> quit
Try it with your current grub.conf file.