10.3 install screws up W98SE dual boot

English Install/Boot/Login
1

i put off updating my 10.1 dual boot because it might be a pain, and it is>:(.
did install (not upgrade)of 10.3 it seems ok but my W98SE boot says can’t control A20 and can’t find HIMEM.sys.
after hours of searching your forum found a fix for A20 problem which suggests a mod to config.sys file but that file is now gone!!
and NO warnings!!!
my HIMEM is in the /windows so why the error?
saw a post with same problem but no fix.
this is most disapointing since i spent hours trying to read up how to upgrade and found little other than “do install, not upgrade”.
there are many posts about grub yet no warnings or easy to find tutorial to refer to while installing.
during my install it proposed 4maybe 5 more partitions. seemed ridiculous,saw one (2?)was only 7MB so i deleted it. here’s my
sudo /sbin/fdisk -l
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xdd7667d7
Device Boot Start End Blocks Id System
/dev/sda1 1 3270 26266243+ c W95 FAT32 (LBA)
/dev/sda2 3271 9729 51881917+ f W95 Ext’d (LBA)
/dev/sda5 3271 3361 730926 82 Linux swap / Solaris
/dev/sda6 3362 5914 20506941 83 Linux
/dev/sda7 5915 9729 30643956 83 Linux
sudo cat /boot/grub/menu.lst

Modified by YaST2. Last modification on Thu Aug 14 04:18:18 UTC 2008

gfxmenu (hd0,5)/boot/message
##YaST - activate
###Don’t change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.3
root (hd0,5)
kernel /boot/vmlinuz-2.6.22.5-31-default root=/dev/disk/by-id/scsi-SATA_WDC_WD800JB-00EWD-WCAHL5404774-part6 vga=0x317 resume=/dev/sda5 splash=silent showopts
initrd /boot/initrd-2.6.22.5-31-default
###Don’t change this comment - YaST2 identifier: Original name: windows###
title Windows
rootnoverify (hd0,5)
chainloader (hd0,0)+1
###Don’t change this comment - YaST2 identifier: Original name: floppy###
title Floppy
rootnoverify (hd0,5)
chainloader (fd0)+1
###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – openSUSE 10.3
root (hd0,5)
kernel /boot/vmlinuz-2.6.22.5-31-default root=/dev/disk/by-id/scsi-SATA_WDC_WD800JB-00EWD-WCAHL5404774-part6 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3
initrd /boot/initrd-2.6.22.5-31-default

Please help! i’m an elec engineer and this is too hard!! W98SE was so easy.
i did media check of LXF dvd prior to start.
did edit during grub to rootnoverify(hd0,0), no help, next time back to 0,5.
thanks
trying to use less win

2

How did you install it in the place of suse10
Suse 11 intend to let suse10 untouched
So you have to tell it to use the space occupied by suse10 this can be done in customized install
As hymem.sys as far as memory goes it is in autoexec.bat or config.sys.
If it is autoexec.bat than it runs as the first thing
in windows
dobby9

3

hi, all i recall is install not upgrade the 10.1 after reading other posts here.
there needs to be a “sticky” to explain!
i can see my himem.sys file from linux and with a W98 boot but when booting says can’t find.
thnx

4

Linux would have no effect in your paths or files on the DOS environment.

Please copy paste the results of your config.sys here.

5

hi, as i said, my config.sys is gone now.
some other file must be calling for himem.sys, but can’t find but i see it from 10.3 or 98 boot floppy.
how do i uninstall 10.3and fix my Win?
thnx

6

1.Did you save your critical data from Win98 before you began?

  1. You had 2 Win partitions. Was one used as a dump for cross filing from each OS? Something was fractured by the 10.3 install and it may be that some part of your Win98 install was scattered to the other Win partition and now was overwritten. That is unlikely but something is amiss.

  2. A missing win 98 file should be able to retrieved off the Win CD? If the files can be seen from SUSE, make a copy of the file on a floppy and stuff it in Win 98.

  3. Does Win98 actually boot or does it stall?

  4. Is 10.3 booting or does nothing boot. Let’s pretend that “boot” means the desktop eventually appears. Will 10.3 safeboot to console?

Now, as to difficulty, I don’t know. You had a successful dual-boot scheme, including partitions. It should have been simple task to tell 10.3 to install to the formatted partitions formerly containing the earlier SUSE. You simply instruct the installer reformat the 10.1 partitions with the correct mount info and 10.3 installs into those partitions.

During the install the installer shows the intended GRUB scenario and all one does is click on it and edit if necessary.

I am not being deliberately condescending as I know you are frustrated. But, the situation can be remedied perhaps without reinstall. You might also retrieve any missing Win98 files from the Microsoft Knowledge Base or Support.

So, what boots and what doesn’t?

7

Are you getting the grub boot loader? And the option to boot windows?

I see the /boot/grub/menu.list
has an entry for windows
but it look incorrect

You seem to have to win partn’s
/dev/sda1 1 3270 26266243+ c W95 FAT32 (LBA)
/dev/sda2 3271 9729 51881917+ f W95 Ext’d (LBA)

but grub points like this:

title Windows
rootnoverify (hd0,5)
chainloader (hd0,0)+1

I’m thinking it should be
title Windows
rootnoverify (hd0,0)
chainloader (hd0,0)+1

8

thanx all for responding,
ad: 1.saved most, but did not do full backup
2. suse made 2nd win partition, seems typical.
3.can see file but did del/recopy-no change
4. win gets to missing himem message, ctrl+alt+del
5. 10.3 boots/runs good
as i said, yast proposed 4(5?) more partitions, no obvious way to tell installer to reuse.
did use yast again and noticed it says grub is placed in a NOT recommended place -mbr?

cat: am getting grub screen 10.3/win choice
yes you are right. i did an edit during grub and tried that-no change. will edit file next
i did notice several other posts in jan08 for exactly same problem but no fix: search “himem” apparently was problem with 10.3

9

OK - 10.3 is booting and running correctly. GRUB is fine and giving a menu at boot.

Now - the issue of data. If there is nothing critical missing from what you saved, you can do a reinstall of Win98. First, you would absolutely bakup/save a copy of menu.lst for GRUB.

The problem is with the BIOS and/or Win98. I also Googled himem.sys and got a list of stuff, including this. This may be useless since you say config.sys is kaput but look here:HIMEM.SYS

In the BIOS, make sure that everything is as it was before the new install of 10.3. I haven’t run Win98 for a very long time but it was on Pent IIs and I always changed a couple things in the BIOS in order to run Linux. There was a “switch” that told the BIOS that a Linux system would be running. I am sorry I can’t be more specific but at my age…

I do remember with certainty that I used to experiment with the various Linux of that day and Win98 and on more than one occasion, I installed Win98 after Linux was on the machine, of course with the proviso that the first partition was for Win98, etc. And, I do remember clearly that Win98 “saw” the Linux installation and I booted it from the Win98 bootloader. I also was doing it the other way and using LiLO.

What I am saying is this:

If you can’t repair the Win98 installation with BIOS tweaks or via an article from Google as above, you are going to have to reinstall Win98. The partition is there in the proper place, etc.

If Win98 doesn’t see the Linux install and offer to boot it or you don’t want to edit the Win98 bootloader, get Win98 running properly first.

Then, you can boot into 10.3 with the CD/DVD and edit/reinstall GRUB.

So, essentially, you are still where you where when you wrote the post. I am sorry I couldn’t offer a real solution. Also, when you reinstall Win98, I think you will be unable to get all the security updates from over the years it was actively supported. Thus, it might be wise not to use Win98 on internet.

You can also see here about himem.sys -Himem.sys missing or corrupt Normally, one has a boot floppy for Win98 (I vaguely remember) that will restore the missing files. When I was running Win 98, most Linux distros would break everything and there was a lot of extra work.

So, if you are going to reinstall Win98, 10.3 is working properly so you can just leave it as is and edit/reinstall the GRUB after Win98 is running good.

Another article: Himem.sys missing or corrupt Also here - dual boot win98 & linux - Google Search

This one mentions the Win bootloader from Debian -Dual Boot Windows and Linux Grub - Debian Linux with Windows 98 ME NT 2000 and XP

10

@roman6

If it can help you to recreate your lost CONFIG.SYS (I’m too using Win98SE), here is the content of mine :


DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE
device=C:\WINDOWS\COMMAND\display.sys con=(ega,,1)
Country=033,850,C:\WINDOWS\COMMAND\country.sys
11

(This is a follow-up of a thread I started here :
Windows 98 failed to boot very early (Grub, OpenSuse 11.0) - openSUSE Forums )

Ok.
I tried to manually edit (because I don’t think Yast would allow this) :


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

to


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

in /boot/grub/menu.lst
but with no changes (boot still failed)

I also tried to add the option “/A20CONTROL:OFF” to the HIMEM.SYS line in the CONFIG.SYS file, but it is WORST: the computer hang and I had to press the reset button.

What could have been changed in the BIOS by the recent OpenSuse Linux ?

Or

You might restore the Win98 MBR and then boot SUSE from the Winloader.

So the MBR could have been modified during the 11.0 installation ? Is there a way I can restore it ? (I mean at least for the Windows partition; I understand that the newer installation might have altered my previous installation (in the MBR). But how to recover it as it was - or make it working - for Win 98 ?)

12

So the MBR could have been modified during the 11.0 installation ?
YES

Is there a way I can restore it ?
Use the win98 install cd

Then when win98 is working. Use the suse dvd to boot and repair grub.

13

thanks to all:
i went back into yast because it said grub was in a bad spot: MBR. it let me restore mbr and i chose to put it in /boot- still no change.
then i edited /boot/grub/menu.lst to hd0,0- no change.
can we get an expert to help since we now have another incident plus the 3 i saw back in jan08?

14

Thanks.
But I’m a bit scared to do such a thing.
I don’t have a bootable OpenSuse 11.0 DVD (It is installed on a dedicated HD partition).

What if I trash the MBR or something in Grub ? (I fear I won’t be able to boot anything.)

Is there something else I should do before trying that (so that at least I will still be able to boot OpenSuse 11.0) ?

15

This is getting confusing - we seem to have 2 of you looking for answers.
AmigaPhil and roman6

AmigaPhil: What exactly is your problem.
You say you have suse11, so how did you install it?

roman6: As you seem to think you have corrupted part of your win98 install, why not re-install over the top, which is a feature of win98 as I recall. Then reboot with the suse dvd to setup grub. It’s really not that complicated. Though I have to say, you seem to be in such a mess, I’m inclined to suggest you wipe the disc clean and start fresh.

16

Hi
Also can either of you check that the boot flag is set to the win98
partition.

–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 12:37, 2 users, load average: 0.21, 0.16, 0.20
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12

17

Roman6 -

98SE has a repair feature as mentioned in post above that allows you to keep your settings and data.

BOTH of you are likely going to have to “repair” 98SE, letting it do its magic in the MBR. 98SE does not have a boot loader but the code it places in the MBR reaches out and “touches” the first active partition where 98SE should be residing.

As several of us have suggested, you first repair the 98SE install and then you can determine exactly how you want to bootload the other stuff, including 98SE.

This nightmare scenario is slowly returning to memory. I always used LiLO during that era because it worked. It was manual but the Mandrake of that day had Partition Magic installed and these little adventures were fairly routine.

If you cannot boot into 98SE, then you decide if you need the data in 98SE. Just that simple. But, as we have already said, 98SE has the reinstall, change no data/repair feature. And, yes, it may not work as it is supposed to.

So, first to repair 98SE, if that is what you want. You can leave the SUSE in there, it isn’t disturbing anything. After 98SE is fixed, you can determine how to boot everything.

I think I read that OpenSUSE is dropping LiLO with next release. However, LiLO or GRUB or GAG or even the Win98SE, you must figure it out.

I used install Linux first and then install 98SE afterward and 98SE would recognize and boot the Linux install, with the caveat that the MBR belongs to 98SE and the first partition.

So, repair 98SE, then figure the rest.

AmigaPhil - copy your 98SE data to a safe place, as in a FAT32 partition where you can retireve it and take the repair plunge.

There is doubtless and answer to this mess out there but might take hours to stumble upon it in search. As I was looking, I realized that I used LiLO, not GRUB as GRUB was just a notion then. And, There was blue screens and the dreaded “l” that showed instead of LiLO’s menu.

As I remember it, one kept boot floppies for 98SE cause it broke so often. And on those boot floppies were the very items which you both are missing. Which will do no good until the MBR thing is cleared up. And, one also kept boot floppies created by whatever virus program was installed. What a mess of floppies!

So, there it is.

Now, I also want to commend the members of this board for not offering up abusing statements about “Windoze”. There are some Linux forums (distros also) that would have already degenerated into name calling.

And, again, unless you can find a Windows guru here, if you want to continue to find an answer other than 'repair" option by reinstall without data destruction, you will find one quicker at Microsoft support/knowledge base or a Windows forum.

A note: When GRUB or SUSE repairs a MBR, they use different code values than would Win98SE. The previous posts linked at least one excellent GRUB resource and you also may want to investigate LiLO after 98SE is repaired.

All SUSE documentation always stresses (and always has) the need to backup critical data before the install. And, this is how we learn (me also by destroyed stuff) that the advice is good to heed. I now put anything I need on external HDs which are not bootable. Not permanent perhaps but more so than cd or dvd which can easily be corrupted.

18

I don’t have a DVD burner. So I copied the content of the ISO to a dedicated partition (on another HD), and used Grub to boot it. That’s how I installed OpenSuse 11.0, and that’s why I fear to lose any ability to boot at all.

My problem seems to be the same one reported by roman6. When I try to boot Windows, the boot stop very early with an error message from Windows saying that HIMEM.SYS is missing (while it is not).
Before posting a bug report, I thought it would be best to check first in the forum, and I opened a thread
( Windows 98 failed to boot very early (Grub, OpenSuse 11.0) - openSUSE Forums ) for that problem. Later, I saw that roman6 already had reported the same problem; so I decided to post on this thread to avoid multiple discussions about the same topic.

I’m scared to boot the Win98 DVD to replace the MBR in case I lose Grub. Maybe I can prepare a bootable floppy with Grub on it (?), in case…

Er, what do you mean by “boot flag” ?
My Win98 partition is on (hd0,0). Here is the entry in /boot/grub/menu.lst :


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

(I already tried to manually change rootnoverify to (hd0,0) and chainloader +1, with no improvement.)

19

Hi
You might try setting the boot flag on the partition that contains
win98 with fdisk (assuming it’s on partition 1) eg


malcolml@kermit-opensuse:~$ su -
Password:
kermit-opensuse:~ # fdisk -l

Disk /dev/sda: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe71be71b

Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        3918    31463302    7  HPFS/NTFS
/dev/sda2            3918       12161    66219899    f  W95 Ext'd (LBA)
/dev/sda5            3918        4192     2208906   82  Linux swap /
Solaris /dev/sda6            4193        8109    31463271   83  Linux
/dev/sda7            8110       12161    32547658+  83  Linux
kermit-opensuse:~ # fdisk /dev/sda

The number of cylinders for this disk is set to 12161.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): a
Partition number (1-7): 1

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or
resource busy. The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.
kermit-opensuse:~ # fdisk -l

Disk /dev/sda: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe71be71b

Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        3918    31463302    7  HPFS/NTFS
/dev/sda2            3918       12161    66219899    f  W95 Ext'd (LBA)
/dev/sda5            3918        4192     2208906   82  Linux swap /
Solaris /dev/sda6            4193        8109    31463271   83  Linux
/dev/sda7            8110       12161    32547658+  83  Linux

As you can see there is now an asterisk (*) in the boot for sda1 (or
active partition for windows speak)

–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 0:07, 1 user, load average: 0.02, 0.52, 0.39
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12

20

I think I have found a solution, without the need to do a Windows Repair or to replace the MBR. :slight_smile:

The problem is not due to a corrupted or a missing file (HIMEM.SYS), unlike what the Windows’ error message suggested, but because the Extended Memory Management unit can no more recognize and make use of the A20 line (I understand it as a reserved memory area).
This is better explained in the Microsoft Knowledge Base,
here: The “Unable to control A20 Line” error message
and here: HIMEM.SYS Err Msg: ERROR: Can’t Enable A20

I can now boot my Windows 98 partition again.
All I had to do was to edit the CONFIG.SYS file, and add a “/M:1” option to the HIMEM.SYS line.
So the first line in CONFIG.SYS looks like:


DEVICE=C:\WINDOWS\HIMEM.SYS /M:1

It’s still a mystery to me as to why the installation of OpenSuse made such a requirement in the Windows config (a change in the BIOS or on the MBR ?), but at least the problem is now solved for me. :wink:

( @roman6 : Hope this will help you too. )