If one were to get a backed up eprom from someone, could they revive a dead drive. I have a dead 812, but no floppy.

Hi there,

Sure C0deking would rush to explain the real thing and give you the best advice

The EEPROM is unique for each unit, i.e. you should not replace your 812 eeprom with the eeprom of another 812 owner.

As far as I know, there is a fixed part of the EEPROM unique for your writer [really unchangeable], but there is another part [checksum] related to that part that would be replaced if you write the EEPROM content of ANOTHER unit. Then problem arise...

Knowledge is power, ....

Good point. Thank you,

@40tacos
Thanks for your reply in the other thread. Yes they're all burnt at 8x except the middle although CopytoDVD requested 8x writing but only 6x effective!!! i just updated to the newest ver 3.0.34 and the program reduced the speed to 6x compared to the others burnt at 8x with ver 3.0.32 with 8x effective. I guess that's why i got the better result? Any idea why the speed was reduced? something to do with the program (newer ver) or the EEPROM Utility (after resetting learnt media)? By the way i attach a scan of Taiyo Yuden DVD-R burnt @8x. is it a good burn? i havent seen a TYG02 scan before. Thanks

This is my first time playing around with Codeguys' new EEPROM Utility. I can't believe what i've got!!! The best burn ever with a cheap media??? Anyone can beat that? Any comments? The media was written at 6x. I don't know why copytodvd can only burn this kind of media at 6x although it's a 8x certified media. ( 8x wrting requested but 6x effective). Anyway i'm happy with the result (much better than TYG02 above) though it was a bit slow @6x. Thanks Codeguys.

Wow.. Thats some good scan with the cheap media that your using..

Ive found that burn quality varies with different types of burning software.. Ive gotten different results when using Nero, CloneDVD and others.. You should see how those do with the same media..

BTW: You may be able to achieve the 8x burn your looking for with other burning software..

Please correct me if I am wrong but isn't the above function encouraging in some way to play with the eeprom. The only difference about playing with the eeprom would be, using a utility instead of changing things manualy. Either way its still playing with the eeprom whether you are doing it manualy or not.
I only ask because its the best way to understand

Agreed.Well, the 'fixed' part, the first 64 bytes, is not really fixed, it can be changed. Right, the checksum depends on some bytes of that part. Omnipatcher crossflash option disables this check, so the checksum is not really a problem. The main problem is that nobody outside Liteon knows what these 64 bytes are used for.
Each drive has a (changeable) calibration area that is optimised for the drive specific OPU and analogue hardware. These values are unique for each drive, so taking these values from another drive usually makes no sense. Changing these values influences the write, but not the read behaviour of the drive.
Do not play around with your eeprom settings unless you know what you are doing or you can afford the total loss of your drive.

hrm... now I wonder what the 411S@811S patcher really does... if it in fact modifies the unique portion of the eeprom, perhaps that's why so many people have problems with bad burns... who knows...

The Z-Mod patcher adds data to the eeprom which was not available before because the 411 firmware did not use some eeprom addresses at all which were used by the 811 firmware. The missing data caused major problems especially on DVD-R media before. Z-Mod V4 uses the identical average calibration values gathered from a large amount of real 811 eeproms for each drive it is applied on. This approach works for drives which are close to the average, but will produce bad results for non average drives.

I have Lite-On 411S@811S patched with Zebra Mode 6 months ago so far has work as 811S flawlessly both +/_ Rs. I also burning majority of brand DVD disc 4X (+R) at 8X without any difficulty. Needless to say I have also speed hacked the drive with Codeguys.

/me @ 26 = still 20/20 vision
A little more playing couldn''t hurt

Find below Scans of princos

After clearing the eeprom, I have much higher PI but lower PIF.

The first scan was burnt AFTER eeprom clearing
The second scan was an existing DVD-R burnt at 4x before eeprom clearing

why two different media brands, shouldn't u be comparing two of the same media?

i just used the tool with my 812s@832s, can't wait till i burn one of my ritek G04's and see what's it like, i'll try and post one if i do.....

You can't compare the PIF values debro. They use different PIF sum ECC block. The princo graphic is using 1, the ricoh is using 8 (version 2.3.0 of Kprobe2 was using 8 and you couldn't change it).

I cannot get this to work on my "straight out of the box, never burned a disc yet" 1633S. When I try to backup firmware I get a 1k file, and omnipatcher says it is an "invalid .BIN size".
My current firware is BS06 if that makes a difference.

Jeez, you are backing up EEPROM = 1kb. NOT the firmware!

Please read before you apply this tool , or even better don´t use the tool untill you know what you are doing.

lol.

Oops. Cheers. Just out of bed, jumped straight in. Not usually just as thick as this!!

I appreciate your concerns but from many hours studying the firmware and eeprom images, we know that the areas, that we are changing, are safe to set to the values that we are changing them to. Also as we have provided a function to backup the eeprom first and then automated the reset learn process, there is little to no risk involved.

Yes, I´m sure you are right on that one.
When I put a word of warning above, I had "self modders" in mind.

But still, I think we have to make some kind of guide. Now there are two nice tools. One "too much".

Apologies for above scan .... A little confusing, it was done a while ago, and I replaced the media before I saved the scan, back when i was batch scanning for another thread. [b]The scan WAS a princo[b]. Regardless to say, I have deleted the offensive file.

Find below, the series ranging from previous media, through to
1) Immediately after clearing eeprom (above) - 8x burnt
2) Second burnt after eeprom cleared - 8xburnt
3) Thrid burnt after eeprom cleared - 8xburnt
4) Fourth burnt after eeprom cleared - 8xBurnt
5) Immediately after clearing eeprom. - 4xBurnt

Previously burnt Princo Media.

2nd after clearing eeprom - Burnt at 8x

3rd after clearing Eeprom - burnt at 8x

4th after clearing EEprom - burnt at 8x