Re: [SLE] Dual-Boot: HIMEM.SYS corrupted after 7.2 update
Hello,
This could be semi-OT, but I hope some of our list members with dual boot
experience can help me.
I have a Sony Vaio PCG-C1XS that I have fixed up to dual boot Windows98 a nd SuSE Linux. Two weeks ago I updated the SuSE Linux side from 7.0 to 7.2.
Update seemed to go pretty well, and afterwards I booted into the linux s ide. Looked pretty good, so I shut down and went to bed. (Yep, another late night update ;-) Yesterday, I needed to boot into Windows to do somethin g for my wife, but after the Windows98 splash screen came up, it reverted t o the DOS screen and showed the error message that there was insufficient memory. I was prompted to hit any key, and when I did,
t could not find \WINDOWS\HIMEM.SYS. I confirmed that the file is there, b ut when I open it using the editor, it appears to be corrupted. It starts w ith about 40 lines of garbage characters that look like what a binary file lo oks like when you open it in vi. After the garbage, it looks
was overwritten by system error output.
As I see it, I could fix this one of two ways - rewrite
e or use the recovery CD to restore the drive. I moved to NetBSD and then Lin ux from a Mac OS background, so I don't have a lot of experience fine-tuning
DOS/Windows configuration files. Rewriting HIMEM.SYS would be a bit of a n adventure, but if someone here knows what I should put in
ld probably do it.
I hesitate to use the recovery CD, because I suspect it will remove my li nux partition as well as everything I put on the notebook on
in the time I have been using it. Is that the case, or will it just restore the system files that are there?
As I mentioned, this may be somewhat off-topic, since I am asking more fo r Windows info than I am for linux info, but I trust you more to help me preserve my linux system. I would appreciate whatever help you could off er.
TIA, Sean -- Theo. Sean Schulze theo.schulze@myokay.net
"[T]he key to maintaining leadership in the economy and
at are about to emerge is likely to be the social position of knowledge professionals and social acceptance of their values." -- Peter Drucker
-- To unsubscribe send e-mail to suse-linux-e- unsubscribe@suse.com For additional commands send e-mail to suse-linux-e- help@suse.com Also check the FAQ at http://www.suse.com/support/faq and
Ok, My recommendation is to completely replace himem.sys Have you not got another copy of it in "c:\" instead of "c:\windows"??? Incidentally you cannot "re-write" himem.sys.... Your only option is to replace it. You'll probably find one on your Win98 bootdisk floppy (you know the one which you made.....you did make one, didn't you?? :-)) --Thomas Adam the system said i like HIMEM.SYS the HIMEM.SYS fil the file, I cou the Windows side the technology th the
archives at http://lists.suse.com
Thomas Adam
"The Linux Weekend Mechanic" --
On Monday 08 October 2001 11:23, THOMAS ADAM wrote:
Ok,
My recommendation is to completely replace himem.sys
Have you not got another copy of it in "c:\" instead of "c:\windows"???
Using find from the linux side, I found a copy of himem.sys in the C:\sonysys\vsrcdfd\img\sys directory and copied it over. Now Windows boots (your call on whether that is good or bad :-), but I don't know that it was the copy of himem.sys that fixed it or not. While trying to find an answer to this problem, I also discovered that something called patch_lilo_conf added a line to my "other" parameters in /etc/lilo.conf so that it looked like this: other = /dev/hda1 optional # automatically added by patch_lilo_conf label = win98 loader = /boot/chain.b table = /dev/hda According to man lilo.conf, that "optional" means "Omit the image if it is not available at map creation time." I commented that line out, ran /sbin/lilo and rebooted, and Windows came up fine. So, I don't know if it was a corrupted himem.sys or something done automatically "for" me by patch_lilo_conf. Guess I could uncomment it again and try it... Oh, well. Now it is off to fix the changes the update made to my /etc/fstab. Where I previously had /dev/fd0 mounted to /floppy and /dev/hde mounted to /cdrom, I now see that they have been changed to mount to /media/floppy and /media/cdrom, respectively. I'll have to change the symlinks in my root directory as well, since /floppy is now a symlink to /media/floppy and /cdrom is now...well you get the picture. [snip]
Thomas Adam "The Linux Weekend Mechanic" --
A Student at the "Southampton Institute", Southampton, Hants, ENGLAND
Thanks, Sean -- Theo. Sean Schulze theo.schulze@myokay.net "[T]he key to maintaining leadership in the economy and the technology that are about to emerge is likely to be the social position of knowledge professionals and social acceptance of their values." -- Peter Drucker
participants (2)
-
Theo. Sean Schulze
-
THOMAS ADAM