LIGHTNING UK!

That label will show up in Explorer on your computer. A standalone player may or may not read / display it.

There are free tools out there that will convert your files to DVD Video format. Then it's a simple case of dropping the VIDEO_TS folder into ImgBurn and burning. 'AVStoDVD' and 'DVD Flick' spring to mind.

Think of an ISO like a box.... that's all it is. You put things in it, but they don't change. So if you put MKV/MP4 files in an ISO 'box', when you look inside the ISO 'box', you still have the same MKV/MP4 files. Either you used to start off with compliant DVD Video (VIDEO_TS) stuff (and not MP4/MKV) or you used another program to convert to DVD Video format (VIDEO_TS) and then used ImgBurn for the burning part. Lots of freeware conversion tools can automatically call upon ImgBurn for the burning phase.

ImgBurn burn as-is, it always has done. So if you feed it MP4 / MKV files, that's what you'll end up with on the disc. If your play needs proper DVD Video discs (ones with the VIDEO_TS folder and usual set of files), you'll need to convert your MP4 / MKV files into that format before then burning the VIDEO_TS folder. You must have been using different software (or an additional piece of software) on your older PC and have started skipping a step on your new one.

Don't block it at your firewall. Let it through or turn off the 'check for updates' option.

No, I just downloaded it and checked it for myself.

Mirror 7's download still matches the CRC/MD5/SHA1 values posted.

Post the log please.

This is not going to be an ImgBurn bug. Please post the log.

2630945 / 16 = 164434 remainder 1 So you're 1 sector into the next ECC block (a block of 16 sectors) and that's why your burnt disc shows up as having a size of 2630960 sectors. It's rounded up to the next multiple of 16. Can you copy and paste all of the disc info from the box on the right when you're in Read mode and that burnt disc is in the drive please?

Yes, it's exactly what I said it was in my first reply. The source image size isn't a multiple of 16 sectors. Drive pads it during burn -> burnt disc comes out looking bigger -> read mode reads the full (bigger) disc.

Can you post the log of the original burn too please? It's probably to do with the size of the original image not being a multiple of 16 sectors - so it's then rounded up to 16 when you burn (the drive does that). That in turn makes the burnt disc look larger.

How are you 'testing' it? Mounting the ISO in a virtual drive program and running it from the virtual drive?

Yes, it’s proprietary and closed source. DT and Alcohol developed it. MDS v1 supported multiple sessions / tracks, but it wasn’t required within ImgBurn, I only needed single session / track for dvds.

I did actually say what I use in my previous reply. Just not in one word haha. IOCTL_SCSI_PASS_THROUGH_DIRECT

Yes, DeviceIoControl and the SCSI passthrough direct ioctl. I used to get the MMC docs from the t10.org website. No idea if it’s still running or if they’re still available. ImgBurn isn’t open source, sorry.

There’s no driver. It uses the scsi passthrough interface (spti). The MMC specifications detail the command set used by optical drives.

I think I explained that in my previous reply. The program has basic support for MDS, nothing more. It’s a private format and only v1 of it is supported at all.

It's 'single track only' in that file format. My MDS stuff was only basic and only for DVDs (well, DVD9) really as it dates back to DVD Decrypter days. For CD, the program favours BIN/CUE and that one supports multiple tracks / sessions.

The message is correct. Use the program that created the image - probably Alcohol 120% or Daemon Tools. MDS/MDF is their native format.

Essentially, it shows that the 'streaming' flag will be set to 'true' within the write command. It allows the program to burn BD-RE at full speed (i.e. 2x) even when they've been formatted with spare areas enabled. It's made possible by the 'streaming' flag telling the drive to not perform its auto write/verify process during the burn.

You’re mixing up queue files with cue files. A queue file is an internal file type and format. A cue file is an image file and should be loaded via the ‘browse for source file’ button when in Write mode.

It isn't behaving itself - maybe use a different program for your virtual drive? Just keep clicking cancel until the errors go away.

What sort of device is your G: drive?

ImgBurn doesn’t see the filters, your system does. Once they’re properly known/installed, directshow will use them. Of course it could always be that your flac files aren’t supported by madFlac.