Path: utzoo!utgpu!watmath!clyde!att!rutgers!mit-eddie!killer!gtmvax!dms3b1!dave
From: dave@dms3b1.UUCP (Dave Hanna)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice 5.0 don't work (the way I want it to)
Summary: Make sure EndCLI is available!
Keywords: Lattice 5.0
Message-ID: <169@dms3b1.UUCP>
Date: 8 Dec 88 23:07:13 GMT
References: <866@koko.UUCP> <731@sas.UUCP> <168@dms3b1.UUCP> <18017@agate.BERKELEY.EDU>
Reply-To: dave@dms3b1.UUCP (Dave Hanna)
Distribution: na
Organization: Daltech MicroSystems, Dallas
Lines: 47

In article <18017@agate.BERKELEY.EDU> pete@violet.berkeley.edu (Pete Goodeve) writes:
>Just in case it helps shed any light, I'm running 5.0 without any trouble.
>My configuration is A1000 with 4.5M memory and two floppies.  VD0: is SYS:,
>with C: and all the other essential system directories there.  [Is't possible
>by the way, that some people having trouble have omitted to provide L:,
>LIBS:, DEVS: or something on their C system disk? ...just a thought.]
                 ^^^^^^^^^
		 that's it - something.
>I compile in a subdirectory of VD0:, but rather than transfer the compiler
>files to RAM, I run them off two floppies; DF0: contains the compiler
>executables, DF1: has the includes and headers.
>
>I have a command script that basically sets things up as follows:
>
>	assign LC: df0:c
>	assign LIB: df1:lib
>	assign INCLUDE: df1:CompactH
>	path LC: add
>
>The original C: is always available of course with all the normal system
>commands (especially RUN, for lc's sake).  All works fine.  Where's the
>difference?  I dunno.
>					-- Pete --

After posting article <168@dms3b1.UUCP>, I spent another 4 or 5 hours
experimenting last night, and finally isolated it.  I'll spare the 
gory details of how I arrived at this conclusion, but if EndCLI is
available to it, it runs, otherwise it doesn't.  (Why EndCLI?  Beats
the h*** out of me.)  This would be masked if you are running with a 
complete C: directory available, either on HardDisk or a large RAM:.  
Since I have a stock 2000, I don't want to put an entire C: directory 
in RAM:, and I want to have a disk with my source code on it.  
That means I need to get the compiler and include files all on one disk,
so the set-up described above doesn't work very well.

I now copy c:Run and c:EndCLI to RAM: in my startup, and it seems to
run fine.

Now if I can just get make to work right....  But that's another story.


   Dave Hanna.
-- 
Dave Hanna,  Daltech MicroSystems    |  "Do or do not -- There is no try"
P.O. Box 584, Bedford, TX 76095      |                        - Yoda
(214) 358-4534   (817) 540-1524      |
UUCP:  ...!killer!gtmvax!dave        |