Sorry guys, but I'm still struggling with something that is presumably
incredibly simple.  In fact it's driving me completely mad.  I really would
appreciate it if someone could shed some light on this as I'm totally
stumped.

I'm running NT4, and I wonder if this may have something to do with the
mystery.

I've got MPLAB 4.12 and have installed C17 as well.  MPLAB is installed on
my main NT drive, which is E:, in the following directory:
E:\PROGFILE\MPLAB.  I've tried installing MCC in various places, including
the E: drive, and currently it's on my old DOS drive in C:\MCC.

I'm working through the demo in the Compiler User's Guide in section 2.7.
Basically this involves combining a .c file, four .o files, and a .lkr file.
I've followed the instructions to the letter, and when I come to build the
project here is what happens.....

------------------------------------------
Building AD.HEX...

Compiling AD.C:
Command line: "C:\mcc\bin\mcc17.exe /w2 /Ms /p=17C756 /iC:\MCC\H\
C:\MCC\EXAMPLES\AD\AD.C"
MPLAB-C17 v2.30 Copyright 1997, 1998 Microchip Technology Inc.
Errors:    0
Warnings:  0

Linking:
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 "

MPLAB is unable to find output file "AD.HEX".

Build failed.
------------------------------------------

The compiler is seemingly working fine, and I can see the AD.O file that it
generates.  The problem apparently arises with the linker.  Whatever is
going wrong, I can confirm that the linker does *not* generate the AD.HEX
file.

But here is some weird shit: I start up a command prompt, and 'cd' to the
C:\MCC\EXAMPLES\AD directory, where my 'C' source file is.  So the command
prompt looks like this:

C:\mcc\examples\ad

OK, so I'm in the directory where my ad.c and ad.o files are.  I can do a
dir and see them.  Nothing weird so far.

I then type in the linker command line *exactly* as shown in the list out
above (without the quotation marks) - in fact I cut and paste it to be
sure - and the linker works fine and generates the AD.HEX file!!

In other words, it works from the command prompt but not from within MPLAB.
Even more weird: if I attempt a build again from within MPLAB, it *still*
says "unable to find output file AD.HEX" even though that file is now
sitting there quite happily in the C:\mcc\examples\ad directory.

Even better: if I import the HEX file into MPLAB I can single step through
it and everything.  In other words it behaves like a successful build.  But
I can't build the damn thing from inside MPLAB.

It's a major hassle having to go out to the command line each time I want to
do a build, and I cannot believe it's necessary.  I must be doing something
wrong that's so simple it's staring me in the face, but I'm damned if I can
spot it.

Can any of you give me some pointers before I go completely mad?  I still
half wonder if this is some subtle incompatibility with NT4.  Do any of you
use NT4?

Oh yes: here are the lines from my "Edit Project" dialogue box:

Target Filename: ad.hex
Include Path: c:\mcc\h
Library Path: c:\mcc\lib
Linker Script Path: c:\mcc\examples\ad

Many thanks in anticipation!

Steve

Steve Thackery
Suffolk, England.
Web Site: http://www.btinternet.com/~stevethack/