Path: utzoo!utgpu!watmath!clyde!bellcore!rutgers!mailrus!ames!eos!labrea!agate!violet.berkeley.edu!pete From: pete@violet.berkeley.edu (Pete Goodeve) Newsgroups: comp.sys.amiga Subject: Re: Lattice 5.0 don't work (the way I want it to) Summary: it does for me... Keywords: Lattice 5.0 Message-ID: <18017@agate.BERKELEY.EDU> Date: 8 Dec 88 09:42:02 GMT References: <866@koko.UUCP> <731@sas.UUCP> <168@dms3b1.UUCP> Sender: usenet@agate.BERKELEY.EDU Distribution: na Organization: University of California, Berkeley Lines: 21 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.] 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 --