Problems when burning DVD+R DL with DVD Decrypter 3.5.4.0

[herrde]

Hi all,

I recently bought a DL recorder (BenQ DW 1640) and I am now doing my first steps into DL recording.

So far, I did a copy of Star Wars: Episode II (RC 2) using DVD Decrypter 3.5.4.0 in ISO mode (as I heard that it's no good to use Nero for DL burning). The copy runs flawlessly in all standalone players that I tested so far.

So far, so good.

Yesterday, I tried the same with "Starship Troopers" (also RC 2), again using DVD Decrypter's ISO read and write modes. I tried two different DVD+R DL brands, and both gave me write errors at the same point while burning, so I don't think it's a media related problem. The error message that DVD Decrypter gave me was something like "Invalid write address at XXXXXX - YYYYYY" (where, as I said, the addresses where completely identical with both media brands). Sorry that I can't remember the error message more exactly.

Now, I just read the ImgBurn 1.0.0.0. has been released, which uses the latest DVD Decrypter engine. But furthermore, it says on its homepage that the ISO engine has been improved a lot and that it actually parses the file etc. etc.

Will ImgBurn give me better results than DVD Decrypter? Or which program should I use to make backups of my DL DVD's?

Any help is greatly appreciated!

Thanks a lot in advance,

Gero

[herrde]

Hi A380,

thanks for your speedy reply!

In fact, you might be right - both failure discs had media code RITEK-D01-01, whereas my successful very first burn try was a Verbatim disc with a different media code...

The errors started at 51%, so I suppose you're right again - does "51%" always mean that it's the second layer?

Would it be possible that ImgBurn 1.0.0.0. burns those RITEK discs correctly (as opposed to DVD Decrypter 3.5.4.0? Or is there any other program I could try?

Thanks again!

All the best,

Gero

[feedback]

Would it be possible that ImgBurn 1.0.0.0. burns those RITEK discs correctly (as opposed to DVD Decrypter 3.5.4.0? Or is there any other program I could try?

Thanks again!

All the best,

Gero
I would try ImgBurn with the Ritek and see if they work. With the new and improved burning engine you may have more success.
It is one of the better burning apps. available.

I have heard the ONES is good, it uses fuzzy logic, but it is not free.

[FilipeAmadeuO]

Have you tried upgrading your DL recorder (BenQ DW 1640) firmware ?

[herrde]

@feedback: ok, I am now off to my elecronics store to get some more RITEKs in order to do more testing. I will post the results here later on!

@Filipe: yes, my DW 1640 has the latest firmware (BSLB)!

Thanx,

Gero

[herrde]

I'd say that your dvd burner doesn't like the Ritek and I think that using ImgTool doesn't change that although I'd give it a try if you have some Riteks on your table.

I have come to the same conclusion now as I did a few more tests. I tried another RITEK disc with ImgBurn and the same original movie DVD - same result as with the other RITEKs, burning stopped at about 50% with an error message. Then I tried another RITEK with the same DVD again, but this time with the latest NERO version - again, the same result, stopped burning at the layer change.

To be perfectly sure, I then tried the movie DVD with ImgBurn and a Verbatim disc - worked flawlessly!

So it seems to be a matter of fact that the BenQ DW 1640 doesn't like the RITEK Double Layer media at all (at least not the "+" version) - which I think is a shame, because exactly that media type is on the actual media compatibility list for the BenQ DW 1640!!!

I hope that BenQ is going to fix this with the next firmware version - I hate it when I can't use any media that is certified and made for my burner!!!

Thanx for all your advice!

Gero

[setarip_old]

@herrde

having read MANY posts at several different forums regarding DL DVD+Rs, it appears that presently the most/only reliable DL DVD+R media for ANY burner is Verbatim...

[herrde]

Hi,

just a small update - I have now received and tested those RICOH printable DL's (manufacturing ID: RICOHJPN-D00-01) too.

Everything ran completely ok, the disc was burned fine and it also runs well in both of my standalone DVD players.

So it seems that so far that the only manufacturer that shouldn't be used is in fact Ritek...

All the best,

Gero

[setarip_old]

I have now received and tested those RICOH printable DL's (manufacturing ID: RICOHJPN-D00-01) too.
Everything ran completely ok, the disc was burned fine and it also runs well in both of my standalone DVD players.

Congratulations on finding D/Ls that work for you!

[herrde]

Congratulations on finding D/Ls that work for you!
Well, as I wrote further above, the Verbatim DLs work even better for me - they seem to be the best for every DL writer at the moment according to all forum posts in this forum and on club.cdfreaks.com...

Best,

Gero

[setarip_old]

Yes, and as I posted earlier in this thread, I'm amongst those feeling comfortable with Verbatim - but it's still good to know that the Ricoh media you've purchased works for you ;>}

[blutach]

I completely agree with setarip_old - I only use Verbatims for DL burning (about 10 so far) and no coasters. They are pricey but great disks.

Regards

[Rozy1]

blutach, your guides are great, and helpful!

I too am having trouble buring with Memorex /Ritek media (D01) with 2 successful and 3 coasters. 1 coaster said it burned ok, but wouldn't play. The others and 2 discs I returned had the errors described below.

My question is is this a media problem because the log says check condition? Or invalid address for write? I cannot believe it is that hard to make these discs consistently. I have checked my aspi layers, read every forum imaginable and created the iso with PGCEdit meticulously.

The last step will be to get rid of all nero programs and remnants on my computer, try again, then off to OfficeMax for some Verbatims. It seems if it is the media then sooner or later one of these remaining 20 discs will be successful with this same iso file right?

BenQ 1640 fw BSMB
Decrypter 3.5.4.0/ImgBurn/PGCEdit all updated

[Rozy1]

Here's the iso creation information:

mkisofs log for DVD "CRASH"
From: "H:\Crash"
DVD-TEXT General Name: ""
Provider ID: "CRASH"
Number of VTS: 14
Output file: "I:\CRASH.ISO"
Volume label: "CRASH"

mkisofs 2.01.01a03 X (i686-pc-cygwin)
Layer break is at absolute sector 2040288. (Offset in L0 is 11.)
Layer break cell:
2040277: VTST 1 , 1 TTN 1 (1:52:21) Title 1 Cell 14 (00:06:57.23), V/CID: 1/14

The pad was 11 for file VIDEO_TS.VOB
Total translation table size: 0
Total rockridge attributes bytes: 0
Total directory bytes: 6296
Path table size(bytes): 42
Max brk space used c000
4019169 extents written (7849 MB)

ISO created OK.





And the Iso Burn log:


I 00:34:06 ImgBurn Version 1.0.0.0 started!
I 00:34:06 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)
I 00:34:06 Initialising SPTI...
I 00:34:06 Searching for SCSI / ATAPI devices...
I 00:34:07 Found 1 DVD+RW and 1 DVD±RW!
I 00:35:49 Operation Started!
I 00:35:49 Source File: I:\CRASH.ISO
I 00:35:49 Source File Sectors: 4,019,169 (MODE1/2048)
I 00:35:49 Source File Size: 8,231,258,112 bytes
I 00:35:49 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING
I 00:35:49 Source File Implementation Identifier: mkisofs
I 00:35:49 Destination Device: [2:0:0] BENQ DVD DD DW1640 BSMB (E:) (ATA)
I 00:35:49 Destination Media Type: DVD+R DL (Disc ID: RITEK-D01-01) (Speeds: 2.4x)
I 00:35:49 Destination Media Sectors: 4,173,824
I 00:35:49 Write Mode: DVD
I 00:35:49 Write Type: DAO
I 00:35:49 Write Speed: 2.4x
I 00:35:49 Link Size: Auto
I 00:35:49 Test Mode: No
I 00:35:49 BURN-Proof: Enabled
I 00:35:49 Optimal L1 Data Zone Start LBA: 2040288 (VTS_01, PGC: 1, Cell: 14)
I 00:35:49 Optimal L0 Data Zone Capacity: 2,040,288
I 00:35:49 Optimal L0 Data Zone Method: IFO Cell Boundary, 'Seamless Playback Linked in PCI' Flag Not Set
I 00:35:49 Filling Buffer...
I 00:35:53 Writing LeadIn...
I 00:36:12 Writing Image...
W 00:58:21 Failed to Write Sectors 2040608 - 2040639 - Write Error
W 00:58:21 Retrying (1 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (2 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (3 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (4 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (5 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (6 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (7 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (8 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (9 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (10 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (11 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (12 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (13 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (14 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (15 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (16 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (17 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (18 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (19 of 20)...
W 00:58:21 Retry Failed - Invalid Address For Write
W 00:58:21 Retrying (20 of 20)...
W 00:58:21 Retry Failed! - Invalid Address For Write
W 07:40:45 Retrying (21)...
W 07:40:45 Retry Failed! - Invalid Address For Write
W 07:40:46 Retrying (22)...
W 07:40:46 Retry Failed! - Invalid Address For Write
W 07:40:47 Retrying (23)...
W 07:40:47 Retry Failed! - Invalid Address For Write
W 07:40:47 Retrying (24)...
W 07:40:47 Retry Failed! - Invalid Address For Write
W 07:40:47 Retrying (25)...
W 07:40:47 Retry Failed! - Invalid Address For Write
W 07:40:47 Retrying (26)...
W 07:40:47 Retry Failed! - Invalid Address For Write
W 07:40:47 Retrying (27)...
W 07:40:47 Retry Failed! - Invalid Address For Write
W 07:40:47 Retrying (28)...
W 07:40:47 Retry Failed! - Invalid Address For Write
W 07:40:47 Retrying (29)...
W 07:40:47 Retry Failed! - Invalid Address For Write
W 07:40:47 Retrying (30)...
W 07:40:47 Retry Failed! - Invalid Address For Write
W 07:40:47 Retrying (31)...
W 07:40:47 Retry Failed! - Invalid Address For Write
W 07:40:47 Retrying (32)...
W 07:40:47 Retry Failed! - Invalid Address For Write
W 07:40:47 Retrying (33)...
W 07:40:47 Retry Failed! - Invalid Address For Write
W 07:40:47 Retrying (34)...
W 07:40:47 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (35)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (36)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (37)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (38)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (39)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (40)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (41)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (42)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (43)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (44)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (45)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (46)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (47)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (48)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (49)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (50)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (51)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (52)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (53)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (54)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (55)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (56)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (57)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (58)...
W 07:40:48 Retry Failed! - Invalid Address For Write
W 07:40:48 Retrying (59)...
W 07:40:49 Retry Failed! - Invalid Address For Write
W 07:40:49 Retrying (60)...
W 07:40:49 Retry Failed! - Invalid Address For Write
W 07:40:49 Retrying (61)...
W 07:40:49 Retry Failed! - Invalid Address For Write
W 07:40:49 Retrying (62)...
W 07:40:49 Retry Failed! - Invalid Address For Write
W 07:40:49 Retrying (63)...
W 07:40:49 Retry Failed! - Invalid Address For Write
W 07:40:49 Retrying (64)...
W 07:40:49 Retry Failed! - Invalid Address For Write
W 07:40:49 Retrying (65)...
W 07:40:49 Retry Failed! - Invalid Address For Write
W 07:40:49 Retrying (66)...
W 07:40:49 Retry Failed! - Invalid Address For Write
W 07:40:49 Retrying (67)...
W 07:40:49 Retry Failed! - Invalid Address For Write
W 07:40:49 Retrying (68)...
W 07:40:49 Retry Failed! - Invalid Address For Write
W 07:40:49 Retrying (69)...
W 07:40:49 Retry Failed! - Invalid Address For Write
W 07:40:49 Retrying (70)...
W 07:40:49 Retry Failed! - Invalid Address For Write
W 07:40:49 Retrying (71)...
W 07:40:49 Retry Failed! - Invalid Address For Write
E 07:50:51 Failed to Write Sectors 2040608 - 2040639 - Write Error
I 07:50:51 Synchronising Cache...
I 07:50:52 Closing Track...
I 07:51:07 Finalising Disc...
E 07:53:23 Failed to Write Image!
E 07:53:23 Operation Failed! - Duration: 07:17:33
I 07:53:23 Average Write Rate: 156 KB/s (0.1x) - Maximum Write Rate: 3,360 KB/s (2.4x)






This shows that the bad address is AFTER the layer break (sector 2040608) where 2040288 is the break. If that matters.

[Rozy1]

After shutting down all things Nero:
For an update to anyone interested, Robots failed at the exact same sector with a new iso image from PGCEdit.

But Crash burned ok. And Inspector Gadget did too. Go figure. I'm off to buy Verbatims anyway.

[LIGHTNING UK!]

You should have no problems with the Verbatims.

Everything else in my log looked ok.

[Rozy1]

Thanks LUK! Here's what puzzles me though. I explored the discs on the computer and they had a video TS folder and all the appropriate .ifo and .vob files and the total size was exactly the same as the .iso image. This is after a burn which stopped at 50% with invalid adress errors.

I tried the discs (5 coasters) in a good Sony DVPNS90V (which plays almost anything) and it will play fine with the exception of the later chapters. (I am skipping thru or using the display mode to jump to the later chaps.) Using the disc menu to select the later chapters does not work either.

So, did all the information get to the disc? I assume some .ifo/pointer/map info didn't get there even though the movie itself did, huh. It just seems like it can't be that hard to make this media reliable, and it's easier to believe that either I made a mistake somewhere (the .iso files were ok from PGCEdit and your programs are easy to use though) or Fox has outsmarted me here with their protection. Thanks a million for your help!

[LIGHTNING UK!]

The file system is at the start of the disc, that's why it looks ok.

It would work ok until you hit whatever cell / chapter is on / after that sector it stopped on.

[Rozy1]

Thanks LUK and all for the advice. 2 Verbatims have burned successfully so far. I have e-mailed Memorex to return theirs.