Hi ! I just had a Wisp628 customer (I re-sell Wisp628 localy in Sweden)=20 mailing me about programming problems with a 12F675. They programs=20 once and then get all sorts of problems (both with XWisp and XWisp2). I verified that I got the same "problems" using my own Wisp628 and a=20 12F675. Of course this was due to the "internal MCLR" problem as=20 descibed on Wouter's Wisp628 page. Blink-a-LED file b675-1.hex=20 (*external* MCLR) works just fine. Blink-a-LED file b675i-1.hex=20 (*internal* MCLR) shows this problem. I happend to have a "dongle"=20 made according to the description on Wouter's page (actualy I think it=20 was *made* by Wouter), and with that connected between the Wisp628 and=20 the programming cable, re-programming of HEX files using internal MCLR=20 works just OK. Now, two questions. 1. How does the "Wisp628=20 community" handle this in general ? 2. Will this, in any way, be=20 different in the new Wisp628 firmware that is currently under=20 development ? Best Regards, Jan-Erik S=F6derholm. --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist