LIGHTNING UK!

You need a RAW image of the bootable floppy disc. Copying files + sticking them in a folder + making an image is not enough. Put the disc in the floppy drive and use the 'Create Boot Image' option to do a raw read. This will only be available in NT based OS's though. If it works, you'll end up with a file 1,474,560 bytes in size.

Oh I dunno, I remember calweycn being despised equally as much on the old forum. Thankfully he got the message on that one, went away and never came back. I used to cringe every time he emailed 'support'. Seems he's stopped doing that now and instead just comes on here to wind everyone up. I think I preferred it when it was just me that he pissed off.

calweycn, Once again, there is no magical command to enable / disable for overburning. I simply look at the size of the image, compare it to the size of the disc and warn the user if it's bigger. I know you read all the other forums so perhaps you should look over at cdfreaks a little more. There were loads of posts in the BenQ forum a while back about overburning. There were clear faults found in firmwares that means drives basically just 'crashed' if you tried to do naughty things - i.e. overburning too much (and also too little in BenQ's case). The risk you take when overburning is that your drive runs into one of these firmware bugs and gets stuck. When it gets stuck, it's stuck for EVERY program. You have to reboot so that it resets and springs back into life. When the program sends a command to the drive it sits there waiting for a reponse. The 'DeviceIoControl' API does not return control to the calling app until the command has been processed (unless you're using 'immediate' or 'overlapped' commands). Until the program has control, you can't close it down - it's as simple as that.

I don't understand this. You have a very weird way of thinking calweycn. You can't call something a 'ripper' because it can create an ISO file, that's just plain ridiculous.

Your drive hangs and that causes the program to hang, not the other way around. When the drive recovers, so will the program.

nah, I just like to tease you all The 2.1 release is imminent, I'm just a bit busy with other stuff at the moment and haven't had time to finalise everything.

I'm not sure DVDRAM will work the same way a normal DVD-R or DVD+R would do. The player may try to read the disc in the true DVDRAM way and not as if it's a DVD Video disc. (Sorry for being a bit vague, I don't have any real experience with standalones / dvdram etc). Your original power calibration error is due to a hardware/firmware/media mismatch. Assuming your firmware is up to date, you need to source some discs that your drive supports properly. The easiest way to do that is to find someone else with that drive, who is getting decent result. As such I would recommend you pay the cdfreaks forum a visit. They have forums for most makes of drives. Basically though, you should look to buy some discs using the MCC or TY (Taiyo Yuden) dyes.

It's /S for silent. Please refer to the NSIS website for anything else you need to know about the installer.

The buffer does empty out each time the drive performs WOPC type stuff. Show us a screenshot from DVDInfoPro displaying the IBG stuff.

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.