more on flash-write failure

Hi,

I've investigated the flash-write problems with an interactive test prog 
which reads/writes/verifies to locations 0300 to 030F, and compared this 
to the results from serial-monitor.fs

What I'm seeing with my test prog is:
- I do a flash-write, then do a flash-read to verify
- the flash-read most often produces the original data, not the
   data I've just written (although about 1 in 5 times, it produces
   the data just written)
- after a reset, I'm seeing the data my test prog has written

What I'm seeing with serial-monitor.fs is:
- I do a flash-write (via the 'Fnnnnxxxx' command), then a
   flash-read (via the 'fnnnn' command). When testing with locations
   0300 to 030F, I'm never seeing the values I've written - not even
   after a reset.
- I've studied serial-monitor.fs (at least, at forth source level),
   and can't see anything amiss

I've carefully verified that all code-memory-protect is off, in both my 
test prog and serial-monitor.fs.

Anyway, this is not unduly impacting me. I'm using the bootloader from 
www.microchipc.com, and between a couple of hacks to the bootloader, 
plus a hacked-up picforth include file, I'm able to compile picforth 
progs to a .hex format which will download and run fine via this bootloader.

In fact, I have no real need to write to program flash in my code, and 
as for program flash read, I'm doing just fine using the PicForth 
primitives like ftable, c", str-char, etc.

-- 
Cheers
David