[QUOTE=ala42;2027500]There is nothing to fix. The firmware MID table scanner takes the first match when searching for MCC_____004, which is the correct entry. The bad entry is not used.[/QUOTE]
I love your program!
However, I must respectfully disagree with your assertion that there is nothing to fix, unless you mean in MCSE. I agree that the MCSE-patched firmware is not the source of the problem, so your program is performing its intended function flawlessly.
However, there is indeed something that needs fixed in the firmware, unless you know of some reason there is a duplicate and blank entry for MCC-004 firmware in this particular Pioneer model, or why I only experienced this issue with this media, and not the MCC-003 or MKM-001 media that I also use. It seems more than a coincidence.
From what you wrote that “firmware MID table scanner takes the first match…which is the correct entry.” Is that because it scans from end to beginning like Liggy suggested? If not, then the first in the table would appear to be the one with no speed info.
Also, can you explain why the EXACT SAME DISC that only offers 4X in my DVR-212 offers all the write speeds in my DVR-111? See the attached as proof. This was after inserting two discs that showed all available speeds for the DVR-212 in the ImgBurn windows, then the third (pictured) showed only 4X. This is in line with my observations that it occurs one-third of the time. ImgBurn clearly identified that disc as MCC-004, so shouldn’t the DVR-212 be reporting back all available speeds that corresponed to that MID?
So, recorder with no duplicate entry works correctly every time, and recorder with duplicate, blank entry works sporadically. Coincidence? Not likely. Deductive reasoning says there is a cause-and-effect relationship here.
By the way this is Verbatim MCC-004 media made in Taiwan, which is known to be good…
So, if everyone else is convinced there is no fix to the firmware needed and that the duplicate, blank entry is OK since it should never be referenced, then I’ll just have to choose one of my suggestions to patch it and see how it goes. Otherwise, I’ll keep running into this problem.
Note that this has occurred both when the recorder was flashed with DVR-212D 1.24 official firmware patched for speed and bitsetting (but not RPC1) with MCSE, and then crossflashed to a DVR-212 with DVRFlash and the kernel provided here, and then flashed directly to official DVR-212 1.24 firmware also patched for read speed and bitsetting with MCSE…