View Full Version : Classic and Account Capabilities??
01-22-2003, 10:25 AM
I'm having the issue that when I set a non-admin user to use only certain applications in the accounts prefernce pane that they can't use classic either?
Is there any way around this?
01-30-2003, 02:04 PM
Well, I'm at a lose too.. I have been looking everywhere and I have no idea why classic won't start (I have the same problem)
If someone doesn't know the solution to the problem might someone know what classic looks for when it starts?
I even created a test user and selected Run only these apps under capabilities. I selected everything and Still classic will not start.
I think my brain is bleeding from the frustration of the problem.
So really if anyone knows anything please reply to this... =)
01-30-2003, 07:31 PM
Try looking up the documentation for Apple Remote Desktop. There is a workaround for that app that I believe would work for Classic. Post back if you can't find it - I 've got a hard copy around here somewhere.
01-31-2003, 09:44 AM
Thanks for the advice... So I downloaded the RD doc and my next question is, after a quick once over, where should I be looking on this doc for the workaround for Remote Desktop.
And specificially do I have the right doc. I just looked up Remote Desktop Documentation on apple/support and got that.
01-31-2003, 12:43 PM
I'm looking for the article. The gist is that you need to manually allow access to /System Folder/Library/CoreServices/Application that you need to start - in your case this would be Classic Startup.
Hope that helps - I don't off the top of my head remember how to do what you want manually.
02-28-2003, 10:09 PM
Apple has a technote about this very topic. While trying to find an answer to this question, I found this thread. Next I went straight to the source. I found technote 107442 which describes our scenario but does not offer a solution. The technote was created 2/6/03 (updated on 2/11/03) and ends with a comment that it'll be updated when more information is found.
So, for now I guess you either live without Classic on those accounts or you upgrade their privileges. I'm opting for the first since the effect accounts are for children and the desired applications are just games (some of which are educational, but we'll manage).
03-03-2003, 10:08 AM
Ok, well thanks to the folks at apple for this. I was talking to one of their techs who made it a priority to solve this little deliema...
So I gotta say Kudos to him.
The answer falls under my, Apple makes good software, but it's only until 5 or 6 revisions out... =) (I swear I have had more problems with X than I would like.)
Anyway to solve the problem with classic under 10.2.3 and I assume .4 (until 10.3 the guy told me) you do this:
Under capabilities, The top options (burn cd/dvd - remove items from the Dock, etc) Check/Uncheck as you desire
Then Check "Use Only These Applications" And here is where it gets GHETTO!!, yet in some strange way makes perfect sense - Yet another Apple trait I have often found ot be true =) Nobodies perfect I guess, It would be something else if it were Windows I suppose) with everything checked, start to copy stuff out of the utilities/Applications directories that you don't want people to use. So for example, you don want people to use the bluetooth stuff, make a directory under ~admin and copy it there. If it's not in the Utilities Folder then it does not get read, so regular users can't use it.
I think the only things I have in my Utilities folder are the following: (it sucks to have anything in there to be honest, I only want students using Applications not utilities) but anyway I guess these are mostly harmless until they fix it:
Damn, I lost my little pad with what I wrote down. Well, in its absence this is the gist: I took out the Administrative things, Like Netinfo, Terminal, Directory Services, etc. I think we all know what we don't want users palying with. And I left In the generic stuff. At that point to my utter Amazement, it worked. Classic started up and everything.
Yeah I know this kinda defeats the purpose of capabilities, but until 10.3 we're stuck with it I guess.
If I find my list I will post what I left in the folders.
03-03-2003, 04:37 PM
The other solution, the one I'm presently using, involves unchecking the "use only these applications" option. Then go through the computer and using user, group, and other rights to allow or disallow running of the other applications. My next step will be to author a drag and drop AppleScript to automate this process. You can accomplish this with the following commands:
chown :groupname filename
chmod o-x filename
The colon in front of the groupname is required. This can be done in the terminal. Read about these commands using the "man chown" and "man chmod" commands. If this doesn't make any sense, you'll need to study up more on Unix commands and the Terminal.
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.