Version 3.0.8 released.

[HenrikOlsson]

Hi,
I just noticed that version 3.0.8 was released a couple of days ago.
Support for a bunch of new devices and some fixes. From the version history page:

Added support for devices: 16(L)F1454, 16(L)F1458, 16(L)F1459, 12(L)F1571, 16(L)F1572,
16(L)F1574, 16(L)F1575,16(L)F1578, 16(L)F1579, 12(L)F1612, 16(L)F1613, 16(L)F1614, 16(L)F1615,
16(L)F1618, 16(L)F1619, 16(L)F1703, 16(L)F1704, 16(L)F1705, 16(L)F1707, 16(L)F1708, 16(L)F1709,
16(L)F1713, 16(L)F1716, 16(L)F1717, 16(L)F1718, 16(L)F1719, 16(L)F1764, 16(L)F1765, 16(L)F1768,
16(L)F1769, 16LF1554, 16LF1559, 16(L)F18313*, 16(L)F18323*, 16(L)F18325*, 16(L)F18345*, 16F753,
16HV753, 18F97J94, 18F87J94, 18F67J94, 18F96J99, 18F86J99, 18F66J99, 18F96J94, 18F86J94,
18F66J94, 18F95J94, 18F85J94, 18F65J94
* preliminary support, no datasheet available at time of build

Removed support for 16F527 (device not currently compatible with PBP)

Fixed HPWM for 16(L)F1788, 1789
Suppressed error 311 for K50 parts with PBPL
Fixed WRITECODE block size for 16(L)F1946, 1947
Added message concerning use of high-level commands on PORTF/G on 16(L)F1946/7, 16(L)F1526/7, 16F946

The following devices are not currently compatible with PBP: 10F200, 10F204, 10(L)F320, 10(L)F322, 12F520, 16F527, 16F570, 16(L)F18855, 16(L)F18875

/Henrik.

[Ioannis]

Thanks for posting Henrik.

Ioannis

[aratti]

Since I have lost my registration number and can not find any trace of the purchasing documents (all I remember is that I purchased the gold edition on line via Melab site)

Any suggestion on how can I obtain a copy of my registration number?

Cheers
Al.

[HenrikOlsson]

Hi,

Since you did the original purchase via MeLabs I'm sure they'll be able to help you out.

With that said, if you have it installed and activated I think you'll be fine by just downloading 3.0.8 and installing it over you're previous version. I'd try that myself but the download page says that it required MPLAB X and I don't want to mess around with that just now.

/Henrik.

[Ioannis]

Henrik is right, no problem with the update.

As for the MPLABX there is no problem in "messing" with it. Just download the beast, install it with a lot of patience and forget it. Also you do not need to uninstall the old version (8.xx) you have.

Ioannis

[aratti]

Eureka! I found the text file with all the registration keys. It was burried into an archive of an old computer that is a couple of years that I don't use it anymore. I was planning to take it to the Council Eco rabbish collector. Thank you Henrik for this thread, that gaves me the opportunity to recover these important documents.

Any way, thank you both for the advice, which are always useful.

Cheers
Al.

[grahamg]

Will version 3.0.8 still work with mplab 8.92

[Ioannis]

No, it asks for MPLABX.

Ioannis

[grahamg]

I have installed 3.0.8 and it works fine with mplab 8.92.

[HenrikOlsson]

[speculation]
Perhaps it does - untill you try to compile (or assemble rather) code for a chip for which there is no assembler include file in the older version of the assembler included in MPLAB 8.92.
[/speculation]

[Ioannis]

I believe so too.

Ioannis

[longpole001]

code folding - what is that btw

[Dave]

Henrik, Maybe you should look at another source of your crashes. I have been using registered versions of MCSP since 2003 and MCSPX since 2011 and have NEVER had it crash during a session. I have used registered versions of PBP since 2.37 and every version up to the latest.

[MichelJasmin]

Henrik, Maybe you should look at another source of your crashes. I have been using registered versions of MCSP since 2003 and MCSPX since 2011 and have NEVER had it crash during a session. I have used registered versions of PBP since 2.37 and every version up to the latest.

Sound crazy but I had MCSP crashes when Visual Studio ( <2010 ) was running too. Looks more stable with VS2010 but I try to avoid working with both environment open. I had repeating crashes with previous version of VS when iTunes was running in background. I uninstalled that iCrap and never tried again.

[rmteo]

code folding - what is that btw

Code folding is a feature of some text editors, source code editors, and IDEs that allows the user to selectively hide and display – "fold" – sections of a currently-edited file as a part of routine edit operations. This allows the user to manage large amounts of text while viewing only those subsections of the text that are specifically relevant at any given time. Identification of folds can be automatic, most often based on the syntax of the computer language in question, or manual, either based on an in-band marker (saved as part of the source code) or specified out-of-band, only within the editor.

For more info, see Code_folding

[HenrikOlsson]

Henrik, Maybe you should look at another source of your crashes. I have been using registered versions of MCSP since 2003 and MCSPX since 2011 and have NEVER had it crash during a session. I have used registered versions of PBP since 2.37 and every version up to the latest.

Dave, I'd be happy to but the fact remains that it's MCSPX that crashes "randomly", for me and for others so it's not something unique at my end. Of course some other application may be the root cause of it but still it's MCSPX that crashes....

For me it does it on two different machines by the way, both running W7. I can't remember it ever crashing on my old XP laptop though.

People have tried to help Mecanique and Melabs by posting error messages and crash/debug information but they don't seem to be able to do or say anyting about it.

Just like you I've been a long time user, I still have my PBC installation floppy which I later upgraded to PBP (it says v2.31 on the floppy) and then on from there. I find the compiler extremely stable and reliable. It's only after the introduction of MCSPX that it (the IDE, not the compiler) started to crash on me.

/Henrik.

[longpole001]

thanks

gee i like the sound of that option - it be very nice to have

rmteo

Re: Version 3.0.8 released.
Quote Originally Posted by longpole001 View Post
code folding - what is that btw
Code folding is a feature of some text editors, source code editors, and IDEs that allows the user to selectively hide and display – "fold" – sections of a currently-edited file as a part of routine edit operations. This allows the user to manage large amounts of text while viewing only those subsections of the text that are specifically relevant at any given time. Identification of folds can be automatic, most often based on the syntax of the computer language in question, or manual, either based on an in-band marker (saved as part of the source code) or specified out-of-band, only within the editor.

For more info, see Code_folding

[eltra11]

Hi Henrik
thank you very much on your kind support.
mike