Hi everyone,

here's my problem. Installed SusE 9.3 and so far, so good...learning a lot and loving it even more...problem is, I can't boot to Windows XP. I've already gone though the mandatory sticky and have read other posts but can't seem to fix the problem.

When I turn on my computer, I get to the screen where I'm asked for the operating system I'd like to boot. No problem starting up SuSE, but when I select Windows, I get WinXPs splash screen and then an error. Can't recall exactly but it says something like:

xmt2002 program not found - skipping autocheck
autochk program not found - skipping autocheck

...and afterwards, a blue screen with giberish (or so I think).

I've done my homework and here's some background...


1. I'm using a laptop and only one hard drive .


2. This is how my partitions look like:
/dev/hda 29.7 GB IBM-DJSA-232 0 66143
/dev/hda1 19.5 GB Win95 FAT32 LBA 1088 44431
/dev/hda2 4.7 GB Extended 55568 66143
/dev/hda3 5.0 GB Linux native 44432 55567
/dev/hda4 501.4 MB Linux swap 0 1087
/dev/hda5 4.7 GB Win95 FAT32 LBA 55568 66143

(note that both of my Windows partitions are FAT32; I'm accesing them from Linux)

3. This is my /boot/grub/menu.lst

# Modified by YaST2. Last modification on Sun Sep 25 14:18:33 CST 2005

color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,2)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 9.3
kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 vga=0x314 selinux=0 splash=silent resume=/dev/hda4 showopts
initrd (hd0,2)/boot/initrd

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
root (hd0,0)
chainloader +1

###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 (hd0,2)/boot/vmlinuz root=/dev/hda3 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off nosmp noapic maxcpus=0 3
initrd (hd0,2)/boot/initrd

4. I followed this procedure exactly as instructed:

portal.suse.com/sdb/en/2004/05/fhassel_windows_not_booting91.html

but ended up with a prompt saying that there were no drivers to update. I was already using the latest version.

5. I also ran the fix mbr DOS command but messed up the MBR and couldn't start in either OS. Had to recover the Linux installation and I'm able to boot back to SuSE...but not Windows XP!

6. Finally, I tried to recover my Windows XP installation with the original CD but I'm asked for an administrator login and there's none!! I'm the only user to this laptop!! Couldn't get beyond that point.


Please help!! I'll try whatever you suggest!!

Thanks!!
foliva

Please...anyone?

Come on guys...your my only hope!

I give up...wiping my hard drive this weekend....going back to Windows. Wish I could say the dual booting was my only issue, but had some others. Linux is definitely not ready for prime time.

Hi foliva,

You know that there are lots of linux distros.You can try another one
and see if you're luckier with it. Saying linux is not ready from prime time
just because you could not set up a dual-boot is too easy.
Re-install windows first, than why not trying Mandriva (free version).
It is usually very good at settings partitions the way you want them and
handling dual-boot with xp.

cheers

...the wisdom of crowds.

Thanks for the suggestion. The problem with the dual boot was just one of many things I encountered throughtout my 2 week exposure to Linux. Printing, scanning, wireless, recording, OpenOffice, system performance, Wine, battery issues...I mean, I think I had them all (and that's just to name what's on top of my mind).

I'm no IT guy but I'd say I feel comfortable around computers and learning stuff....and here's my veredict...again...Linux is not ready for prime time. It's for the hobbist and not for the average user. I don't have the time.

I work for a company paying some 200 Windows/Office licenses. Our IT manager and the managing director were looking forward to my review on SuSE (as I can speak for the average user). Guess we'll continue to pay for those M$ licenses.

Going back to good ole Windows.

just as everyone using windows the first time has to learn some things, you have to learn using linux distros. if you have used windows for a long time, you expect it to be the same in linux, which is not - thank god for that!

when you alter something in the windows partition (by accessing it from linux), esp. in the boot files, windows might have problems booting. i see you have FAT32, which is ok, because with NTFS there are some problems to be expected, because the filesystem is secret to microsoft.
if you see the splash screen, then win.exe and boot.ini (and there brother and sister files) are fine, however, the programmes that are called then might have some fatal errors.
btw, changes in the MBR are always critical... in your GRUB lines, everything seems fine. however, it is akward, that your first part is not labelled with a number (hdaX is usually done with X an integer and with a windows partition 1 reserved for windows, as it cannot reside in anything other than the first primary partition).

I agree with you Unihiekka...I just didn't expect the learning curve to be that steep...again, I consider myself a little geekier than your average employee and had a hard time adjusting and finding solutions to my Linux-related problems. When tweaking Linux becomes "Windows friendly" (meaning, making the transition from Windows a no-brainer) I will maintain my veredict "not ready for prime time".

See you in two years.

(posted from Firefox using Windows XP).

For folvia:
I know how you feel about the issue. I believe to are correct in your opinion. Linux is becoming more splintered every day with different versions now over the hundred mark. It seems that Linux is becoming more complex also.
Each different version was started because someone had a problem with Linux. That is except for those who see only profit in Linux and not a community.
Many of the problems are because hardware vendors pander to M$ where they perceive the big bucks are located. So, some vendors, who must show a profit to exist, do not abstract out to the greater audience and provide support, as well as, the profit centers.
Your organization must also show a profit of sorts, go back to M$ and continue using that ware but do not forget that Linux is still here and marching on so be prepared, get started today. One day in the future, could be in a year, you will find that Linux has a place in your organization so get ready today -- you will find a programer who can modify/operate your edition of Linux to make it more robust -- you will say: we couldn't do this with M$ but now we are tooling along just fine with Linux -- we have made good contribution to a community who wants us, needs us, and is happy with us.
So, look at your hardwares, look at your softwares, observe your Informatio Needs and then contribute to the better good by using Linux when your ready. Thank you for your viewpoint.

Remember:
a journey begins with a single step
life is a day at a time

You got the source code !

Paul_E_T

Who made this stupid rule about not posting url's.
I guess you'll never know my solution to this issue because you've also thrown away the body of my post.

Ridiculous Rules. I'm not inclined to reform my careful directions again.
You might have warned me before I started the post.

Post #2 .. two can play this silly game.

Post #3, completely free of URL's.

vmguy:
If you plan to post URL's befor your 5. post, introduce a non-standard character into the address, e.g. http: //www.someserver.com
This rule should have been pointed out and explained to you in the forum rules. It's purpose is to prevent spam.

foliva:
My impression is that you are dealing with a Windows problem. This may have been caused by the resizing process during the installation of SUSE. But I don't think this is distro specific, like samael26 assumed. Partition resizing is always a risky operation! Before starting the Linux installation, it is recommended to run defrag and scandisk to ensure the drives integrity, but even then you are not 100% safe.

I guess the only solution is to reinstall Windows from scratch. You may try password recovery of your Windows system (which is possible with some Linux tools), but I am not sure if this will get you any further.