Script losing their paths to Standard Additions
Script losing their paths to Standard Additions
- Subject: Script losing their paths to Standard Additions
- From: Lyle Petro <email@hidden>
- Date: Fri, 10 Aug 2001 08:57:44 -0600
Hi,
I am hoping someone can help me with a rather baffling problem (for me
anyway). I have a number of scripts that are running on many Macs
here. I have been in the process of reinstalling both the system
software and program software on these machines as I find time (due to a
desire to repartition large drives on these Macs). On most of the
machines, this has proceeded with no problem. On a few however, the
scripts have started to behave erratically. Occasionaly when they run,
they will display an error such as "<<script>> doesnt understand the
<<earslvol>> message". If I click OK and try again, the error comes up
again and again. However if I click edit and thereby bring up the
script in Script Editor, the offending command is highlited.
Confusingly, to me, the offending command is displayed as "current
date". I would have expected it to display raw event codes if this was
a problem. Yet, I know this is in the Standard Additions, so it should
always be available (and yes, it is in the Scripting Additions folder of
the offending Mac). If after opening the script in Script Editor, I
simply close Script Editor, the scripts run fine. Any ideas. Thanks.
Lyle Petro
Saskatoon StarPhoenix