LIGHTNING UK!

This looks to be the same issue you had back in 2016. http://forum.imgburn.com/index.php?/topic/24354-io-error/ The error your drive is returning shouldn't really be the first error you get. I might expect 'invalid address for write' after another issue (maybe a 'write error'), but it isn't normally the first and only error. Weird. It's impossible to say where the problem lies. You'd have to try another drive / different media to see if you still get the same problem.

Does the same thing happen if you boot windows in safe mode? To not even get a BSOD (assuming that part of windows is functioning correctly), I'd say it must be motherboard or PSU related. As for your 'little detail', that's normal. If you have a blank disc in the drive but haven't selected an image file, it'll prompt you to pick one when you click the 'write' button.

The bootable bit needs to provide you with access to the bits you've added in the 'Source' box. It needs to do that by loading the appropriate cd drivers - normally some sort of *.sys file via config.sys and then maybe mscdex.exe via autoexec.bat So your bootable bit will have drive letter A: or something and the cdrom part ('Source') will be under a different drive letter.

Maybe an updated firmware would solve the issue? http://www.firmwarehq.com/Lite-On/iHBS112%2B2/files.html You could also try burning at 4x instead of MAX. The error your drive is returning shouldn't really be the first error you get. I might expect 'invalid address for write' after another issue (maybe a 'write error'), but it isn't normally the first and only error. Weird.

Sorry, no. Unless 'Erase' gets its own 'Mode', I don't see it becoming a standalone feature you can control via CLI.

Mirror 7 is different, the other mirrors should all host the exact same file though.

You should go by the MD5 on the website really. If you've only got 2 files in the ImgBurn folder, it hasn't written either of the 2 exe files. ImgBurn.exe and ImgBurnPreview.exe Maybe that's due to your AV software or similar?

That sounds weird. Which files do actually get installed? There should be 4 in the ImgBurn folder itself and 2 in the sounds folder. What you install / don't install from the offers makes no difference to the actual ImgBurn side of things. So if files are missing, it must be failing for another reason.

Only a disc quality scan of the disc that just failed to verify (as per the log in post # 45) - if your Asus supports it. That's where I was heading with the last line of my previous post.

Sorry, press F8.

There shouldn't be anything 'wrong' with it, data is just data. The drive shouldn't know or care about what it's burning - unless you've managed to find some *very* special combo of 1's and 0's that always cause a problem. It also doesn't appear to be failing at the same point. Can your Asus do disc quality scans in the likes of cdspeed / dvdinfopro / opti drive control / kprobe?

I'm not sure the LiteOn iHBS112 actually supports M-Disc does it? Believing that it doesn't, that'll be the problem. You'll have to buy some different discs.

Does the Asus do the same when you turn the 'Perform OPC Before Write' option back off? I don't know how unlucky you can be with drives/discs, but something isn't right there.

The value comes from the drive itself. So, for whatever reason, it returned weird sizes for the buffer itself and/or the amount used. If it keeps doing it, you could enable I/O debug mode so it logs the size of the buffer before it starts to burn and captures the usage (again, as reported by the drive) during the actual burning phase.

The drive doesn't appear to like the discs. Try them in another drive.

Whatever has been found doesn't appear to even burn CDs, so it's purely a reader. Of course without the log / device manager info, we can't tell if it's just seeing something 'virtual' that's been install and if the physical drive does indeed have an issue.

The log would help too.

If there is, it'll be in the settings under the 'Build' tab.

They prevent you from reading anything (scrambled at least) on the disc when the region code of the disc doesn't match that of the drive - thus even brute force CSS cracking isn't possible.

Did you even download the right thing? Nothing is or has ever been forced on the user.

As its author, I probably know if I've totally abandoned it or not. If I'd abandoned it, I wouldn't be here and neither would this forum.

Was the disc info you posted there from a blank disc? Your drive doesn't seem to have initialised it correctly. If that's what you get with all blanks, it might not support that MID (RITEKF1) at all.

Yes, it could be the player. But... without checking the burn quality of the discs that skip, it's hard to know where the problem lies.

If the drive doesn't support the 'advanced setting' to clear OPC, you're probably out of luck. Are you using MKM-003-00 discs or have you purchased the wrong ones?

Ah ok, it makes an MDS for that ISO because it's below the size where DAEMON Tools mounts as a BD, yet it contains BD Video files. If you mount such an ISO in DT, it'll emulate a DVD-ROM and BD Video doesn't always play from that type of media - because players don't expect to see it on DVD-ROM discs. When you mount the MDS in DT, it'll tell DT to emulate a DVD+R instead of a DVD-ROM. If you have no interest in ever mounting that specific image in DT etc, just ignore the MDS or delete it.