Help! DH20A4H QP53 problem

Hi All!

I’m new here and it seams that you guys make burning DVD’s into a science, so what better place to ask for advice concerning my DH20A4H dvd burner then here?

The thing is the thing won’t burn my DVD+R DL disks. I got several brands, including EMTEC and VERBATIM with mediacodes RICOHJPN-D01-67 and MKM-003-00.

Normal DVD+R disk are no problem, 16x al of them. But no go for the DVD+R DL’'s… even at 1x writing speed.

The software I use: Nero 8 and imbBurn. The pop-up i get with imgburn when i want to burn a DVD+R DL, is this:

I 12:43:47 ImgBurn Version 2.4.1.0 started!
I 12:43:47 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)
I 12:43:47 Total Physical Memory: 261.616 KB - Available: 53.736 KB
I 12:43:47 Initialising SPTI…
I 12:43:47 Searching for SCSI / ATAPI devices…
I 12:43:47 Found 2 DVD-ROMs, 1 DVD±RW and 1 DVD±RW/RAM!
I 12:44:28 Operation Started!
I 12:44:28 Source File: ***********
I 12:44:28 Source File Sectors: 3.825.924 (MODE1/2048)
I 12:44:28 Source File Size: 7.835.492.352 bytes
I 12:44:28 Source File Volume Identifier: **********
I 12:44:28 Source File Volume Set Identifier: 34672923
I 12:44:28 Source File Implementation Identifier: Sonic Scenarist 3.1
I 12:44:28 Source File File System(s): ISO9660; UDF (1.02)
I 12:44:28 Destination Device: [1:1:0] ATAPI DVD A DH20A4H QP53 (E:) (ATA)
I 12:44:28 Destination Media Type: DVD+R DL (Disc ID: RICOHJPN-D01-67) (Speeds: 4x; 6x; 8x)
I 12:44:28 Destination Media Sectors: 4.173.824
I 12:44:28 Write Mode: DVD
I 12:44:28 Write Type: DAO
I 12:44:28 Write Speed: 1x
I 12:44:28 Link Size: Auto
I 12:44:28 Test Mode: No
I 12:44:28 OPC: No
I 12:44:28 BURN-Proof: Enabled
I 12:44:28 Book Type Setting: DVD-ROM
I 12:44:28 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes
I 12:44:28 Optimal L0 Data Zone Capacity: 1.913.760
I 12:44:28 Optimal L0 Data Zone Method: Copied From Original Disc
E 12:46:14 Failed to set L0 Data Zone Capacity!
E 12:46:14 Reason: Power Calibration Area Error
E 12:46:14 Operation Failed! - Duration: 00:01:46

Now what is my problem? Maybe you guys know something. I also tried the 20A4H.QP53A.patched-fb-eos-eoht firmware, posted elsewhere on this forum, but it didnt change a thing…

Also I’m not realy intrested in speed… 2,4 speed burns are fast enough for me, as long as the come out good.

Thx in advance,

S!

Welcome to CD Freaks. :flower:

Is that the same error you get with MKM 003 [the part you bolded]? If so, do you get it with every speed you select up to 8x?

Hi there! Thx for the quick reply! :bow:

Yes that is the same message when i use MKM-003-000 discs, with different speeds tried…

However I just managed to start burning one of my EMTEC discs after using a lot of DVD+R’s, only to find out it would only go half way… :rolleyes:

Here is the log:

I 13:17:09 Operation Started!
I 13:17:09 Source File: **********
I 13:17:09 Source File Sectors: 3.825.924 (MODE1/2048)
I 13:17:09 Source File Size: 7.835.492.352 bytes
I 13:17:09 Source File Volume Identifier: ***********
I 13:17:09 Source File Volume Set Identifier: 34672923
I 13:17:09 Source File Implementation Identifier: Sonic Scenarist 3.1
I 13:17:09 Source File File System(s): ISO9660; UDF (1.02)
I 13:17:09 Destination Device: [1:1:0] ATAPI DVD A DH20A4H QP53 (E:) (ATA)
I 13:17:09 Destination Media Type: DVD+R DL (Disc ID: RICOHJPN-D01-67) (Speeds: 4x; 6x; 8x)
I 13:17:09 Destination Media Sectors: 4.173.824
I 13:17:09 Write Mode: DVD
I 13:17:09 Write Type: DAO
I 13:17:09 Write Speed: 4x
I 13:17:09 Link Size: Auto
I 13:17:09 Test Mode: No
I 13:17:09 OPC: No
I 13:17:09 BURN-Proof: Enabled
I 13:17:09 Book Type Setting: DVD-ROM
I 13:17:09 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes
I 13:17:10 Optimal L0 Data Zone Capacity: 1.913.760
I 13:17:10 Optimal L0 Data Zone Method: Copied From Original Disc
I 13:18:17 Filling Buffer… (20 MB)
I 13:18:18 Writing LeadIn…
I 13:18:20 Writing Session 1 of 1… (1 Track, LBA: 0 - 3825923)
I 13:18:20 Writing Track 1 of 1… (MODE1/2048, LBA: 0 - 3825923)
I 13:18:20 Writing Layer 0… (LBA: 0 - 1913759)
I 13:30:14 Writing Layer 1… (LBA: 1913760 - 3825923)
W 13:30:23 Failed to Write Sectors 1927072 - 1927103 - Reason: Write Error
W 13:30:23 Retrying (1 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (2 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (3 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (4 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (5 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (6 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (7 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (8 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (9 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (10 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (11 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (12 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (13 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (14 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (15 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (16 of 20)…
W 13:30:25 Retry Failed - Reason: Invalid Address For Write
W 13:30:25 Retrying (17 of 20)…
W 13:30:26 Retry Failed - Reason: Invalid Address For Write
W 13:30:26 Retrying (18 of 20)…
W 13:30:26 Retry Failed - Reason: Invalid Address For Write
W 13:30:26 Retrying (19 of 20)…
W 13:30:26 Retry Failed - Reason: Invalid Address For Write
W 13:30:26 Retrying (20 of 20)…
W 13:30:26 Retry Failed - Reason: Invalid Address For Write
W 13:35:16 Retrying (21)…
W 13:35:16 Retry Failed - Reason: Invalid Address For Write
W 13:35:17 Retrying (22)…
W 13:35:17 Retry Failed - Reason: Invalid Address For Write
W 13:35:18 Retrying (23)…
W 13:35:18 Retry Failed - Reason: Invalid Address For Write
W 13:35:18 Retrying (24)…
W 13:35:18 Retry Failed - Reason: Invalid Address For Write
W 13:35:18 Retrying (25)…
W 13:35:18 Retry Failed - Reason: Invalid Address For Write
W 13:35:18 Retrying (26)…
W 13:35:18 Retry Failed - Reason: Invalid Address For Write
W 13:35:19 Retrying (27)…
W 13:35:19 Retry Failed - Reason: Invalid Address For Write
W 13:35:19 Retrying (28)…
W 13:35:19 Retry Failed - Reason: Invalid Address For Write
W 13:35:19 Retrying (29)…
W 13:35:19 Retry Failed - Reason: Invalid Address For Write
W 13:35:20 Retrying (30)…
W 13:35:20 Retry Failed - Reason: Invalid Address For Write
W 13:35:20 Retrying (31)…
W 13:35:20 Retry Failed - Reason: Invalid Address For Write
W 13:35:20 Retrying (32)…
W 13:35:20 Retry Failed - Reason: Invalid Address For Write
W 13:35:22 Retrying (33)…
W 13:35:22 Retry Failed - Reason: Invalid Address For Write
W 13:35:22 Retrying (34)…
W 13:35:22 Retry Failed - Reason: Invalid Address For Write
W 13:35:22 Retrying (35)…
W 13:35:22 Retry Failed - Reason: Invalid Address For Write
W 13:35:22 Retrying (36)…
W 13:35:22 Retry Failed - Reason: Invalid Address For Write
W 13:35:22 Retrying (37)…
W 13:35:22 Retry Failed - Reason: Invalid Address For Write
W 13:35:23 Retrying (38)…
W 13:35:23 Retry Failed - Reason: Invalid Address For Write
W 13:35:23 Retrying (39)…
W 13:35:23 Retry Failed - Reason: Invalid Address For Write
W 13:35:23 Retrying (40)…
W 13:35:23 Retry Failed - Reason: Invalid Address For Write
W 13:35:23 Retrying (41)…
W 13:35:23 Retry Failed - Reason: Invalid Address For Write
E 13:35:24 Failed to Write Sectors 1927072 - 1927103 - Reason: Write Error
E 13:35:24 Next Writable Address: 1913760
I 13:35:24 Synchronising Cache…
W 13:35:32 User opted to skip the ‘Close Track/Session/Disc’ functions.
E 13:35:32 Failed to Write Image!
I 13:35:33 Exporting Graph Data…
I 13:35:33 Graph Data File: C:\Documents and Settings\C. van den Bogaerd\Application Data\ImgBurn\Graph Data Files\ATAPI_DVD_A_DH20A4H_QP53_DINSDAG-6-MEI-2008_13-17_RICOHJPN-D01-67_4x.ibg
I 13:35:33 Export Successfully Completed!
E 13:35:33 Operation Failed! - Duration: 00:18:22
I 13:35:33 Average Write Rate: 3.767 KB/s (2.7x) - Maximum Write Rate: 5.585 KB/s (4.0x)

Judging form this information it seams that it just won’t burn “the double layer”… :sad:

Or am i wrong?

Try better media.

I was under the impression that the Verbatim MKM-003 discs were one of the best…

Which mediacode is a better choise?

You might also update the firmware to QP59. That should help. The link is somewhere here.

firmware QP59

http://www.badongo.com/file/8509699

but the link is more like dead

[QUOTE=khynho;2053004]http://www.badongo.com/file/8509699

but the link is more like dead[/QUOTE]

This should be the same file as originally posted to above:

http://rapidshare.com/files/113323578/QP59.rar.html

Be careful, I believe this is for “S” drives only (see laser diode/OPU discussion in this forum).

superhero

thanks superhero for re-upload the file. mine it’s A version but I want to try what my drive does with that firmware

[QUOTE=khynho;2053427]thanks superhero for re-upload the file. mine it’s A version but I want to try what my drive does with that firmware[/QUOTE]

You should flash only firmware for your drive not another drive in case of manufacture firmware cause doing so will void your warranty if you put wrong firmware flash. First you should try different media and also slow your burn speed down as well and not mutltitasking. Those are simple solution to first try before flashing…

Hi khynho, in this link you can find a test firmware (QPV1WIN) for the DH-20A4H “A” version. :wink:
I think it’s newer than unofficial QP59.

yes, I already know about warranty limitation, however I’m the kind of person who enjoy trying and learning new things.
but anyway thanks for the tips.

thank you very much, I’ve donloaded it now and flash was ok, may be, later I can put some scan.

yes, as far I know, it’s recent than QP59, 2008/01/24, while QPV1 is 2008/04/10.

btw I though that the QP59 firm mention above was “official”, I meam, it was uploaded by someone who own a DH-20A4H QP59 drive.
then I don’t know why if lite-on crew have been working in this drive they didn’t release a firm update on their page yet ???

seems that the QPV1 firmware didn’t work as I expected on my drive.
here you have two bad burns. I think I’ll go with the codeking’s QP53(A) firm but I need to investigate/try a little bit before end a conclusion