ZC4ME

Well crap....I was updating my Flash&Burn software tonight and while I was at it, I saw that there was a firmware update also, so I decided to do that to. I made sure I had the correct file downloaded and used the firmware update program from moates.net and it appeared to do the update properly BUT from that point on, the flash&burn software no longer recognized the burn1 being plugged into the usb port. I tried SEVERAL times to unplug the unit and plug it back in and also restarted the computer, but still no recognition. The computer recognizes the device and the device manager says that it is working properly, but it just does not recognize the burn1. I emailed Craig asking what it could be, but I figure he won't get to the email till Monday and I wiould really like to get this figured out as I am trying to burn an Uber bin for a buddy. Anybody have similar issue that they were able to resolve without sending the unit back to Moates?

TurboEF9

First off, dude, craig will e-mail you back today. He's cool like that.

Second, as with any device, you shouldn't update the fireware or BIOS unless you are experiencing a problem. Anyway, the only thing I can think is you inadvertently used the wrong firmware. As I've updated mine with (and my Ostrich) with the latest and it didn't do anything wrong. Have you tried to reupload the fireware using the update program?

Uploader:
http://www.moates.net/zips/firmware/...areUpdater.zip

Firmware:
http://www.moates.net/zips/firmware/FNB_5_9_F.zip

I've been using the BURN1 for a while now, and have experienced only one problem (with the old slower AT29C256s).

ZC4ME

Hey, your right, Craig got back with me first thing this morning (AWESOME!!!!) He said that I most likely have one of the older units (I bought it over a year ago) and that the firmware update most likely corrupted the unit. He is having me send it back to him and he is sending me a new one at no charge.....now that is customer service. On top of that, he is working with me on shipping so that I can have it back by next weekend

I was having a problem...I could not get an Uber bin to burn so that the car would actually start and I was using th AT29C256 chip, lol. I was also getting some assembly error in Uber, so who knows what I was actually doing wrong. I did not have any problems burning the same type of chip when burning a TE bin. I wish I knew what was causing the assembly error when I opened the bin. I thought it was due to the fact that I did not have the bin file saved in the uber directory, so I moved it into that directory, open it up and it seemed to open properly this time, but the car would still not start. Now I have to wait to get my burner back in order to try some other things.

Chris Harris

Ok, I'm going to have to say that if you didnt have any problems burning a TurboEdit BIN with the BURN1 but had problems burning an Uberdata BIN with the BURN1...the burner isnt the problem

ZC4ME

Yea, I doubt the burner itself was the problem, I thought it might be software related so (and as I stated in a different thread) I downloaded the newest version of Flash&Burn and then noticed there was a firmware update, so I did that too. Bad idea, lol, I guess I have the older version of the Burn1 and Craig said it most likely corrupted the burner. So, he is replacing it for me, which is awesome. Man I am reading all over, trying to learn more and more.

Craig Moates

By the way, I want to FIX that slow 29C256 problem. It can be fixed with a firmware revision I think. However, I don't have any of the slow chips on hand. I thought I did, but can't lay my hands on one. If you or someone could send me a couple to work with, I'll get it straightened out if possible. Just get with me offline.

Thanks!

TurboEF9

Craig, I'll send you some.