Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!xanth!mcnc!rti!sas!toebes From: toebes@sas.UUCP (John Toebes) Newsgroups: comp.sys.amiga Subject: Re: Lattice 5.0 don't work (the way I want it to) Keywords: Doesn't use LC: assignment Message-ID: <731@sas.UUCP> Date: 5 Dec 88 14:45:26 GMT References: <866@koko.UUCP> Reply-To: toebes@sas.UUCP (John Toebes) Organization: SAS Institute Inc, Cary NC Lines: 46 In article <866@koko.UUCP> rayz@koko.UUCP (Ray Zarling) writes: >I just got my upgrade to Lattice C v5.0, and I am bitterly disappointed! >Yes, it seems to have all the goodies as advertised. Yes, it produces >executables that seem to be typically 15% smaller than under 4.01. BUT... >The only way I can run it on my system is to boot from the compiler disk! > >But 5.0 now requires the compiler passes lc1 and lc2 to be in your C: >directory! (I tried putting the subdirectory with the compiler on the >AmigaDOS path, but that didn't help.) 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]. /*---------------------All standard Disclaimers apply---------------------*/ /*----Working for but not officially representing SAS or Lattice Inc.-----*/ /*----John A. Toebes, VIII usenet:...!mcnc!rti!sas!toebes-----*/ /*------------------------------------------------------------------------*/