LIGHTNING UK!

I will look into it. It would have helped to see the actual error in the log, but going by the CUE I found online, it's noticing differences in a pregap sector - and they're generated by the program.

Somewhere in the product listing you should see the various read and write speeds for the different media types supported by the drive. Are you after a dvd drive or a bd drive?

The speed of the connection can and will limit the speed of the drive. A fast bd drive won’t work properly over a usb 2 connection. I doubt you could buy a recent model that doesn’t have the correct connection type required to achieve what the drive is capable of. Therefore, you probably don’t need to worry too much.

ImgBurn doesn’t instruct the OS to ask you to run it elevated. Apps configured like that have the little yellow shield in the icon. If UAC is disabled, obviously it won’t prompt - because everything then runs as admin. When enabled, it’ll prompt if the app asks to be elevated - which again, ImgBurn doesn’t.

Post the log please.

ImgBurn is not a command line tool and the flag to eject is only looked at after an operation (read/verify/burn etc) has completed. There's no way to use it to just eject the disc like that.

Not at all like an idiot, don’t worry [emoji1303] If you’re doing tests and making comparisons, it’s just best to test like-for-like (as much as possible anyway). So the iso must be played from a virtual drive and you must then use the same software player to play the burnt disk.

Are you mounting the ISO as a virtual drive and then playing from the virtual drive, or are you simply loading the ISO in whatever playback tool you've chosen to use? The two methods could cause the playback software to behave differently. If the ISO is really ok, there's no reason for it to behave differently when burnt to disc - subject to the device being able to read the disc nicely / quickly enough. Whilst there are probably people on the forum that could offer some advice, your issue doesn't sound like it's related to ImgBurn... or even burning in general. You might be better off asking for help at somewhere like videohelp.com

Your disc is copy protected. I'm afraid ImgBurn can't help you here.

Db is correct, it’s an issue in a totally unrelated library.

Please post the log.

When you say you've checked the CD-R, what exactly have you done? Once the disc has burnt and you get that error.... if you 'ok' the box and then switch to Read mode, can you copy and paste everything from the box on the right of the main window please? It seems as if your drive is reporting that the disc is still empty - hence the session count coming back as 0 on the burnt disc.

Can you post the log please? Also, 'ImgBurn Support' is the best section for your topic, not 'chat'. I've moved it.

Does this drive not work? It says the enhanced model of this vinpower drive supports scanning. https://www.vinpowerdigital.com/products/wh16ns58dup

Ok, maybe it was the load segment value was throwing it off before. Most other bits get noticed and corrected by the program when it detects you want to build an OS installation disc. As you're using etfsboot.com, it doesn't look like you're building a UEFI bootable disc, it looks like a legacy bios one. This is the same issue covered a couple of days ago in this thread... But if it boots for you, I guess it's all good and your VM has handled it.

Google doesn't throw up a whole lot when searching for that error. Is your vm in UEFI or legacy bios mode? I assume that if you follow the OS installation disc guide in the Guides forum and actually do it via the GUI, you get the same result?

You can also make a little registry change during the installation. That’s what I did the other day when making a VMware workstation vm of it.

The guide. Try with platform ID set to UEFI and for the boot image, select \efi\microsoft\boot\efisys.bin Sectors to load is 1 I think.

The reason I asked is that those guides predate uefi (mainstream at least) and are meant for bios boot.

Do you use bios boot or uefi? The iso you build needs to match what your vm is expecting.

There are guides for Windows OS installation discs in the Guides section. That would be the best place to start https://forum.imgburn.com/index.php?/forum/4-guides/

Are you saying the full erase on 2.5.8.0 behaved differently somehow or didn't you even attempt it? As the erase command hasn't changed, I doubt any one version would behave differently to another one. The drive is in control of the format process, not the program. Logs from the process would help, otherwise this post is better removed so as to not spread false information.

Back in the day, it was all about the LiteOn iHAS drives - nothing else really worked. Even with those, you had to enable the 'Force HyperTuning' option on the drive for them to burn those oversized images nicely. As yours appears to support the hypertuning option, give it a try. You're definitely more likely to succeed in burning an oversized image on a MKM-003-00 disc though.

If my memory serves me correctly, that info is specific to LiteOn drives. Some tool available for their drives used to display it, I found out where it got that info from and then implemented the same command within ImgBurn so I could display it in the log (just as an FYI type entry). As db said, it's not an internal count that ImgBurn is performing and there's no limit of any sort imposed by the program.

I would assume it's the number of discs it has burnt.