Shared Libraries and launching Classic: a follow-up

Regarding the problem launching Classic (reported yesterday), linked indirectly to Shared Library extensions, Daniel Zimmerman replies: "The culprit in this case is, in fact, Open Transport. Here's what happens: When Classic boots Mac OS 9.1, it does some tweaking of the TCP/IP Preferences file to allow it to work properly inside Mac OS X. Unfortunately, the code in Classic which does this is somewhat broken - in certain cases, such as if you have more than 2 'search domains' listed in the Network preference panel of OS X, this Classic code can corrupt the Mac OS 9.1 system heap, and either cause Classic to fail to boot (with a bomb and an 'address error' dialog), cause Classic to hang near the end of its boot, or just cause random crashes later while Classic is running. The work-around is to boot into OS 9.1 from the partition being used to boot Classic, set the TCP/IP Preferences to match the ones which are set in the OS X Network pane, and lock the TCP/IP Preferences file after closing the TCP/IP control panel. Now Classic won't try to update those preferences any more, because the file is locked, and it will work every time. I have no idea how this affects people with dynamic IPs, though; I suppose it can't hurt them to try it and see how well it works (or doesn't work)."

Another reader solved the problem by removing a Hosts file from his Preferences folder.

Update: Jason Harris had this problem. He writes: "Disabling Shared Library Manager PPC fixed the problem, but I didn't have much functionality in Classic. After much trial and error, I discovered that the library that was causing the problem was Open Transport ASLM Modules. Removing this fixed the problem, but I had no internet access in Classic. It turned out that I had too many files in System Folder:Fonts (I had 300 ). I think I was exceeding the maximum number of open files. Removing some fonts fixed the problem without losing any functionality in Classic."