LIGHTNING UK!

1. Nope, sorry. 2. ImgBurn is a 1 thing at once program and has what's known as an SDI - single document interface. Nero uses an MDI - multiple document interface. Saving the project or simply opening a 2nd instance of ImgBurn (via the usual shortcut or by pressing F12) would be the way to go. http://en.wikipedia.org/wiki/Multiple_document_interface 3. Write mode's Write Queue is for disc images. A Build mode project file is not a disc image. You'd have to actually build the ISO files and have the program add them to the Write Queue, then switch to Write mode and burn them.

Can you cancel out of it? Can you verify the disc as a standalone function? Try burning at 24x rather than 'MAX' speed.

If you've changed the sptd service's 'start' value to 'disabled' (4?) and rebooted, you won't get the message from ImgBurn. It's a little odd that their installer says your platform isn't supported. In any case, SPTD is unlikely to be the cause of your problems. Why don't you post a copy of the burn log - as per the pink box up the top We'll then take a look and see if we can get you burning again.

Which mirror? They seem fine to me. Did the MD5 hash (of SetupImgBurn_2.5.6.0.exe) match the one posted on the ImgBurn download page?

The mp4 file is useless, you can't do anything with it except play it on a machine supporting mp4 files. Putting in in a BDMV folder doesn't change what it is. So just forget about the mp4 file and delete it. You're wasting your time compressing to 10gb if you want to maintain as much of the original quality/detail as possible. Obviously you want the output files to be around the size of the discs you're going to be burning to - i.e. 25GB for a normal single layer BD-R disc. If you want to keep menus then you'll have to look for a program that supports doing that. Maybe RipBot does? I don't know. The likes of BDRebuilder/ClownBD can do it though.

Don't forget you're probably just working on a single title/playlist from the original BD structure (the 'main movie' one). So the extras and menus etc will be gone. You can strip unwanted audio/subtitle streams from the output - thus reducing the size. In the end, you might only be reducing the bitrate by a tiny amount - only you know if you can notice the difference, try it.

Whilst I've never used RipBot myself, a quick Google suggests you didn't configure it correctly if you've ended up with an MP4 file. One screenshot I saw seemed to show MP4 / MKV / AVCHD output options. If you're running it with the intention of creating a folder structure that'll leave you with a playable disc then you should be using the AVCHD option. The only alternative I know of is to get an MKV and use tsmuxer to create the proper BD video structure. Rather than wasting discs, make an ISO, mount it in a virtual drive program and test it with PowerDVD etc. Failing that, buy yourself a BD-RE. They're very useful.

It should/will update when the other labels (on the Write Queue window) update - because that's how it works internally. You don't have to actually close the 'Write Queue' window for the changes made to become active/relevant.

That label is currently only updated at the start of the burn, not during it. I will make it so it's updated instantly with the correct value.

You're using rubbish discs and your drive doesn't like them - buy better ones. Burning at a slower speed (4x) may produce a working burn. Cleaning the drive with a cleaning disc may help too. btw, your version of ImgBurn is out of date.

There's probably another program on your machine that's shutting it down. Does the program start up with a red edge? I understand that's some sort of 'sandbox' feature of certain antivirus programs.

The drive is certainly failing on those discs but that doesn't mean it'll fail on some decent Verbatim ones. You're just going to have to try it.

If your drive doesn't want to burn to those discs then there probably isn't anything you can do. It's all covered in here - http://forum.imgburn.com/index.php?showtopic=8000

Right so you have an NVIDIA chipset motherboard. Ok so this is the important bit... The program instructs the drive to load the tray and it's returning success. It then asks the drive if it's ready ('Test Unit Ready' command) and it's not getting a response - meaning it just sits there waiting. I'm afraid there's nothing I can do about this issue, it's not my issue to fix. Personally I'd be looking at drivers (sata controller and any filter drivers you might have). Try installing these - http://www.geforce.com/Drivers/Results/14875 Try again in safe mode and see if that makes a difference. You could also try it from inside Windows XP with the help of Hiren's Boot CD.

Did you make it by reading a disc or by 'building' one? Read mode generates the name automatically so I can forgive you for forgetting what is said in the 'Destination' box. There's no excuse for Build mode though - you'd have had to tell it where to put it. Go into Write mode and look in the 'Recent Files list in the 'File' menu. Your image should be item 0 in there.

There are no settings to check, your system is just hanging on a very basic command that it shouldn't be. Can you please right click the drive drop down selection box and click 'Family Tree'. Close the prompt and copy+paste the info from the log into your reply. After that, burn another disc with I/O debug mode enabled to capture additional info. To do that, just press the F8 key before you hit the 'Write' button. You should see an entry in the log window saying it has been enabled. Save the log once it's stuck at the 'cycling tray' bit and upload it here on the forum (don't copy + paste debug logs please).

What do you have in the way of mapped network drives... anything? If not network drives, what drives do you actually have listed in 'My Computer' ? (Screenshot?) It looks like the explorer style component I use on the 'Disc Layout Editor' window has some issue with your machine. This guy here has/had the same problem but never came back to his thread. http://forum.imgburn.com/index.php?showtopic=17352

Going by that screenshot, 'Auto Insert Notification' (MCN) is indeed disabled on your PC. You don't need to disable MCN itself, doing that causes more harm than good. Windows uses it to detect changes to the drive's status/discs. All you need to do is disable Autoplay if you're worried about discs auto running and giving you viruses. What kind of dodgy places are you getting your discs from anyway to have to worry about such things?! As my 'Location' (left column of my posts) states, I'm from the UK.

Windows options... but ImgBurn can show their current state. Look in the Settings on the 'Device' tab. You should see an 'Operating System Options' box. Are all 3 checkboxes checked?

No, you don't have to use Verify mode (actually, you can't use it because you're building+burning on the fly), you just leave the little 'Verify' box ticked under where you pick the 'Destination' device. Do you have Autorun/insert enabled?

This is not something a program would do. Buy good (Verbatim) discs.

Do you verify when you burn? Assuming the verify operation completed successfully, your disc should be fine. (Post a log please - as per the pink box up the top ) If Windows can't see the disc has changed you may need to close ImgBurn and refresh the 'Explorer' ('My Computer') window so it checks the disc again. Ejecting + reinserting the disc whilst doing that make Windows realise it needs to check the disc again.

You mean so it changes automatically (upon startup) based on the user's current OS language settings? I could make it attempt to default to it on a fresh install (or when there's no language setting saved/available). What the user picks manually via the Settings will override it though.

Try installing it again via the standalone installer, reboot, then uninstall it again. They set funny permissions on the registry key so things can't mess with it.

No, it's not used / installed by VCD. Uninstalling Alcohol / DT doesn't remove SPTD. You have to run the standalone SPTD installer to uninstall it - and you can get that from the Duplex Secure website.