At 06:55 -0600 on 6/4/97, Matthias Ulrich Neeracher wrote: > "Richard Johnson" <rjj@medialab.com> writes: > >I'm trying to use Mac Perl to fire up a set of distributed apps on idle > >workstations overnight. > ... > > ... > >Even better, is there a way to specify the authentication info (user name > >and password) for the program link on the remote machine, without popping > >up a dialog on an unattended machine? > > How about installing Peter Lewis' Script Daemon on the remote machine? This > allows you to connect to the Telnet port (23) of the Machine, send the login > & password and then execute the AppleScript locally. Excellent suggestion. I'd have to know the owner name and password on each Mac, however, as Script Daemon 1.0.1 doesn't (yet?) allow logins as anyone else. At 03:54 -0600 on 6/5/97, ziege@ito.umnw.ethz.ch wrote: > Try the System Extension "AutoGuest INIT 2.0". The user documentation says: > ... > "Solution: If guest access is available on the target machine, always log > "on as a guest without bringing up the authentication dialog box. > ... Another excellent suggestion. I found the AutoGuest INIT and code resource (version 2.0a1) on http://hyperarchive.lcs.mit.edu/HyperArchive.html I think I'll try both ways, given that some of the daytime users of the Macs will certainly object to our standardizing their owner names and passwords :-). Hopefully AutoGuest still works under 7.6.1. (Maybe it even works under 8.0b6?) Failing any of this working, I might just bite the bullet and write my own background app to listen on a particular UDP port, and launch the renderer for me. That way I'll be able to launch it from a Perl script on any machine I happen to have running, rather than having to do it from one that groks AppleScript. Richard ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch