Franc has already given you some extra info on the A20 line. If Memtest did not
find any RAM errors, and if the problem does not recur, I would chalk it up to a
momentary glitch as Franc suggests. Was it due to the Ubuntu install problem? I
don't know....I am not sure how a Linux install might affect such things. The fact
that you were able to correct it the way you did points to 'glitch' more than to a
permanent hardware problem. Obviously, it is something to keep an eye on, and a
good excuse to make sure your backups are up to date.
:-)

Hope that helps.....
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm


"Alex Wenzel" wrote in message
oups.com...
Well, I didn't expect answers to a German message erroneously posted in
an all-English group, I'm amazed...

Here are some more clarifications:
The problem is already gone. It was solved by entering the BIOS once,
changing *nothing* and saving on exit. Strange.
But anyway, I'm interested in what exactly the problem was.

BTW: Before I tried the failed Ubuntu install to the separate parition,
everything worked correctly.
And I later did another install of Ubuntu (from another CD, the first
one turned out to be defective), whithout getting the "himem.sys"
error. Some other problems, but nothing related to DOS/Windows. Now
everything works and dual boots fine.
Please see additional comments below.

glee wrote:
Do you have any of these versions of Norton SystemWorks installed: Norton
SystemWorks 1.0, Norton SystemWorks 2.0, Norton SystemWorks 2000, Norton
SystemWorks
2001, Norton SystemWorks 2002?

None of them. But an old version of Norton Utilities (4.0). But nothing
from these programs seems to start at boot time.
There is, however AVG Free Antivirus installed, which checks at boot
time.

If you still get an error message, please refer to the next solution.

Restart the computer in Safe Mode Command Prompt Only.
Type edit config.sys to open the Config.sys file in the DOS Edit program.
The Config.sys file may include the following line. You may need to append a
space
and /M:1 only or add the entire line.

device=c:\windows\himem.sys /m:1
snip
The value for the /M: line can range from 1 to 17. The value of 1 works for most
computers. IBM PS/2 and Compaq Prolinea computers may require a value of 2.

What exactly is "himem.sys /m:1" for?

Most of the answers I got in the German group insist that this is a
sign of an upcoming hardware failure. I'm not sure about that. Memtest
finds no errors in RAM. What do you think about it?

"Alex Wenzel" wrote in message
newsp.s5ynmqp4l0h2fi@tp600e...
(some stuff unreadable for the non-German speaking audience; dealing
with the error messages "HIMEM.SYS is missing. Make sure that the file
is in your Windows directory." and "Unable to control A20 line. XMS
driver is not installed.")