Glen, if those are Parallax/CVASM object files, the device data
is included in the file. If you still have access to the source files, or
the author, have him re-assemble the source with the "/S" option which
will strip the device data leaving just the object file. Then you set the
fuses in whatever programmer software you are using.

   - Tom

At 08:42 10-03-02 +1100, Glen Torr wrote:
>Howdy,
>
>I have inherited (reluctantly) a project for which the previous developer
>has supplied files to allow production. I have very limited access to the
>previous developer.
>
>The files supplied have an .obj extension and I think they may have been
>produced with a parallax assembler. I also believe the developer used an
>epic programmer.
>
>They import into MPLAB (V5.5 and V5.4 tried) ok and program the PIC (16F873)
>using a picstartplus, the pic exhibits some correct functionallity but this
>varies seemingly randomly between successive programmings.
>
>The only clue I have is that configuration of the pic is inconsistent, ie
>weak pullups are enabled sometimes and not others.
>
>Is it possible to readily locate config info in an obj file and edit it or
>somehow convert parallax obj to pic hex ?
>
>Any Help appreciated, Many Thanks
>
>Glen Torr


------------------------------------------------------------------------
Tom Handley
New Age Communications
Since '75 before "New Age" and no one around here is waiting for UFOs ;-)

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.