Originally posted by dhc014
You will need to get a binary firmware in order to test since the windows flashers will not work directly.
No-no, everything is much simplier. There are two flashers on www.btcusa.com
: one of them is for BCE 4816IM, the other is for 5224IM. Both flashers extract to temp directory, they extract 4 files - three of them are for flasher itself, and the 4-th is .hex file with firmware. Both flashers check the drive model, but allow to select a .bin or .hex file with firmware. So it is not a problem to start a flasher for BTC 4816 and choose a file with firmware for BTC 5224. The trouble is: when i decided to overclock my drive, i wanted to check flash programs first. So i started flasher for BTC 4816IM
first, and tried to update it with firmware for this drive. I wanted not to overclock, but to update my BTC 4816IM with a new firmware for it. So i chose a 4816.hex file, and started flashing. Flasher reported "Erasing..." and then "Updating...". My computer started to lag, and a few seconds after the first rectangle appeared in a progress bar, it showed blue screen of death with some kind of "program stack error". After i pressed reset button the drive was totally dead - even the eject button didn't work.
I have a WinXP SP1, and that was for the first time i saw a WinXP BSOD. So i didnt have a chance to overclock my BTC since it is dead. maybe CDRInfo staff will be more successfull - i am not sure, if it is a flasher-killer or my buggy WinXP