ala42...just curious i just got a new benq 1620...i sped up the cmc mag e01 to 12x. after a couple good burns it then will burn a sort of half circle at the end of burn. this doesn't mean the drive is going bad does it? i read somewhere that 12x burns with this media were pretty good, but 2 out of 3 or so doesn't sound to good to me. should i just put the max burn back to 8x and keep using that? is there any other strategy that worked for someone else?

Hard to say without seeing the scan. Even with a scan, one bad scan means nothing. Several bad scans only mean that your current batch does not like higher speeds.
It took me 9 burns (on stock firmware) and one week to decide (guess) that my first 1620 was bad. It got good results on TY and bad results on Ricoh media. The replaced drive burned the Ricohs fine, so my guess (hope) was right.
It is not so easy to decide if bad scans are caused by the firmware, the burner or the media as long as you just have one single drive.

@ala42,
Great tool for the BenQ community!

Any chance of making this work on the exe's as well as the cvt's?

I don't think because as somebody said on a thread, BenQ has its onw compression method, and BenQ changes it when he does a new firmware. So the hackers should work everytime to extract the CVT file. Thank you hackers too!

I could, but I am not shure if I should.

I only ask because I have been trying the Philips P3.4 firmware and can't find a cvt of it...know of any source?
How are these cvt's extracted anyhow?

MCSE currently only supports B7T9 for savety reasons. To enable +R changes, a critical change to the firmware is neccessary. I have not implemented a save autopatch yet.
More or less it is a simple copy operation. A hex editor and 10 minutes research will tell you how it has to be done.

I was just wondering if a patched cvt be put back into a exe?

I tell you maybe tomorrow .

MediaCodeSpeedEdit V 1.0.3.6 adds support for some further firmware releases. Here are the Benq/Philips relevant changes.
The patch mechanism is identical to the one used in V 1.0.3.5 for B7T9. The main job was to manually check that the patch mechanism also works with these firmwares. I have flashed MCSE modified files of these four firmwares to check the drive is still alive after flashing, but have not done any burning tests.

I just tried to load B7P9 into the patcher and it doesn't do anything.

Did the same for me and also 47L9 doesn't load. B7T9 still does though. Phillips 3.0 loads. I don't have 3.2 or 3.4 .cvt. ala42 or anyone have a link to those?

Does a hexdump of B7P9 @$20 look like this ?

Yeah ala42, Philips 3.0 (1640PP30.CVT) "loads" but still same problem as with MCSE version 1.0.3.5...

CVT's of 1640PP32 & -34 would be much appreciated.

Edit. ala42, something like this;

The four bytes at $20-$23 are not correct, change them to

Will do so.

I think it's on time you provide proper CVT's, compatible with your nice tool.

I need a hex editor or some different .cvts to use the tool

No

Thanks ala42. Now the new (1.0.3.6) MCSE tool is working great...

Just burned a RiTEKG04 at 8x on firmware B7P9.

So why are the bytes wrong?
Is it just the way someone else extracts them?

Do all the .cvts that don't work need the same 4 bytes changed at @$20?

Mine looks just like your attached image.

From the information I have in cvt files at address $20-$23 a length has to be stored, which may differ between different .cvt files. When loading a .cvt file MCSE performs a basic file check which also checks this length data. The TDB dos flasher will also not accept bad formed cvt headers.

Thanks,
The reason I ask is because I was trying to figure out cvt extraction and it seemed like that other cvt was right. If you have some tips for me shot them my way.

I'm using MCSE 1.0.3.6 with TDB's B79R RPC1 patched cvt and I'm having trouble with the media I'm trying to overspeed. They take a long time to start up (WOPC maybe?) For example, I'm trying to get MXLRG02@MXLRG03 (Qscan says they're ok to burn at 12x btw) but it just spins for a long time during the lead-in and eventually fails. I also tried OPTODISC OR4@CMC MAG M01 (@12x) and MCC003@MCC004 but they took forever to start up and then only burned at 4x.

Dvdinfopro shows the correct available write descriptors. I've tried a few times with both media and the same thing happens. I don't really want to waste any more media... My burner was working great before the flash. Has anyone else experienced this issue?