[kjb]

Hope I can find some help here.

I am able to launch and use Appleworks just fine from my user account. My wife, when logged in under her account, cannot. When she attempts to launch the program, the Dock moves for a split second as if the program will launch, and then nothing happens.

I've checked for the .plist file in my wife's preference folder, but there isn't one to delete.

I've also tried creating a new user and the new account can't start AW either. Anyone have any clues??

I'm running 10.2.6 on an iBook 500.


Thanks,

Kevin

[BJPirt]

check that she has 'execute' permissions on the application, maybe?

[Powaqqatsi]

Originally posted by BJPirt:
check that she has 'execute' permissions on the application, maybe?

Probably not, I think if the permissions are set to deny she would get a message saying that. I think that means a corrupted user. Try to trash al the prefs and if that doesn't work you need to create a new user and delete the old corrupted user.

[kjb]

Originally posted by Powaqqatsi:
Probably not, I think if the permissions are set to deny she would get a message saying that. I think that means a corrupted user. Try to trash al the prefs and if that doesn't work you need to create a new user and delete the old corrupted user.

I've created a new user and have the same problem with it. I ran repair permissions last night from the Jag install disk and that didn't do anything either.

Anything else I should try??

Thanks,

Kevin

[Sven G]

Repair Permissions probably doesn't verify AppleWorks, because it's not a system file; anyway, have you tried to check the permission on the AppleWorks app? Select AppleWorks, and then do File ---> Get Info and disclose the Owner and Permissions triangle: it should be set to something like

Owner: administrator (or your admin account's name), read/write;

Group: admin, read/write;

Others: read/write.

P.S.: I don't think you should run Repair Permissions from the install CD, because it contains an older version of OS X: run the utility from your startup volume, instead.

[Powaqqatsi]

Is one of the two accounts in a different language ? It could be a language-conflict. If not I would suggest to go and reinstall AppleWorks (I know that's the quick and dirty solution and I'm not 100% sure if this even works.)

[EnVoy]

I have been having the same issue with QuarkXpress (4.11 (runs in classic)). It runs fine under the user (Admin) it was installed, but it wont run under any other user. I get this:

"You cannot run QuarkXpress on a locked volume [84]."

The volume is not locked (I believe), I have repaired permissions, done fsck, Reinstalled the sys software, etc...

I have even installed Quark under different users, with the same results. Which ever user it is installed under can run it, others cannot.

Permissions are:

Quark:

Owner: (admin account's name) read/write;

Group: admin, read/write;

Others: read/write.



The HD volume is:

Owner: system read/write;

Group: admin, read/write;

Others: read only.


Any ideas?

[Sven G]

Originally posted by EnVoy:
I have been having the same issue with QuarkXpress (4.11 (runs in classic)). It runs fine under the user (Admin) it was installed, but it wont run under any other user. [...]

Maybe it's this problem, which seems to be similar: you could maybe solve the problem by relocating XPress in a folder with read/write privileges all the way, for example in Applications (Mac OS 9) - not sure if that would work, however...

[EnVoy]

you could maybe solve the problem by relocating XPress in a folder with read/write privileges all the way, for example in Applications (Mac OS 9)

It is there!

[kjb]

...well, a reinstall of AW did the trick. The thing I'm most confused about is if a reinstall was the answer, why could one user access the program and all others not?? Isn't this supposedly impossible under OS X? I was under the impression that all necessary application and system level stuff resided outside the home folders of the registered users of the machine. I guess this isn't the case, although I wonder if it's more a result of the notoriously "bad" carbon port of AW to OS X.

I guess it's really no matter to me, I'm cool w/ it working and getting my wife off of my back regarding it.

Cheers all,

Kevin

[Sven G]

Originally posted by EnVoy:
It is there!

Well, then you could try to give the Applications (Mac OS 9) folder read/write privileges also for "other" users (the last item in the Permissions section in the Get Info window); this, of course, would also have effect on the other apps in that folder...

[EnVoy]

Well, then you could try to give the Applications (Mac OS 9) folder read/write privileges also for "other" users (the last item in the Permissions section in the Get Info window); this, of course, would also have effect on the other apps in that folder...

Tried it, doesn't work.....

[Sven G]

Then, probably your only option is to give the user you want to launch XPress administrative privileges: make her/him an administrator, if possible.

[EnVoy]

Then, probably your only option is to give the user you want to launch XPress administrative privileges: make her/him an administrator, if possible.

Can't do that one either, strict rules around here! The wierd thing is, I work on the exact type of machine (dual 1.42 MDD G4) as the problem machine, and Quark works fine across all users! Both machines have the same set of users, set up the same way. I have duplicated the privilage settings of te folders/Quark.app of my machine on the problem machine, still to no avail.

The only thing funky is my machine's OS is factory installed, the problem machine had to get wiped and reinstalled from the Software Install and Restore disk. When OSX was installed, it didn't install Classic, that I had to install seperatly. Kind weird, so I'm going to re-install the OS on the problem machine next...