🚀 go-pugleaf

In article <1dbtnn5.vac0b6bij56oN@p16.nas1.is2.u-net.net>,
real-address-in-sig@flur.bltigibbet (Rebecca and Rowland) wrote:

==> Salvation Films <Marc@nospam.redjez.demon.co.uk> wrote:
==> 
==> > System:  B1-7.1
==> > 
==> > Since upgrading to 36 MB of Ram, when I go to print the Mac freezes.
I
==> > have replaced the print monitor but it still freezes. Any
suggestions?
==> 
==> Which printer driver, print monitor, and printer are you using?  Direct
==> serial or LocalTalk connection?
==> 
==> Things I'd try: re-build the desktop, trash any suspicious looking
prefs
==> files, zap the PRAM (use TechTool to keep hours of use (etc) data), and
==> if *that* fails, I'd re-install the OS.
==> 
==> btw, I've got a 20MB 475 running 7.6.1 and it's *much* nicer (faster
and
==> more stable and does more) than 7.1 (which is what I was running
==> before).

I agree.  Our 36MB 475 is as stable as anything under 7.6.1.  It was OK
under 7.1.  Wasn't there some updates for 7.1 (SU3.0?).

Anyway, I also have Classic II with 10MB.  I saw random crashes when we
upgraded the memory.  It turned out that this was caused by bad memory
chips.  But the odd thing was that the memory passed the memory tests
programs I used.  The issue was that the memory was forgetting its contents
over time (after experimentation, I manged to find the bad location and the
time over which it was forgetting - about a second - but I know a lot about
Macs.  This wasn't an easy thing to do!)

Fortunately, the supplier was OK about my returning it as I could reproduce
(and explain) the crashes.

So, make sure that all the memory ugrades are securely located, the system
is a stable variety (e.g. 7.6.1 upwards), the disk is OK (this could also
be a disk error) and try and work out more about when it happens - e.g.
always with another application etc.  Try and turn off non-Apple extensions
if you use them.

Sorry - general question, general answer.  We need more specific data ...