• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How to prevent Classic from starting?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to prevent Classic from starting?


  • Subject: Re: How to prevent Classic from starting?
  • From: Jeffrey Mattox <email@hidden>
  • Date: Thu, 18 Dec 2003 02:26:00 -0600

Almost. If the stuff that I do involves a Keychain Scripting command, then the compiler complains. For example:

tell application theApp
name of current keychain <-- causes compile error
end tell

I can do this to get it to compile without errors:

tell application theApp
using terms from application "Keychain Scripting"
name of current keychain
end
end tell

But am I still risking Classic loading at run time or, worse, a dialog box asking the user to locate the Keychain Scripting application?

Jeff


At 1:41 AM -0500 12/18/03, Graff wrote:
Here's how to get it to work for any boot volume:
----------
set theApp to ((path to library folder from system domain) as text) & "ScriptingAdditions:Keychain Scripting.app"
tell application theApp
-- do stuff here
end tell
----------

I believe that should do it.

- Ken

On Dec 18, 2003, at 12:05 AM, Jeffrey Mattox wrote:

At 7:59 PM -0800 12/17/03, Paul Berkowitz wrote:
On 12/17/03 7:34 PM, "Jeffrey Mattox" <email@hidden> wrote:

Sometimes my script attempts to start Classic. I've narrowed it down to:

tell application "Keychain Scripting"

How do I force this to remain in OS X?

I've tried tell application "Keychain Scripting.app" -- want OS X
but the compiler changes it back to "Keychain Scripting".

I suppose I could delete all of my OS 9 files, but my users might not
want to do that. :-)

Use the full path to the OS X Keychain Scripting application file in the
'tell' command.

The fact that these shenanigans are required is one of the annoying things about AppleScript. Things that work for months suddenly fail. (does AS = Annoying Shenanigans?)

This works on my system:

tell application "Macintosh HD:System:Library:ScriptingAdditions:Keychain Scripting.app:"

But I won't know the name of the startup disk. I've tried every form I can think of using "of startup disk" without success. I'm stuck.
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: How to prevent Classic from starting?
      • From: Walter Ian Kaye <email@hidden>
References: 
 >Re: How to prevent Classic from starting? (From: Paul Berkowitz <email@hidden>)
 >Re: How to prevent Classic from starting? (From: Jeffrey Mattox <email@hidden>)
 >Re: How to prevent Classic from starting? (From: Graff <email@hidden>)

  • Prev by Date: Re: Strange iDisk name (e.g., name-1)
  • Next by Date: Re: First-class procedures in AS
  • Previous by thread: Re: How to prevent Classic from starting?
  • Next by thread: Re: How to prevent Classic from starting?
  • Index(es):
    • Date
    • Thread