Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!csd4.milw.wisc.edu!mailrus!ronin!dave From: dave@ronin.cc.umich.edu (Dave Koziol) Newsgroups: comp.protocols.appletalk Subject: Re: MultiLaunch programs on Apple Share Message-ID: <1119@mailrus.cc.umich.edu> Date: 22 Jun 89 17:21:54 GMT References: <3877*kenw@noah.arc.cdn> Sender: usenet@mailrus.cc.umich.edu Reply-To: dave@ronin.cc.umich.edu (Dave Koziol) Organization: University of Michigan Computing Center, Ann Arbor Lines: 57 UUCP-Path: mailrus!ronin!dave Larry Pickett writes: >Somewhere I've seen reference to a program which will control the number >of copies of a program present on a file server (AppleShare) that can >be used at one time. We have 13 Mac's on a net and have purchased >10 copies of MSWord. I can either create 10 separate copies on separate >server disks or use some sort of control program so everyone uses the >same server disk but we don't exceed our limit. Any information? >Acknowledge-To: Ken Wallewein writes: > And if one says it can't be done -- balderdash! I've thought of reasonable >methods which will function with or without networks, while not diminishing the >utility of the product. If I can do it without a lot of effort, there must >be a number of methods backed by solid theoretical study. Here at the University of Michigan Computing Center we have written such a program. The program is called MultiLauncher, it was originally written by Shane Looker, and now I'm responsible for it maintanance. It works like this, you run the MultiLauncher Server either ontop of AppleShare, or on a dedicated mac (we run it on AppleShare). The applications are replaced with "fake" apps which look like the real thing, but instead of just running, it requestes the program from the server. The server then responds back with the launcher path if the program is available, or an error message to be displayed. (ex "All copies of MacXXXXX are check out, try again later.") A DRVR is also started which sends a packet to the server every 30 secs, when the app is quit the DRVR sends a check-in. If the users shuts the mac down, the server times out (in our case after 90secs, and checks the application back in). The only current major problem with it, is that it doesn't work well under MultiFinder. The issues I'm currently addressing in MultiLauncher are o Software Packages. For example Systat has 12 different apps, if you own 5 copies, only 5 total copies of those apps can be check out. o MultiFinder Compatibility. Right now the DRVR doesn't get killed when your quit the apps, so it doesn't get checked in until the mac is booted. o A Local copy of the program. For example, some of your users have hard disks, but you still want to include their programs in your total number of copies, and they want the speed of running the programs from their local hard disk, rather than over the network. (Yes, I know running application over the network is slow, but for some large apps they wont even fit on a 2 drive Plus. And have you ever looked at the cost of buying over 1800 hard disks? (That's how many public macs we have!) Besides, I didn't design the program, I *maintain* it... :-) ) Questions or comments about MultiLauncher can be directed to MultiLauncher_Support@um.cc.umich.edu I'm currently discussing distribution of MultiLauncher with my boss, so e-mail the above address if you'd like to see it. Dave Koziol | Internet: koziol@um.cc.umich.edu Computing Center | Bitnet: UserDave@umichum.bitnet University of Michigan | UUCP: ...!umix!um.cc.umich.edu!koziol | GEnie: D.KOZIOL1 ------------------------------------------------------------------------- Disclaimer: "They don't pay me enough to need a disclaimer"