From SuSE to Windows
I hope I don't give anyone a heartattack with the subject heading but I am trying to reboot a system that has both 7.1 and Windows installed. From a cold start I can select windows from the lilo menu and it starts okay. It will also start okay from a Windows restart. However, once I have SuSE up and running if I do a restart and select Windows from the lilo menu it consistently fails to boot with the message that HIMEM.SYS is missing. As this problem only occurs from a SuSE reboot and has only started happening since the system was upgraded from SuSE 7.0 to 7.1 I suspect that it has something to do with the SuSE/lilo configuration. The partitions are as follows: /dev/hda1 /boot ext2 (small boot partition, set as active) /dev/hda2 /windows vfat /dev/hda5 swap swap /dev/hda6 / reiserfs Does anyone have any ideas (apart from dumping windows completely which unfortunately is not an option)? TIA Eddie
HIMEM.SYS is missing. ~ Hmm . . . i got a load of that, and it pissed me off so bad, that i took off winders for permanent. a couple of remarks: my cpu is an AMD K6/2 which may aggravate the position. Winders uses calls to BIOS Linux does not use BIOS Dual boot is not an easy relationship .................... best wishes -- ____________ sent on Linux ___________
Thanks tabanna But as I stated in my original posting, removing windows is NOT an option. Eddie On Monday 23 April 2001 13:40, tabanna wrote:
HIMEM.SYS is missing.
~ Hmm . . . i got a load of that, and it pissed me off so bad, that i took off winders for permanent.
a couple of remarks:
my cpu is an AMD K6/2 which may aggravate the position. Winders uses calls to BIOS Linux does not use BIOS Dual boot is not an easy relationship ....................
best wishes
-- ____________ sent on Linux ___________
On Monday 23 April 2001 14:40, you wrote:
HIMEM.SYS is missing.
~ Hmm . . . i got a load of that, and it pissed me off so bad, that i took off winders for permanent.
a couple of remarks:
my cpu is an AMD K6/2 which may aggravate the position. Nope.. Both run fine here with both K6/2 and k6/3.
Winders uses calls to BIOS Linux does not use BIOS Dual boot is not an easy relationship Works fine here.
He just needs to make sure that his lilo.conf is correct, and re-run lilo again. Eddie, you might also remove that active setting on the /boot partition. That might the confusion that Windows is experiencing. Mike -- Powered by SuSE 7.1, Kernel 2.4.2 KDE2.1.1 For a great linux portal try http://www.freezer-burn.org
I think you main problem is that Winblows is very stingy and unfriendly and "must" be the 1st partion - always hda1. Remember that with dual boot system with Winblows you direct lilo to the MBR (master boot record) which is a DOS format. I have a dual boot sys and have had little or no problems (except since Linux can access and manipulate dos/win file systems you can screw up the window sys). My fstab looks like this: /dev/hdb3 / ext2 defaults 1 1 /dev/hdb1 /boot ext2 defalults 1 2 /dev/cdrom /cdrom auto ro, noauto, user, exec 0 0 devpts /dev/pts devpts defaults 0 0 /dev/fd0 /floppy auto noauto, user 0 0 /dev/hdb4 /opt ext2 defaults 1 2 proc /proc proc defaults 0 0 /dev/hda1 /windows/C vfat noauto, user 0 0 /dev/hda5 /windows/D vfat noauto, user 0 0 /dev/hda6 /windows/E vfat noauto, user 0 0 /dev/sda4 /zip auto noauto, user 0 0 dev/hdb2 swap swap defaults 0 2 And another note, it is my understanding that if your putting Linux on the same hard drive that Winblows is on it is best to put Linux on a Extended partition and any following ext2 partitions on logical partitions within that Extended partition (keeps every one happy - why I don't know). However, if your putting Linux on its own hard drive (the 2nd or 3rd, etc...) then you can build a Primary partition for Linux and then Extended and logicals within after that. Hope this helps. Curtis Rey On Monday 23 April 2001 07:20 am, Eddie Howson wrote:
I hope I don't give anyone a heartattack with the subject heading but I am trying to reboot a system that has both 7.1 and Windows installed. From a cold start I can select windows from the lilo menu and it starts okay. It will also start okay from a Windows restart. However, once I have SuSE up and running if I do a restart and select Windows from the lilo menu it consistently fails to boot with the message that HIMEM.SYS is missing. As this problem only occurs from a SuSE reboot and has only started happening since the system was upgraded from SuSE 7.0 to 7.1 I suspect that it has something to do with the SuSE/lilo configuration.
The partitions are as follows: /dev/hda1 /boot ext2 (small boot partition, set as active) /dev/hda2 /windows vfat /dev/hda5 swap swap /dev/hda6 / reiserfs
Does anyone have any ideas (apart from dumping windows completely which unfortunately is not an option)?
TIA
Eddie
First let me say a big thanks to all those who offered suggestions and tried to help. For those who might be interested I will list some extra pointers and state the final outcome. 1. The machine is not mine, therefore I did not have the option to remove Windows or play about with the partitions. 2. It was working fine with 7.0 until someone did an upgrade to 7.1 3. My machine works fine with 7.1 and I have a similar partition setup WRT Windows. (However, I have multiple ext2 partitions; none with reiserfs). Conclusion: The owner has reclaimed the machine and decided to live with the problem. Eddie On Monday 23 April 2001 13:20, you wrote:
I hope I don't give anyone a heartattack with the subject heading but I am trying to reboot a system that has both 7.1 and Windows installed. From a cold start I can select windows from the lilo menu and it starts okay. It will also start okay from a Windows restart. However, once I have SuSE up and running if I do a restart and select Windows from the lilo menu it consistently fails to boot with the message that HIMEM.SYS is missing. As this problem only occurs from a SuSE reboot and has only started happening since the system was upgraded from SuSE 7.0 to 7.1 I suspect that it has something to do with the SuSE/lilo configuration.
The partitions are as follows: /dev/hda1 /boot ext2 (small boot partition, set as active) /dev/hda2 /windows vfat /dev/hda5 swap swap /dev/hda6 / reiserfs
Does anyone have any ideas (apart from dumping windows completely which unfortunately is not an option)?
TIA
Eddie
participants (4)
-
Curtis Rey -
Eddie Howson -
Mike -
tabanna