> I think what the ProMate does is:
> 1) program all but the code protect
> 2) Verify Ho and Lo
> 3) if it verifies, then program the code protect.
> 4) Verify Code protected (Ho and Lo?)
>
> FWIW, I've had one production burn failure in two years, (I assume it
> was truely a bad die), and no PICs that verify but didn't work.
>
> -Barry

ProPic 2 Gold does the same thing.
By the way, has anyone been called by Microchip lately,
saying you are using Microchip trademarks by using PIC name?
I mean picpoint site, picprog programmer, etc?
We received a fax telling us we can not use ProPic 2
name anymore because PIC is a trademark of Microchip.

Friendly Regards

Octavio Nogueira
===================================================
nogueira@propic2.com                  ICQ# 19841898
ProPic tools - low cost PIC programmer and emulator
http://www.propic2.com
===================================================

----- Original Message -----
From: Barry King <barry@NRGSYSTEMS.COM>
To: <PICLIST@MITVMA.MIT.EDU>
Sent: Thursday, April 27, 2000 4:11 PM
Subject: Re: Production vs. Development programmers


> Dan asked,
>
> > Walter, how do you handle the fact that you cannot verify a
> > code-protected PIC? HI/LO is useless here - or is there a way?
>
> ------------
> Barry King, KA1NLH
> NRG Systems "Measuring the Wind's Energy"
> http://www.nrgsystems.com
> Check out the accumulated (PIC) wisdom of the ages at:
> PIC/PICList FAQ: http://www.piclist.org