Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Fix 'broken Classic apps after new Mac migration Classic
I recently upgraded from a G4 tower to a spanking new G5 Quad, and since my old computer was in tip-top shape I thought I'd save myself some setup time by choosing to "migrate" all the data from the old computer to the new one.

Everything seemed to go well...I fired up the new G5 and was pleased to see it basically looked and felt like my old system, with all my folders and apps where I expected to find them. I noticed, however, that some 'migrated' folders had the tag (from old Mac) added to their names. Very helpful, I thought, that the migration process tagged these folders this way lest I lose track of what was old and what was new on my computer.

The problem this seems to cause, however, is that a few of my Classic apps (I know, I know ... a G5 Quad and I'm still running Classic. I am merely a prisoner of the slow-to-upgrade corporate environment in which I work!) lost track of where they could find extensions, plug-ins, etc. that they needed to function properly. QuarkXPress 4, for example, couldn't find some of its extensions or my auxiliary dictionaries, and had trouble launching (calling up dialogue windows asking me to locate these things, whch frequently froze the launching process). An old version of PowerPoint couldn't find some obscure Microsoft library files.

The fix, simple as it was, was to remove the (from old Mac) tag that had been added to my OS 9 System Folder folder's name. This restored the accuracy of the 'links' that my Classic apps needed to find their extensions, plug-ins, etc. and everything returned to normal.

This issue may have more far-reaching impact than I've run into. It seems changing the Sysem Folder folder's name was not such a good idea after all.
    •    
  • Currently 1.50 / 5
  You rated: 1 / 5 (12 votes cast)
 
[8,140 views]  

Fix 'broken Classic apps after new Mac migration | 7 comments | Create New Account
Click here to return to the 'Fix 'broken Classic apps after new Mac migration' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Fix 'broken Classic apps after new Mac migration
Authored by: Unsoluble on Jul 21, '06 08:25:26AM
That's odd, actually, since Mac OS 9 itself never cared about what the System Folder was called. You could change the folder's name to anything you wanted; things knew where to look because they pointed themselves at System Folderness, not at a specific path. Why wouldn't that still work?

[ Reply to This | # ]
Fix 'broken Classic apps after new Mac migration
Authored by: RussellK on Jul 21, '06 08:51:07AM

I can't explain that. I'd never tried to rename my System Folder in OS9 (or in Classic, for that matter)...but the fix I described worked for at least two apps running in Classic (Quark 4 and PowerPoint 2001).



[ Reply to This | # ]
Fix 'broken Classic apps after new Mac migration
Authored by: cybergoober on Jul 21, '06 09:21:55AM
I would think that setting "System Folder (from old Mac)" as the Classic System Folder in System Preferences -> Classic would have cleared that up...

[ Reply to This | # ]
Fix 'broken Classic apps after new Mac migration
Authored by: daGrimm on Jul 21, '06 09:32:12AM

is your new G5 running on intel?
I was trying to get classic running on a new intel-macbook and it seems not to work without some addotional emulator like sheensaver or stuff, which I'm trying to avoid.
At least I always feel sympathy for those still using classic apart from myself ;-)



[ Reply to This | # ]
Fix 'broken Classic apps after new Mac migration
Authored by: deebster on Jul 21, '06 09:46:02AM

The G5 is a different chip (PPC) to the Intel. Intel Macs do not support Classic.



[ Reply to This | # ]
Fix 'broken Classic apps after new Mac migration
Authored by: RussellK on Jul 21, '06 10:14:06AM

daGrimm...my G5 is not an Intel Mac. I also have a new Intel Macbook Pro at home, and I've been putting off trying to get Classic up and running on it (but will eventually have to try). From what I've read/heard, there a a few workaround options (emulation etc.) but I'm not looking forward to it.

cybergoober...you could be on to something re: the System Folder setting in Classic's preference pane, but I'd never thought of changing that. Besides, Classic itself was running fine (meaning at least Classic itself "knew" where to find its system resources etc.), but some 3rd-party apps were just losing track of the things they needed because the very first folder level of their "link" train was broken...



[ Reply to This | # ]
Fix 'broken Classic apps after new Mac migration
Authored by: redclawx on Jul 21, '06 10:40:47AM

This would happen to any application that hard-codes data to pathnames. An example would be Netscape 4. If you change the pathname to its profile directory anywhere along the path, including the name of the hard drive itself, the next time Netscape is launched it will ask for the location of its profile to use. I don't know about other applications but Netscape was tested for this back when we still ran OS 8.6 and 9.



[ Reply to This | # ]