LIGHTNING UK!

If the buffers get too low, the buffer recovery stuff kicks in. When that happens, the program basically pauses until the buffers have filled up again and waits until hdd activity reaches a set level before burning continues. Take a look in the log and see if you can see what I've described above actually happening. I've never had a need to burn from 2 instances of the program at the same time so it's not something I'd test. If I want multiple burns I simply queue them up and share between drives. If buffer recovery is causing issues with the way you like to work, simply disable it in the settings.

The stuff you knew in the old version is still there (almost exactly the same) in this newer one. As such, you have nothing to worry about. Just remember to switch to 'Write' mode when you need to burn ISO images, and 'Build' mode when you need to burn a bunch of files. There are guides in the 'Guides' forum that will tell you (complete with nice screenshots!) exactly how to make image/burn on-the-fly using the new 'Build' mode. If you've ever burnt a disc from files on your hdd (not images), you should recognise most of the options that ImgBurn offers you. The default settings tend to work best, that's why they're default. If you have a question about any one of them specifically, please don't hesitate to ask.

I've read about so many issues with laptop drives over the years, they're nothing on their desktop counterparts I'm afraid. I think that's why a lot of people just buy usb enclosures and use external ones. Seriously though, before spending too much time on it, get some MCC or Taiyo Yuden discs and try burning those.

Do you have any decent discs you can try with? Your drive is just having real trouble burning to those one - which is understandable because prodisc are certainly not one of the 'better' ones! You might also like to go searching for a firmware update for the drive. Visit the website of whoever made your PC. EDIT: This thread might be useful to you. http://forum.digital-digest.com/archive/in...hp/t-66029.html

The program won't let you build an image or burn the disc (on-the-fly) if you don't add a file/folder to the 'Source' box. That doesn't sound like it'll be a problem here because the 'plus file on the CD as device D:' would cover that. Those files are what you'd add to the cd compilation (i.e. the 'Source' box). Oh and yes I've seen it done before and it's quite usefull once you've got your floppy boot image just right. Just be sure to have a bootable floppy that actually loads your cdrom drivers! If you don't, that 'D:' drive will never exist

Ok, pinned! (no, not really )

Ah Win Me....that's a shame Yes, you'll have to search the net for a tool that can create a raw image of a floppy disc. It'll end up being a file of 1.44mb in size. 'WinImage' is one tool I know of that can do it. Once you have that bootable image, yes you can use that as the 'bootable image' in ImgBurn. You will need to add at least 1 file/folder to the compilation before you can burn the disc though. Simply specifying the bootable image part is not sufficient.

Are you supposed to be having a go a Jill there MJ ?! 'Cus you are (if you didn't realise) !

6KB/s?! That must have taken about 24hours to burn a disc! Anyway, I'm glad it seems to have sorted itself out.

Depending on who makes the enclosure (or rather the chipset it uses), you may be able to update the firmware on it. Prolific chipsets are quite common and there are firmware updates for those - I have a couple of them myself.

When you rebuild it, you must change the 'Double Layer' profile to 'DVD-R DL' (It defaults to DVD+R DL). This is on the 'Advanced' -> 'Media' tab within Build mode. If you burn on the fly rather than going to an image file, this should all be automatic. Remember to change the profile back when you're done with DVD-R DL and move onto DVD+R DL.

Seriously, don't be surprised if you see it again sometime! On the old forum we had a 40 page thread on semaphore timeout errors. There's an even longer one over at the afterdawn forums.

The semaphore timeout period expires because something in the USB chain overrides the timeout period I specify in the program. This is not supposed to happen but it's actually very common with usb drives / enclosures. Basically if the drive takes too long to do anything it just gives up and resets

An image must be built in a specific way for burning onto DVD-R DL media if you want to stick to the DVD Video specs regarding layerbreaks. You'll have to rebuild it with a layerbreak in the correct place - which is a 'fixed' position on DVD-R DL (It can be moved on DVD+R DL which is why they're better for this kind of thing).

Have you just installed some software that could be messing with things? Even though the buffer stuff isn't being displayed, are you finding the burn times any different? The drive (or some buggy software) might just not be reporting the correct buffer values.

It looks like it burns / verifies ok to me. The problem here is that it ejects the disc and then tries to reinsert it before the verify starts. The eject works but the reinsert (load) then fails. Bit odd really!

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.