LIGHTNING UK!

Like I said in another post, a quick erase is just writing zeroes to the first X (800 I think) sectors. A real burn still writes to those 800 sectors (and more) only it uses real data. As such, there is NO logical reason why this should ever be necessary. I cannot/will not add features to workaround a glitch on a particular system I'm afraid.

The reason it does that (requires both boxes) is that windows will show you the label for the filesystem it's working with - and it always works with the 'best' one. As UDF is better than ISO9660, it'll show you the UDF volume label. So even if you've entered a name for the ISO9660 filesystem (and not UDF), as far as windows is concerned, there is no volume label - and hence you won't see a name in explorer when you look at the drives.

We can help you with burning but that's it I'm afraid.

This guide shows you a picture of the 'Labels' tab and where you're supposed to type a name in. http://forum.imgburn.com/index.php?showtopic=1780

Sorry but you must have done something wrong then! If it still says '[Not Configured]', you haven't typed a name in any of the 'ISO9660', 'Joliet' or 'UDF' boxes within the parent 'Volume Label' groupbox.

Buffer underruns have long been a thing of the past. Drives just stop and start now, no problems. You machine must have been busy doing something and the buffer levels fell right off, that's when buffer recovery kicks in. Rather than the burn going stop / start / stop / start / stop / start etc, it stops the once and waits for things to clam down before starting again.

I thought you said it couldn't find a layerbreak cell?! I'm pretty sure it's impossible to have it error out AND work at the same time! From that screenshot you'd obviously select the 2nd one.

lol that option doesn't exist yet blu, it's beta only! honeydipp, click on the 'Labels' tab when you're in 'Build' mode and enter a name in the boxes where it says 'Volume Label'.

Ah that is a bit silly! See now here's a perfect opportunity to fire off an email to whoever manufactures them asking why ISO9660 takes precedence over UDF for normal data (with AVI files etc) DVDs. You've just made your own day!

Players shouldn't (in theory!) mind if something is present that it doesn't fully understand - i.e. descriptors for filesystems it cannot parse. It won't be looking for them and so even if it finds them, it shouldn't try to decipher them. It's weird that it won't read UDF for normal files when a player is only required to read UDF for DVD Video and not any other filesystem. Maybe it just parses different filesystems depending on the type of disc inserted. It might have really basic UDF parsing for DVD Video as it only has to read the VIDEO_TS folder and locate the VIDEO_TS.IFO file. For playing normal files it would have to search all folders / subfolders etc so perhaps that's why it favours Joliet or ISO9660.

Oh sorry, I assumed you were already using 'Build' mode (I didn't fully read your first post). Read the guides forum if you don't understand how to use it. If you're just burning ISO files I have no idea why they're not working. I assume you've tried the obviously bitsetting stuff - if you're using +R media of course!

Turn off 32k gap padding and burn another one.

It was a valid request/suggestion, it just doesn't fit well with the program right now. Sorry Maybe one day though....

At the end of the day, it's an image burning tool. There's no reason to burn an image and leave the disc open. I can't stand multisession myself, never really used it, never wanted to. If I want to keep changing what's on the disc I won't burn it in the first place! Or I just use a rewritable and keep overwriting it. The program doesn't support multisession in any way, shape or form. Therefore it's pointless (and confusing) to add support for leaving a session open. You'd have to use a different tool to burn the second session with - and in which case, you might aswell use that tool right from the beginning.

If you have a specific problem with ImgBurn, please feel free to ask for help. For other problems, you'll have to look elsewhere I'm afraid.

You can't.

The alt key does the main menu stuff at the top! Tried all these before

'ctrl + v' you might like to rethink that one (Hint: Paste) I made that mistake during betas The old keypresses still work, just not from within Build mode - that's the one that messed everything up!

If the drive thinks it's busy, the drive thinks it's busy. It doesn't matter if you cancel the operation in ImgBurn, it's the drive that's doing stuff, not the program. ImgBurn is just asking the 'Are we nearly there yet?' type question every second! Any program that tries to use the drive will just recieve the same old message... 'Logical Unit not ready, Long Write in progress' BCDB worked ok for me on that drive with those discs but you do get higher PI errors at the outer edge. http://forum.imgburn.com/index.php?s=&...ost&p=12762 Have you tried a slower speed or burning a smaller image - just for testing purposes I mean.

and when you say 'not readable', what exactly do you mean? Do you mean Windows give you an error when you try to access the disc? If you load imgburn and have it use your 'other' drive in verify mode or something, can it see the disc? - i.e. does the panel on the right fill up with info? If not, what does it say in the statusbar?

The CLI can't do anything the GUI can't - as CLI stuff just automates GUI bits. Formatting / erasing etc is all done automatically already and that's where the existing '/ERASE' switch comes in. I 'could' add it, yes, but I promise you that there is no need if everything is working as it should do.

If the program defaults to 'Write' mode, how can people find 'Build' mode and then not find their way back to 'Write' mode again?! Maybe I'm just missing something...

As you can see, the program is still sending commands to the drive and the drive is responding. That's a good thing Trouble is, the drive really does still think it's busy doing something with the disc. Are you using decent quality media? What's the media code?

If it's a DVD+RW, you don't erase them. The DVD+RW technology allows for direct overwrite once the media has been formatted. Assuming you're doing a 'quick' erase, all that does is write a bunch of zeros to the first few sectors. Writing an image does exactly the same thing - only it writes real data and to more sectors.

You may need to use the 'RICOH' tab for that drive rather than the NEC one.