Category: Windows / CD/DVD Tools

License: Freeware

Limitations :

OS: Windows All

Size: 0.67 MB (695,197 bytes)

Introduction: OmniPatcher for LiteOn/Sony Optical Drives - A graphical all-in-one patcher for... just about anything! Make a custom-patched firmware tailored for your own needs with this patcher! Here are some key features of "OmniPatcher": · Loading your file · To load a file, you can either use the "Load" button to select a file or just simply drag a file into the main OmniPatcher window. OmniPatcher will work with both .BIN and .EXE firmwares. You can obtain .BIN firmwares by downloading them from dhc014's firmware page or our firmware page or by extracting the firmware from your drive. You can obtain .EXE firmwares by downloading them from the official LiteOn website, from dhc014's firmware page, or from our firmware page. Please note that OmniPatcher does not work with scrambled/compressed executable firmware flashers (all official LiteOn flashers from mid-2004 onwards are scrambled/compressed)! However, you can find firmwares repackaged in unscrambled firmware flashers on dhc014's firmware page and our firmware page. · Saving your file · When you are done selecting all the changes that you want, clicking "Save As" will allow you to choose a filename for your patched firmware. Once you have picked a filename, OmniPatcher will patch the firmware and save it. · · Note: If you loaded a .EXE firmware, you will have the option in the save dialog to save it either as a .EXE firmware or to save it as a raw .BIN firmware. · · Loading your patched firmware into your drive · If your patched firmware is an .EXE file, simply run the .EXE file to flash your drive with your custom-patched firmware. If your patched firmware is a .BIN file, you will need to use LtnFW to load the firmware into your drive. · OmniPatcher Reference: Drive ID · In addition to displaying some basic information about the firmware that you have loaded, you are given the ability to rename the firmware's drive identification. Why would anyone want to do this? First, some people just prefer certain names. Second, some of the bundled software may be locked to a certain drive name. For example, the software bundled with Sony drive will work only if the drive identifies itself as a Sony drive. This way, you can load a LiteOn firmware onto a Sony drive without losing the Sony drive identification. · OmniPatcher Reference: DVD Media Support (only for DVD-writers) · Adjusting write speeds · This is what was formerly known as "speedhacking." In case you are not familiar with it, this will allow you to specify what speeds your burner will allow you to burn certain media at. This is the tool to use if you want to enable 8x burning on 4x-certified media, for example. To use this, simply scroll down the list until you find the media code corresponding to the media that you are using and highlight it. And then on the right, you can select what speeds the drive will allow you to burn the selected media type at. Please note, however, that not all disc types can burn well at higher-than-rated speeds, and this is especially true for low-quality media. And then there are some media types (like the ever-popular RICOHJPNR01) that actually burn better at the higher 8x speeds. This is why you, the user, are given the option to choose which discs you want to allow overspeeding on--try out different speeds and see what works best for your drive/media combination. · A common question that gets asked is why this does not allow people to burn above 4x on their 4x-rated burners. Changing the speed limits for media types is different from overclocking (crossflashing) your drive. The latter is when you change your drive's maximum speed allowable speeds, and this tool allows you to then select which of the available types of media the drive will allow to be burned at that maximum speed. · Warning: Although it is possible to overspeed +RW discs, it is not recommended! You could potentially ruin your disc! -RW overspeeding is a bit safer. · Renaming media codes · Simply select the media code that you wish to rename and edit its MID, TID (for +R only) and RID using the text input boxes on the right. This may be useful if you want to add support for a media type that is unsupported. The way you would do this is to rename an unused code to the code of the unsupported media type and then use strategy reassignment to assign it a suitable write strategy (this last step is important!). · Another use for this feature is to simulate strategy reassignment on firmwares where strategy reassignment is not supported. If, for example, you wish for RICOHJPNR01 to use the RICOHJPNR02 write strategy, then you would rename RICOHJPNR01 to RICOHJPNR02 and RICOHJPNR02 to RICOHJPNR01. This would cause RICOHJPNR01 to use the RICOHJPNR02 write strategy, but the unfortunate side-effect is that RICOHJPNR02 now uses the RICOHJPNR01 write strategy. As a result, if strategy reassignment is available, it is highly recommended that you use that instead of these crude strategy swaps. · Write strategy reassignment · Introduction: Each media code in the firmware has a "write strategy" assigned to it that will tell the burner how a piece of media should be burned. These write strategies are very closely tied to the burn quality of the media that you feed the drive. In many cases, the write strategy already in place for a particular media code is the best one to use. Using a write strategy that is very badly suited for a media type will most likely result in a bad burn and might potentially have negative effects on the laser of your drive, so going around reassigning write strategies at random is usually not a good idea, especially if the one specially designed for that media type already works well. However, there are some cases (especially when overspeeding) where using the write strategy for another media type will help improve burn quality. For example, overspeeding a PRODISCR02 to 8x using the PRODISCR02 code will most likely result in a coaster once the disc hits the 6x and 8x regions of the burn. However, if a PRODISCR03 strategy is used, the disc will burn much better when oversped to 8x. · How to do this: Double-clicking on a +R or -R media code (not RW!) should bring up a list of available write strategies that you can use for this media code. The write strategy currently in use will be highlighted. In the main window, any media code that is using a write strategy other than its own will be marked with a "!". The text below the media list will specify what media types strategy reassignment is available for in this particular firmware (none--when grayed out, +R only, -R only, or both +R and -R). · Note: Unlike write strategy swaps, these reassignments are much more elegantly implemented, and they do not carry any ill side-effects for the "host" media code. Also, the speed codes are actually considered to be a part of the write strategy. So you will also be reassigning your speed code as well. For example, if you reassign PRODISCR02 to use PRODISCR03's write strategy, PRODISCR02 will also use PRODISCR03's speed code. In this example, this would mean that any changes to PRODISCR02's speed code using OmniPatcher will have no effect on PRODISCR02's speed, and any changes to PRODISCR03's speed code using OmniPatcher will affect both PRODISCR03 and PRODISCR02's speeds. · Recommended tweaks · These pre-defined speed adjustments and write strategy reassignments are ones that are generally known to work well. As the name suggests, applying them is usually a good idea. · The "More Commands" button · Save DVD media code report: This will allow you to save a report of the media support list for the currently loaded firmware to a text file, which is useful for reference, easy searching, etc. · Import speed and strategy settings from a report file: This command will load a report file and apply the media settings found in that report to the current firmware. When you save a media code report, the report will include any speed and/or strategy reassignment changes that you have made to the firmware's media support. Thus, this feature may be useful if you want to apply the changes that you made to one firmware to another firmware. For example, if you made a number of changes to the CS0K firmware and want to make those same changes to the CS0M firmware, you can use OmniPatcher to load the patched CS0K firmware and order it to save a media code report. Then, you can load the CS0M firmware and use this command to load the media report for the patched CS0K firmware and apply to CS0M any changes that you made to CS0K. · Rename this code using a media code block dump: This will allow the user to rename the currently-selected media code using the media code block of a disc, which can be obtained through programs such as DVD Identifier. This will make the renaming of codes to add support for unsupported media easier. · Reset media ID and speed changes for this code: This command will reset any name and speed changes that you have made to the currently-selected media code. Note that this command resets only name and speed changes and not write strategy reassignments. Also note that this command resets only the changes that you made since loading the firmware (i.e., any changes made prior to loading the firmware will not be reset). This command is useful if you want to undo the changes that you made to a media code, but do not remember what those changes were and do not want to re-load the firmware (which would, of course, reset all changes).