Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!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: John, what now? (Long) Keywords: Lattice 5.0 Message-ID: <168@dms3b1.UUCP> Date: 7 Dec 88 11:41:12 GMT References: <866@koko.UUCP> <731@sas.UUCP> Reply-To: dave@dms3b1.UUCP (Dave Hanna) Distribution: na Organization: Daltech MicroSystems, Dallas Lines: 99 In article <731@sas.UUCP> toebes@sas.UUCP (John Toebes) writes: >In article <866@koko.UUCP> rayz@koko.UUCP (Ray Zarling) says he can't run Lattice C 5.0 except by booting from the Lattice disks. John Toebes replies: >The LC driver program searches the standard path for the compiler using the >Execute() function. On my system, I put the compiler and all other utilites >in the LC: directory and just put that on the path. Note LC: and C: are on >separate volumes. One advantage to doing this is to allow putting all the >commands on a separate disk and add that as necessary. By using Execute() >[and a few other tricks] we are also able to pick up the compiler even if >it is resident. One additional note, the compiler needs to locate the error >messages in s:lcerrs.txt followed by lc:lcerrs.txt We spent quite a bit of >time examining this issue to see what would work best and this allows one to >make the compiler resident, still have LC: to a separate floppy, but have the >error messages in the S: directory where most configuration files go. > >As to solutions to finding out what is wrong, you should check to ensure that > 1) The programs are in LC: > 2) LC: is on the path. > path lc: add > 3) Try running them from the CLI with: > LC1 <----- NOT LC:LC1 > LC2 <----- NOT LC:LC2 > 4) Make sure you aren't using a shell that setfunctions Execute() in a > non compatible way. We know that the standard Amiga Shell and CLI as well > as WShell are compatible with allowing the resident commands to work. > 5) If you are running REZ, try it without it once. There have been reports > of problems with REZ misrecognizing the type of program and then > attempting to 'patch' the resultant executable on loading. > 6) If the above fail, check to see how badly fragmented your memory is. > It is possible that there is something in your startup sequence that > is eating memory. >If all the above fail, I will be just as stumped as tech support. The compiler >and driver program use as vanilla an interface into the operating system as >is possible. It does not count on any internal interfaces and does run under >1.1, 1.2 and 1.3. [I haven't loaded 1.0 in a while but suspect it will work >under it too]. Okay, I too am having problems. Maybe I should have sent this E-Mail, but I figure I'm probably not the only one. Configuration: A2000, two floppies, no Hard drive, 1 Meg Ram, AmigaDos 1.2 with DMouse, cron, SPUDclock and NAG running in background. Running Dillon/Drew Shell2.07M I made a disk called 'Comp:' with a c directory containing lc, lc1, lc2, lcerrs.txt and lcerrs.deutsch. Also on Comp: is an include directory with the entire CompactH directory copied to it. I run the following commands: cp c:run ram: cp c:assign ram: assign LC: Comp:c assign INCLUDE: Comp:include assign QUAD: RAM: path LC: add cd SourceCode: (where my source file is) assign C: ram: LC hello The compiler puts up its banner, grinds around on the disks for a little bit, says "Compiling hello.c", and then hangs. DMouse is unresponsive (won't bring up a new shell). I brought up a new CLI by clicking on the CLI Icon and ran Xoper, which seemed to show something consuming 100% of CPU dispatch cycles. Starting on your checklist, I was already doing 1 and 2 (the commands are in LC (or at least a directory that LC: is assigned to), and it is on the path. To make sure of 4 (nothing that Setfunction's Execute() ), I got rid of all my background stuff and ran from a straight CLI (broke out of my Startup-Sequence.) Same symptoms. I'm not running REZ. And, since I'm running this right after my Startup, I don't think memory is too fragmented. However, I can execute the same thing as above, except substitute LC1 hello LC2 hello and it runs to completion. Oh, and it does run if I boot disks 1 and 2 of the Lattice Distribution and run from that. I had just about decided that it needed 1.3 to run, when I saw your post that it would run from 1.1, 1.2 or 1.3. I'm going to make up a 1.3 configuration when I get time, but what do I do in the meantime? Any help would be greatly appreciated. >/*----John A. Toebes, VIII usenet:...!mcnc!rti!sas!toebes-----*/ -- 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 |