Preview
Something happened while flashing my 8320B...

Used the hex file that were made for this drive instead of that of the 8400B. I touched nothing and nothing at all seemed to happen. Left it alone for a while and came back about three or five minutes later... still "00% Updating".

I then hit ctrl alt delete (seemed like a loose/loose situation anyway) and when my computer restarted my cdr drive no longer responded, at all!! The drive īdosn't even respond to even opening, and when i run the flashprog (je3.exe) with the hex file it doesn't find any recorder during the IDE portscan...

OK.. i know im not a dunce or anything i've flashed all kinds of different hardware and MoBo's wihtout anything ever going wrong... why did it now? And what can i do about it??

PLEASE HELP!!!!

AnthiStatic -- Sweden
--------------------------------

Well you could try to connect the drive as a secondary master without a slave drive & see if the BIOS detects it...if the BIOS does not detect it i suggest you try to return it to your local store if you still have warranty on it...
If you do not have warranty...well im afraid your drive is a gonner...
I dont know of any desktop equipment you can use to examine the problem correctly...

If you have access to an electronicts lab you can risk trying to take the EEPROM out & examining it & IF its still ok, erase it & program it with the old firmware...
But thats alot of trouble & might cost you more money than you care to spend...

All in all...if you dont wanna hassle...through it away & buy a new one

I suspect that the flash utility needed the drive to be the only drive on the cable or might needed the drive to be a secondary master etc...
& thats why it messed up so badly...

But then again, i could be wrong...

The difference between communisim & capitalisim is that in communisim man exploits man, in capitalisim its exactly the opposite!

(in reply to AnthiStatic)