Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
HI,
I have just installed SUSE 9.3 on the same hard drive as Windows XP. Linux boots fine, but when trying to boot windows it comes up with the blue screen of death.
the computer is an AMD Atthlon XP 3200+, with 512MB of RAM, 120GB SATA hard drive partitioned as follows: 100GB windows NTFS partition, 1GB linux swap partition and a 19GB linux native partition.
I'm new to linux and would appreciate any help you can give.
Does the blue screen have an error message on it? Usually, the famed blue screen of death has some sort of cryptic information on it.
check the windows settings in your bootloader's .conf file to make sure they're ok.
Cheers
[Edit] Your bootloader's conf file will either be /etc/grub.conf or /etc/lilo.conf You can use the command
$ less /etc/lilo.conf
to look at the file, and the [spacebar] and "b" to navigate within the file using the "less" program
The bootloader configuration in SUSE can be found in /boot/grub/menu.lst (contains the actual boot menu) and /etc/grub.conf (contains information about grub installation). Additionally, the output of the command 'fdisk -l' will help us to understand your partition structure.
Sorry for delay, I thought I was going to get an email to tell me that I had got a reply to my post but didn't.
When selecting windows logon I get first screen saying "we apologise for the inconvience, but windows did not start successfully. A recent hardware or software change might have caused this."
It does not matter what option I chose i.e. Safe Mode, Normal Mode, Last Known Good Config, etc, I always get the following blue screen:
A problem has been detected and windows has been shut down to pprevent damage to your computer... Technical info
STOP: 0x0000024 (0x00190203, 0x82F5A268, 0xC000102, 0x00000000)
fdisk -l gives partitions as follows:
disk /dev/sda 120GB
/dev/sda1 * 1 11751 7 HPFS/NTFS
/dev/sda2 11752 11878 82 Linux Swap/Solaris
/dev/sda3 11879 14592 83 Linux
Your configuration looks fine to me. I hope it has nothing to do with data corruption during the resize process. I think there is nothing you can do from the Linux side of your system. Maybe you can run some kind of repair function/filesystem check from your Windows boot CD? This will probably overwrite grub in the MBR, but it can easily be restored.
I've tried booting using the Windows XP CD, but it doesn't matter which option I try ie Safe mode, Normal mode or Recovery I get a message that Windows can't detect a hard drive.
Any help or suggestions would be greatly appreciated.
Originally posted by David245 I've tried booting using the Windows XP CD, but it doesn't matter which option I try ie Safe mode, Normal mode or Recovery I get a message that Windows can't detect a hard drive.
Any help or suggestions would be greatly appreciated.
You are not booting from your Windoze CD. The safe mode, normal and last good known configuration are options displayed when the last time Windoze tried to boot it failed (no big surprise :P)
Windows setup - the one you start after booting from CDRom can't detect your hard drive because it probably needs the SATA (you said you have a 120 GB HD) drivers wich you can find on the motherboard CD or on a floppy that came with the mobo.
Anyway, like somebody said earlier, this is a Win problem, it has nothing to do with your SUSE.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.