LIGHTNING UK!

I finally found this thread again and got round to looking into the issue. It's because when it tells you it WILL write to the disc even though you'd enabled 'Test Mode', it actually unchecks the box for you and doesn't even attempt to burn with 'Test Mode' enabled. I've made exceptions for the DVR-118/218/219/220 drives now so it won't prompt about it not being supported. It also now knows to use the Nu Tech commands for automatically changing the book type.

All LiteOn drives do it and have done for years. The likelihood of the 312 NOT doing it is like 0.1%

From what I can see in your pics, the drivers aren't having trouble loading, they're just not finding any drives they can work with. You may find there's a pre-built image somewhere on the web that tries loads of different CDROM drivers (although I'm sure Hiren's can be made to try loads) - maybe the ones you've tried simply don't support your controller (or the mode it's in - AHCI etc). Keep an eye on the loading screen and which ones (if any) actually find your drive. Then copy that driver to your own bootdisc and include it in the config.sys file or whatever.

Off the top of my head, the LiteOn and LG will (tested with an LG BH12LS38 though). The Plextor is probably a LiteOn or Pioneer anyway so just get whatever is the cheapest. Optiarc are shutting down so I wouldn't invest in one of those if you want firmware updates in the future.

No, that would require conversion and ImgBurn just burns as-is. Use something like DVD Flick or ConvertXtoDVD for the conversion and then burn the output with ImgBurn (which DVD Flick will automate for you).

There are loads of cdrom drivers, are you sure that all of them require himem.sys to have been loaded? Failing that, a quick google search leads me to believe the A20 stuff can just be disabled via '/A20CONTROL:ON|OFF'. Or you can tweak the way himem.sys loads for your machine using the '/MACHINE' switch. http://support.microsoft.com/kb/72302 http://users.cybercity.dk/~bse26236/batutil/help/HIMEM_S.HTM

That depends on if you want to know about problems or not?! If you hadn't verified that disc, you'd never have known it wasn't readable. Does not knowing about a problem mean the problem doesn't exist? No. btw, revert back to using SPTI as the I/O Interface unless you have a specific (possibly user access rights related) reason for using it. Videos/posts on youtube/the web in general about magically fixing drive/media issues by switching to Patin-Couffin are complete rubbish - in case that's where you got the idea from? It's like needing to drive between A -> B in a car with a flat tyre, but thinking the flat tyre won't exist if you take road D instead of road C.

That drive must be 6 years old now, it may benefit from being cleaned with a cleaning disc - or manually if you're feeling brave. You should also try burning at the other supported write speeds - start with 4x. If it still keeps failing, invest in a new drive.

A new program version can't fix a problem between your drive and the media, that wasn't why I mentioned that your one was out of date. Sorry but there has only ever been a SB00 firmware release for your drive - and that's the one you're running now.

The solution would be to use better discs or a drive that has no problem with the 'MBI 01RG40' ones. Your version of ImgBurn is out of date btw.

http://forum.imgburn.com/index.php?showtopic=8000 That's your best chance of success.

Yes, I know all about XDG3. I've done my research and I know that only having 97% of something on a disc is a sure fire way to have a disc that doesn't work, gets you flagged/banned etc. The trucating method died ages ago when a better method was made available. Yes, I'm sure it's not SPTD causing problems. All that ever did was make things run a bit slower on certain configurations.

By default, the program doesn't check/compare CD-DA data due to the way drives offset audio samples when reading/writing (what you write to a specific sector isn't what you'll get back when you read it). All it's doing for audio tracks is checking the sector is physically readable. You can adjust that option in the Settings (so it does compare CD-DA data), but like I said, it doesn't really work in practice due to the drives offsetting stuff. If you've got a glitch in your image, it probably came from the reading stage yeah? So your reader had a problem with the disc - and there's no built in error detection/correction for CD-DA so the drive returned data with a glitch. Is the disc dirty/scratched at all? You may find something like Exact Audio Copy will give you an error free (or at least better) image, especially if you enable secure reading.

You've uploaded 3 Nero logs... this is the ImgBurn forum. If your drive is burning coasters, invest in a new drive - although you could try cleaning it with a cleaning disc (or manually if you're feeling brave) first.

If it's saying it's not a valid IFO file then it probably isn't a valid IFO file. (it's incomplete/corrupt etc) Open it in notepad and see if it says 'DVDVIDEO-VMG' at the start of it. Going by what you've told me about the error ImgBurn is reporting, it won't do.

It looks to me as if Roxio is relying too heavily on values stored within the file system for the amount it should burn rather than just burning the image as a whole. The volume size stored in the file system descriptors doesn't always include everything included in the image - some file system descriptors could be missing, especially when UDF is being used. That's exactly what's happening here, Roxio is missing off some of the file system descriptors (some padding sectors and a UDF anchor point). From what I can tell, Roxio should/would also have a problem burning the ISO I just created in Nero 11. None of the volume sizes stored in its file systems match the true length of the ISO either.

The image is too big for your drive/media combo. You should probably read this now... http://forum.imgburn.com/index.php?showtopic=12200

it's probably easier all round if you just manipulate the 'IO_EnumerateDevices_AutoLoaders' registry key, changing it between 0 and 1.

You seem to have missed my point. The LiteOn iHES312 is NOT a CD/DVD/Blu-ray burner, it's a Blu-ray *reader* and CD/DVD burner. That's to say, it can *read* Blu-ray discs but it can't write them. The iHBSxxx drives are the Blu-ray burners. Maybe you can exchange yours for one of those?

Your drive can't write Blu-ray discs, only read them.

http://forum.imgburn.com/index.php?showtopic=8000 p.s. you aren't using the latest version of the program.

M-Disc is the new 'long life' media. http://millenniata.com/

I don't think Optiarc existed before Sony got their hooks into it Optiarc was the new name given to the NEC/Sony collaboration wasn't it?

Most drives only change the booktype on DVD+RW media when they format it. Simply writing to it isn't enough and obviously formatting the disc wipes the data on it so you can't do it after you've written to it.

AHCI mode on an Intel chipset motherboard with recent Rapid Storage Tech drivers isntalled should be able to support the bitsetting commands just fine... I don't know about other chipsets. Otherwise, yeah, you should be able to take a DVD+RW with its booktype set to DVD-ROM and burn it on the LG.