Linux install gone wrong

SPECS:
AMD 2800+
NF7-S MB v.1.1
1GB ram
ATI 9700 pro
NEC DVD-RW
Yamaha CD-RW

Primary Drive= Maxtor 200GB
C:\ windows xp 25GB (NTFS)
D:\ misc 55GB (NTFS)
E:\ misc 55GB (NTFS)
F:\ Linux 55GB
Slave Drive= Fireball 30GB
G:\ misc (NTFS)

Internet= ADSL, i.e. DHCP

Ok my first mistake was to install linux for the first time @ 0200. I have WIndows XP pro on my C: dirve and installed SUSE 9.1 pro on my F: (same hard drive). I goofed with the partitioning and now am not able to boot from Windows. Get a missing Hal.dll error. I am able to boot from Linux just fine and am able to access all my partitions. When I've tried to access the Windows partition from the boot disk (repair mode). It does not recognize the partitions any longer. Shows up as 135GB of unpartitioned space...

First question; How do I recover my Windows partitions? Without loosing my data.

Second; How do I fix the Windows boot?

Third; How do I set up the internet connection from the SUSE 9.1 install. I am currently using the SUSE 9.3 Live disk and it set everything up automatically. P.S. Knoppix is also able to recognize my internet connection.

Fourth; Should I continue to use SUSE or try something else. I had a copy of SUSE 9.1 pro eval DVD on hand and decided to try it. SHOULD HAVE READ ALL THE INSTRUCTIONS FIRST!!! My main concern is my wife. I'm tired of using Windows and want something that will be easy for her to use. She's not very computer savy, though she's a good learner. Any ideas/suggestions?

P.S. I tried doing a search for this issue and could find nothing, if it has already been covered, please post the thread link, thanks.

Do this:


Boot to linux and open a console. Go into superuser mode or login as root.

Type this command:


fdisk -l


(that's a lowercase L, not an i)

Also do this:


cat /etc/fstab

And paste that as well


And paste the output here. I want to see it.

Disk /dev/hda: 203.9 GB, 203928109056 bytes
255 heads, 63 sectors/track, 24792 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 2 3264 26210047+ f W95 Ext'd (LBA)
/dev/hda2 * 3265 10444 57673350 7 HPFS/NTFS
/dev/hda3 10445 17624 57673350 7 HPFS/NTFS
/dev/hda4 17625 24790 57560895 83 Linux
/dev/hda5 2 3264 26210016 7 HPFS/NTFS

Disk /dev/hdb: 30.0 GB, 30020272128 bytes
255 heads, 63 sectors/track, 3649 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 * 1 3648 29302528+ 7 HPFS/NTFS


/dev/root / iso9660 defaults 0 0
/dev/hdb1 /media/hdb1 auto noauto,user 0 0
/dev/hda2 /media/hda2 auto noauto,user 0 0
/dev/hda3 /media/hda3 auto noauto,user 0 0
/dev/hda5 /media/hda5 auto noauto,user 0 0
/dev/hda4 /media/hda4 auto noauto,user 0 0
/dev/hda1 /media/hda1 auto noauto,user 0 0

SuSE rendering Windows unbootable is a known issue caused by buggy parted used in many Linux distributions as the partitioning backend: http://portal.suse.com/sdb/en/2004/05/fhassel_windows_not_booting91.html

BTW, SuSE 9.3 FTP install and 9.2 DVD ISO image are available. You could try those newer and improved versions instead.

Just asking...such a thing can never happen with Suse 9.0, can it?
So, let's skip 9.1, right?

The bug only appeared in 9.1 of SuSE releases. 9.0 would be going back from 9.1, wouldn't it? Try 9.2 or 9.3 instead if your machine is fast enough.

@Nodsu
No, it wouldn't. Because I'm there. :D
But I had the chance to try 9.1 and I'm now glad that I passed it on.