Hmmm

**Flatline** · 05-26-2005

Here is a working Windows entry from one of my comps:

Code:

###Don't change this comment - YaST2 identifier&#58; Original name&#58; windows###
title Windows
    root &#40;hd0,0&#41;
    chainloader +1

That comp doesn't even have a Windows entry in /etc/fstab; since Windows is chainloaded, it shouldn't be a requirement.

**psic** · 05-26-2005

Try what Budman suggested, to switch the harddrives so windows is on the master one. Then edit the grub settings. You will not need fstab for booting anything, you will need it later if you will want to browse your windows files from linux.

**Vlad_Einhorn** · 05-27-2005

thanks you guys. i fixed it.
this is what i did:
i used the linux installation to delete the linux partition i made the master hd(20g) a fat32 system and then used windows rescue cd to copy all the information from the NTFS format to the FAT32 i then formatted my slave(40g) and partitioned it into two 20g partitions. i made one an NTFS for windows and left the other as FREESPACE. I installed linux ubuntu on the free space and now that windoes is on a fat32 partition grub recognised it. for some reason when windows was on NTFS it refused to see it! anyway i didn't want to take the chance and let grub overwrite the MBR and installed grub onto a normal floopy disk. now i have them both working fine.
thanks for all your help people.

**borromini** · 05-27-2005

Glad to see you fixed it... I'm sorry I didn't read this thread earlier, but Windows still needs a primary partition to boot from (Windows itself can be installed on a logical partition, but it still needs a primary one for its bootloader and boot.ini and stuff like that). So next time you install Linux, make sure you don't delete the primary partition on which Windows stores these files...

**Vlad_Einhorn** · 05-27-2005

alright. thanks mate

EDIT: Fdisk /mbr

worked like a charm for me.

**SzymonDrejewicz** · 06-22-2005

If you have Linux on hda1 and Windows on hdb1 (in other words Master is Linux and Slave is Windows) you can setup GRUB as below:

Code:

title           Microsoft Windows
map &#40;hd1&#41; &#40;hd0&#41;
map &#40;hd0&#41; &#40;hd1&#41;
rootnoverify &#40;hd1,0&#41;
savedefault
makeactive
chainloader     +1

Settings in fstab are not connected with booting systems, it means that you don't need to write anything to /etc/fstab to setup dual boot. Somtimes it's better to read manuals than repartitioning disks

greetings

**mentalabilities** · 10-30-2005

Iv never heard of a problem like this before.

Vlad_Einhorn

email me or message me on yahoo and i might be able to help

Peace

Thread Tools

Display

:-)

Hmmm

Posting Permissions