I started to rewrite the NoPPP software to support the 16f628a and 16f877a devices a while back. I had a zilion problems, half I can atribute to my NoPPP programmer hardware, and a good portion of the remainder had to do with the timing routines. I was using the newer version that was back ported to windows (using djgpp) and added support for the 16f628 (non 'a' verison). I found it searching google for "16f628 noppp" or something similar. That version if you can find it, uses a usleep() compatability function and has the old stuff commented out. The bad news is that that version of usleep() only does some division and calls Sleep(). Unfortunatly Sleep() has a practical minumum resolution of 20ms on most MS OSes (9x,ME,2k that I have noticed). This worked out fine for meeting the minimum requirements for the flash write, but is undesirably slow becuase every 1ms delay becomes 20. I ended up replacing the new and improved NoPPP delay function with the old assembly timer version and that worked just fine for me, but I'm running ME on a 650 PIII. But I eventually gave up and went to a customized Tait programmer and IC-Prog software. For some reason the Tait design can drive my programmer cables of several feet (laptop->programmer->pic = 6-8') even on the lowest delay setting and never miss a beat, wereas my NoPPP had random issues with a 3" short parallel cable and the PIC pluged straight into the socket on the programmer. If you do not need support for the new chips, dont bother porting your stuff into the new version, a quick hack would be to just replace the timer code with a call to Sleep(20) since that meets all of the minumum flash write times. Good luck, Ben Hencke --- Rodrigo Real wrote: > Hi > > I am working with NOPPP programmer for some time in > a Pentium200MHz > for programing PICs. In that computer the > software/hardware works > fine. I made some interface customizations in noppp > based on the DOS > version NOPPP software, an that is the version I am > using. > > Now I am trying to use an AthlonXP to do same job, > and I am with a > timing problem. I guess the problem is with the > microseconds delay > routine, which tries to use a timer that doesn't > exists anymore. I > also tried to work with a linux version of the > NOPPP, but I had the > same problem. > > Does anybody have any suggestion for solving this? > > Thanks, > Rodrigo > > -- > http://www.piclist.com hint: The PICList is archived > three different > ways. See http://www.piclist.com/#archives for details. __________________________________ Do you Yahoo!? Yahoo! Search - Find what you re looking for faster http://search.yahoo.com -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body