Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!mcnc!ecsvax!kms From: kms@ecsvax.UUCP (Ken Steele) Newsgroups: comp.sys.amiga Subject: Re: problem using "assign" Summary: Thanks, here is a disk setup that works Message-ID: <7152@ecsvax.UUCP> Date: 11 Jun 89 19:30:08 GMT References: <7144@ecsvax.UUCP> <17283@louie.udel.EDU> <7145@ecsvax.UUCP> Distribution: na Organization: UNC Educational Computing Service Lines: 38 In article , shadow@pawl.rpi.edu (Deven T. Corzine) writes: > In article <7145@ecsvax.UUCP> kms@ecsvax.UUCP (Ken Steele) writes: > > > >What seems to happen is this. If L1: is already in the drive, > >then LC exits after the first disk swap (to L2:) with the error that > >it can't find LC2. If L2: is in the drive, then LC exits > >with the error that it can't find LC1. > > >Any suggestions? > > In older versions of Lattice C, it used to Execute() "LC:LC1" instead > of "LC1", so it would not follow the path. This has been changed, but > can cause inconvenience for those with only a floppy drive available. > > > Deven Thanks for the help, Deven. For those of you who need to work on an A1000+512k+2floppies (we prefer to say the classical configuration ;-) here is a setup that 5.0 seems to tolerate. Put the executables (lc, lc1, lc2, blink, etc) AND the compacted includes on the same disk. Put the lib files on another disk. Blink looks to LIB: and has no problem with the disk swap. If you know that you will only need a couple of the included libraries then you can squeeze it down to only 1 disk. I need extra room for another library and kept with the 2 disk setup. > -- -- Ken Steele Dept. of Psychology kms@ecsvax.[bitnet || UUCP] Mars Hill College kms@ecsvax.uncecs.edu Mars Hill, NC 28754