![](https://seccdn.libravatar.org/avatar/57c85b03a905b5d466ba6b64fed5cf38.jpg?s=120&d=mm&r=g)
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