🚀 go-pugleaf

A query, please (you can tell it's Christmas and the last job is safely
tucked away).

I still use sys 7.5.2 on a 750/100 and in general it's beautifully stable.
However as I try more stuff I can tell it needs a few new hooks... So I
shall be getting sys 8 and the update to Norton. But...

I get maybe one type 11 error a week. Often less. But in the past two
weeks, while experimenting with RealPlayer 5 and other stuff I have had my
problems with whatever it was that corrupted my system and stopped me
running Norton when booted from the HD.

Each time these type 11 errors have shown up, they have tended to persist
when I reboot. Type 11. Reset (Ctrl-Cmd-start) and some problem or other
crops up again- usually the crash on running Norton from the HD. Sometimes
something else- however, there is never any disk or file damage and if I
shut down and wait a few minutes, then restart, the machine (including
Norton) will run happily for days until I do something odd again and have
another short but irritating run of type 11 errors.

It behaves as though the memory weren't resetting on startup. But I thought
that this was done automagically. Am I wrong? If I restart via the
keyboard, can a problematic memory state persist?

-- 
Peter