Ok, this is my first time burning a PROM with the new v4 of TunerPro. First off I can edit just fine, all of my .ecm > .xdf conversions went fine, I did have to do it again through going to this latest build.

Anyway, I did a fresh install of XP Pro, installed all the OS updates, etc. Then I installed the Burn1 using the USB drives from Moates.net. Then I rebooted and did another windows update which updated the USB drivers for the Burn1. I did this a couple years ago when Craig said it was OK and I indeed had no ill effects. When I did it this time, all on the exact same notebook mind you, the MS USB drivers crashed my system and gave me a blue screen. It wouldn't even boot with the Burn1 plugged in. So I removed the MS drivers and ran the Burn1 with the Moates drivers. BTW, yes I have the latest firmware flashed as well, it's like a year old and I had used the Burn1 many times with perfection but haven't used it in over a year.

The problem is, I have 2 MEM-CAL's each with a 29C256 installed in them. I went to erase and flash them with a new bin and I get nothing but errors!!! Things like when I erase, sometimes it will error and I have to try 3 times until it goes 100%. Then sometimes when I do a blank check it says it's NOT blank. Also once I do get it erased and the blank check goes through, I'll burn the bin and when I verify it with the buffer it won't pass!!!

So, WTF? Lol. This is NOT cool because I have no car and no other computer! Did my Burn1 take a crap or is there a bug in the latest build of TunerPro or did all that USB driver stuff screw something up and I have to again reformat and start fresh?????

Please help!!

Thanks!

 

I reflashed the Burn1 firmware and also removed and reinstalled the USB drivers. Same problem!!!!!!!!!!!!!!!!!

I'm REALLY pissed!

I FINALLY got one of my MEM-CALs to write and verify after who knows how many attempts! Problem is when ever my car gets to temp and going into loop, it bogs like mad! It's done this on 4 different burns now including 2 that were proven to work!!!!!!!!!!!!!!!!!!!!!

WTF?

 

i use the AutoProm & had what sounds like about the same problem the last time i did a fresh install of XP on my laptop. i don't remember what i did to fix it now, but it seems like i had to
change something in Device Manager with the Moates part.
i wish i could remember for certain what i did to fix it.

4.13 is working fine for me.

make sure you have the port set right in in the burning software.

 

...and just a quick suggestion:

I got tired of reinstalling whenever anything went wrong, so instead, one day I got the perfect install I wanted and then ran Norton Ghost. I used Partition Magic to chunk off a few GB of the C drive into a D partition and saved the Ghost file there. If I ever have any other computer problems (virus, spyware, the occassional USB crap which happens MUCH TOO OFTEN, etc...) I just save my Favorites and restore the Ghost image. Five minutes later and it's just like new.

 

I have had this too, but what mine was is when I installed the chip into the programer it wasnt making good contact in programer. It would even say chip was erased till I did a blank check....then I would have a butt load or errors also.

Just my $.02 but you said you didnt use your stuff in a year? I would go back and look at the pins to the chip/s and make sure they're clean,they must make good contact. Then go to programer and make sure zif is making good contact with the chip too, its hard to tell if anyone of them are not making contact so I would just take a pocket knife blade tip and scratch each one to make sure. Last are you using a flat ribbon to your laptop or a usb? If flat ribbon make sure pins to connector are straight and they to are clean, if using a usb cable is it the same one that come with programer? For some reason certain usb cables will not work with certain equipment. They will register when installed into port but all the info transfered will not make it.

Again this is only my $.02 but sounds like you not having a program error as much as a hardware problem. Because some of the eeprom is making it to the chip but not all of it.

 

I think you are right about the hardware thing!

I was fighting it all day yesterday, even the port settings were right as going by moates.net

I messed around with moving the adapter into the burn1 different ways and finally the one MEM-CAL that came back with errors was able to erase, blank check, program, and verify!

It sucks because it looks perfectly clean, I had it wrapped in plastic and I live in the CA desert, lol. I blew it off and stuff when I took it out of the bag for use.

I'll buy some compressed air and if that doesn't work then I'll see if I can send it all back to Craig for disassembly and cleaning.

 

Things to check:

1) Do you have the chip/memcal properly oriented in the BURN1 zif?
2) Is the ZIF firmaly attached to the unit?
3) Is everything clean?
4) Try a different USB cable
5) Make sure the drivers are installed properly and are up to date
6) Make sure you have the driver settings correct (4096 buffer sizes, 1ms latency, etc) - more info on Moates' site


M

 

1) Check
2) Check
3) Still have to use compressed air in the BURN1
4) Hmmm, haven't tried that yet
5) Check
6) Check