Re: Problems with Smile 1.8.4 and system 9.2.2
Re: Problems with Smile 1.8.4 and system 9.2.2
- Subject: Re: Problems with Smile 1.8.4 and system 9.2.2
- From: Paul Berkowitz <email@hidden>
- Date: Fri, 11 Jan 2002 12:15:12 -0800
On 1/11/02 11:33 AM, "Rob Jorgensen" <email@hidden> wrote:
>
On 01/11/02, Phil Calvert commented:
>
>
> Every since I upgraded to 9.2.2 almost none of the menu commands work. I can
>
> select them in the menu (they're not dimmed out) but nothing ever happens
>
> afterward. (i.e. I'll select the find command but the find dialog never
>
> shows up.)
>
>
>
> When I try to set the preferences I get the message "File Mr. iBook:Desktop
>
> Folder:downloads:Smile1.8.4US:Smile :More stuff:Preferences wasn't found"
>
> even though I can follow that path and find that file in question.
>
>
Have you deleted the prefs file to see if a new one could be created?
There's a serious problem with all AppleScript in OS 9.2.2 - but not for
everyone. There must be a conflict between AS 1.8.1, either with a scripting
addition, or with an extension, that makes scripts time out. It's being
investigated by Apple. I can't use scripts at all in applications (like
Entourage) that run scripts from the application in OS 9.2.2. Smile runs
almost completely on scripts run by itself. When you start Smile, it runs a
series of initializing scripts. They're obviously getting stuck. It's not
Smile's fault, and there's nothing Emmanuel can do about it. If there were,
you should be writing him directly: Smile is "feedbackware", as you know.
Since this is something that doesn't affect everyone, maybe you might want
to help out by removing all your 3rd-part osaxen except Satimage and
rebooting. If everything works again, start adding osaxen back in until you
find a culprit. If it doesn't help to remove osaxen (and - who knows- maybe
Satimage osax is one of the problems?) start with only OS 9 All extensions
and see what happens, then start adding extensions back until you find the
culprit.
I'd do it myself, except I'm in OS X full time at the moment. I only
discovered the problem accidentally when I booted into OS 9 and upgraded to
9.2.2 to help a user.
But people without the problem shouldn't underestimate its extent. It's
terrible. Consider yourself very lucky not to have it. If you haven't
upgraded to 9.2.2, don't - until this problem is solved.
--
Paul Berkowitz