dual layer dvd9 rite

[mazafaka]

2 ISOs (project size about 6.2 Gb) created one after another with pgcEdit (& mkisofs) have different content and size!

Please, explain.

What does mkisofs try to find in subdirs? Was ISO created correctly? See attachment.

PS Dear r0lZ, what about my previous post?

[r0lZ]

Still waiting for the attachments to be approved. If you want a quick reply, upload your files at yousendit.com (http://www.yousendit.com/) and paste the links here.

[mazafaka]

For post #94
http://sergepp.chat.ru/new-2.gif
http://sergepp.chat.ru/new-3.gif

For post #101
http://sergepp.chat.ru/NEUKROTIMAJA_log.txt

[lrosado]

Now that is an answer. Thanks for clearing it up for me r0lz, I fully understand the process that happens when a file is edited in anyway. I appreciate your help and patience, I just got into DL-DVD's. Thanks again, will stick with 1:1 copies using DVDDecrypter to rip to ISO then burn with DVDDecrypter/IMGBurn.

[r0lZ]

For post #94
http://sergepp.chat.ru/new-2.gif
http://sergepp.chat.ru/new-3.gif

For post #101
http://sergepp.chat.ru/NEUKROTIMAJA_log.txt
About post 94 (http://forum.doom9.org/showpost.php?p=772799&postcount=94):
That's right. The original position of the layer break is not available in the PgcEdit GUI.

There could be several reason for this problem:
- Mkisofs creates the file system at the beginning of the DVD, as it should, but it uses more space than the standard filesystems found on most pressed DVDs, and even on some burned DVDs. Therefore, all files are shifted a bit.
- Your recordable DVD has less space available than the original pressed DVD. This is often the case.
- You may have entered a wrong value in the "number of sectors in a DL dvd" field of the burn setup dialog.
- You may have modified the DVD, inserting a menu or something else at the beginning.

Anyway, the calculation of PgcEdit is right: The relative start sector of cell 22 is 1899136. The relative start of cell 23 is 1974851. Therefore, the length of cell 22 is 1974851 - 1899136 = 75715 sectors.
The absolute starting sector of cell 22 is 2044822. Therefore, the absolute starting sector of cell 23 is 2044822 + 75715 = 2120537.
The total number of sectors availables on the DL DVD+R (as configured in the burn setup dialog) is 4173824. Therefore, there is 4173824 / 2 = 2086912 sectors available on layer 0.
Since 2120537 is greather than 2086912, cell 23 cannot be used for the layer break.

Try this:
- Examine your DL DVD+R with ImgBurn, and if there are more free sectors than the standard value 4173824, you may change that value in the burn setup dialog, and retry. But since the +R technology is supposed to have always the same number of free sectors, I doubt it will help.
- Try to remove some unnecessary material before VTST 1 (ie, in the VMGM menu, or in the VTSM 1 menu.) Often, the VMGM is not useful, and contains only FBI warnings and studio logos. You can blank it completely using the "Blank out all menu PGCs" function. Tick the option to completely remove the VOB file.
- If it's still not enough, you can try to convert the main menu in VTSM 1 to still with MenuShrink.
- If it's still not enough, you will have to live with it. Just select another layer break position.

[r0lZ]

About post 101 (http://forum.doom9.org/showpost.php?p=776773&postcount=101):

Well, seems you have a folder named NEUKROTIMAJA inside your VIDEO_TS folder! You cannot do that. If you want to burn DVD-ROM files with your compilation, you must put them in the root folder of the DVD, not in VIDEO_TS or AUDIO_TS. Also, do not put IFO, BUP or VOB files in a DVD-ROM folder.
Note also that the file names are too long for mkisofs. Unfortunately, mkisofs (or cygwin1.dll?) has several bugs when it deals with Windows filenames.

PgcEdit removes automatically the backup folders (PgcEdit_backup, VobBlanker_Backup, etc...) from the compilation, but it cannot remove the other folders, like NEUKROTIMAJA. But when it detects such files or folders in VIDEO_TS, it should warn you, and open the DVD folder automatrically, to let you remove them.

This problem is strange, though. Maybe you have a problem with your filesystem? You should try to do an Error-checking of your D: drive. BTW, what OS are you using? Win XP? With NTFS partitions?

Please try the latest release of PgcEdit. I have changed the way mkisofs is called. It might work fine now. (BTW, I have to fix a little bug in the burn DL GUI. Maybe it's better to wait for 0.6.3.1.)

Was ISO created correctly?Hum, no, I don't think so. If mkisofs has included some alien files in your VIDEO_TS folder, it's really a bad thing, since it's illegal. Try to redo the ISO with PgcEdit 0.6.3(.1).

[mazafaka]

Thank you for detailed answer!

The problem (no, problems) with mkisofs & cygwin1.dll. It dislike long filenames. But after filenames shortening it warn
mkisofs: No such file or directory. Can't stat D:\VIDEO_TS\NEUKROTIM
mkisofs: Can't open device 'D:\VIDEO_TS\NEUKROTIM'
mkisofs: Unable to parse DVD-Video structures.
Hmm, up level dir name is truncated by few chars.

And as I said before:
1. Open project (just VIDEO_TS, no DVD-ROM files)
2. Push "Burn DVD/create ISO", OK, OK, etc. - 1.iso created successfully.
3. Push "Burn DVD/create ISO", OK, OK, etc. - 2.iso created successfully.
Finally, binary comparing.
Result: 1.iso != 2.iso and sometimes sizeof 1.iso != sizeof 2.iso
Is it OK??

PS Of course WinXP SP2 NTFS

PPS Could you recommend for testing something esle from software for DL recording (I mean ISO creation too)? (I used CopyToDVD for burn-on-the-fly, till I found a serious bug in it)

[hardkid]

I have read this thread and tried methods to burn DVD-R Dual Layer, described herein. As a result I have a DVD that plays on a standalone DVD player (Pioneer 920), but the layer break seems to be 20 minutes from the beginning of the film - at least there is some bug - the movie is paused and goes in steps for about 2-3 secs and then continues normally. So, please tell me, is there some up-to-date method to burn DVD-R DL just as good and error free, as DVD+R DL? Where can I find that solution? I was stupid enough to buy 20 DVD-R DL...

Thanx

[[Tobi]]

@ hardkid

With my last test (PgcEdit 0.6.3beta8), the DVD-R DL was created correctly.
If is a little bit wrong with the layer break, the DVD should hang at the end of the Layer 0.

A little more precise description what you have done, could help to analyze the problem.

[r0lZ]

@hardkid

Well, there is something that PgcEdit don't do. It leaves the original seamless playback joint cell flag as it is in the original DVD. This could be why you experience a pause after 20' of the movie. You can manually set the flag in the LB selection dialog, or in the PGC Editor window. Anyway, this flag is set by most ripping apps, unless you turn this option off.

The problem can be caused also by wrong parameters in the burn setup or the main burn GUI. Are you sure you have specified that yopu burn a DL-DVD-R? And set the right number of sectors in L0?

A pause can also be caused by bad media.

Anyway, Tobi is right. Currently, ImgBurn is unable to set the LB of a DL DVD-R at the wrong place. The -R technology imposes it at the end of L0.

If you wish, send me your IFOs. I'll have a look.

[r0lZ]

@mazafaka

D:\VIDEO_TS\NEUKROTIM... is an illegal filename! As I have said elsewhere, you CANNOT have DVD-ROM files in VIDEO_TS! Only IFO, BUP and VOB files. "NEUKROTIM" is obviously not a legal name for a DVD-Video file. Also, if VIDEO_TS is in D:\, all files on D: will be burned, as DVD-ROM files!

Try with a structure like:
D:\rip\my_dvd\VIDEO_TS\ <with the DVD-Video files>
I use this kind of pathname, without problem.

Do not use VIDEO_TS elsewhere in the pathname. It must be the LAST folder in the hierarchy.

[mazafaka]

r0lZ, I'm so sorry. I didn't say that my D:\VIDEO_TS contains folders film1, film2, etc. And each film* contains AUDIO_TS and VIDEO_TS. Should I rename d:\video_ts?

[r0lZ]

Yes! It might confuse mkisofs.

[hardkid]

Please tell me why my burning could fail - I was using a Verbatim DVD+R DL disk.

I 22:09:10 Operation Started!
I 22:09:10 Source File: C:\Images\BRAM_STOKERS_DRACULA.MDS
I 22:09:10 Source File Sectors: 3*893*536 (MODE1/2048)
I 22:09:10 Source File Size: 7*973*961*728 bytes
I 22:09:10 Source File Implementation Identifier: SONY DVD Video
I 22:09:10 Destination Device: [0:0:0] HL-DT-ST DVDRAM GSA-4167B DL11 (G:) (ATA)
I 22:09:10 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2,4x; 4x; 6x)
I 22:09:10 Destination Media Sectors: 4*173*824
I 22:09:10 Write Mode: DVD
I 22:09:10 Write Type: SAO
I 22:09:10 Write Speed: 4x
I 22:09:10 Link Size: Auto
I 22:09:10 Test Mode: No
I 22:09:10 BURN-Proof: Enabled
I 22:09:10 Optimal L0 Data Zone Capacity: 1*960*736
I 22:09:10 Optimal L0 Data Zone Method: Copied From Original Disc
I 22:10:27 Filling Buffer...
I 22:10:28 Writing LeadIn...
I 22:10:35 Writing Image...
W 22:22:49 Failed to Write Sectors 1961280 - 1961311 - No Seek Complete
W 22:22:49 Retrying (1 of 20)...
W 22:22:49 Retry Failed - Invalid Address For Write
W 22:24:12 Failed to Write Sectors 1961280 - 1961311 - Invalid Address For Write

Omitting retries here

W 22:24:26 Retry Failed - Invalid Address For Write
W 22:24:26 Retrying (20 of 20)...
W 22:24:26 Retry Failed! - Invalid Address For Write
E 22:24:50 Failed to Write Sectors 1961280 - 1961311 - Invalid Address For Write
I 22:24:50 Synchronising Cache...
I 22:24:51 Closing Track...
I 22:25:12 Finalising Disc...
E 22:25:29 Failed to Write Image!
E 22:25:29 Operation Failed! - Duration: 00:16:18
I 22:25:29 Average Write Rate: 4*587 KB/s (3.3x) - Maximum Write Rate: 5*565 KB/s (4.0x)

[hardkid]

@Tobi

Thanx, I downloaded the latest version, but is there a step by step instruction FOR IT? I want to experiment again. My previous experiment was in strict accordance with blutach's guide (How to burn Dual Layer Disks with PgcEdit).

Thanx

[[Tobi]]

I am not sure how it has come to these error.

If the layer break passes from PgcEdit to ImgBurn with CLI, following entry must stand in the log.

***User Specified L0 Data Zone Capacity***

In your ImgBurn.log stands, the L0 Data Zone Capacity was copied from the original disc.
There are several possibilities how it has come to this errror.
I suggest, you wait to r0lZ or Lightning UK have read.

[[Tobi]]

I do not know whether there are actual guide.
I cannot help, Sorry.

[r0lZ]

I see in the log:
I 22:09:10 Optimal L0 Data Zone Method: Copied From Original Disc

I suppose this means that you did not use PgcEdit to create the ISO. I don't know how ImgBurn works when doing a 1:1 direct copy. Therefore, I can't help. Sorry.

[LIGHTNING UK!]

Looks like a drive/media/firmware issue to me. Could just be a bad disc, or it could be that LG need to release a firmware update to make the drive write to those discs properly.

The actual position of the layerbreak would have no effect on the burning part.

[hardkid]

@ Tobi

Did you edit your reply and wiped off some valuable information from it? It seems to me, there was some instruction with steps and pictures. I mean the guide "How to burn DVD-R DL disks"? I'm sure I saw this and now that I'm back to read it thouroughly and experiment at last - it's gone. So, the question remains - is there a 100% definite answer to this problem?

[r0lZ]

There is a guide by Blutach on how to burn DL-DVDs with PgcEdit on my homepage. Should be the one you are looking for.

[hardkid]

@ r0lZ

Yes, I know about this guide. I followed it and had an error dvd-r dl. Then somebody posted some corrections and remarks to that guide in this thread. With steps and pictures. I think it was Tobi. But now it is gone. So, I'm still looking for a final cut of the guide, which gives 100% compatible and error-free DVD-R Dual Layer.

[r0lZ]

The only important thing to burn a DL DVD-R is that you must use ImgBurn to retrieve the number of sectors in L0, and copy this number in the PgcEdit Burn Setup dialog.
Set also the DL Media type to -R in the main burn dialog, of course.
The rest of the guide should be identical.

[blutach]

This is the second issue I have seen with this drive,media and firmware combination. Take LUK!'s advice.

Regards

[hardkid]

@ r0lZ

Ok, I'll try to spoil another DVD-R DL :-)

@ blutach

This is a misunderstanding. The problem with drive/media/firmware is a separate problem. In this case I was just burning a standard DVD+R Double Layer disk and had a burning error. Probably this was a bad media, since other 30 disks burned OK.

But another problem was the DVD-R Dual Layer disk. I did everything as per your guide, and the whole process was OK, including burning. But when I started watching the resulting DVD - I had a 2-3 sec pause somewhere 20 minutes from the beginning of the feature. Maybe you wrote some updated guide? Is it possible to make the same correct DVD's with DVD-R DL blank disks, as correct as DVD+R DL? At all?

Thanks.

[r0lZ]

IMO, no! The -R technology is inferior to the +R, and you have to write data near the outer edge of the disc, even if the DVD is not full. This means that there are sensible data on a zone of the DVD which is often defective, and can also easily be soiled or scratched.
But that doesn't explain why you got a pause in your main title. Have you checked the seamless falgs?

[hardkid]

How to check for seamless flags? Also, what I am doing now is the following:

1. Copy all files from a DVD to HDD with DVD Decrypter in file mode. Correct?
2. Open them with PGCEdit 0.6.3.1 and choose Burn DVD/Create ISO. Correct?
3. In Setup I check free/L0 sectors with ImgBurn in ISO mode. OK?
4. In Setup I insert the data from step 3 (above) into two lower fields. OK?
5. Press OK and an image is created with mkisofs. Right?
6. Burn this image with ImgBurn. Right?

This is all, as far as I understand? Thus, we make an ISO with an old layer break removed and a new one inserted, right? What removes the old layer break and at what stage?

One more thing. When I get the Layer Break Menu, I have no colored lines at all, no yellow, green or blue (see the picture attached) Should I choose the one which is already highlighted or choose another one (guided by what?)

Thanks.

P.S. Now watching the disk made like this, so far no problems.

[r0lZ]

The procedure is correct, though it is better to burn the ISO directly from within PgcEdit (by selecting the Burn with ImgBurn option.) This way, PgcEdit passes the LB position to ImgBurn automatically. If you launch ImgBurn manually, it will have to guess the position of the layer break. Anyway, since the LB position is fixed for a -R, this is not really a problem.

PgcEdit doesn't remove the original "layer break" automatically. Mainly because there are no "layer break" in the DVD files. The real layer break is only a way to burn some sectors in a particular way. What we call incorrectly "layer break flag" is indeed only the inverse of the seamless playback (or seamless joint) flag. This is because the seamless joint flag must be clear at the position of the layer break. But this flag can also be clear for many other reasons. For example, it must be clear on the first cell of a PGC, and on any cell that, for any reason, cannot be played seamlessly.

You can check if the seamless joint flag is still clear at the original position of the layer break this way: open the PGC Editor on your main title PGC (by double-clicking on the main title PGC label in the left pane of the main PgcEdit window.) In the cells list, see the column labelled "Layer Break ?" with checkboxes. (Note the ? in the label, which means that the information here is only a guess!)
As I said above, the first cell must have the seamless flag clear, and will therefore have the LB checkbox ticked, but it should be grayed out. Don't change it!
Often, if the last cell is a tiny black cell of less than 1 sec, it has also the seamless flag clear, and you should not change it, too.
But if you notice another cell with the LB checkbox ticked, somewhere in the middle of the main title, then it is probably that cell that was used as the original LB. You should clear the LB flag. (Note that the 1st value in the Cell Types flags button will be incremented by 8, because the seamless joint flag is now ON.)
Save and burn.
Note that it is possible to set the seamless joint flag also from the layer break selection dialog of the burn function, with the "Seamless Cell" button. But since this dialog shows only the cells that are suitable for the layer break position, you cannot use it to verify all cells of the main movie.

In the LB selection dialog, PgcEdit tries to guess the best position for the layer break. If it finds an original LB (seamless flag clear), it will probably select that cell by default.
Anyway, you can select any cell you want. It's really up to you. Use the preview to select a cell where the pause will be less noticeable. The colour codes are there to help you, but you don't need to use a coloured cell.
If you select another cell and there is a cell with the seamless flag clear, don't forget to use the "Seamless Cell" button on the original cell to clear the original "layer break" flag (ie, set the seamless joint flag.)

Maybe I will add a function to verify the seamless flags of all cells of the main movie, and warn the user if there is a non-seamless cell somewhere. But it's dangerous to remove it automatically, because, as I said, there are many reasons for this situation.

[eriksen76]

The procedure is correct, though it is better to burn the ISO directly from within PgcEdit (by selecting the Burn with ImgBurn option.) This way, PgcEdit passes the LB position to ImgBurn automatically. If you launch ImgBurn manually, it will have to guess the position of the layer break. Anyway, since the LB position is fixed for a -R, this is not really a problem.

PgcEdit doesn't remove the original "layer break" automatically. Mainly because there are no "layer break" in the DVD files. The real layer break is only a way to burn some sectors in a particular way. What we call incorrectly "layer break flag" is indeed only the inverse of the seamless playback (or seamless joint) flag. This is because the seamless joint flag must be clear at the position of the layer break. But this flag can also be clear for many other reasons. For example, it must be clear on the first cell of a PGC, and on any cell that, for any reason, cannot be played seamlessly.

You can check if the seamless joint flag is still clear at the original position of the layer break this way: open the PGC Editor on your main title PGC (by double-clicking on the main title PGC label in the left pane of the main PgcEdit window.) In the cells list, see the column labelled "Layer Break ?" with checkboxes. (Note the ? in the label, which means that the information here is only a guess!)
As I said above, the first cell must have the seamless flag clear, and will therefore have the LB checkbox ticked, but it should be grayed out. Don't change it!
Often, if the last cell is a tiny black cell of less than 1 sec, it has also the seamless flag clear, and you should not change it, too.
But if you notice another cell with the LB checkbox ticked, somewhere in the middle of the main title, then it is probably that cell that was used as the original LB. You should clear the LB flag. (Note that the 1st value in the Cell Types flags button will be incremented by 8, because the seamless joint flag is now ON.)
Save and burn.
Note that it is possible to set the seamless joint flag also from the layer break selection dialog of the burn function, with the "Seamless Cell" button. But since this dialog shows only the cells that are suitable for the layer break position, you cannot use it to verify all cells of the main movie.

In the LB selection dialog, PgcEdit tries to guess the best position for the layer break. If it finds an original LB (seamless flag clear), it will probably select that cell by default.
Anyway, you can select any cell you want. It's really up to you. Use the preview to select a cell where the pause will be less noticeable. The colour codes are there to help you, but you don't need to use a coloured cell.
If you select another cell and there is a cell with the seamless flag clear, don't forget to use the "Seamless Cell" button on the original cell to clear the original "layer break" flag (ie, set the seamless joint flag.)

Maybe I will add a function to verify the seamless flags of all cells of the main movie, and warn the user if there is a non-seamless cell somewhere. But it's dangerous to remove it automatically, because, as I said, there are many reasons for this situation.

Jeez, I'm a bit confused about all this, all though seems as a very good explanation.

Until now, before I burn the DL I always open the movie .ifo file with ifoedit to see where the orginal layer break is. Then in the PGC selection just before processing, I select the exact same spot.

I guess that is ok, even though I might have removed some trailers, warnings or other stuff? Haven't had any issues yet using the same spot.

If I have somehow made a mock strip or run the DVD9 through Dvdshrink etc. etc. which removes the orginal layer break. (when looking it up with ifoedit) Then I guess I can simply select whatever layer break I want and make it work anyhow.

The before mentioned way of removing layer breaks has never caused me any probs on my DVD5 rips

Comments on this DL methods are more than welcome

Rolz? ;-)

/Eriksen76

[r0lZ]

You can locate and/or remove the LB with IfoEdit, too, but it's more complicated than with PgcEdit. And since you have to load the IFOs in PgcEdit anyway, why use another tool?

Note: If you want to benefit from the 32K gap method of PgcEdit when burning single layer DVDs, don't forget to load and save the DVD with PgcEdit before burning it, or the 32K gaps will be lost (because IfoEdit do a very basic GetVTS Sectors.)
When burning a DL DVD, the IFOs are saved anyway by PgcEdit before the burn, so it doesn't matter.
To learn why you should use the 32K gap method (and avoid Nero!), have a look at the guide by blutach on my homepage.

[ron spencer]

-R DL is dead in the water...I don't know why anyone bothers with it...just check the review sites like cdrlabs, cdfeaks, etc....they hardly play anywhere

[eriksen76]

You can locate and/or remove the LB with IfoEdit, too, but it's more complicated than with PgcEdit. And since you have to load the IFOs in PgcEdit anyway, why use another tool?

Note: If you want to benefit from the 32K gap method of PgcEdit when burning single layer DVDs, don't forget to load and save the DVD with PgcEdit before burning it, or the 32K gaps will be lost (because IfoEdit do a very basic GetVTS Sectors.)
When burning a DL DVD, the IFOs are saved anyway by PgcEdit before the burn, so it doesn't matter.
To learn why you should use the 32K gap method (and avoid Nero!), have a look at the guide by blutach on my homepage.

How can I easily remove a layer break with PgcEdit. I believe I tried it once, but after saving the dvd with PGCEDIT, and I re-opended with Ifoedit the layerbreak was still there. At the same exact spot. (According to Ifoedit)

So far I haven't burned a DVD5 using PGCEDIT, and therefore not the 32K gaps option on these either. So a import/save in PGCEDIT will create those gaps, and make sure they are there even when using IMGBURN and Classic_0.91.7? Or do I have to use the burning engine in PGCEDIT for this?

/Eriksen76

[r0lZ]

See my prev post on how to remove the LB. Just untick the "Layer Break ?" checkbox, and save. BTW, in an old version, there was a bug in the PgcEdit GUI, and toggling the LB flag has no effect. It is fixed now.

You can use ImgTool Classic to burn the files saved by PgcEdit with the 32K gap option ON. ImgTool is only a GUI over mkisofs. PgcEdit uses mkisofs directly.
Of course, you need to create the ISO with PgcEdit to burn a double layer DVD9. ImgTool cannot pad the files to place the LB at the right position in the ISO.

[eriksen76]

See my prev post on how to remove the LB. Just untick the "Layer Break ?" checkbox, and save. BTW, in an old version, there was a bug in the PgcEdit GUI, and toggling the LB flag has no effect. It is fixed now.

You can use ImgTool Classic to burn the files saved by PgcEdit with the 32K gap option ON. ImgTool is only a GUI over mkisofs. PgcEdit uses mkisofs directly.
Of course, you need to create the ISO with PgcEdit to burn a double layer DVD9. ImgTool cannot pad the files to place the LB at the right position in the ISO.

Ok! Thanx again for your fine explanations. I guess you're refferring to the guide where I open the Video_Ts folder with the files in, and double click on the movie pgc. Then I un-tick the small "flag" (whatever its called) where the layer break is, and save the whole thing.

You right, it works - Much faster than "muck strip method" using Ifoedit.

/Eriksen76

[hardkid]

I have several DVDs to backup, but they bear a new sign "DVD protected from copying". What does it mean? Or it means nothing for us? :-)

[ron spencer]

means nothing

[hardkid]

I'm doing this:

1. Making an ISO with DVD Decrypter
2. Burning this ISO with DVD Decrypter - using MDS file for layers info

As a result - I got 4 faulty DVD+R Double Layer disks (total I burned 5). The picture just hangs at some spot, the disk hangs.

What am I doing wrong? I thought with DVD Decrypter it's the easiest and safest way to burn DVD+R DL (Verbatim) disks? Or should I use PGCEdit + ImgBurn, as with DVD-R DL disks?

Thanks

One more thing:

Just checked the previous 10 disks burned exactly as described above - they are OK! And these 5 (all five, not 4!) - they all hang!
What could be the reason for it? HDD fragmentation, any conflicts?

Sometimes the Decrypter gives me this:

W 16:32:00 [0:0:0] HL-DT-ST DVDRAM GSA-4167B DL13 (G:) (ATA)
W 16:32:00 Media region code is mismatched to logical unit region!
W 16:32:00 Logical unit region code: 1
W 16:32:00 Media region code: 5
W 16:32:00 The slower 'Brute Force' cracking methods will be used instead of I/O Key Exchange.
W 16:32:00 Visit http://www.rpc1.org for Region Free (RPC Phase I) Firmware.

or this:

W 17:15:03 Possible Structure Protection Found!
W 17:15:03 1 area has been marked as 'suspect'.
W 17:15:03 Dummy sectors will be inserted where necessary.

Can the above be the cause of errors? In my case and in general - are they any harmful?

[hardkid]

I burned one more disk with PGCEdit + ImgBurn this time, it gave no errors during burning. But this time I turned "Verification" on, and at verification stage it failed!!! What does it mean? That the problem is not in the software, not in the disk itself, but in the LG drive, it's hardware or firmware?

Now, please recommend me the best burner available now, the best for DL disks, since single layer disks seem to have been burned OK.