New PBP3 user

[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!

[HenrikOlsson]

Hi,
Yes, if you download the package including MPLAB/MPASM then you might not get the latest but you should get one that should work.
You mention an older version being left on the laptop, is it possible that you've got MicroCodeStudio setup to point at that older version?

There's a tool called PBP_MPASM_Connector.exe (in PBP3\MPASM-MPLAB_Setup\). Run it and make sure that it points to the current version of your MPASM installation and not the old one.

I run PBP3 on two W7 64bit machines (and previously on one XP machine) and I haven't seen this /s parameter error - which again may have nothing to do with your initial question regarding the programmer.....

/Henrik.

[muddy0409]

There is no PBP3\MPASM-MPLAB_Setup anywhere.

PBP_MPASM_Connector.exe is in MPASM_suite.

Ran that with no difference in the outcome.

Dammit, I just will put up with the extra mouse-click required.
Thank you so much for all the hair pulling. I just hope you don't lose any more sleep over this.

Shit, these things are great when they work as you expect & want them to, ain't they?
I s'pose I'm just getting too picky in me old age.

Thanks again Henrik.
We will undoubtedly run into each other again, the next time something crops up, if I don't switch these damn things off permanently first.

[HenrikOlsson]

Hi,
That doesn't sound right.....
On my system there's C:\PBP3\MPASM-MPLAB_SETUP\PBP_MPASM_Connector.exe Obviously you might have PBP3 installed somewhere else but I can't see how the PBP_MPASM_Connector.exe would end up in the MPASM Suite installation folder....

Simply running it won't change anything. If you have multiple versions of MPASM installed you must make sure that the path to the correct version is what the tool points to. If the tool point to the older version you have on your system then that is what PBP will invoke for assembly and you'll get the /s parameter error - that's theory anyway.....

/Henrik.

[muddy0409]

Did have 2 versions of MPLAB.exe, 5.49 installed feb 2013 and 5.03 inst mar 2006

deleted the early one and reran the mplab setup then checked the close thing in PBP3 assembler edit.
ALL NOW CORRECT

So should I delete the full MPASM stuff and install the latest? But I am rather inclined to now leave well enough alone. Ya think?

[HenrikOlsson]

Great!
Personally I'd leave it alone until I see a specific reason (like lack of support for a specific chip) for updating.
I don't know if 5.49 even might BE the latest.

/Henrik.

[muddy0409]

Boy o boy.
I finally decided to do something that someone agrees with.
Yep, I will leave well enough alone. I only use the smaller 16F and some 16C chips that all appear to be supported.
Thank you so much for listening and helping.
If I can be any help to you in future, please do not hesitate to contact me. That should give us both something to laugh about??

Thanks again.

[Acetronics2]

So should I delete the full MPASM stuff and install the latest? But I am rather inclined to now leave well enough alone. Ya think?

Hi, Peter

as the latest 8.92 MPLAB IDE is working pretty fine ...

why not install it "as is " ... ???

That would avoid any surprise in the future ...
and you wouldn't have to ask yourself if the "xxxxxer" version is the correct one or not ...

Just my two cents ...

Alain

[muddy0409]

I think I will leave well enough alone.
Thanks Alain.