LIGHTNING UK!

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.

Are you sure you mounted a CUE file in Daemon Tools? The virtual drive is reporting those sectors as unreadable (not something I thought would happen from a CUE file). Is the image ok? Can you copy and paste it elsewhere? You may actually just be able to rename that .img file to .bin.

For whatever reason, your machine is returning a really weird error when the program asks your drive to burn the sectors. That error is not from the drive, it's from the OS. It could be a dodgy driver issue or something. Maybe try uninstalling the usb controller from within Device Manager (so it wipes out the controller, hubs and the devices connected to them), reboot and let Windows find it all again.

Post the log please

I don't dismiss stuff if people are sure they unchecked any offers they were shown. The setup exe is kinda old now and I have actually been contacted (recently) to say there's an updated 'clean' plugin... so maybe their last one had an issue. When it first came out, there was no such issue with 3rd party software installing when it shouldn't have - or at least not that I experienced for myself.

I believe this is covered in the faq.

Multisession stuff will probably fail if you have test mode enabled - which you do there. Please reset your settings back to default. The stuff you read on the internet about magic fixes for issues (i.e. changing the buffer to 72mb) are complete nonsense. Once Test Mode is off, burn a disc and post the log from that if it fails please.

Post the log please.

So that's 3 different drives failing to burn the discs and reporting a 'Write Error'? These things shouldn't be dependant on the OS as the burning is a drive internal process. Maybe try putting one or more of the drives in another machine and see if you have the same issue? Are the ones that are failing all from a new batch or anything?