EPIC, Code programming error at 0000

[shorton]

DOH! You are right, I thought it was too small, I was wrong. It fits it fine. I bet I thought it was too small when I ordered the ZIF last year. Should have looked closer.

Anyway, thanks, I'll try the laptop with the on-board socket.

[shorton]

Now that I know it fits I tried the 628A in the on board socket. Same result. Took 40 attempts to get the laptop to program it. Hooked it back to the desktop, programmed 3 times in a row. Strange.

[skimask]

Now that I know it fits I tried the 628A in the on board socket. Same result. Took 40 attempts to get the laptop to program it. Hooked it back to the desktop, programmed 3 times in a row. Strange.

Had problems with mine awhile back, like 3 or 4 years ago...
Do you have any 'Temperature monitoring' or 'CPU monitoring' software running in the background?

My problem was (and it took me almost a year to figure this out) every time one of these programs would try to do an update (i.e. read a CPU temp, read a fan speed, etc), it would kick out my programmer software and dump somehow. And it was really sporadic since my 'monitoring software' would only do a read every minute, so I suppose I would get errors about 50% of the time because it usually takes less than a minute to program a PIC.

One day, for some reason, I decide to change my update rate to something like every 10 seconds. (Important point that I missed for about a year: Most of the time, it takes far less than a minute to program a PIC, but it almost always takes more than 10 seconds to program one). After I made that change, nothing worked, for about a month.

After awhile, again for some unknown reason, I decided to shut off all my monitoring programs (I haven't made the connection between the 2 events yet), everything started working great. It just didn't add up.

About 2 weeks after that, my girlfriend used my laptop and shut it off instead of putting it in standby like I always do.
Well, the reboot put the 'monitoring software' back into the '10 seconds between reads' mode and neither of my programmers worked again.
Now I made the connection... Every time the laptop's 'monitoring software' would read the CPUs temp or Fan speeds or whatever, it would cause my Warp13a OR my EPIC to error out at the exact moment that it was trying to do the read.

Funny thing is, this has only happened on my laptops, never on my desktops.
I don't know why, I don't care. I just run a clean system now without a crapload of stuff running in the tray.

[shorton]

Thanks for the suggestion. I don't have any monitoring software going. I've scoured the startup stuff via "hijackthis" and made sure I don't have anything running in the background that's not regular core windows junk.

Programming with the laptop fails instantly over and over until, oftern after about 30-40 tries it will "hit" and go on and program. It reads sucessfully every time, never fails. And it erases every time, too (set to erase before program), also never fails. Only the write fails and it appears to do so the instant it gets going. I guess 0000 is the first plae it tries and that is thus the error message.

Melabs told me a timing change to make in the 628A file. Haven't had time to try it yet.