MACSCRPT Archives

January 2006

MACSCRPT@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"John A.M. Darnell" <[log in to unmask]>
Reply To:
Macintosh Scripting Systems <[log in to unmask]>
Date:
Tue, 24 Jan 2006 07:53:22 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (55 lines)
Another option, kludgy in its approach, but with a strong likelihood of 
working is to save the scripts as text on OS9 and then reopen them as 
scripts in OSX.

R,

John A.M. Darnell
Project Leader
Internal Software Development
Walsworth Publishing Company

Trivia question:  In Robert Heinlein's Children's classic, "The Star 
Beast," Lummox was growing what as a hobby?



Daniel Jalkut <[log in to unmask]> 
Sent by: Macintosh Scripting Systems <[log in to unmask]>
01/24/2006 07:49 AM
Please respond to
Macintosh Scripting Systems <[log in to unmask]>


To
[log in to unmask]
cc

Subject
Re: OS9 'Classic' compiled Applescripts can't be read on OSX. Any 
workarounds or solutions?






It sounds like you've lost some information.  Are the CD and USB 
Flash drive formatted with HFS+? You might be losing the resource 
fork in the transition.  If possible, try creating an archive of the 
items on Mac OS 9 (e.g. with Stuffit) and then unstuff them on OS X.

Daniel

On Jan 23, 2006, at 12:14 PM, Simon Brown wrote:

> I've only
> recently upgraded to OSX and was surprised to find that all the OS9
> compiled scripts that I transfer either from CD or USB Flash drive 
> show up
> as Terminal documents, but can't be opened with Terminal, Script 
> Editor or
> Script Debugger. I tried using the OS9 version of Script Editor in the
> Classic environment but without success. It seems that the files just
> aren't recognised as valid Applescripts.

ATOM RSS1 RSS2