The first four partitions are:
sda1 = (hd0,0) = compaq utility partition —> is that right?
sda2 = (hd0,1) = where you installed opensuse
sda3 = (hd0,2) = a windows partition ----> what’s on it?
sda4 = (hd0,3) = a windows partition → what’s on it?
Please answer those three questions and also this one: Windows nearly always comes on a partitin before Linux because Compaq company install it first in the factory. How did it come about that Suse is on the drive in a partition that comes before windows?
sda1- 67.3GB windows C drive(Windows Partition NTFS)
sda2- 9.7GB / partion (Linux Native ext3)
sda4- 5.3GB windows E drive (Recovery Partition NTFS)
sda3- 29.3GB extended partition which comprises of :
sda5- 21.4GB windows D drive(NTFS Partition)
sda6- 1.019GB swap partition (Linux swap)
sda7- 3.8GB unallocated linux native
sda8- 2.9GB /home (Linux Native )
My laptop came from factory with two partions: 107GB windows boot partion or C drive and 5.3 GB recovery drive .Now this will sound messy:
I first divided the 100 GB partion into 67.3GB (C drive)and 40GB partition
which was further split into 29.3 GB and 9.7GB partition.
From the 29.3 GB I first installed opensuse on 8GB space which resulted in
21.3GB(Windows - sda5)and 8GB linux partition and later i found that was not enough space for linux and I should increase it so the 9.7GB became my root and 8GB was split into 1.019GB(swap) ; 2.9GB( /home ) ;3.8GB (unallocated linux partition).My laptop used to run Opensuse-vista dual boot with this configuration too but recently I found the problem when I needed to reinstall grub.
All these developed because I installed suse a lot of times trying different things but it did not work.
In my experience with dual-boot, it works perfectly only if we have all the windows partitions at the top level of the HDD.
In your case sda2 is a linux partition, which is what confuses windows.
An ideal partitioning for dual-boot would be:
sda2-ntfs (for all your personal files)
You may have to rearrange all your partitions once again using GParted/builtin opensuse partitioning utility.
OK it’s vista – First you identify which partition has these two filesystem pieces on it: the file “bootmgr” and the directory “boot”. You can discover that from openSUSE by mounting the windows partitions and looking at the contents from Nautilus/Konqueror/Dolphin. Lets suppose it’s sdaX [where you’ve gotta find out what X is (probably 2)]. Then subtract 1 from X to get y (e.g. if it’s sda2 then Y is 1). That makes the Grub designation for the vista partition (hd0,Y).
Then edit the file menu.lst located at /boot/grub/menu.lst and change one of the windows entries to this:
###Don’t change this comment - YaST2 identifier: Original name: windows###
You need special privilege to edit menu.lst: open the file for editing with like this in KDE:
Thank you very much!Windows is booting but linux is not boot without giving the parameter apm=off noapic which I found out from failsafe booting and straight after booting a sorry dialog came telling me that hard disk is failing.What should about that.
Sir I am really confused because that dialog did not appeared again in my next boot . Details which I could make out was due to ceratin increase in internal temperature of my laptop it was showing in the dialog.
One more thing I want to ask you that most often I do not shutdown my Windows and just put it in the hibernation but with the hibernation mode in windows when i am using linux automatic mounting of windows partitons and other ntfs partitions fail and at the same time when windows is shutdown automatic mounting occurs.
I can’t help with grub, I have my own problems in that area, but your automounting problem is probably due to the way that Windows handles Startup Shutdown.
When Windows starts up, it sets a bit on the drive, commonly called the ‘dirty’ bit. When you shutdown Windows it clears this bit. During startup this bit is checked to determine whether Windows shutdown properly during the last boot, if not it will schedule a CHKDSK to determine that your disc is OK. During hibernate / resume this dirty bit is left set, now automount will fail on linux boot because it’s set.