MacOS 7.6 Notes
MacOS 7.6 Installation and Use
Brought to you by
Copyright 1997 by Bill Fox
Last Updated: Mar. 8, 1997
Friday 2/7/97, the MacOS 7.6 finally arrived in the mail. Here's kind of a running commentary on my experience installing it and my recommendations. First, let me say that MacOS 7.6 is excellent. It runs faster, much faster than System 7.5.x and is much more stable once all conflicts, if any, have been identified and resolved. I was unlucky and had an obscure conflict, one that was very difficult to find. Yet, I did find it after a lot of frustration that comes through below. MacOS 7.6 is not really at fault as no beta testing program can eliminate all problems with all the third party software out there. Remember that MacOS 7.6 is NOT an updater but a new OS and deserves to be treated that way. If you've got a lot of applications and inits and have problems after an easy install, do yourself a favor with a clean install and reinstall the third party stuff one at a time to ensure against having my too long and frustrating problem. Okay? Here goes:
Feb. 7, 1997 -- It took me about an hour and a half to install MacOS 7.6 on both my PowerBase 180 and Mac 7100/80--this included reinstalling Open Transport v1.1.2 since MacOS 7.6 installs the previous version 1.1.1. I followed the instructions to a "t" and the installer appeared to run without a hitch on both machines. However, curiously I ended up with no Chooser or Find File on the PB 180. A simple reinstall fixed this. I had QuickTime 3D 1.5 installed already so I did not install QT 1.06 and this caused no problems. I also had newer ObjectSupportLib and Thread Manager extensions and neither were disturbed by the installer.
Before installing MasOS 7.6 on my PB 180 computer, I erased the Open Transport 1.1.2 files, including TCP/IP and the installer ran without stopping. On my 7100/80, I left the OT 1.1.2 files on the computer and I was prompted eight times to overwrite them during installation. I don't have a clear choice to recommend. Reinstallation of OT 1.1.2 was not a problem.
The initial results were both amazing and slightly demoralizing. Everything seemed to run much faster on the computer and online, though it was pretty late Friday when I got around to testing it which may have accounted for some of the speed. I began checking my online connections, an ISP, AT&T Worldnet and CompuServe. Then came the crashes on my PB 180 where I had none with System 7.5.5. I experienced crashes to Macsbug 6.5.4a1 with Eudora Light 3.01 and 3.02, Filemaker 3.0 viewer for Apple Spec 11/96 and, worst of all, ClarisWorks 4.05 word processing which is my principal word processor. In fact, I couldn't open any previously-created text documents without getting errors, especially "File not found." How depressing, 2 out of 4 of these applications are Claris'. On the 7100/80, I got a few crashes and packed it in for the night, now Saturday morning at 2:30am.
Feb. 8, 1997 -- Saturday, I decided to just tackle my PowerBase 180 and leave the 7100/80 for later. I removed Macsbug 6.5.4a1, shut off RAM Doubler, de-installed OT 1.1.2, reinstalled OT 1.1.1 and OT/PPP 1.0. I did not experience any more crashes with the software noted above in several hours use. Then I tried to open Fetch 3.02b2 and the system crashed. It worked fine on 7.5.5 and one previous time. I rebooted and used Fetch 3.01 instead of the beta version. After several more crashes while online, I checked my OT/PPP and TCP/IP setups very carefully and found that I had accidentally mismatched the configurations while testing them. I had my ISP settings on OT/PPP and CompuServe settings on TCP/IP. Amazingly, it worked but was apparently unstable. After matching them up correctly I experienced no more online crashes. Initially, I could not open any of my pre-created ClarisWorks word processing text documents with ClarisWorks 4.04 (7100/80) or ClarisWorks 4.05 (PowerBase 180) or WordPerfect 3.5.2 (either computer). Fortunately,Word 6.01 opened the documents so that I could update For MacOS Users Only!. I looked for an updater or some comment from Claris but there was neither. In all the pre-release stuff I read that WordPerfect would have a problem with MacLinkPlus 8.1 translators but I did not see anything on ClarisWorks. ClarisDraw seemed to open drawings just fine.
The ClarisWorks problem was fixed by my trashing every vestige of it, especially the "Claris Folder" in the system folder and "XTND Translator List" in the preference folder, and reinstalling it. The MacOS 7.6 installation, probably the MacLinkPlus portion, modified some part of ClarisWorks so that it could not open its own text files. I got crashes and "File not Found" error messages.
With both of the major problems fixed, I still got an occasional Type 1 error when I open the new Extensions Manager. It is usually the first time after startup. I just select it again and it opens fine.
Feb. 9, 1997 -- I decided to take the longer but safer route with my PowerMac 7100/80 and do a clean install of MacOS 7.6 even though I had already installed it. Clicking the "Options" button during the installation allows one to select a clean install and the installer proceeds to do so easily. I clean-installed ClarisWorks to rectify the problem identified with my PB 180. It took a while to move all my control panels, extensions, fonts and preference files to the new system folder. Nevertheless, at the end it worked flawlessly except for the same but worse Extension Manager problem noted for my PB 180. I traced part of the problem to a bad font suitcase. After deleting the font, the problem was no worse than that of the PB 180.
Finally, I reactivated RAM Doubler 2.01 on my PB 180 and have experienced no problems.
With one exception, MacOS 7.6 is working smoothly with my frequently-used applications on both my PowerBase 180 and PowerMac 7100/80. The exception is the new Extensions Manager--I get occasional Type 1 errors when I select it on either computer. This is a conflict that I'll have to isolate. Here are the main things that I learned:
It is not necessary but I recommend a clean install even though it is a royal pain. There really are too many things that are different in MacOS 7.6 to treat it as an updater. If you have some corrupted files, this will save you a lot of headaches.Feb. 10, 1997 -- Sunday night I isolated the conflict with MacOS 7.6's new Extensions Manager on my PowerBase 180--it was TypeIt4Me 4.7b1. I deleted it and have had no further Type 1 errors or freezes. However, I was unsuccessful on my 7100/80. Following the usual halving process, I first identified CE Toolbox of QuicKeys as the culprit and disabled it and the other parts of QuicKeys. Then, several reboots later on Monday night I had another Type 1 error when selecting the new Extensions Manager followed by others at apparently random times. I repeated the halving process and this time identified Apple QD 3D HW Driver extension as the culprit and disabled it. Several reboots later I got a Type 1 error and several times again at apparently random times. I gave up for the night, disabled the new MacOS 7.6 Extensions Manager and installed Now Startup Manager 7.04 as my control panels/extensions utility--no further problems.If you have been using Open Transport 1.1.2, don't reinstall it immediately. Try getting by with OT 1.1.1. OT 1.1.2 may cause you problems so install it experimentally after you've attained stability or not at all.
Let the installer reinstall OT/PPP 1.0 even if you have been using it. Be sure to save your settings.
Finally, if you have problems with an application, trash every vestige of it, especially anything you put back (or left, if you didn't do a clean install of 7.6) in the system folder, and reinstall it from scratch.
Feb. 11, 1997 -- I installed MacOS 7.6 on my PowerMac 8500/120 at work. We bought a few copies retail (there are plenty around in stores in N. Virginia and S. Maryland) to test our LAN, WAN and internet connectivity with the new operating system. Pressed for time, I decided against my better judgement to do an easy install rather than a clean install--I have little "junk" on my work computer. I also unchecked MacLinkPlus 8.1 since we use WordPerfect and we are waiting for a patch from Corel. Everything went smoothly until the reboot after installation. My computer froze midway during the obligatory desktop rebuild. I rebooted and it froze again at roughly the same place. I rebooted with extensions off and the rebuild was successful. I rebooted again with the extensions on and the rebuild occurred again but was successful. Why? I haven't a clue but I'm not going to argue with success. For several hours on our LAN, WAN and internet, the 8500/120 has worked flawlessly. No problems with the new Extensions Manager as noted above for my own computers. Too much silly unused "junk" on them, especially the 7100/80, I guess!
Feb. 12, 1997 -- Well, after two days of running near flawlessly (this word is geting overused, especially for the extant situation), late Tuesday night my PowerBase 180 crashed while downloading email with Eudora Light 3.02. The crash rendered the computer totally unuseable. I have nearly completed a clean install, painfully slowly reinstalling each application rather than moving their extensions, control panels and settings from the old system folder. As of Wednesday night, so far so good. I am beginning to feel like giving up on MacOS 7.6 but I did an easy install so this big one may have been my fault or coincidental. I clean-installed MacOS 7.6 on the other two computers but they still have niggling problems (a couple of freezes and a single Type 1 with the Extensions Manager on the 8500 plus a continuation of Type 1's on my 7100).
Feb. 13, 1997 -- MacOS 7.6 -- Best Thing Since Sliced Bread? Okay, I am basking in the euphoria of having isolated the origin of all my problems...er...at least those with the installation of MacOS 7.6 on my three computers, a PowerBase 180, a 7100/80 and an 8500/120. The culprit all along was a utility called PowerPeek 1.02, not CE Toolbox nor TypeIt4Me nor Apple QuickDraw 3D HW Driver. PowerPeek monitors and reports the amount of native PPC code and number of patches in each application/init so it was really difficult to track down since it manifested its problems through other applications/inits. After removing PowerPeek 1.02, all three computers run perfectly--faster and more stable than ever, not an error or freeze since.
Looking back at the running commentary of my experience, my frustration could have left the impression that MacOS 7.6 is bad. While my observations were 100% accurate, as noted above, nothing could be further from the truth--I love 7.6...well, now I do. I received lots of mail from people saying that they had no problems with 7.6. For example, Andrew Holowka, MIS manager for Air Liquide, wrote that he was a 7.6 beta tester and neither he nor any of 110+ beta testers had any of my problems. He wrote that he had identified the Type 1 error problem with Extensions Manager and that it had been fixed last November. He further wrote that none of the 70+ Macs at his work site had problems with 7.6. But work sites usually have few "nifty" utilities and this may be a weakness in the design of Apple's beta testing program--Apple needs many more knowledgeable but "average" users with tons of apps, utilities and inits. I thank Andrew for spurring me on to find the source of my problems. Otherwise, I might have given up. Really.
My problems were not the fault of MacOS 7.6 per se. MacOS 7.6 with its inits alone work flawlessly. No beta testing program can ever find and fix every problem with every other piece of software. Actually, it is amazing that I had only one conflict problem given all the "junk" that I have on my computers. MacOS 7.6 is sufficiently new to be installed as a new program rather than a simple updater.
Let my experience that I've documented on this page serve as an example that the severest of problems anyone may encounter probably result from conflicts and that they are resolvable.
The final rack up? One faulty install out of six fixed with a reinstall. ClarisWorks' text file translation ability axed but fixed with a reinstall of ClarisWorks. PowerPeek 1.02 conflict with the new Extensions Manager fixed by removing PowerPeek.
- My system's use of RAM diminished by about 2 MB, low 9's to low 7's.
- The mega-RAM leak is not fixed. It has never occurred when just using Netscape but if I open or use other applications, especially non-online applications like ClarisWorks, I occasionally get it again. I am using OT 1.1.1 and OT/PPP 1.0.
If you have problems, MacFixIt set up a Troubleshooting Mac OS 7.6 Page so you might try looking at it for help.
[Back to top of page]
Copyright © 1997 by Bill Fox.
All rights reserved--no commercial use permitted without my expressed permission.
Of course . . . . . . and I am proud to be an Evangelista! . . .
[Back to top of page]
Saw something? Send a tip or a correction
The archive ran on reader tips. What did you see, where, and do you want the credit? Something wrong on this page? Say so and it gets fixed.