LIGHTNING UK!

It would appear that way, yes. Do you have any optical drive related programs installed / running that could be screwing with things? I had a look around lastnight and it would appear your drive is just a rebranded liteon anyway - I tried 16x with my iHAS422 but it burnt at 16x just fine. I may revert it to the original firmware and try again though, perhaps it's something they fixed in the newer one. There don't appear to be any firmware updates available for your drive.

I've never seen any BD-RE DL from Verbatim and I don't think they mention them on their website. I'm sure they'll bring some out one day though. I've been doing this long enough now to have seen where all the failures come from and therefore what to avoid buying. That's why I stick with Verbatim. Not that you really need telling now, but don't waste your time on the LG BD-RE. It's awful and fails in most people's drives! God knows why they supply them with their

So potentially you have 500 MMC-004-00 branded by Memorex that your Samsung drives refuse to burn?

Here we see ImgBurn setting the speed to '0B 06' (0x0B06 = 2822 KB/s = 16x)... and here we query the drive to see what the selected write speed is.... 0x0B07 = 2823 KB/s = 16x Ok so it's one byte per second faster than I'd asked for but that's just a tiny calculation difference and nothing to worry about. The drive should still be burning at 16x.

Is that MCC-004-00 stuff you're using not branded by Verbatim then?

Yes, ImgBurn will automatically booktype to DVD-ROM on the majority of LiteOn based drives. btw, your links don't work.

Sure thing, I'm always interested to hear what 3rd parties have to say about such matters

Including the dklang file probably isn't such a good idea. Why would you want it portable anyway? It's hardly something you'd take round your mates house to show them, or need urgently when you're repairing a neighbours PC!

Do you have access to any other drives (non samsung) that you can put those burnt discs into? I don't get why your drive says it's burning them ok and then reports the disc info as though it was still a brand new blank disc.

With ImgBurn as it is now, no. The reason being, I'd only add CLI support for burning an Audio CD when that feature has it's own mode - i.e. gets implemented properly rather than piggy backing the 'Create CD CUE File' feature. Don't ask when that'll be done because I have no idea!

Because there's no way to bring up the 'Create CD CUE File' window. This of course assumes I make no changes to the program in order to direct files passed via CLI to that window.

Maybe someone had those discs before you and took them back because the RITEKF1 dye is shite.

Ok so now try slowing the burn down to 8x or 12x. Have you tried other discs? Do the discs you've just tried to burn actually look like they've been burnt on the bottom? Do you have the latest nvidia nforce drivers installed? Whichever way you look at it, reporting 'Fibre' is just plain wrong.

Do both machines give exactly the same info? What other cd/dvd related software do you have installed? I really can't imagine both machines would give exactly the same info if the discs really were blank - assuming no other software is messing with the info returned by the drive. Does it recognise originals / previously burnt discs properly?

You might be lucky enough to get the code for it - which you can then tweak to add the other things you wanted (except number 2 is impossible).

So was that the disc you just burnt to? As in THE actual disc? It seems a bit odd that the drive would report success to all of the disc writing commands without actually making a single change to the disc. What controller is that drive connected to for it to be being reported as using a 'Fibre' interface?!

You know what it's like, do it for one and you've got to do it for every single number that gets printed anywhere.... that's where it starts becoming a pain in the arse.

Oh and number 2 can already be done by a 3rd party dll. http://www.svcd2dvd.com/#ImgburnShellExt

Showing it in bytes is the only way to make it accurate and that's what ImgBurn is all about. Making the units user changeable is of course possible but it's something I'd rather not do if I'm honest. Showing all 3 certainly isn't an option, there's just not enough space for it.

I've no idea. I'm sure there are lots of examples on the web though.

ImgBurn relies on DirectShow / ACM for decoding your audio files. As such, you'll need to have the appropriate filters installed for the types of files you'll be burning. Support for MP3, PCM, WAV and WMA should be built into Windows - at least it is on XP / Vista / 7. For other file types, try the following: AAC - CoreAAC - http://www.free-codecs.com/download/CoreAAC_Directshow_filter.htm AAC - ORBAN - http://www.orban.com/plugin/ or http://www.free-codecs.com/download/aac_aacplus_player_plugin.htm APE - Monkey's Audio - http://www.monkeysaudio.com/ FLAC - madFlac - http://forum.doom9.org/showthread.php?t=130498 ( http://madshi.net/madFlac.rar ) M4A - CoreAAC - http://www.free-codecs.com/download/CoreAAC_Directshow_filter.htm M4A - ORBAN - http://www.orban.com/plugin/ or http://www.free-codecs.com/download/aac_aacplus_player_plugin.htm MPC - Radlight - http://www.free-codecs.com/download/RadLight_MPC_DirectShow_Filter.htm OGG - CoreVorbis - http://www.free-codecs.com/download/CoreVorbis.htm OGG - Radlight - http://www.free-codecs.com/download/RadLight_Ogg_Media_DirectShow_filter.htm OGG - xiph - http://www.xiph.org/dshow/ WV - WavPack - http://www.wavpack.com/downloads.html or http://code.google.com/p/wavpack-directshow/downloads

Nope

Copy + paste the disc info please.

Just hover the mouse over where it says the image size in bytes and the tooltip will pop up showing the value in bytes, KB, MB and GB.

I don't want to write a dll to handle shell extensions and that's the only way to do it - this has been mentioned several times before. Number 4 is already possible though... but it won't work unless you run ImgBurn as admin once.