ctmal wrote:Ok, that's the same one I have. Attached is a picture(excuse my art skills) on how the chip should go in(just in case). The white dot is pin 1. Also, make sure the two jumpers(circled in yellow) are set in the upper position(pins 2 & 3).Also, I have had success using picpgm. I would use this since we know it works with it.
Do you have another pic to try? I just want to weed out the possibility that the pic is the issue.
yeah i have tried all three of the pics i have and i have had the jumpers and chip position correct. I am also contacting mcumall the company i bought it from and they say that they think the chip is not being recoignized.
chris
i tried it and i was able to auto detect all but one one chip (i think the other one is bad) but then i go to write it writes about 1/4 of the data and then when it goes to verify it and when it verifies it says complete but only 1/4 of the data is on the chip.
chris
I'm pretty much at a loss but have you tried using another computer?
ctmal wrote:I'm pretty much at a loss but have you tried using another computer?
ya tried two comps the major thing is that confusing me is that when i put in one of the chips it says
Checking connection of JDM Programmer ...
Error opening portio.sys driver for LPT access!
No PIC Programmer found! Check connection!
No PIC detected!
but all of the others work, the ren24 also worked before so i don't think the chip was bad (but dimming looked more like a strobe light than dimming) i am going to try them in the ren 24 and see what happens.
chris
ailgup wrote:ya tried two comps the major thing is that confusing me is that when i put in one of the chips it says
Checking connection of JDM Programmer ...
Error opening portio.sys driver for LPT access!
No PIC Programmer found! Check connection!
No PIC detected!but all of the others work, the ren24 also worked before so i don't think the chip was bad (but dimming looked more like a strobe light than dimming) i am going to try them in the ren 24 and see what happens.
chris
LPT access means its looking for the printer port for some reason instead of the com port. Can you set it up to look for com1 directly(or whichever com your plugging into) instead of autodetect?
