This tool is obsolete and no longer available. Please use the new [thread=97590]OmniPatcher[/thread].<HR>
Speedhacking Tool Pack for LiteOn DVD Writers
What is speedhacking?
DVD writers keep track of various DVD media codes and what speeds media with certain media codes are certified for. The speeds the media is certified for is what the DVD writer will allow you to write the media at. Speedhacking is the process of changing this list of media codes stored in the DVD writer so that it will think that a disc that is certified for a particular speed is actually certified for another speed.
What can I do with speedhacking?
The most popular and common use of speedhacking is making the burner think that your 4x-rated media is actually certified for 8x. This would allow you to burn 4x media at 8x speeds (4x@8x). There are other uses for speedhacking, such as enabling 4x burning for 2x media (2x@4x), or enabling 1x burning for media where 1x burning is turned off (this may interest some people, as LiteOn disabled 1x burning for 1x-certified Princo discs; speedhacking can re-enable 1x burning for these discs).
How is speedhacking different from overclocking?
Overclocking a drive, such as converting the LDW-451S to a LDW-451S@851S, allows the burner to burn at 8x on media that supports 8x burning. Speedhacking deals with the “on media that supports 8x burning” part by making the burner think that certain 4x media supports 8x burning. If your burner doesn’t support 8x burning, telling the burner that your 4x media supports 8x won’t do anything, as the burner will still burn at a max of 4x. You’ll have to overclock your burner first to support 8x burning before a 4x@8x speedhack will do you any good. In short, these are two different, but somewhat related topics. Speedhacking, when used for enabling 4x@8x for certain media, can be seen as a supplement to overclocking.
How can these tools help me?
Without these tools, speedhacking would entail manually editing the drive’s firmware, changing the values of a few bytes here and there. It’s not a particularly difficult process, but not everyone is comfortable manually editing their firmware, not everyone has a hex editor to do the editing with, not everyone knows how to use a hex editor, and because the locations of the bytes that need to be changed varies between firmware versions, not everyone is comfortable searching out the location of the media code tables and figuring out which byte is the right byte to change. Finally, for people who are comfortable doing manual hacks, it is a somewhat tedious and annoying process, especially when dealing with the -R media table where it’s necessary to count bytes to make sure that you’re at the right position. These tools automate the speedhacking process and make it a much easier and less intimidating process.
How safe is speedhacking? Are there any undesirable side effects?
When done correctly, speedhacking should be a perfectly safe process with no side effects (such as changes in write-quality). For each media code that gets speedhacked, only one byte is flipped in the firmware. Speedhacking does NOT affect the EEPROM in any way! However, keep in mind that not all media can be burned very well at overspeed. Only certain good media have been known to burn well at overspeed. Thus, do not be surprised if an overspeed burn turns out poorly, as the media was never designed for overspeeding.
What drives can I use this with?
These tools can only be used on firmwares for LiteOn DVD writers. These tools have been tested successfully on various firmware versions, both old and new, for the 401S, 411S, 451S, 811S, 851S, and 812S. With the exception of old versions of the 401S firmware, these tools should work on any firmware version for any LiteOn DVD writer, including OEM-rebadged LiteOn drives. Additionally, these tools work on both .BIN and .EXE firmwares.
<HR>Latest version is 3.1.1 (27 May 2004)
Download from: http://codeguys.rpc1.org/patchers.html<HR>
Q: What about faster reading speeds?
A: The speedhacking tool is for patching burning speeds. Use Readhacker to patch reading speeds.
Q: What media can burn well at overspeed?
A: Check my list at the bottom for media that members of this forum have confirmed to work well at overspeed. If you’re not sure, you could always test it and find out. Just be sure to report back with your results so that people can benefit. Also, it’s still recommended that you try things out because both burners and media do vary, and just because someone had good results won’t mean that you will, and just because someone had bad results won’t mean that you will.
Q: How do I use this tool? How do I patch my firmware? How do I…?
A: Please read the documentation first. If you still have questions, feel free to post them in this thread, and I’ll try to get them answered.
Q: What about other drives? And tweaking write strategy tables? And why don’t you have to edit the write strategies to get speedhacking to work?
A: I don’t know much about NEC/Pioneer drives. As I gather from reading posts about NEC and Pioneer hacking, it seems that the process on those drives is more involved. In regards to write strategies, the speed is specified independently of the write strategy, which is why speedhacking works without having to mess with the strat tables. Whether or not messing around with the strat tables would make speedhacking work better is unknown (probably yes, but I haven’t played around with it enough to say much). One thing is for sure, though: LiteOn strat tables are convoluted and somewhat difficult to parse (multiple tables scattered all over the place). The formatting and placement of the tables also seem to vary a lot between firmware versions, which has so far discouraged me from doing much with the strat tables (I did try once, and got slightly improved results, but it really wasn’t worth the effort needed). In any case, as speedhacking seems to work fine right now without any tweaking of the write strategies, I’m content leaving things as it is.
Confirmed reports of media codes that work well when speedhacked.
*) CMC MAG/F01/00, 4x +R media, burned at 8x
*) CMC MAG/R01/00, 2.4x +R media, burned at 4x
*) MCC/002/00, 4x +R media, burned at 8x
*) RICOHJPN/R00/01, 2.4x +R media, burned at 8x
*) RICOHJPN/R01/02, 4x +R media, burned at 8x
*) RITEK/R01/01, 2.4x +R media, burned at 6x
*) YUDEN000/T01/00, 4x +R media, burned at 8x
*) BeAll G4001, 4x -R media, burned at 8x
*) MCC 00RG200, 1x/2x -R media, burned at 4x
*) RITEKG03, 1x/2x -R media, burned at 4x
*) RITEKG04, 4x -R media, burned at 8x
*) TAIYOYUDEN, 1x/2x -R media, burned at 4x
Special thanks to… ala42 for posting the +R hacking instructions that I used to develop the +R/W patching process… ala42 again for helping me out when I was trying to figure out the format of the -R/W codes… pinto2 for writing the graphical guide for the commandline tool (which he discontinued after the GUI came out)… and everyone in the forum for your encouragement and support.