| Click here to select a new forum. |
| AppleScript strange error |
Posted by: feeef on 2014-11-11 12:42:26 I have tried to do some scripting with applescript on my 9500 (System 7.6.1) and I am always having the same error. This is a strange one and it is always coming back when I try to run a script (even the most simple script).
Has anyone ever had this error? Is it something that wasn't installed correctly on my system?

|
Posted by: Elfen on 2014-11-12 07:46:40 Does this error happen with other applications?
As I remember, you do not assign Finder as an application, but do an exit or quit to go to it.
|
Posted by: feeef on 2014-11-12 12:58:51 This script is generated by the recording button and just going to the finder. It works well on Mac OS 8.1.
I tried different scrips and I always get an error. However, when a script is pre-compiled, everything works well. It is just the compiler that fails here 🙁
Maybe something is messed up in my system... I will try to do a fresh install of the same system on another drive and see if it works ok on that one.
|
Posted by: feeef on 2014-11-18 06:26:29 I tried to do a fresh install of 7.6.1 and had the same error. I couldn't even compile the default example scripts from the install.
I tried to do a fresh install from the 9500 CD install (7.5.2), I also tried to do a minimal system install with just applescript... I always got the same error when I try to compile a script from the script editor.
Does anyone have a 9500 running system 7 to see if everything works?
I was thinking that AppleScript on system 7 is not PowerPC native and the 68 emulator fails somewhere on my machine...
FYI, this Mac had a G4 700MHz upgrade and now I is running on a G3 500MHz (which handles my SATA card correctly). It has the same behaviour with both upgrades. I have a 604e 233MHz card so I should try with this one at some point to see if the problem comes from the processor...
|
Posted by: IPalindromeI on 2014-11-18 09:33:54 if the 68k emulator was the problem, you'd be bombing VERY early, as System 7 is mostly 68k code
|
Posted by: feeef on 2014-11-18 10:54:10 So I don't understand at all where this is from 🙁
It looks like a software problem but only with this Mac and with System 7 (all of them)... :-/
|
Posted by: IPalindromeI on 2014-11-19 03:19:21 I think it's the CPU - can you remove the accelerator and try without?
|
Posted by: feeef on 2014-11-19 04:06:20 Well, I have tried 100 different things with no success, and at some point I removed some ram sticks, re-installed the system and it works now! 🙂
I think I had some bad RAM sticks so I will try to get some new ones. I think OWC still sells those 128MB for quite cheap.
How much RAM can system 7 handle? Can it go to 1.5GB ?
|
Posted by: Elfen on 2014-11-19 07:44:56 What ever Apple has crippled the 9600 to handle RAM is the amount you have to play with. The system as far as I know can handle as much RAM as you can throw at it. The more you throw at it, the happier it will be.
|
Posted by: feeef on 2014-11-19 07:55:24 Thanks Elfen, I may go for the 12 sticks then! 🙂
|
Posted by: feeef on 2014-12-18 00:47:54 I come back to this post as buying new RAM sticks brought back the issue.
I have made some investigations, I tried 2 different 9500 motherboards, I tried many different memory sticks and it looks like the applescript engine on system 7 bugs when there is more than 512MB of RAM in any case.
The problem is that each time I made it bug with too much RAM, even after removing the excess RAM I had to re-install the system to make it work again.
Everything works fine under Mac OS 8 and 9 so it is something to do with 7. (7.5 and 7.6 have the same result)
There may be a fix or something I missed here because the 9500 and the 9600 officially supported more than 512MB of RAM and both shipped with system 7. |
Posted by: feeef on 2015-01-20 01:25:06 It seems I found a solution to that so I should be able to use the 1.5GB of RAM of my 9500 with 7.6.
I just replaced the AppleScript and AppleScript lib extensions with those coming from a Mac OS 8.1 install. It looks like it is working well so far. 
|
| 1 |