LIGHTNING UK!

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.

I guess it wasn't removed properly then - the SPTD registry key is still present. 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sptd' shouldn't exist if it's not on the system.

Your issue is nothing to do with ImgBurn or burning in general. What you're noticing could be from some sort of conversion your player is performing (PAL/NTSC etc).

Try burning at 8x or 16x. 4x might produce bad burns with your drive/firmware/media combo.

GI images are only supported in their most basic form (single session/track data image). The 'GI' forum is closed source and I don't have the specs for it. Can you mount the GI file in Roxio's virtual drive? If so, do that, read the disc to a new image using ImgBurn (which will save in BIN/CUE format) and then write that image instead. You're running an old version of ImgBurn btw.

Even if the burner wasn't ultimately going to be the playback device, I'd still want all the discs burnt by it to verify successfully and would ditch the ones that didn't. It's good that you finally got a decent burn. The iHASx24 B drives are so inconsistent with certain settings, that's why I ended up trying various ones in the iHAS124 B thread in the Drives section.

Your problem is the same as one I answered a day or two ago. http://forum.imgburn.com/index.php?showtopic=19620 Burning a 'bad' image doesn't make for a 'bad' disc. You could have a completely useless image file containing nothing but random data and it would (should) still burn + verify correctly. Getting an error during the verify process means the disc isn't readable in that drive, it doesn't mean it won't be readable in another drive - but it isn't exactly a great sign! The same applies for any results to do with the quality of the burn... they're only really valid for the drive in which the disc was tested. Another drive may find the disc easier/harder to read. I don't know why kprobe doesn't pick up on the same problem area that causes the drive to be unable to read the sectors around the layer break. It's that kind of thing which reminds me just doing a kprobe scan *is not* enough and that verifying still very much has its place.

No, the MDS isn't part of the disc. It can and does contain info about the physical format of the disc - info that's not found in an ISO file and would otherwise be lost. Obviously they aren't physically the same, that's why I went on to explain that the MDS is a little info file and ImgBurn will pull in the actual data in (i.e. what gets burnt to the disc) from the ISO file. If you try and load an ISO when an MDS is present, the program may (it depends on the size of the ISO) tell you off and say you should have loaded the MDS (so it could get the physical format info from it). So when it comes to writing an image (based on MDS/ISO) in ImgBurn, the program knows how to deal with either of them being selected and will burn accordingly. The guide I linked you to in post #4 tells you to just pick the MDS file if it's present.