"overwriting previous address contents" - NOT the usual fuse problem

[pic18f442]

It is on the laptop. I'm in the process of nuking and re-installing everything again, so I can't give exact details - but Microcode Studio Pro automatically installed MPASM V3.9 in c:\progra~1\mecanique\mcsp\mpasm . If I select this version, it works. If I instead point it to the MPLAB\mpasm folder, it fails.

I've verified the versions by manually running each MPASM on the .asm file, and also viewing the output of the list file.

[pic18f442]

OK, I _think_ I have 'fixed' it (fixed, as in this is a hack but it seems to work). In case anyone else is having the same trouble, try the following

1) Download MPASM 5.2 from microEngineering Labs - http://melabs.com/support/mpasm.htm

2) copy this over the top of the existing MPASM in the MPLAB folder.

You should now be able to compile files in MPLAB, but not debug them, as no object file or debugging information is generated(!)

3) In MPLAB, go project -> build options -> project, then the PICBASIC PRO tab, then click 'use alternate settings'. Make sure it says -n ampasmwin -k# -oo -> the -oo passes -o to the assembler, which forces it to generate an object file.

This seems to work, but I'm not sure why I didn't have to go through this for the desktop.

[pic18f442]

Sorry, posted too early - the above doesn't actually work as the generated files are wrong and cannot be simulated

On my desktop, simulating a PBP program then viewing Program Memory gives

Line:Address:Opcode:Label
1:0000:EF02:GOTO INIT

on my laptop, you get

GOTO 0 instead, so it instead becomes an endless loop. The INIT location is still shown elsewhere in the code, but the instructions are not updated to match!

[Darrel Taylor]

The project compiles ok for me with PBP 2.60A and MPLAB 8.53.
The files generated do not match the ones in your zip file though.

Your P18F442.inc header from MPASM does not match, and it appears to be creating code for a 16-bit processor.

It's possible that the registry entries are invalid.
And that would happen if you just copy installations from another computer, because the setup program writes those entries.

You may want to try the attached file that was written by Charles Leo.
It hasn't been tested completely but seems to work so far.

It attempts to correct the paths and registry entries needed to compile with PBP and MPASM.
It also writes a new PBPMPLAB.bat file in your PBP folder, in case it was modified.

Make sure MPLAB is closed before running it.
If you have multiple MPLAB installations, open the correct MPLAB first, then close it.

If your "System Search Path" has a path to MPASM, that should be removed manually.

[pic18f442]

Thanks very much for your help, but I'm afraid that suggestion didn't work.

I took the nuclear option and re-installed windows on the laptop hard drive, then installed MPLAB and PBP. It worked! I then let Vista update itself. Then the problem came back.

I think given the time spent already, I'll use a different laptop running XP.

Thanks again.