Font engine issues in non-admin account

I have an account with administrator rights (a privileged, or -pr account) for installing software and a non-privilged account for everyday use, on my Windows XP computer. I am having the following font issues with Illustrator CS3. When using the non-pr account, a number of fonts are unavailable, e.g. <Symbol> (Adobe type 1) and <Symbol> (Open Type). Also, names for available fonts are not forced to display in English, despite my having checked the box for EDIT>PREFERENCES>TYPE_Show_Font_Names_in_English. For example, the name of the Symbol_Italic font is displayed in Greek letters. When I log on as the -pr user, the font engine works fine. Both Symbol fonts are available, and all font names are displayed in English. The font engine in InDesign CS3 works fine from either account, so this seems to be a bug in Illustrator.

Did some research on this the other day, to see if i could get Software Update to run in the middle of the night like Windows can do.
Software Update requires Root powers, so when you give it your Admin Password your opening a sudo window of 5 minutes for it to complete it's task.
Software Update doesn't check for updates while in Standard User becuase Standard Users supposedly can't do anything about it anyway and it would be a obvious distraction. "Mommy the computer....!!!"
Apple should have a option in Software update preferences to let certain Standard Users know a Software Update is ready just for the purpose your explaining. I run in Standard as well.
I ran some Software Update commands via the Terminal for a launchd just to see what I could do.
Apprantly one can DOWNLOAD updates automatically with launchd in Admin, but not install them because of the need for sudo.
I just misssed a perfect opoortunity (todays update) to run a launchd to do automatic downloads of Software update, then see how to go about installing them afterwards. So fsck me, I'll have to wait now. (unless i use my other machine! ahhh!!)
Anyway the program you want is this little gem: Lingon
it's on Sourceforge (grab the image)
Ok so that takes care of the Software update downloads (man softwareupdate in Terminal for commands)
/usr/sbin/softwareupdate --download --all
Will do the automatic downloads, now it's just a script away to let you know ( a nice pop up window) that you have something in your folder where the Software Update just downloaded into.
That's the next question is where that is and how to run it.

Similar Messages

System PATH environment variable issue when user log off and log in or switch from admin to non-admin account

Hi,
Problem Description:
After installing my new product version, when user does log-off and log in again into admin account
or switch from admin account to non-admin account, PATH environment variable shows incorrect path of my product (previous product version’s path) using command prompt.
It seems windows refresh issue during session changes (log off and log in / switch from Admin to
Non-admin account).
Why PATH environment variable is not refresh immediately after log off and log in again or Switch
from admin to non-admin mode?.
Please see my thread for more details http://social.msdn.microsoft.com/Forums/vstudio/en-US/445ab42c-bdff-405a-8d53-558e1b6c7d34/path-environment-variable-issue-when-user-logoff-and-login-or-switch-from-admin-to-nonadmin?forum=windowsgeneraldevelopmentissues
Also submitted bug for this in connect.microsoft.com portal.In that it has lots of information
like problem statement, Reproduction steps and Expected Results.
Bug ID: 871782
Could you please any body help me for this?. your support will be appreciated.
Thanks,
Marichamy

Why PATH environment variable is not refresh immediately after log off and log in again or Switch
from admin to non-admin mode?.
I wouldn't have any expectation of what you are doing to work the way you expect. E.g. why is the %ABC% being replaced at all? There is some help about this ambiguous scenario in the cmd help...
/V:ON Enable delayed environment variable expansion using ! as the
delimiter. For example, /V:ON would allow !var! to expand the
variable var at execution time. The var syntax expands variables
at input time, which is quite a different thing when inside of a FOR
loop.
/V:OFF Disable delayed environment expansion.
So, what's the setting for the /V: switch that your users would be using? Perhaps you should be using the ! instead of the % for your ABC variable?
Oh. There's more below where I found that...
Delayed environment variable expansion is NOT enabled by default. You
can enable or disable delayed environment variable expansion for a
particular invocation of CMD.EXE with the /V:ON or /V:OFF switch. You
can enable or disable delayed expansion for all invocations of CMD.EXE on a
machine and/or user logon session by setting either or both of the
following REG_DWORD values in the registry using REGEDIT.EXE:
HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\DelayedExpansion
and/or
HKEY_CURRENT_USER\Software\Microsoft\Command Processor\DelayedExpansion
to either 0x1 or 0x0. The user specific setting takes precedence over
the machine setting. The command line switches take precedence over the
registry settings.
In a batch file the SETLOCAL ENABLEDELAYEDEXPANSION or DISABLEDELAYEDEXPANSION
arguments takes precedence over the /V:ON or /V:OFF switch. See SETLOCAL /?
for details.
If delayed environment variable expansion is enabled, then the exclamation
character can be used to substitute the value of an environment variable
at execution time.
So, I guess the essence of your "bug" will boil down to whether you
need the feature to get the result you want and the
truth of that first sentence but it certainly looks like a "can of worms" to me. ; )
HTH
Robert Aldwinckle

Access to Resources via Non-admin accounts

Is there any way to provide access to resources so that they are accessible via
non-admin accounts. For e.g. to Retrieve my JMSConnectionfactory i do a
Environment env = new Environment();
env.setProviderUrl(url);
env.setSecurityPrincipal(username);
env.setSecurityCredentials(password);
Context ctx = env.getInitialContext();
The username and password here is the admin account. This works fine but if i
use a non-admin account(member of Operators group), i get exceptions on Domainloghandler
runtime
Problem: I need to register a mbean that needs to access JMS Resources. Since
our deployment team doesnt want to provide us access to admin accounts, we use
a "operators" group account to register our mbeans. if i do this, i get a
Access not Allowed for subject:principals=[operator, Operators], on ResourceType:
DomainLogHandlerRuntime Action: execute Target: registerToMe.
This happens when my managed resource tries to access a JMS ConnectionFactory.
Instead if i register my mbeans using the admin account, everything is fine and
my managed resource works nice.
This is on weblogic 81 SP1 on Solaris. Please let me know if you need more details.
Any clues/hints/solutions greatly appreciated. There is not a lot of documentation
on how to access/register mbeans using non-admin accounts.
TIA
Raj

I have done some more debugging on this and have narrowed down the issue to the
location where my initialcontext is being obtained.
so if i register my mbean as a non-admin account and do an operation on the managed
resource which fetches initial context, i get the below exception. This is how
i get my initialcontext
weblogic.jndi.Environment env = new weblogic.jndi.Environment();
env.setProviderURL("t3://machine:8102,machine:8103");
env.setSecurityPrincipal("operator");
env.setSecurityCredentials("operator");
Context ctx = env.getInitialContext();
I am doing this from a mbean thats registered on a different managed server(t3://machine:8101)...
Whats wrong with this?
TIA
Raj
"Raj" <[email protected]> wrote:
>
Is there any way to provide access to resources so that they are accessible
via
non-admin accounts. For e.g. to Retrieve my JMSConnectionfactory i do
a
Environment env = new Environment();
env.setProviderUrl(url);
env.setSecurityPrincipal(username);
env.setSecurityCredentials(password);
Context ctx = env.getInitialContext();
The username and password here is the admin account. This works fine
but if i
use a non-admin account(member of Operators group), i get exceptions
on Domainloghandler
runtime
Problem: I need to register a mbean that needs to access JMS Resources.
Since
our deployment team doesnt want to provide us access to admin accounts,
we use
a "operators" group account to register our mbeans. if i do this, i get
a
Access not Allowed for subject:principals=[operator, Operators], on ResourceType:
DomainLogHandlerRuntime Action: execute Target: registerToMe.
This happens when my managed resource tries to access a JMS ConnectionFactory.
Instead if i register my mbeans using the admin account, everything is
fine and
my managed resource works nice.
This is on weblogic 81 SP1 on Solaris. Please let me know if you need
more details.
Any clues/hints/solutions greatly appreciated. There is not a lot of
documentation
on how to access/register mbeans using non-admin accounts.
TIA
Raj

Screen sharing to OS X Lion Server with non-admin account

I have set up a Lion Server with one admin (in addition to the root user) and several non-admin normal accounts. In Server.app, I have enabled remote login with ssh, and remote management via screen sharing. I am unable to use Screen Sharing to connect to the server from the non-admin accounts, but able to use the admin account. I've read that it is only enabled for admin users, but need to access from non-admin accounts, and I can't add these accounts to the admin group. Is there a way to do this with Workgroup Manager? I tried changing the Remote Management settings in System Preferences by adding the non-admin, but when selecting 'Observe' and 'Control' in the options for the user, they are not saved.

I resolved this issue by deselecting the "Enable screen sharing and remote management" in Server.app and going to System Preferences, Sharing Preferences, Screen Sharing, and allowing access for "All Users". If you have some users you want to allow VNC, you can create a group, add the allowed users to the group, and add the group under "Only these users".

Can't login to local NON-admin accounts-Directory Access set to server

I have a strange problem on a set of laptops that I cannot resolve and am hoping someone can help me.
Here is the issue:
I have a set of building laptops (PowerPC, OSX.4.11) that seemingly will not "search locally" in the authentication process. The logins seem to work fine for NETWORK logins to our Open Directory Master xserve, but these machines will not login to any LOCAL non-admin accounts. The local root and local admin account logins do, however, work fine. ?? The remainder of the building computers (Intel iMacs OSX.4.11) appear to have the exact same settings and login fine both locally and via the network home directories.
I have tried the following:
Deleted DirectoryService preferences folder (MacintoshHD-->Library-->Preferences->DirectoryService)
Deleted the mcx cache in Directory Access
Tried adding a new non-admin user to test (still will not login)
Removed and re-created LDAP configuration (all set to custom)
Tried setting the LDAP to the automatic settings ("Add DHCP-supplied LDAP servers to automatic search policies")
Disabled all network connectivity (turned off Airport and disconnected the ethernet cable), still cannot login to local accounts
Tried to bind in LDAP configuration (when I did bind the machine, it would no longer authenticate to the network authentication server, so I did an "unbind" and restarted and it went back to performing the network logins, but still will not login to local non-admin accounts).
Reset passwords in System Prefs and also re-typed them in NetInfo Manager
Deleted login keychains
Deleted mcx.plist
Reinstalled the OS from disk and local logins worked TEMPORARILY--UNTIL I set the LDAP directory access to authenticate to our server (which I also need for the network logins to work),then, the issue started again.
*Same results with both ethernet and wireless connectivity enabled.
*Note: I also manage these local accounts via WGM (installed on the local machine) and even tried disabling that and still no luck.
Please help...I have spent hours and hours trying to find a solution and nothing seems to work! What am I missing??

Mostly just a bump...
How about that .local extension, or trailing / ?

Installing apps from non-admin account

I read an earlier post that installing apps from a non-admin account is a bad idea because SL applies the wrong permissions. I normally install from a non-admin account.... I don't see that the permissions on stuff I've installed are any different from apps that came with SL. Most everything is drwxr-xr-x. Was this fixed, or am I missing the problem.

KJK555 wrote:
+"That isn't a problem at all. Applications should not require that the user have write+
+access to the application."+
I didn't say anything about a user having write access permission, I was talking about read
permissions. All apps installed in the /Applications directory should have group permissions
set to admin or wheel (depending on the type of app), so the system can read them without
problems. That's the Unix way.
I completely disagee. The system already has read permission to all applications in the /Applications folder. It doesn't matter what the group privilege is set to. The "other" permissions are set to read only. System (root) can read it regardless. If you can show me an Apple tech article that says that apps installed in the /Applications folder should have their group privilege changed to "admin" or "wheel" then I would gladly take that back.
+"Leopard does not put any ACLs on anything installed in the /Applications folder"+
That's right, it doesn't normally, but if it finds an app that it does not have permission
to read, it will assign an ACE(s) to it so that it can access it.
I just tested that in 10.5.8, and it does not happen as you say. I can't try it in 10.6. I'd appreciate if you could provide a specific example where you can make this happen.
Besides, all users, by default, have read only access to all applications. Unless a user specifically changes permissions on an app to deny read access to everyone, then this isn't an issue.
http://discussions.apple.com/thread.jspa?threadID=1875193&start=60&tstart=0
http://discussions.apple.com/thread.jspa?threadID=1866808&start=15&tstart=0
http://discussions.apple.com/thread.jspa?messageID=8776714&#8776714
http://discussions.apple.com/thread.jspa?threadID=1850256&start=30&tstart=0
http://discussions.apple.com/thread.jspa?threadID=2351437&start=15&tstart=0
http://discussions.apple.com/thread.jspa?messageID=9447059&#9447059
http://discussions.apple.com/thread.jspa?messageID=9067640&#9067640
I know what ACLs are and how they work. I have read through those and cannot find in any of those threads anything about what you had been talking about.
+"That is also false. Root rights are granted by the user entering the admin username+
+and password when prompted. It does not matter where an application is installed in+
+order for it to be given root permission."+
http://support.apple.com/kb/HT2963
"Application installers, Applications folder
A third-party application installer incorrectly sets permissions on the files it installs,
or even the entire Applications folder. Symptoms of the Application folder's permissions
being set incorrectly include applications appearing in the dock as question marks, and/or
not being able to connect to the Internet. It is also possible that software installed while
logged in as one user will be inaccessible when logged in as another. To avoid this, make sure
you are logged in with your normal user account when installing software that you wish to use
with that account."
That has to do with third party installer apps that developers have not written properly to conform to OS X standards. It isn't an issue with applications that install by drag-and-drop. It sounds to me like you have looked at the permissions that Apple has put on its own apps and jumped to the conclusion that third party apps won't work unless they have the exact same permissions applied to them. That simply isn't true.
"Software access=user access
Most applications executed by a user only have access to the files that the user has access to.
Backup software, for example, may not back up Mac OS X system files that have root ownership."
Utilities, especially disk utilities, are to be installed in the /Applications/Utilities folder, for reasons
stated above.
No. That is completely wrong. Like I said earlier, an application is given root permission by user authentication. It matters not one little bit what the application's enclosing folder is. I personally have no third party apps in /Applications/Utilities; just what Apple puts there as part of a standard OS X installation.
More permission tips:
http://www.bombich.com/mactips/image.html
http://mostlyslow.blogspot.com/2009/04/technical-mac-os-x-permissions-issues.htm l
Have you even read those? I suggest that you do; because most of what you have written about how file/folder/application permissions in OS X is completely wrong.

Lightroom 3 asks for serial number launching in non-admin account

The following information was provided by Carey Burgess (Adobe Employee):
Does Lightroom 3 launch and work fine in an admin account, but when you launch the application in a standard (i.e. non-admin) account it asks for a serial number?
If so, then it is likely due to a file permissions issue either in the original (admin) account or with the standard account.
(Although you need administrator access to install Lightroom, and you do need proper access permissions to your photos, you should be able to run Lightroom without issue in a standard user account.)
Lightroom 3 stores registration data (the serial number) in a file called Lightroom 3.0 Registration, which is stored by default in one of these locations:
    * Mac OS: /Library/Application Support/Adobe/Lightroom
    * Windows XP: C:\Documents and Settings\All Users\Application Data\Adobe\Lightroom
    * Windows 7/Vista: C:\ProgramData\Adobe\Lightroom
- Check for the registration file in the appropriate location for your system.
If the file does not exist in that location, then ensure you are logged in with the admin account (the one where Lightroom doesn't prompt for a serial number) and check the user-specific location instead:
    * Mac OS: /Users/YOUR USER NAME/Library/Application Support/Adobe/Lightroom
    * Windows XP: C:\Documents and Settings\YOUR USER NAME\Application Data\Adobe\Lightroom
    * Windows 7/Vista: C:\Users\YOUR USER NAME\AppData\Roaming\Adobe\Lightroom
If the file exists in the user-specific location instead, then I would suggest that you ensure that you have quit Lightroom, and then move the registration file from the user location to the default system-wide location. Lightroom should now no longer prompt for serial number when you open it from a non-admin account.
If the registration file did (or now does) exist in the default system-wide location, but you are still being prompted to enter a serial number when opening Lightroom in a standard user account, then that account does not have sufficient access permission to the registration file.
To resolve this aspect, there are two possible solutions (the first being the recommended solution):
1. Change the access permissions on the Lightroom folder that contains the registration file to grant "Read" access for the standard user account. (You can do this for each account individually, or you can use a broader group like Everyone.)
For more information about changing permissions, see one of these articles:
    * Windows XP: http://support.microsoft.com/kb/308419#4
    * Windows Vista/Windows 7: http://windows.microsoft.com/en-us/windows7/What-are-permissions
    * Mac OS: http://docs.info.apple.com/article.html?path=Mac/10.6/en/8342.html
2. Copy the registration file from the system-wide location to the user-specific location for the standard user account. (You would need to repeat this step for each standard user that needs access to Lightroom.)
Reply here if these steps do not resolve your issue, or if you have any questions.

Months ago, I had a routine clearout of old software boxes etc and chucked out my Lightroom 1.0 box. A couple of weeks ago I reinstalled Lion on my mac to find that I cannot register Lightroom. I have the 3.0 upgrade serial, the 2.0 upgrade serial, but the 1.0 was on the box..
I followed the instructions above to find the files in crashplan form before the fomat that hold the registration details. I have tried placing them in the location described, but it doesn't seem to work.
The serials (or something) are in the file, but given in the string that is difficult to decipher - and doesn't work in the registration screen, wrong size and a mix of letters and numbers rather than just numbers as my 3.0 serial is.
Any suggestions for what I could do? Could I send the strings in to Adobe to be deciphered? Perhaps move files around a bit more?
Thanks in advance,
Rog.

Running Photoshop CS3 under a non-admin account?

Is it possible to run Photoshop CS3 under a non-admin account with Mac OS 10.4.11? If yes, is it stable then, and are there any known issues?

Buko and Ann:
Can you support with some documentation please? A quick Google search has many sites recommending to create two accounts. I could fine none (quickly) that stated it might not be necessary. I'm not so much concerned with being right (as it would be somebody else that was wrong) but purely to know that all the articles I have read are also full of sh!t.
I can assure you however that it is not a nuisance to work in a standard account. Certainly any maintenance I do is usually administered through the admin account. It would be a f!cking exasperating not to be able to log in as admin at the end/beginning of the day and manage these tasks on my time. In batch modding files I do find myself typing in passwords I shouldn't have to type, but I batch mod files infrequently and only because our file server is set up with no trust to individual users. I know if I change the setup someone will immediately delete someone else's directory just to teach me not to fiddle.
Rich: I've run CS2 and CS3 (and CS2 & CS3 ;)) in standard accounts with no problems. The only thing I can think of off the top is that Sing system error which was certainly permissions related. I will disclose that my office is relaxed (gov't) and I no longer consider myself a power-user. Though that probably means I am closer now that ever. I click a button and the computer does its thing. No worries.
I'm open to new ideas, and love to learn. I suppose the above is only strongly worded in response...
J

Making non-admin account

I've been using an admin account for everything (no scolding please), but am considering using a non-admin account instead.
Seems to me easiest would be I could simply change it from admin to non-admin, and back again when necessary. Would there be any problems doing it this way?
Or must I create a new, non-admin account and copy / migrate my current home folder from the admin account, and as much else as possible, over? If I have to go the second route, what's the easiest way to do that? Thanks.

Thanks Kiraly, Yeah, I think that's what BD had in mind when he said make sure to have another working Admin account before changing to non-Admin.
I've just been doing a little experimenting. I already have another Admin "test" account. What I've noticed is I can use the password from that one in the "main" working Admin account, but not the other way. Strange. Tried logging in to the "test" account with the "main" account password, but it wouldn't let me. But no problem logging in to the "main" account with the "test" password. In any case, since I've already got another working Admin account, it should be no problem, as you say, to change this one to non-Admin and use the test pword to authenticate when necessary.
*BD, if you're reading this,* you didn't think it would be all that dangerous to keep this one Admin. referring, I suppose, to the low risk of my wreaking havoc to the system files and data. Apart from the issue of my wife also using this account--and I actually don't think she'll do anything bad--isn't the main risk supposed to be a security one? That, navigating with an Admin account, some sort of rootkit, backdoor or keylogger, or whatever, might have unimpeded access to the system itself?

Photoshop Elements 6 in non-admin account?

I just got the long-awaited Photoshop Elements 6 for Mac and installed it. The installation seemed to go well. But when I tried to use it, non of the layer styles and effects show up. I have read the Adobe site and see that it is intended to run only in and Admin account, but doesn't that defeat the purpose of several accounts. I tried letting the rebuild the mediadatabase.db3 file as suggested here,
http://www.scrappersguide.com/forums/showthread.php?p=28421
but that hasn't fixed the problem. I'm hoping some one here has a solution that will let me work in a non-admin account.
Thanks!

Previous versions also had permissions problems. Maybe some of the fixes will help the current version
<http://forums.macnn.com/82/applications/237093/installing-photoshop-elements-3- a/>

Possible conflict with iTunes 7 and non-admin account

I've tried burning cd's in my usual windows account (limited) and it comes up with the error message "disc burner or software not found", but when I log into my admin account and try and burn an mp3 then it burns just fine. I wonder if they changed the way version 7 burns cd's...
Any solutuions or fixes?

I'm not really looking for a way to roll it back. I was just hoping to find a fix for the current version, or make them aware that there is a problem with running it in a non-admin account.
Thanks for the info though!

How to run admin tasks with non-admin account ?

Hello,
The title says it all: I want to allow some non-administrative accounts to run admin tasks which must be run as root.
A solution would be to use 'sudo' and give rights to those non-admin accounts on the binaries used by the tasks. But I notably use 'chmod' and 'chown' in those tasks, and I would not want to give to non-admin accounts rights to run those commands as root outside the admin task scripts. But from my understanding of 'sudo', if I do it, non-admin accounts will be able to use chmod and chown outside the scripts. Is this right ?
The sid bit could have been a solution I think, but sadly it is not supported on Mac OSX 10.5.
Thanks

I am trying to use the sudo route add command in a script, which should run as part of a vpn connection config file. I get an unable to run script error in the log.
I searched and found the following older discussion
http://discussions.apple.com/thread.jspa?messageID=1986808
I tried that but I get a syntax error when trying to save the sudoers file I chose to save anyway.
Tried to run the command from the terminal and got the following error
postdrop warning: unable to look up public/pickup:no such file or directory.
Can you give me an example of your sudoers file with the correct syntax etc.
Thanx

Reader X will not open (non-admin account)

I installed Adobe Reader X on an admin account for the computer. On the non-administrator accounts, Adobe Reader X will not open. There are no error messages or anything - it just will not open in non-admin accounts. Is there a setting I've overlooked to allow other users to access it?

How do you open the Reader on the non-admin account - directly (from the Start menu or desktop shortcut), or by double-clicking a PDF file?
After you do that, can you check with the Task Manager's Processes tab if AcroRd32.exe is running?

Can't run programs from non-admin account: redux

Background: I have years of experience with PCs, very little with Macs. I work with children in a group home. The tech support people who set up this iMac (OS X 10.2) have long since departed, and no one in the organization has any clue as to what changes they made to this system, and I'm sure that those tech people made some changes. For example, in admin accounts other than "root," either there is no access to the Utilities folder or the folder has been well hidden.
The Problem: The boys in this home will use a non-admin account. The programs I have installed for them will run under admin accounts but not under the "boys" account, which is non-admin. The system tells me that the account does not have enough access privileges to run the programs. (Program that had been installed before I got access to this iMac will run under the "boys" account.)
In discussions on this forum several months ago, I thought the answers I got here had helped me solve the problem. Then, for administrative reasons, I did not touch the iMac until last week. What I thought had been solved is not solved.
From "root," using the "Capabilities" option in the Accounts folder, I have added to the "Add other applications..." section the programs I want "boys" to have access to. But this doesn't work. When I log in to "boys," access is denied: insufficient access privileges.
If I give up on this system, the boys will not be able to use this iMac, and that would be a shame.

I realize that it sounds like I ignored all the previous advice before I drafted this latest post. But the first thing I did when I returned to the iMac was to look at the posts.
I didn't touch the system for six months. I was waiting for approval from administration to upgrade the OS. By the time I got the approval, upgrading was no longer an option -- according to the manager of the local Genius Bar. This system is not capable of running 10.5, and Apple will no longer sell 10.4. I can find 10.4 on the Net, but those are private sellers and the price is too high.
Now that I've got that out of the way, the current task: I have no idea why, but the gains I accomplished six months ago have disappeared. The "boys" account can run none of the software I installed. No one else has touched the system. (I live alone.)
I logged on as "root" and went to Accounts. Using 10.2's Capabilities function, I tried to check all the boxes for "boys." But when I close the screen and then re-open it, the system has unchecked "Open all System Preferences"; "Change Password"; and access to "Utilities."
At this point I cannot create new folders under "boys." "boys" can run software that was installed before I got the machine, but that's all.
I have to assume that I inadvertently did something that wiped out my previous gains. But I ain't got a clue.

Can't run programs from non-admin account

I'm new to the Mac and rusty with -- but not new to -- UNIX. I'm working with an iMac running OS X 10.2. I have installed several programs in a non-admin account (called "boys"), but they will not run from that account. The "get info" screen tells me that the "boys" account is the owner of the program. Read/write permission is enabled. When I try to run the programs, I get this error message: "The operation could not be completed because you do not have enough access privileges." I have installed the same programs in an admin account, and the programs run just fine from that account. I'd like to get this working so that the boys in the "boys" account can actually use the system. I have "inherited" this system from prior users. Programs that were on the system when I got my hands on it do run -- for the most part -- from "boys."
iMac Mac OS X (10.2.x)
iMac Mac OS X (10.2.x)

Thanks for the reply, Ken. My various unsuccessful attempts to solve this problem led me to create a folder named "Programs." (I know, my PC roots are showing.) I did this for two reasons: 1) I hoped that this would give me more control over what was happening; and 2) I wanted to give the children with whom I am working an easy way to find the programs that I want them to use. When I use < cd /users/boys > and then do an ls- l, I see the Programs folder. An ls -l on that folder shows all the program I have loaded and indicates that the "x" permission is applied to owner, group and others. Moreover, I assumed (incorrectly, perhaps) that installing the programs using the "boys" non-admin account would make them the "owner" of the programs and that "x" permission would follow. Well, ls -l indicates that they are the owners and that they do have execute permission. I can only guess that the prior users of this system -- and nobody in this organization seems to know where they are -- did something that requires more than Advil to overcome.
J...
iMac Mac OS X (10.2.x)
iMac Mac OS X (10.2.x)

Font engine issues in non-admin account

Similar Messages

Maybe you are looking for