Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!ames!sun-barr!newstop!sun!stpeter.Eng.Sun.COM!cmcmanis From: cmcmanis@stpeter.Eng.Sun.COM (Chuck McManis) Newsgroups: comp.sys.amiga.tech Subject: Re: Lattice 5.05 with WShell... Keywords: lattice wshell hmmm... Message-ID: <136986@sun.Eng.Sun.COM> Date: 10 Jun 90 07:58:30 GMT References: <267063fd-6b6comp.sys.amiga.tech@tronsbox.UUCP> Sender: news@sun.Eng.Sun.COM Organization: Sun Microsystems, Mt. View, Ca. Lines: 21 In article <267063fd-6b6comp.sys.amiga.tech@tronsbox.UUCP> (Bill Cavanaugh) writes: >I attempted to use the Lattice "lc" command to compile a file that was in >RAM:. I typed "lc -Lm file.c", and got the message "File RAM:-Lm.c does not >exist. Try again." >What's the deal? It works with a standard CLI, but not with WShell/ConMan. >Is there some path expanding going on? Is there some way I can turn it off? This is the first really bogus bug that Bill Hawes has ever subjected me to. It took me about 3 hours to figure out what the problem was. Basically, in the WSHell update there is a program in rexx: called lc.rexx which is a _silly_ frontend for Lattice C with the same name as the lattice command. It takes all different arguments. (Much wordier ones too) Anyway, either delete it or rename it to something like rexx:boguslc.rexx and that will "solve" your problem. -- --Chuck McManis Sun Microsystems uucp: {anywhere}!sun!cmcmanis BIX: Internet: cmcmanis@Eng.Sun.COM These opinions are my own and no one elses, but you knew that didn't you. "I tell you this parrot is bleeding deceased!"