Note typo on 2.46 should read 2.43 on original post

Quote Originally Posted by Acetronics View Post
Hi,

I do not want to be rude ...

BUT, instead of loosing your time ( might I say " and ours ??? " ) Wouldn't it be MUCH more Clever to reload all your PBP files from a Safe source ( i.e. a genuine PBP 2.60 release .... ).

I know some mods have to be done on the libs to use Darrel's goodies ... I saw you made Hazardous ( ! ) mods too ...

BUT surely worth the time to restart from a SAFE basis ...

You MUST admit you do not know where you are, at this time ...

Alain


From your comments you imply that I am using a non genuine copy, my copies/upgrades, are all from CROWNHILL !!!, 2.60 only arrived couple of weeks ago, so I suggest you refrain from making that type of accusation.

The PB2.60 WAS a clean new install. !

My hazadous mods ??? correcting the file where Melabs admitted there was a correction needed, if you had bothered to look at the version history, you would have seen the remark about the bank 2 setting, 2 versions on from my original 2.43.


This is what it says about the corrections in the 2.45 file Note last line but one.

Previous Release: 2.45
Adds support for PIC12F508, 509, 683, PIC16F505, 684, 688, 716, 737, 747, 767, 777, 87, 88, PIC18F2331, 2431, 2515, 2525, 2585, 2610, 2620, 2680, 4331, 4431, 4515, 4525, 4585, 4610, 4620, 4680, 6410, 6490, 8410 and 8490.
Allows spaces in path/filename.
Improves compatility with MPLAB® 6.
Updates USB routines to version 1.25.
Removes dependence on some Microchip PIC18Xxxxx macros.
Fixes subtract bit from byte and word to word result.
Fixes PIC16F648A BANK2 RAM setting.
Fixes some PIC18Xxxxx bank selections.

I know exactly where I am,

1. there was an error made by Melabs on 2.43, yes my fault for not checking the version changes, but then I wonder how many do.

2, in my opinion there appears to be an error on the M16F62XA.INC file.
I have PB 2.43,2.5,2.6 ( All legal and paid for from Crownhill) and on all of them it shows what I think is an error.

All I have asked was, does someone else think that there is an error in the M16F62XA.INC file.

So instead of jumping on someone without knowing all the facts, you could either have ignored the posting, or given a simple opinion on the entries in that file and without making unfounded accusations !.