Mac OS X 10.4: Classic: Problems starting, more
Problems starting -- possible fix A number of readers have reported problems starting Classic under Mac OS X 10.4.
MacFixIt reader Adam North, for instance, writes:
"I had a Classic installation that was fine under 10.3.x Upgraded to Tiger tonight and classic will not startup. I get the updating system components message after which I get the OS 9.2 splash screen and then a big stall. No extensions appear to load along the bottom of screen. Tried all the recommended tricks: fixed OS 9 permissions, fixed permissions on boot drive, tried to boot classic with extensions off via system preferences, tried to boot classic by calling extensions manager, reinstalled classic startup.app with pacifist off of Tiger DVD"
Some users experiencing this issue may be subject to a conflict caused by the QuickTime DiVX 5.2 component.
This file is located in the /Library/QuickTime folder. If you are having problems starting Classic, try removing the DiVX component from this folder, and attempt to re-launch Classic.
ResourcesMore from Late-Breakers
Great fix - thanks - worked for me - was pulling my hair out - Classic just
wouldn't get past the first millimeter of its startup bar - I removed the DivX
codec and suddenly it worked. Means you have to watch DivX movies in
VLC or put codec back during QuickTime use.
I've also noticed that an old Bridge game program mostly runs but occasionally stalls. I've waited at least a half-hour on that one with ending up still force quitting it (which indeed kills all classic apps). While it's stalled you can't get to other classic apps, either, to shut them down nicely.
In neither of the above cases is there excessive processor use.
The more serious problem I have with Classic is a kernel panic at then end of startup if there is no network (or maybe airport, but I'm guessing network) access. You can also sometimes provoke this by fiddling with network access while classic is running. The kernal panic log hows com.kernel.nke or something like that that made me think of the big changes that affected all the other network driver vendors, but you'd think Apple would get it right. Starting with extensions disabled works.-kby
Options". I removed it from the Classic system folder and the problem has gone.
- by Steven from Netherlands July 30, 2005 11:45 AM PDT
- I have found the solution to this problem in the Discussions on apple.com. You have to reinstall the Classic Startup.app from the installation DVD. The described solution is originally for OS X 10.3, but worked for me for 10.4.2.
- Like this Reply to this comment
-
(5 Comments)http://discussions.info.apple.com/webx?14@721.saRRavaLXEk.381568@.689e74dd