LIGHTNING UK!

Do people use blindwrite for simple ISO type images? That's all the burn engine really supports at the moment. I tend to associate BlindWrite with complex images - usually incorporating some form of protection etc.

Yes, they'd only write at 6x as well. So if others truly burn faster (in ImgBurn or DVD Dec), it MUST be drive/firmware/media issue.

Memorex are probably ritek. Stick with verbatim DL discs, nothing else.

Nero doesn't display the real burn rate. If it allowed you to, you could set the burn speed to 100x and it would say it's burning at 100x. Being that 6x isn't even a supported speed... (and that comes directly from the drive) .... I can only assume it's starting the burn at 6x with the idea of jumping to 8x later on in the burn - as in Z-CLV style or whatever it's called. Then as time goes on and it gets to the point where it's gonna jump to 8x, it's deciding - no way, 8x will make an awful burn! - and is sticking with 6x. I've not checked but are you on the latest firmware for that drive? If the buffers are full, the program is sending data to the drive as quickly as it's accepting it. It honestly cannot possibly be burning any quicker and the drive is causing the hold up.

The only way in which the program could be limiting the burn to 6x is if the buffers are always on 0% or fluctuate A LOT! If that's the case, it has become impossible to burn any faster - probably due to some configuration issue with your PC. Other than that, your drive is slowing down the burn on purpose so it doesn't create a coaster. That's done by the drive OPC stuff (be it Active OPC, Walking OPC etc).

The program that creates the image is reponsible for that stuff. It can't be done once the image has been made. Image burning tools are dumb, they shouldn't even need to look at the data in the image (I do a little bit), so there is no way to check for 32k spacing.

It's only doing that because you've put a /CLOSE switch there too. Because it's not allowed to start (no media), it kinda assumes 'Error' and so the /CLOSE switch kicks in. I've added a /WAITFORMEDIA switch that should help you.

Hello again Any chance I could mail you another version with some debugging info in it to help me? If so, please email me at the address in the programs 'About' box.

EEPROM would be the one where it remembers it - even after powering off/on the drive.

It only needs to be a cell, not a chapter. I'm just not sure if your authoring program allows for such things. Other than that, if you're not willing to put a chapter in there, you're out of luck I'm afraid!

Incremental was really just added as a workaround for Pioneer 109 drives when they sucked at burning in DAO mode. Now the firmware is fixed, Incremental is pretty pointless. It's L0, not LO. L0 meaning Layer 0. i.e. if Layer 1 starts at LBA 10, Sectors in L0 = 10 0, 1, 2.... 9 = 10 sectors

I believe it's in $

DVD Decrypter has not vanished off the face of the earth just yet. ImgBurn is a burning tool, don't try to turn it into something it's not.

In that case, none of the cells were ok for layer breaks. So that disc has a cell the spans it and may crash / jump more than normal at the layer switch. You would have gotten a message in the log to that effect.

No, padding is in the filesystem - and as mentioned above, I don't touch that. The image must be created properly in the first place. If you don't burn from an MDS, ImgBurn will scan the IFO files to find potential places for a layer break. By that I mean it'll look in the IFO files for cells that start on an ECC boundary and are within the acceptable LBA range.

It's just a left over. No reason to remove it, so I left it in!

This is a burning tool, nothing more.

This was suggested earlier too actually! As I said in that post, multiple copies is never something that's bothered me, and if it ever was, clicking 1 button isn't a huge deal. I could implement this and make it auto check for new media etc and continue on its merry little way. 'tis certainly something to thing about.

Maybe you should read up on what an image burning program does!

lol it's close! I hope coujo doesn't mind that, and I hope he'll update ImgTool Classic to use ImgBurn instead of DVD Decrypter. I think he will because DVD Decrypter causes him problems anyway because it's illegal to even mention that name on his website because of where he lives!

How the layer break is calculated is dependant on the type of image you're burning, and which program (if any) invokes ImgBurn. i.e. Burning an MDS will mean ImgBurn gets the LB info from the MDS directly - so LB is preserved. With the latest PGCEdit, the LB info is passed via CLI. So if it gets it wrong, ImgBurn will do too. With a standard DL image (ISO, IMG etc), you'll see info in the log if there is a problem calculating the LB position. Keep an eye on it. Try posting the log here too if you still have it.

I think all programs that used DVD Dec for burning will move over to ImgBurn now. Be it via a hack (if the author has stopped updating them), or when the author gets a chance.

No, it can't / won't change the filesystem of the image so that the layer break can be positioned in a nice place. What it will do is read the IFO files and try to find as many potential positions for the layerbreak - before then displaying them in a box where you can choose the one you want to use. To see what the program finds within an image without actually burning it, right click on the 'sectors' text within the 'Source' box when you've selected a double layer image. You should get a context menu come up and the rest is pretty obvious

Sorry, I didn't mean YOU had the virus, I meant someone else was sending them on your/their behalf. Hope you get it sorted out

Shrink would need minor hacking around with to swap DVD Decrypter for ImgBurn when burning. Trouble is, I'm not the man to do it.