Re: problem with scripts in OS X
Re: problem with scripts in OS X
- Subject: Re: problem with scripts in OS X
- From: David Simerly <email@hidden>
- Date: Mon, 24 Sep 2001 09:56:04 -0700
- Url: http://www.digital-native.com
on 9/24/01 4:21 AM, JollyRoger at email@hidden wrote:
>
> After installing a script in OS X using my own installer program ,
>
> regardless of whether its saved as run only or not , it fails to launch.
>
> I have tried changing permissions , all to no avail .
>
> The only way to make it run is to re-compile it - which is obviously less
>
> than acceptable.
>
> any ideas / do you (Chris) know why this is happening?
>
>
<sarcasm>
>
Because Mac OS X is an incomplete version of a brand new OS that was
>
released to the public way too early?
>
</sarcasm>
>
>
Seriously, the state of AppleScript in Mac OS X is unacceptable. Half of the
>
stuff just doesn't exist. And half of what does exist doesn't work like it
>
should! Sorry for the rant; but it's irritating to see this coming from
>
Apple.
I think it's more likely that this is an operating system based on UNIX,
with which many Mac users (myself included), don't yet have a lot of
experience. But my short experience with it so far tells me that the problem
here is probably one of file owner permissions.
I've noticed that when copying scripts across the network, or when installed
from an installer that doesn't do its job completely, the file can end up in
the new location with the old owner still assigned, and read-only or less
permissions for everyone else. The result is that the script won't launch.
Try setting the permissions on the master copy of to script to Read/Write
for owner, group, and everyone, and then run your installer again. I bet it
will launch then.
DS
______________________________________
Digital Native
Your guide through the virtual jungle.
______________________________________
"Do the right thing -- it will gratify some people and astonish the rest."
-- Mark Twain