>Sometimes after running MacPerl for months on a machine it starts to >take about half a minute to compile script. The run fast as ever, but >first the whole machine is unresponsive... It makes all those nifty >little droplets major pains. > >Any clues? >Christian > At the risk of suggesting what may already be obvious to you... Sometimes it seems to help to quit the MacPerl application after running certain scripts. But relaunching the MacPerl application takes time. This has the added benefit of of reseting MacPerl's memory, which could help avoid hassles with memory complications. If MacPerl is not already opened on the computer when a file is dropped on a MacPerl droplet, or when a droplet is double clicked, then the MacPerl application automatically launches before it even looks at the code contained in the droplet. This takes time, too. Have you recently adjusted the amount of memory allocated to the MacPerl application on your mac? Are you using virtual memory? In a posting earlier this month "John-Michael Keyes" <jk@syndicatedmedia.com> said MacPerl "seems" to run scripts faster with virtual memory off. Hope this helps, David Seay # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org