LIGHTNING UK!

It looks like you've already tried and failed to burn to that disc. Use another new one please.

Read mode has a setting to configure the 'default destination'. Check the Read tab in the settings.

The program predates Windows 10 and you have to do something special to make the OS report itself as what it really is. Samsung drives don't have a way of querying if it's actually going to change the booktype to anything else. The program has asked it to booktype to DVD-ROM and it has accepted the command, that's why the log entry exists during the write phase. For whatever reason, the drive hasn't done what was asked if it and the booktype remains as DVD+R DL. I shouldn't worry too much. If you're burning avchd, your player will be new enough to not care about the booktype. Some won't even play if the booktype *has* been changed.

You need to save it in Unicode format. It should be an option in the 'Save' dialog box. Probably under the 'File Type' drop down box. If that still doesn't work, get back to me

SPTI is the only one I've ever really used and the only one gets updates within my program code. Because SPTI is all done via Microsoft's API, there are other bits of code that can tie in with the core I/O stuff... like where it can show a device's 'Family Tree' and the speed of a USB connection.

Any of the green ones.

It's 'by design', so I doubt it'll change. As for a workaround, using the default I/O method is it

Ok so it turns out that ElbyCDIO's 'Exclusive Access' function only locks out the window file system, it doesn't lock out anything else... including other instances of ImgBurn using ElbyCDIO or indeed, SPTI. So the only way to really lock it out is to use SPTI as mentioned earlier.

It should be able to, yes. Clear it once before burning your first mkm-003-00 disc and then leave it alone.

You probably just need the right discs.

It says it's written a leadin containing cd text, so it looks like the disc should have cd text on it. Go into read mode with that disc in the drive and click on the media information button. See if it lists what you expect for titles and artist etc. Beyond that, I guess your player doesn't read cd text.

Post the log of the burn please

It's down to the OS to publish it... and it's probably down to parallels to make it available to the OS. So, if both of those are doing their job, it'll show up in ImgBurn.

Post the log please

Try adjusting the output size down a bit if it keeps making a video_ts set that won't fit on a disc.

Does it play MP4 from a disc? Maybe try a USB stick or convert the MP4 to DVD video or BD video format and burn those files instead.

Your drive or machine has got stuck. Turn it off and on again.

I guess you'd need to try some more verbatim ones with that mid to see if it's just a coincidence that the drive is failing in general now or if it's just the discs. You could try enabling the 'perform opc before write' option in the settings to see if it will help the drive achieve a decent burn on this slight variation of a previously working mid.

I had a go at burning a disc with clonebd to see what it did and it doesn't appear to lock the drive at all when it burns. Other apps can still use the drive (via both elbycdio and via spti) when it's burning. I was hoping to find it made use of some superior locking method, but it appears it doesn't. I've emailed someone and asked if they can assist.

The LiteOn iHAS models can do it. I think the 'iHAS124 F' and 'iHAS324 F' are probably the only 2 still around as 'new' drives. Optiarc / Vinpower's special 5280S-CB-Plus model is also designed for overburning, but they might be harder to find, depending on where you live. All of them work best with Verbatim MKM-003-00 media. You can buy enclosures for 'normal' sized optical drives that'll let you just plug them into your laptop via USB as you've been doing with your slimline one.

If you posted a topic about it long ago, is it really still an issue for you? I've only ever used spti and never had a problem with it. I have roughly the same issue as you if I used elbycdio on Windows 7. The drive is still accessible in the 2nd instance of ImgBurn, even though the elbycdio driver claims it has locked the drive successfully. I could try contacting someone to see if elby/ SlySoft/RedFox can explain what's going on. My details on the interface date back *many* years now.

I've no idea. What does Windows tell you to do?

Right, the problem here is that you've changed the I/o interface. It only works how I've described it when using the default spti one. I don't know why it's not locking it properly when using ElbyCDIO, the locking mechanism is handled by the driver itself rather than ImgBurn. Maybe something has changed?

Can you post the log please.. always post the log

It only logs that message if the drive rejects a 'Write' command (to LBA 0) where the 'streaming' bit is set and the response code has been set to 'invalid field in cdb'. So for whatever reason, that's what happened at that specific moment in time.