I've also run into this problem when the current path to the linker/assembler isn't in the environment. With NT I believe that is set in the Control Panel/System Icon/Environment tab. Add the path to MPLAB by extending the PATH variable. It doesn't matter if MPLAB knows about the compiler if the compiler doesn't know about MPLAB and can't find the MPASM stuff. I think some (all?) compilers spawn another process to assemble, thus leaving MPLAB out of the loop. But as Bob said ... I could be wrong... etc.. Dan -----Original Message----- From: Bob Drzyzgula To: PICLIST@MITVMA.MIT.EDU Date: Saturday, August 28, 1999 4:01 PM Subject: Re: Another plea for help >On Sun, Aug 29, 1999 at 01:44:28AM +0100, Steve Thackery wrote: >> >> Command line: "E:\PROGFILE\MPLAB\MPLINK.EXE /o AD.HEX /l C:\MCC\LIB /k >> C:\MCC\EXAMPLES\AD\; C:\MCC\EXAMPLES\AD\AD.O C:\MCC\LIB\C0S17.O >> C:\MCC\LIB\IDATA17.O C:\MCC\LIB\INT756L.O C:\MCC\LIB\P17C756.O >> C:\MCC\EXAMPLES\AD\P17C756L.LKR " > >This all looks to me like a classic current directory >problem. Note that, in the above, "AD.HEX" is the only >file for which no absolute path is specified. > >Dollars to doughnuts you've got a file "AD.HEX" sitting >on one of your hard drives somewhere that you don't >expect. Try using WinNT's Find File function in Windows >Explorer, have it look for files named "AD.HEX" on >"all local hard drives". I bet you'll find at least >two, the one you created from the command line, and >the one that was created by MPLAB; the one that isn't >where you expect would be where the current directory >is for the MPLINK command out of MPLAB. MPLAB probably >has a different concept of the current directory than >MPLINK, thus causing the conflict. > >I could be wrong, but it's something to try anyway. > >--Bob > >-- >============================================================ >Bob Drzyzgula It's not a problem >bob@drzyzgula.org until something bad happens >============================================================