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


Click here to return to the 'easier way...' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
easier way...
Authored by: Anonymous on Apr 22, '01 11:17:08PM

in terminal...


sudo chmod a-x /System/Library/CoreServices/ClassicStartup.app

this will set the executable bit of classicstartup.app to off, which won't let it launch. You get a weird error in the finder if you try and launch a classic app, but it's just a permission denied error, which makes sense... to change it back, just do the same thing with a + instead of a -

there ya go!



[ Reply to This | # ]
easier way...
Authored by: adyblain on Apr 23, '01 02:16:34AM

That's a good tip. I have a few partitions on a 60Gig disk, two of which have Classic system folders. One has Final Cut on it, the other all my other Classic apps. I never want Classic environment to launch from the partition with Final Cut on it. I will double boot into that when I need to. Is there a way I can stop Classic from launching from that particular disk?



[ Reply to This | # ]
easier way (adjusted) ...
Authored by: Brad Puett on May 16, '01 02:51:44PM

For those of us that like to "copy & paste" these hints, instead of retyping them, here' s the samee command, with 2 minor adjustment:s (still using terminal ... )


sudo chmod a-x '/System/Library/CoreServices/Classic Startup.app'


[All I did was add a space between "Classic" and "Startup" (that's the way my app is named), which required me to add single quotes on both sides of the path/app name]



[ Reply to This | # ]