Path: utzoo!utgpu!attcan!uunet!pdn!boake2!jc3b21!fgd3 From: fgd3@jc3b21.UUCP (Fabbian G. Dufoe) Newsgroups: comp.sys.amiga.tech Subject: Re: How applications can autoinstall (a little long) Message-ID: <526@jc3b21.UUCP> Date: 15 Dec 88 23:48:55 GMT References: Organization: St. Petersburg Jr. College, FL Lines: 28 The problem I see in this discussion of s:Startup-Assigns is I don't want the assignments hanging around indefinitely. For one thing, another application might use the same logical device name. So when I start an application that requires assignments I execute a little script file that does the assignments. For the Lattice C compiler, for example, I execute StartLC. StartLC does several assigns (assign LC: Lattice_C_5.0.1/C, assign QUAD: RAM:, assign INCLUDE: Lattice_C_5.0.2:lib, etc.) When I'm through with that application I execute another script file called EndLC which deletes those logical device assignments (assign LC:, assign INCLUDE:, assign QUAD:, etc.). That restores my environment to its pre-StartLC condition. Now that I have IconX in WB1.3 I can execute those files from the Workbench. Of course, the foregoing doesn't solve the problem of how to oopy an application to your hard disk and have the assign statements in the script files changed automatically. But I guess you could write a script file that would copy all the application's files to a directory name specified as a parameter. Then it could write a StartApplication script file using that same directory. --Fabbian Dufoe 350 Ling-A-Mor Terrace South St. Petersburg, Florida 33705 813-823-2350 UUCP: ...codas!usfvax2!jc3b21!fgd3 ...uunet!pdn!jc3b21!fgd3