Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!usfvax2!jc3b21!fgd3
From: fgd3@jc3b21.UUCP (Fabbian G. Dufoe)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice LC question (Was "assign problem")
Message-ID: <674@jc3b21.UUCP>
Date: 12 Jun 89 06:05:53 GMT
References: <7146@ecsvax.UUCP>
Organization: St. Petersburg Jr. College, FL
Lines: 51

From article <7146@ecsvax.UUCP>, by kms@ecsvax.UUCP (Ken Steele):
> 
> 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:,

     LIB: should be assigned to L2:Lib and INCLUDE: should be assigned to
     L2:CompactH (assuming you're running version 5.0 or later).

> and I added LC: to the search path. The source file is in sys:src.
> SYS: is in DF0: and L1: is in DF1:. I then proceed to run the
> ever-popular "lc -L sys:src/hello". After the sign-on garbage, I am
> asked to insert L2: in ANY drive. If I put L2: in DF0:, then
> compilation proceeds (with much-o disk swapping). If I put L2: in
> DF1: (removing L1: of course) THEN I get the big screen-flash abort,
> with the complaint that "LC2 is unknown command."

     This is a characteristic of the way "Path" works.  If a directory in
     the search path is not mounted the command just skips it instead of
     asking you to insert the necessary disk.  The "lc" command simply runs
     "lc1" followed by "lc2" (and followed by "Blink" if you specify "-L").
     If "lc" were a single command you wouldn't have the problem because it
     would be loaded before you removed L1:.  But when you replace L1: with
     L2: you remove the directory containing "lc2".  Then "lc" tries to
     call "lc2".  Although the directory where "lc2" resides would be
     searched if the disk were mounted, the "Path" command won't advise you
     to insert the disk.  It just skips the missing directories and comes
     back with an "unknown command" message.

> 
> It seems as if LC is looking in currently mounted volumes for
> LC2 instead of the logical device LC:.  Has any else noted this?
> 
> If true, can LC be patched/zapped to look for lc:lc1 and
> lc:lc2 _safely_?

     In a word, no.  It would be an easy fix for Lattice, though, since
     they have the source code.  

> 
> Thanks for the help.

--Fabbian Dufoe
  350 Ling-A-Mor Terrace South
  St. Petersburg, Florida  33705
  813-823-2350

UUCP: ...uunet!pdn!jc3b21!fgd3