🚀 go-pugleaf

In article <9169@boulder.Colorado.EDU> fozzard@boulder.Colorado.EDU (Richard Fozzard) writes:
>several times a day.  This is not a hardware quality control problem, but
>a software one. This is where Apple REALLY needs to get its act together.
>I admit I use a wide variety of software, but even users with the simplest
>of needs have seen these problems often.  The Mac must be at the top of
>the #boots/CPU-hour statistics among all computers, ever.

Weird. we have about 8 Mac+es and 5 Mac-II(x)es, and we don't experience those
problems. Personally, I take the following precautions when installing a system:

- build it from scratch (copy system folder, reboot from floppy, remove original
   system folder, run installer to get a fresh system, run Font/DA mover
   to install fonts/DA's from their original files (not from the old system),
   and copy trustworthy init's. Then make a copy of the whole lot).

- run virus checks regularly. I caught a virus once (NVIR a or b).
   If infected, do not repair but remove the application/system
   and get a fresh copy.

- don't use fishy INIT's and DA's. 

We do not experience crashes normally, only in specific software,
like MacDraw II. For the time being we've given up on Claris. Their
quality control must be lacking. I'm ordering FreeHand.
If you program the Mac yourself, use the programmer's key and a debugger
to save yourself from tricky situations. Good luck.

Ge' Weijers                                    Internet/UUCP: ge@cs.kun.nl
Faculty of Mathematics and Computer Science,   (uunet.uu.net!cs.kun.nl!ge)
University of Nijmegen, Toernooiveld 1         
6525 ED Nijmegen, the Netherlands              tel. +3180612483 (UTC-2)