WRITE: One more PBP 2.60 Surprise ...

[Charles Linquis]

A good user-supported bug list would go a long way in making people comfortable with any upgrade. It would also be a good way for MELabs to get input. I'm certain that Darrel is doing a great job telling them what he finds, but he is only one person.

The problem with the "bug-list" approach is that without proper moderation, it could easily degenerate into an alternate PBP forum.

[Charles_Leo]

I've been considering a "known issues" list in the support section of our website. Would that help? Discussion could take place here on the forum, though I might need an email wakeup call occasionally. Once things are defined and confirmed, I could update the website with a summary.

All submitted bug reports are investigated, but only a few are confirmed. The investigation process is part of my support responsibility, as is the listing of the issues.

I believe there are currently two confirmed bugs in PBP 2.60.

1.) The WRITE command issue described in this thread. The best workaround is the define that Darrel mentioned:

DEFINE WRITE_USED 1

2.) The header files 16F1826.BAS and 16F1827.BAS have bad register aliases. Each file can be corrected with:

PORTL   VAR     PORTB
PORTH   VAR     PORTA  ' PORTC invalid, change to PORTA
TRISL   VAR     TRISB
TRISH   VAR     TRISA  ' TRISC invalid, change to TRISA

[Charles Linquis]

A known issues list would be a perfect solution for me.

The fact that I didn't know the WRITE problem existed scares me to death because I use that function extensively to store variables. My '8723's have 1024 bytes of EEPROM, so I'm often writing to locations above $FF.