LIGHTNING UK!

Well, it depends on a few factors. ImgBurn attempts to read those last 2 sectors before deciding if they should really be part of the image. If they're unreadable, it won't include them. Sometimes it'll add stuff to the CUE file too, so it knows a bit more about the image and can adjust what it responds with accordingly.

That's not quite what I said. I said that specific line in the log was based on the 'Disc Capacity'. The values in the warning message are based on TOC information and Track Information. You can't just use 'Disc Capacity' when reading a disc unless it's single session/track.... and ImgBurn isn't just designed to read those, hence it never uses the 'Disc Capacity' value to decided on how much to read. The problem is, either number (Track Info, TOC Info) could be incorrect and you can't 100% rely on either of them.... which is why the warning exists. Your 'Track Information' and 'Disc Information' (Disc Capacity) would both suggest that Track 1 (as it's the only one on the disc) is 93122 sectors in length, but the TOC has other ideas and thinks it's 93124. That's common when dealing with discs recorded with the TAO method. So... if there's a difference between what your drive is reporting via the two methods, the program warns you about it. This is not a bug in the program (as the thing you linked me to would suggest), it's there for a reason.

Actually, I think your log shows it is creating the image correctly. >> I 17:12:44 Source Media Sectors: 93,122 ^^ That's from the disc capacity and is basically there for cosmetic reasons. I 17:13:04 Reading Track 1 of 1... (MODE1/2048, LBA: 0 - 93123) ^^ That's from the TOC (or Track Information, one of the two). It's 2 sectors larger and therefore should be correct... if that's what you're saying? ImgBurn doesn't use the disc capacity when making the image. It does however, like to tell you about potential issues when it notices that something isn't right. Copy and paste the disc info text from the box on the right when you're in Read mode please as it'll quickly tell us where the problem is coming from. Firmware bugs are more common than you'd think.

Track 60 is probably too short. 4 seconds is often the shortest a drive will allow.

Yes, once you've added your file to the 'Create CUE' window, right click its entry within the list and pick the 'Display DirectShow Filter List' option.

24 bit files may not be supported by madFlac. I see the info about your initial file saying it's 24bit.

Install the recommended filter from the Audio CD guide - i.e. madFlac

The installCore plugin is what offers the 3rd party apps during the setup wizard. If you aren't interested in the offers, just opt out of them. Simple.

There is code in it to try and get around the situation where drives don't behave themselves, but it takes time to actually get to the stage where it gives up Or perhaps your drive eventually returned what the program was asking of it

It's unlikely that anything other than your drive/firmware/media combo is/are responsible for the 'power calibration errors' etc. Could you perhaps post a log from where you've run into issues?

Lots of guides for this in the Guides forum.

You'll probably have to give up with that. If your drive keeps looping round as it's trying to determine the gap between tracks (it queries the drive for specific info), there isn't much I can do I'm afraid. If you have access to another drive, you could try it in that.

I see no log

That's true, I don't have bad eye sight The first time you run the program, the main window should be top/middle and the log should be bottom/middle. After that, the location (top left corner) gets saved in the registry and used each time you load it again. So if you change resolutions, scaling etc, that could cause a problem as its 'old' location may no longer be the optimal one. If you're saying it doesn't work correctly on a totally clean install (so no HKCU\Software\ImgBurn reg key), that might be something I can look at fixing.

Even so, it’s developed on a pc with a single monitor. I don’t and wouldn’t use anything above normal (100%?) scaling.

There shouldn't be any problem with it. Download it again, from a different Mirror site.

Please post a new log from the current version of ImgBurn and a drive / media combo that should actually work

That drive can't burn BD discs, only read them. It should be able to burn DVDs and CDs though. Also, you should update to the current release of ImgBurn.

I’m sure winimage must be able to open its own images. It would be useless otherwise. When ImgBurn reads the floppy to an image, it’s a straight sector dump of the disk. There is no method of writing that back to a floppy disk within the program. It’s meant for use when building a bootable optical disc.

Try winimage, it’s what I always used to use.

ImgBurn is for optical drives and discs, not floppy drives / discs. Windows can copy a floppy disc.

There are firmware updates available for your drive. A newer one may perform better with the media you're trying to use. https://www.firmwarehq.com/Pioneer/BDR-206/files.html

As the program is calling your disc a ‘data’ disc, you do not have the correct dvd video compliant file/folder structure. Try again when you’ve got one. Burning the same thing over and over won’t change the outcome.

I wrote it.

Not sure why you'd want to be using Samsung anyway... you don't have a Samsung drive, it's a LiteOn one. The program would do it automatically by default anyway, so don't worry about messing with it yourself.