New PBP3 user

[muddy0409]

ok, A little bit of jiggery pokery looks like its going.
Thanks.
Am now printing on a LCD

[muddy0409]

All seems to be working OK.
Just one more question:
In my old MCS 2.60 when selecting COMPILE PROGRAM the programmer (MELABS usb model) loads up all ready to PROGRAM VERIFY from the programmer popup.
However, in the MCS attached to BP3, at the completion of the COMPILE PROGRAM action, the programmer loads up, but I still have to OK the assembly completion POPUP before I can tell the programmer to PROGRAM.
Is there a way to automate this operation the same as in 2.60? I have looked thru the help in both MCS and MEPROG but can't really see anything pertaining to this. Probably wouldn't recognise the way to do it anyway, even if it was spelt out.

Thanks.

[HenrikOlsson]

Hi,
I don't have that programmer so I'm just guessing here but try changing Edit -> Compile and Program Option -> MPASM Close After Assembly.

/Henrik.

[muddy0409]

I have tried that. It comes up with

Error in parameter "/s".

Dunno what that means.

[HenrikOlsson]

Hi,
Do you get the same error if you click the [Compile] button instead of the [Compile and Program] button?
I'm trying to determine if the error message is comming from the compiler, the assembler or the programmer software.

EDIT: Ok, it's most likely from the assembler.....
The /s parameters is what controls the MPASM progress window. Looking at an older version of the MPASM documentation they don't mention that parameter/switch at all though. My guess is that the version of MPASM you have installed is too old....

Find the MPASMWIN.exe and double click it. What version does it say in the titlebar? My MPLAB installation is 8.85 and the MPASM version within it is 5.45 and I don't have the issue you mention.

You can download an installpackage including MPLAB 8.90 from MeLabs download page. If your MPASM version is older than 5.45 I suggest you do that and try again.

/Henrik.

[muddy0409]

5.49

Didn't the MPASM suite come with the PBP3 download, only 3 weeks ago? That should have been the latest then?

I does say for win 9x, I want to keep the same version on my Win7/64 laptop and my XP pro desktop PC.
I may have even left the older version active on the lappy for that reason. So if that is the case, this version has been working as I want it, on the desktop for years. So that would suggest the assembling instruction from PBP3 is the problem. I will just shoot out into the workshop and check that what I just said is correct.

This whole problem is no big deal, it is, after all, just 1 more mouse click. I just wondered why the difference.

[muddy0409]

Hmmmm...curiouser & curiouser.

The desktop (XP pro) has the same version of MPASM, installed in 2013.
PBP3 was installed 2 weeks ago.

The programmer does what I want on the PC.

The laptop Win7/64 has the same MPASM also installed in 2013
PBP3 was installed 2 weeks ago.

PBP 2.60 works the way I want, on both machines.

To my simple way of thinking, the only difference is the WIN versions. XPpro vs Win7/64

Oh dear!