If you do suffer a memory leak, keep an eye on free memory (About this computer dialog) and restart when it starts to occur, before a crash is likely. Some of these could result from a memory leak, which still plague Mac OS 8. If it recurs, suspect a bug in the application, an extension conflict, or similar if it doesn’t recur, keep an eye open for similar problems. Then try to reproduce the error which caused the crash.Once restarted, check the startup disk and the disk on which the application was running, using Disk First Aid (and any other disk utility you may prefer) to repair any residual errors.Save all your other work and restart your Mac.
Here’s what we did to fix memory problems. But apps could and did run out of memory, when they would simply quit with an error alert. My Power Mac G3 worked well with Mac OS taking a lion’s share of just over 50 MB, my mail client with less than 7 MB, and the whole of Microsoft Word in under 20 MB. As apps were far more conservative in their memory requirements, this worked better than you might expect. The maximum my Blue & White Power Mac G3/350 could accommodate was just 1 GB.
Most users stuck with only enabling it when their software needed it, and made do with the limitations of physical memory of 384 MB or even less. Some apps required it, while others couldn’t run when it was enabled. In Mac OS 8.6, virtual memory was optional. No wonder we had to publish MacUser every two weeks. So for a while, I was writing about three quite different operating systems: the mature if flawed embers of 8.x, the fraught newcomer 9.x, and the first sight of Mac OS X. Just to complicate matters, Apple released the Public Beta of Mac OS X just a month before Mac OS 9.0. Mac OS 9.0 was released in October 1999, but was a beast, and had so many problems that most users remained on 8.6, released earlier that year.
As the world moved into the new millennium, Macs were in mayhem.
0 kommentar(er)
