Print

[nahid569]

hello, last time this happened to me I loaded the ISO instead of the DVD file. You seem to have loaded the DVD file so your fine but maybe the DVD file is not right. Also did you set the number to 1913760.

[prelude]

QUOTE(nahid569 @ Sep 16 2008, 05:27 AM)

hello, last time this happened to me I loaded the ISO instead of the DVD file. You seem to have loaded the DVD file so your fine but maybe the DVD file is not right. Also did you set the number to 1913760.

yep the .dvd file has the layer break info in it.

[nahid569]

ok there is the problem, you have to set the layer break in IMGBURN or dvd decryptor manually. Its under ISO write mode and then layer break is right there. After doing that remove the layer break info from the DVD file and just have the ISO on it. You should be perfect then

[prelude]

QUOTE(nahid569 @ Sep 16 2008, 07:45 PM)

ok there is the problem, you have to set the layer break in IMGBURN or dvd decryptor manually. Its under ISO write mode and then layer break is right there. After doing that remove the layer break info from the DVD file and just have the ISO on it. You should be perfect then

if i set the layer break manually in imgburn, would it make a difference if i load the .iso instead of the edited .dvd file as you mention?

[cory1492]

QUOTE

I 19:41:07 Optimal L0 Data Zone Capacity: 1,913,760
I 19:41:07 Optimal L0 Data Zone Method: Copied From Original Disc

Setting it manually in imgburn will not overcome these two problems:

QUOTE

I 19:41:07 Destination Device: [0:1:0] HL-DT-ST DVDRAM GSA-4163B A106 (F:) (ATA)
I 19:41:07 Destination Media Type: DVD+R DL (Disc ID: RITEK-S04-66) (Speeds: 2.4x)

1 - it is a really old disk drive (they were made back in 2004/2005 if what I'm googling is correct)
2 - RITEK-S04 are relatively new and still a somewhat uncommon media code (Ritek's are just plain crappy disks to begin with, though S04 is an improvement over D01)

The problem is, your drive doesn't support that media/type of disk. Either get a new burner, or hope there is a firmware update for yours that does support that media code (highly doubful), or get disks that yours can support (ritek D01 or verbatim/mkm 001.) The errors imgburn is giving you should be rather clear that the drive does not support writing any data sectors on that type of disk... though it looks like it did the lead in/out ok (meaning that disk was probably coastered.)

[prelude]

QUOTE(cory1492 @ Sep 17 2008, 10:22 AM)

He set the break just fine, see where it says in the log

Setting it manually in imgburn will not overcome these two problems:

1 - it is a really old disk drive (they were made back in 2004/2005 if what I'm googling is correct)
2 - RITEK-S04 are relatively new and still a somewhat uncommon media code (Ritek's are just plain crappy disks to begin with, though S04 is an improvement over D01)

The problem is, your drive doesn't support that media/type of disk. Either get a new burner, or hope there is a firmware update for yours that does support that media code (highly doubful), or get disks that yours can support (ritek D01 or verbatim/mkm 001.) The errors imgburn is giving you should be rather clear that the drive does not support writing any data sectors on that type of disk... though it looks like it did the lead in/out ok (meaning that disk was probably coastered.)

thanks corey1492 for your input. i actually had the same "invalid address for write" error even using verbatim (made in singapore) discs. you are correct about the drive being old and i've already updated to the latest firmware after the first coaster. it didn't make any difference though.

you've also confirmed my suspicion that manually setting the layer break or loading a .dvd file with layer break info doesn't change anything, lucky i didn't have time to try this yet or another coaster for me.

in addition to my drive, i've also tested it on my brothers laptop which contains another older lg supermulti drive (but different model) with the exact same error.

this weekend i will try burning my backup image at a friends house and see if i can get a good burn. then hopefully i will find the culprit, whether i got a bad batch of discs or my lg burner.

on a side note i've searched on google and found at least one other person with the same burner as me successfully burning 360 backup image OK.