I prepeared to reflash my LiteOn Yesterday, but while reflashing came an Errormassage->

>LiteOn IT CDRW drive flash utility Version pre-0.5 Date 04/10/2000
>Vender ID :LITE-ON
>ProductID :LTR-BOOT
>Revisionlevel :0024
>Data Code :2000/10/
>Please Wait 35 seconds ..34..28..
>Vender ID :LITE-ON
>ProductID :LTR-BOOT
>Revisionlevel :0024
>Data Code :2000/10/

>Data compare fail in Adress 0x3c000 Expect 0x5a Got 0x17
>Data compare fail in Adress 0x3c001 Expect 0x3 Got 0x51
>Data compare fail in Adress 0x3c002 Expect 0xc4 Got 0x17
>Data compare fail in Adress 0x3c003 Expect 0xda Got 0x71
>Data compare fail in Adress 0x3c004 Expect 0x6a Got 0x28
>Data compare fail in Adress 0x3c005 Expect 0x28 Got 0
>Data compare fail in Adress 0x3c006 Expect 0 Got 0x78
>Data compare fail in Adress 0x3c007 Expect 0xff Got 0x10
>Data compare fail in Adress 0x3c008 Expect 0xf7 Got 0x6a
>Data compare fail in Adress 0x3c009 Expect 0xe6 Got 0xa8
>Data compare fail in Adress 0x3c00a Expect 0xa8 Got 0
>Data compare fail in Adress 0x3c00b Expect 0x1 Got 0xff
>Data compare fail in Adress 0x3c00c Expect 0x58 Got 0xf2
>Data compare fail in Adress 0x3c00d Expect 0x60 Got 0x20
>Data compare fail in Adress 0x3c00e Expect 0x1 Got 0x7a
>Data compare fail in Adress 0x3c00f Expect 0x66 Got 0
>Data compare fail in Adress 0x3c0010 Expect 0x6a Got 0
>
>Too many compare errors programm terminated

Lucky day :(
What can I do now. The was no change in Error in new prepares.

LS17,LS38,LS3j no luck !!!!

HELP ME

'_*13*_'
|+\__/+|
|++\/++|
|_|\/|_|

(in reply to wvi)

WHY I'M NOT SO LUCKY??????????????? MY LITEON 12101B CANNOT BE REPAIRED. WHEN JUMPER IS ON, BIOS DETECTS IT AS "GLKJÑDFGJGARBAGE" THEN PFLASH SAYS:

Data compare fail in Address 0 Expect 0 Got 0x63
Data compare fail in Address 0x1 Expect 0 Got 0xf8
.
etc (many others)
.
Too many compare errors.
Errors in Data Compare. Flashup stopped.

HOW CAN I CHANGE THE BIOS CHIP??

(in reply to wvi)

Hi

I did exactly the way u decribed it y putting the jumper on the two pins but I still get the "atapy soft reset failed" and something like "inquiry+atapi command error".
But most important of all. is after inserting the jumper where the pin is, the drive was not detected at all and i have try putting the jumper in the two upper pins nut same result.

If u can give some suggestions that would be great.


Thanks

(in reply to wvi)

I fried my brand new 40 speed trying to overclock it to 48 speed. This was down to a bad floppy. I rebooted and new detection of my drive, i do have others in though. So i prepared a new floppy and checked it this time, everything seems ok, so i reboot with the floppy in, and tried flashing my drive again, (from pure DOS may i add). Well would you believe it, no messing with jumpers or anything, it re-flashed it and works as a 48 speed and everything recognises this to be a 48 speed lite-on. So i am now gonna get another 40 speed Lite-On, and convert that one too. Brill drives, keep up the good work Lite-On.

(in reply to wvi)

I think I have another way to recover it.

I flashes any 32x firmware to my 24102B.(Please don't blame my fault..)Everybody know that 24102B can't be flashed to a higher model.So you know I get my 24102B dead.
(The LED remains light since boot & it can't be detected in POST procedure. It also occured no matter how many times I boot... )

Oh my god,can someone help me ...?

Finally I have a idea to download a firmware in binary form (you can get any version suitable for your model in the hyperlink appeared in this website), flash it then I see the LED turns off.

Then when I boot again I see my 24102B detected.
Oh yes, I think I make it.

Then I also find a dead one could be recovered no matter how long it has been flashed ,even if you turn off & boot again.

In other way,you can flashes it in wrong fireware and recover it with it's suitable fireware every time when you like...

This is my experience in 24102B model.I can't make sure if it could work in other model....

(in reply to wvi)

but when i flashed my 12101b with ls17.bin,it doesn't work, i updated it to ls38,it doesn't work yet.who can tell me why?

(in reply to wvi)

Hello,

after I#180;ve read this thread (because I own a LTR12101B) I got I deadflashed LTR12101B from a friend. I set the jumper
and the drives was recognized as LTR-Boot-something. But when I tried to flash with ls17.bin,
the flash fails with the same error messages as MACHURIAN already mentioned. So I used
another firm, the ls38.bin and everything did well! The drive works fine again, but it seems to me that there are different models with the same Name out on the market, because my own
drive could be updated using the dos flash utility form MATTHEW, but the drive from my friend couldn#180;t. My drive was build in Jan. 2001, the Drive from my friend was Feb. 2001.

Using the Winflash utility with my friends drive it was dead again, but i could recover it again with ls38.bin.

(in reply to wvi)

Does anyone know of any jumper trick for Ricoh? I flashed it with wrong firmware and now it's dead [B)]

(in reply to wvi)

quote:

---

Originally posted by shepherd

I think I have another way to recover it.

I flashes any 32x firmware to my 24102B.(Please don't blame my fault..)Everybody know that 24102B can't be flashed to a higher model.So you know I get my 24102B dead.
(The LED remains light since boot & it can't be detected in POST procedure. It also occured no matter how many times I boot... )

Oh my god,can someone help me ...?

Finally I have a idea to download a firmware in binary form (you can get any version suitable for your model in the hyperlink appeared in this website), flash it then I see the LED turns off.

Then when I boot again I see my 24102B detected.
Oh yes, I think I make it.

Then I also find a dead one could be recovered no matter how long it has been flashed ,even if you turn off & boot again.

In other way,you can flashes it in wrong fireware and recover it with it's suitable fireware every time when you like...

This is my experience in 24102B model.I can't make sure if it could work in other model....

---

Hey how can u flash when you can't detect the drive?

(in reply to wvi)