On Mon, 15 Dec 1997, Richard Rathe wrote: >On 12/15/97 Bart Lateur wrote: > >>Droplets fail to launch MacPerl from a network drive, if it wasn't >>running. BTW that's a MacOS problem (7.5.x), don't ask Matthias to fix >>this. >> >>Everything works fine if MacPerl was already running. > >I see the same problem with "low memory" on my PowerBook 520 with System >7.1. The Finder reports "non enough memory" if a droplet starts MacPerl >when other apps are running. If I start MP first and THEN use the droplet - >no problem. I assume these two phenomena are related. Er... not quite. Although the behaviour is similar, the cause is different. And although I think this is pretty elementary, I think I should clear this up. The reason why droplets fail to launch MacPerl on a network drive, is simply because MacOS (7.x) doesn't look on the network drives for applications. You'll get the same effect, and this time it IS related, whenever an app is not on a local drive but on a network drive, and not running: 1) when opening a document by using cmd-O or doubleclicking 2) when using Applescript (or AppleEvents) to activate the app, e.g. with the Applescript line tell application "MacPerl" to activate Although not tested lately (I haven't had access to a network in weeks), I think this is correct. Bart. ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch