>I don't agree with this one at all. The IDE offers full path and library >searches for all object modules and you can format the exact location for >each one. So please explain WHY it is the ONLY way to do it. Of course it Well, Dennis, it isn't unusual for me to have two modules which are seemingly separate programs in my chips. For instance, I've done several products which use a BIOS at a fixed address, plus an application layer at another fixed address. The entry point to the apps "main()" must, therefore, be provided at the same point in every compile of the app (the BIOS is compiled separately). It takes multiple passes with the linker (4 actually) to get the two modules compiled from scratch. I get two hex files for some products (they are factory programmed with the BIOS, I just drop the application on afterwards). Here's a neat trick, for those who like this approach: Have your boostrap code (part of the main() of the BIOS) exit to the application with a GOTO (or, if you have a big chip, last address - a couple so you can set the banks up correctly). In an unprogrammed chip, this will be an ADDLW -1 command which will essentially wrap you back to address 0, starting the bootstrap again. If part of the bootstrap code initializes pins and toggles something, you can verify operation by looking for the pin to buzz at the right frequency. This technique is especially handy for the 17C parts with external memory. Andy ================================================================== Andy Kunz Life is what we do to prepare for Eternity ------------------------------------------------------------------ andy@rc-hydros.com http://www.rc-hydros.com - Race Boats andy@montanadesign.com http://www.montanadesign.com - Electronics ==================================================================