Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!oliveb!pyramid!comdesign!ivucsb!dan From: dan@ivucsb.UUCP (Dan Howell) Newsgroups: comp.sys.amiga Subject: Re: Arp.library Message-ID: <502@ivucsb.UUCP> Date: 30 Jan 89 00:47:42 GMT References: <8901162138.AA11702@jade.berkeley.edu> Reply-To: dan@ivucsb.UUCP (Dan Howell) Organization: The Audio Club at UCSB, Isla Vista, California Lines: 12 In article <8901162138.AA11702@jade.berkeley.edu> MOLNARRM@UREGINA1.BITNET (Dennis Gorrie) writes: |Is there a way I can set ARP.library in memory permanenly to avoid this? I'm not sure about this, but somebody correct me if I'm wrong. I think making an ARP command resident (using WB 1.3 resident, not ARP resident) will keep arp.library in memory. At least I think this is the case, because I make a few commands resident in my startup sequence, and have never had a problem running and ARP commands even if the WB disk is removed. Is there any other reason that I might have never encountered this problem? -- Dan Howell <...!apple!comdesign!ivucsb!dan>