Classic will not start-needs to update files?

Karen,

Try this again. Launching Classic, trying to update, and eventually getting that error message.

Then launch Console (/Applications/Utilities). It should open displaying the console.log. See if there's a message about the problem updating the classic specific files. It should be at the very bottom since I'm having you do this immediately after the above Classic routine.

If you don't see anything in the console.log, then check the system.log. Press the 'Logs' icon in the upper left-hand corner. You'll see a sidebar displaying the various logs. Click the 'system.log' to see what that log has to say.

One of those logs should give us a more detailed explanation of the error, and how to proceed from there.

Eric, I hope you won't mind if I piggyback onto this discussion...

I too just started getting the "Classic was unable to update its files in System Folder" alert. I opened Console as you so helpfully suggested, and here's what it told me:

AUTOUPDATE: copy Classic from /System/Library/CoreServices/Classic Startup.app/Contents/Resources/UniversalForks failed, file is corrupt

So I found the invisible folder called UniversalForks and found a bunch of system files in there. Anyway, I'm not sure what to do now. I have the original Panther CD (an Upgrade disc). Should I (or am I able to) reinstall Classic? I've never tried that and I'm not sure if I can.

Or can I go to another Mac that has a good Classic installation and copy all the visible and invisible files in the UniversalForks folder and paste them into my Mac with the problem?

-Rob

I hope you won't mind if I piggyback onto this discussion...

Usually no. 😉

AUTOUPDATE: copy Classic from /System/Library/CoreServices/Classic Startup.app/Contents/Resources/UniversalForks failed, file is corrupt

Uggh! My worst fears, you've got a corrupt file inside the package.

O.k. trying to copy stuff over and into the Classic Startup.app package usually renders it useless. I know it's sort of useless already.

Anyway, short of an archive and install, best thing is to re-install just the Classic Startup.app from the CDs with Pacifist, then you'll need to update it because some of the subsequent 10.3.x updates includes updated bits inside the Classic Startup.app.

I've been following this problem for years, even suggested that a kbase article be written -- but the idea was rejected. As the OS X evolves so to do the instructions. I'm bad I don't bump my own threads to keep the instructions active in this forum.

I'll go dig up the last version I wrote and post it as reply. They're long, step-by-step to guide you through this.

I wrote them when 10.3.5 was the latest version. But I tried to write them forward looking. So insofar as you've updated to 10.3.6, then whether you see 10.3.5 Combined update, then go for the 10.3.6 Combined udpate.

Looks like the latest version I have is the 'more advanced' all-Pacifist approach. That is, you use Pacifist to install and update just the Classic Startup.app. It looks really long, but it takes less time than the alternative.

(The alternative is at Part III, where you just re-run the Combined udpate equivalent to version of 10.3.x that you're using -- running a Combined update takes longer than using Pacifist.)

Sorry, I meandering. If I'm confusing let me know before you attempt this.

The following are instructions for using Pacifist to reinstall (and update if required) the Classic Startup.app from the CD in case of corruption, etc. Checking your logs can help to determine whether this is necessary, e.g. there's a item count error, which is causing the update error when launching Classic.

I. Reinstalling Classic Startup.app from retail Panther CDs

1. Put 10.3, disk 1 CD in the drive.
2. Quit Classic (if in a partially open state), and launch Pacifist.
3. Select "Open Package" (either under Pacifist's "File" menu or button on the opening window.)
4. Navigate to this package and "open" it:

   /Mac OS X Install Disc 1/System/Installation/Packages/Essentials.pkg

   In a few moments, a Pacifist window will open, showing the contents of that Essentials.pkg.
5. Click the disclosure triangle next to "System" (folder); then "Library" (folder) underneath it; then "CoreServices" (folder) underneath that.
6. Highlight/select "ClassicStartup.app". (Do not click the disclosure triangle.) Aftering selecting, the buttons in the top left corner will become live.
7. Click "Install" in the top left corner.
8. Accept the "Install" of the app, and authenticate (enter your admintrator's name and password) as instructed. Pacifist will start installing the Classic Startup.app from the CD.
9. During the install process, Pacifist will prompt you whether Stop Installation, Leave Alone, Replace, or Update the "ClassicStartup.app". Press the Replace button.

Once Pacifist is done, you'll have a fresh copy of Classic Startup.app from the CD. Two notes at this point:

• If your 9.x System Folder isn't in English, you need a localization/translation; go to part II.
• If your 9.x System Folder is in English and you've updated OS X after originally installing from the CDs, then you need to update the Classic Startup.app; go to part III (skip part II).

II. Reinstalling the translations in the Classic Startup.app from retail Panther CDs
You only need to perform the following if your OS 9.x System isn't in English. Please note, that in the following I have you only install the translations/localized files inside the Classic Startup.app. I assume that you originally installed the translations when you first installed Panther.

1. Put 10.3, disk 2 CD in the drive.
2. Launch Pacifist.
3. Select "Open Package" (under "File" menu or use the button)
4. Navigate to this folder:

   /Mac OS X Install Disc 2/Packages

5. Select/open the 'language' package that matches the language of your 9.x System Folder, e.g. select/open French.pkg if your 9.x System is in French.
6. In a moment, the Pacifist window opens showing the contents of the relevant language package.
7. Click the disclosure triangle next to "System" (folder); then "Library" (folder) underneath it; then "CoreServices" (folder) underneath that.
8. Highlight/select "ClassicStartup.app". (Do not click the disclosure triangle.) Aftering selecting, the buttons in the top left corner will become live.
9. Click "Install" in the top left corner.
10. Accept the "Install" of the app, and authenticate as instructed if necessary. Pacifist will start installing the localized files inside the Classic Startup.app from the CD.
11. During the install process, Pacifist will prompt you whether Stop Installation, Leave Alone, Replace, or Update the "ClassicStartup.app". This time, press the Update button. (You're updating with the translated file now, not replacing.)

Once Pacifist is done, you've succesfully installed the localized/translated files inside the Classic Startup.app. Note:

If you've previously updated the OS after originally installing from the CDs, then you need to update the Classic Startup.app; go to part III.

In case you're wondering, there are only a handful of files inside a language package, e.g. French.pkg; a language package doesn't contain a complete version of the Classic Startup.app. So that's why you have to go through Steps I and II.

III. Updating Classic Startup.app to (latest) version

1. Download the complete Combined update equivalent to the copy of 10.3.x that you're using.
2. Locate your copy of the relevant 10.3.x Combined update package; if it's in a disk image (.dmg) double click the image to mount it. (You need the actual package, not a receipt.)
3. Launch Pacifist.
4. Select "Open Package" (under "File" menu or use the button)
5. Navigate to the 10.3.x Combined update package.
6. In a moment, the Pacifist window opens showing the contents of the relevant 10.3.x Combined package.
7. Click the disclosure triangle next to "System" (folder); then "Library" (folder) underneath it; then "CoreServices" (folder) underneath that.
8. Highlight/select "ClassicStartup.app". (Do not click the disclosure triangle.) Aftering selecting, the buttons in the top left corner will become live.
9. Click "Install" in the top left corner.
10. Accept the "Install" of the app, and authenticate as instructed if necessary. Pacifist will start installing the localized files inside the Classic Startup.app from the CD.
11. During the install process, Pacifist will prompt you whether Stop Installation, Leave Alone, Replace, or Update the "ClassicStartup.app". This time, press the Update button. (You want to update the files you installed in Part I at this point, you don't want to replace. The Combined update only contains some items inside Classic Startup.app, not the complete package.)

Once Pacifist is done, you should have an updated copy of the Classic Startup.app.

Probably best to repair permissions after all of this.

Launch Classic (cross fingers).

Thank you, thank you, thank you! Boy am I glad I decided to piggyback!

Your instructions were more than clear. It's exactly the kind of help I needed. The vert best part is, it worked!

What can I say, but thank you - again & again.

-Rob

Rob,

Thanks for posting back. Glad it worked.

Have tried what you suggested using Pacifist, replacing and updating files, but still not able to launch Classic, and getting the same error.

Actually Karen, those suggestions were for Rob, since his error message cited a corrupt file. No biggie, we'll try to get you fixed up.

Your error message is different. 😟, But your fix is actually much simpler. Sorry you went through the trouble with that Pacifist stuff. The logs can be very informative. They help me determine what you should do. And in the future, can help you too troubleshoot the problem much more efficiently.

Anyway, let's get at your problem. From the Error Codes list, I can tell you exactly what "err=-45" means. It means that a file is locked.

A bit of background: inside the Classic Startup.app package are updated 9.x extensions and control panels (and some other stuff) needed for Classic. On launch Classic checks the versions in 9.x System Folder, and updates the ones as needed. You have a locked file, so Classic Startup.app can't delete or remove that old locked file to replace it with a new one. At that point Classic stops and give you that error 'problem update system resources' message.

Your log entry tells us which file is locked and causing the problem. Look at the first half:

Copying /System/Library/CoreServices/Classic Startup.app/Contents/Resources/English.lproj/SystemFiles/CarbonLib

That includes a very long path. But the key item is the last bit: ClassicLib. That's an OS 9.x extention. The rest of the message indicates where the app was trying to copy CarbonLib (and thereby where the problematic locked file resides): /System Folder/Extensions.

So Classic Startup app is trying to update the 'CarbonLib' extension in your OS 9.x System Folder (in /System Folder/Extesions folder). But it can't do it because that file is locked.

So here's your fix, although it may be clear to you already.

1. Find your 9.x System Folder. Double-click to open it.

2. Then double-click on the Extensions folder to display the contents.

3. Scroll down until you find CarbonLib.

4. At this point you could just dump it in the trash, and try launching Classic again -- the Classic Startup.app will now be able to instll the udpated version so you won't be without it.

(If you don't like trashing the CarbonLib, then 'Get Info' on the file, and unlock it. Then launch Classic again.)

Let me know how it goes.

I'm having a similar problem, but my system gives yet another error message...

Nov 15 12:03:55 localhost Classic[404]: AUTOUPDATE ERROR: count of 33 localized files and 32 universal files doesn't match

I just upgraded from 10.2 where Classic worked fine. I used my 10.3 install CDs to upgrade, then Classic no longer worked. I ran the 10.3.6 combo upgrade next. still no luck. Finally I tried reinstalling OS 9 off my computer's original software restore CD. No luck with any of that.

Any tips on how to handle this one?

Thanks,
Eric

AUTOUPDATE ERROR: count of 33 localized files and 32 universal files doesn't match

That's another common one, something's wrong inside the Classic Startup.app.

Reinstall and update it with Pacifist as I directed Rob to do above.

Eric., "Classic will not start-needs to update files?" #7, 05:47pm Nov 7, 2004 CDT

Thanks. I went ahead and downloaded Pacifist, and reinstalled Classic Startup off the original install CD and then from the Combo update. Then I repaired my permissions (looked like a lot of repairs were made) and restarted. I'm no longer getting an error message, but now when I try to start Classic it flashes on the screen and disappears, basically not even beginning to load. No log messages are showing up in Console.

At this point, should I reinstall OS 9 off my restore CD?

Before you do that. I want to make sure what you did, you said:

reinstalled Classic Startup off the original install CD and then from the Combo update.

Just to be absolutely clear on this.

In Part I, step 9, you press the 'Replace' when prompted by Pacifist. You want to replace the bad version on hard drive with a fresh copy from you CDs.

But in Part III, step 11, you press the 'Update' button when prompted by Pacifist. At that point you want to update the (freshly installed copy from the CD) with the help of the Combo Update.

Are you sure you pressed the right buttons? If you're not, then I'd suggest doing it again.

If you are sure you pressed the right buttons, then do some basic troubleshooting.

1. Open Disk Utility. Under the 'File' menu, select 'Fix OS 9 Permissions'. This will make sure the permissions are correct on your OS 9.x System Folder. (This isn't normally checked by 'Fix Permissions' of Disk Utility.) Try launching Classic again.

2. In the Classic System Preferences, Advanced tab, rebuild the Classic desktop. Try Classic again.

3. Trash the Classic preference in:

/Users/<username>/Library/Preferences/ByHost

You'll see a file like 'com.apple.Classic.xxx.plist' -- where I have 'xxx' you see a bunch more characters. Dump in the Trash.

Then launch the Classic System Preference to set the System Folder to be used for Classic. (You dumped the preference file, so this setting is lost.) Then try launching Classic again.