Why won't Classic start in Tiger 10.11

Question

Level 1

11 points

Why won't Classic start in Tiger 10.11

I am running OS 10.11. My classic will not start up. I reinstalled OS9 several times to no avail. Why am I having this problem?

Posted on Feb 17, 2012 1:44 PM

Reply

Answer 1

kurt188

Level 4

1,340 points

Feb 17, 2012 2:08 PM in response to ljcline59

It would be handy to heed this piece of advice: Just because something isn't working for you is not a good enough reason to start reinstalling the operating system. We first need to understand the problem before we can decide what should be done to solve it.

You've provided no information to go on, so we need more details before we can begin to solve this puzzle.

1. What did you do just before this problem started? Be specific; that includes installing anything, removing anything, etc.

2. What error messages did you get (if any)? Quote them verbatim.

3. If you got no error messages, what did the startup window show you (post a screen shot in your reply)?

4. Does your Console log show any errors related to OS 9 (most recent activity is always at the bottom of the Console window)

Reply

Answer 2

ljcline59 Author

Level 1

11 points

Feb 17, 2012 5:24 PM in response to kurt188

I do not recall installing anything, or removing anything. Your mentioning a Console log is new to me. I did find it. I found several Console log files. The most recent one, dated today, did show some sort of error. I copied and pasted it into this message. I have seen on this site that there have been others with the same problem I have. Nothing they suggested doing worked. I don't use OS9 very often, but being a teacher, I still have some software that requires that system. I hope you or someone can help.

Here's the 501 console log

Mac OS X Version 10.4.11 (Build 8S165)

2012-02-17 19:51:13 -0500

2012-02-17 19:51:31.374 SystemUIServer[193] lang is:en

BALIncreaseFileIDs: Failed to increase MAX FDs to 128 (rc=-1)

Feb 17 19:54:44 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:54:45 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:54:46 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:54:47 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:54:49 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:54:53 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:55:01 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:55:09 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:55:10 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:55:12 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:55:13 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:55:15 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:55:19 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:55:27 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:55:37 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:55:44 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 19:56:09 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:00:02 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:00:03 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:00:05 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:00:06 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:00:08 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:00:12 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:00:20 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:00:30 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:01:02 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:03:20 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:03:21 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:03:23 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:03:24 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:03:26 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:03:30 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:03:38 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:03:54 Lawrence-Clines-Computer /usr/sbin/ocspd: starting

Feb 17 20:05:33 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:05:35 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:05:38 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:05:39 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:05:41 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:05:45 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:05:53 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:06:04 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:06:36 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:19:51 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:19:52 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:19:55 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:19:56 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:20:02 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:20:10 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Feb 17 20:20:26 Lawrence-Clines-Computer mDNSResponder: ERROR: getOptRdata - unknown opt 4

Mac OS X Version 10.4.11 (Build 8S165)

2012-02-17 15:16:12 -0500

2012-02-17 15:16:21.110 SystemUIServer[190] lang is:en

BALIncreaseFileIDs: Failed to increase MAX FDs to 128 (rc=-1)

Reply

Answer 3

Limnos

Level 10

411,091 points

Feb 17, 2012 9:13 PM in response to ljcline59

What error messages are you seeing when you try to start Classic?

Do you have a System Folder selected in Classic preferences in System Preferences?

Since you just installed OS9, is it upgraded to 9.1 or greater which is a requirement for Classic?

Reply

Answer 4

ljcline59 Author

Level 1

11 points

Feb 18, 2012 3:19 AM in response to Limnos

There are no error messages appearing when I start Classic.

Yes, a system folder is selected.

It is an upgrade to 9.2.2 that attempts to start.

All I get is a tiny sliver of the progress bar.

Not one of the extensions appears in the window, and I have allowed it to go on attempting to start for more than 10 minutes with no results.

I have tried starting with extensions off. I get the same results.

I looked for the elusive DivXNetworks folder that other users with the same issue have removed from their library and gotten their Classic to work, but I don't have that folder on my machine.

It seems to be an issue with OS 10.4. My version is 10.4.11.

Reply

Answer 5

a brody

Level 10

82,841 points

Feb 20, 2012 6:51 AM in response to ljcline59

If you installed 9 from something other than the restore discs that came with your Mac, that might be a problem, depending on the Mac model. Only Macs older than August 21, 2001 could install 9.2.1 from the 9.2.1 retail installer. Only Macs older than January 9, 2001 could install 9.1 from the 9.1 retail installer. Only Macs oder than October 23, 1999 could install 9 from any 9 retail installer. Retail installers look likeand did not say Upgrade, Dropin, or OEM on them, and the version of 9 was written on one side in black in fine print.

Reply

Answer 6

a brody

Level 10

82,841 points

Feb 20, 2012 7:14 AM in response to a brody

The mDNSResponder program is the Unix background program for Spotlight. If you are doing anything in terms of file searching on hard drives, or using any system utilities that are non-Apple that can affect Spotlight's ability to index. Disable anything non-Apple in relation to that, and Classic may run better, that is if you had used the correct 9 installer as I mentioned earlier.

Reply

Answer 7

ljcline59 Author

Level 1

11 points

Feb 20, 2012 9:14 AM in response to a brody

Hello, and thanks for responding. My machine is a MacMini. All info from the system profiler is below:

Machine Name: Mac mini

Machine Model: PowerMac10,1

CPU Type: PowerPC G4 (1.2)

Number Of CPUs: 1

CPU Speed: 1.25 GHz

L2 Cache (per CPU): 512 KB

Memory: 1 GB

Bus Speed: 167 MHz

Boot ROM Version: 4.8.9f1

It came with OS 10.3 and an extra install CD for an upgrade to Classic 9.2. At that time Classic worked fine.

I upgraded to 10.4 when it came out. I kept up with the upgrades and now am running 10.4.11. I can't be sure,

but I think I started having this problem with the very last upgrade to 10.4.11.

Reply

Answer 8

BDAqua

Level 10

238,961 points

Feb 20, 2012 10:14 AM in response to ljcline59

mDNSResponder is actually Bonjour...

http://www.manpagez.com/man/8/mDNSResponder/

Are there any Console messages going on when you try to start Classic?

Reply

Answer 9

ljcline59 Author

Level 1

11 points

Feb 20, 2012 12:20 PM in response to BDAqua

No console messages automatically show up when I start Classic. I did not even know there was any such thing as console messages until 2 days ago. If I go into the console messages folder I can find tons of messages, but I have no idea what they mean.

Reply

Answer 10

BDAqua

Level 10

238,961 points

Feb 20, 2012 1:31 PM in response to ljcline59

What exactly happens when you go to System Preferences>Classic, then click Start Classic, or try to set the System folder for Classic?

Reply

Answer 11

ljcline59 Author

Level 1

11 points

Feb 20, 2012 3:21 PM in response to BDAqua

I go to System Preferences and click on start.

There are no error messages appearing when I start Classic.

Yes, a system folder is selected.

It is an upgrade to 9.2.2 that attempts to start.

All I get is a tiny sliver of the progress bar.

Not one of the extensions appears in the window, and I have allowed it to go on attempting to start for more than 10 minutes with no results.

I have tried starting with extensions off. I get the same results.

I looked for the elusive DivXNetworks folder that other users with the same issue have removed from their library and gotten their Classic to work, but I don't have that folder on my machine.

It seems to be an issue with OS 10.4. My version is 10.4.11, but I can't be sure.

Reply

Answer 12

BDAqua

Level 10

238,961 points

Feb 20, 2012 3:51 PM in response to ljcline59

In Classic Preferences>Advanced, what happens if you choose Open Extension Manager instead of Turn Extensions off?

Reply

Answer 13

a brody

Level 10

82,841 points

Feb 20, 2012 5:07 PM in response to BDAqua

Bonjour, also known as Rendezvous is a system that assists in file and printer sharing. Conundrums betweeen Classic and X have been known to take place when Appletalk is in the mix with old networking drivers. Any chance you are using some networked device with your Classic applications? If not, I'd focuss on disabling those extensions that you don't need.

Reply

Answer 14

ljcline59 Author

Level 1

11 points

Feb 21, 2012 3:15 AM in response to BDAqua

I have tried that and I get the same results.

Reply

Answer 15

ljcline59 Author

Level 1

11 points

Feb 21, 2012 3:24 AM in response to a brody

I never have used any networking devices with Classic. However, I do have a wireless D-Link that we use in the house for my son's MacBook and my wife's iPad.

Reply