Path: utzoo!attcan!uunet!cs.utexas.edu!rutgers!sun-barr!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice LC question (Was "assign problem")
Keywords: looking for lc?'s in all the wrong places
Message-ID: <109395@sun.Eng.Sun.COM>
Date: 12 Jun 89 01:44:11 GMT
References: <7146@ecsvax.UUCP>
Sender: news@sun.Eng.Sun.COM
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 21

In article <7146@ecsvax.UUCP> kms@ecsvax.UUCP (Ken Steele) writes:
>It seems that the Lattice LC is not maintaining the correct
>directory path to lc1 and lc2.  Here are the symptoms.

>lc, lc1, lc2, blink are in L1: (no subdirectory).  Libs and includes
>are in L2: (in appropriate subdirectories). LC: is assigned to L1:,
>INCLUDE: and LIB: are assigned to L2:, QUAD: is assigned to ram:,
>and I added LC: to the search path. The source file is in sys:src.

This is a "feature" of the path command. When an unmounted volume is
in the path, it is skipped rather than giving you lots of "insert volume
XX:" messages. Sometimes that is desirable, other times it isn't. The
solution to your problem is probably to make LC1 and LC2 resident. If you
have the ram of course. If not, then you will need to put some stuff like
LC2 in the mounted disk. 


--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.
"A most excellent barbarian ... Genghis Kahn!"