>
> I see where you're heading with this... Are you suggesting that the
> code got corrupted on its way into the chip? But I checked the verify
> option in winbloze... I'll have to take a look at the pk2cmd in Linux
> though...
>


I would recommend to read pk2cmd manual, and enable options like erase
and verify on every programming. It will slow down things a bit but
You will remove some variables from the problem. I had a lot of times
when programming went wrong for unknown reason and was OK on the next
try. Had to reconnect Pickit into another usb port sometimes.

Prepare such a tested command line for you, and store it for future,
or create a script or an alias. I was typing it in a shell window of
piklab so not to switch windows all the time.

-- 
KPL
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist