All Activity

That's also my understanding of how it's basically done.

I don´t know how it´s done, but I think it appends the last operated session on top, then the trimming process starts removing the oldest log entries by session not line by line. So at the end when it reaches the cap limit, the number of lines will vary accordingly with the limit beeing 5000, oldest log being saved from start to finish not somwhere mid session.

Well, it must be 5,000 lines at the max. And when it reached 5,000, then the entirety of the last dated operation is removed from the Log. The Log, as far as I've ever seen, never ends with an incomplete Log. So, if it is capped at 5,000, when the Log exceeds that # of lines, then the oldest entry from a particular start of a Log is removed to free up space since the Log as far as I can tell never ends with a partial operation. Either way, thanks for looking for that info for me!

Search in forum for "5000" to see more answeres pointing it is limited to 5000 lines.

I wouldn't think it's based on a line count. That would potentially leave an incomplete operation listed at the end of the Log.

If I recall corectly it´s 5000 lines.

What is the retention rate for ImgBurn's Log? It appears to be 7 days, but I don't know that for sure. Thanks!

To be honest, I never successfully ever got a bootable image created in Build Mode to boot. So, I can't help, sorry.

Hi all - New ImgBurn user, but comfortable with Windows OS and computing in general. I've been trying, without any luck, to create a bootable ISO file with ImgBurn The reason I need a bootable file is that I use Ventoy to load ISOs on a USB drive, and they must be able to boot up. I've not been able to get any information on this in the forum or in ImgBurn documentation. Maybe I'm wrong about that, if so, could someone please point the way. To get a bootable ISO, one needs to use the Advanced>Bootable disk tab in ImgBurn. The choices are obscure, with no guide to making the right values. I'll show a screen shot of the 'Bootable Disc' window: The source and destination are straight forward,(H:\ISOs and Images\ are a folder on the Ventoy boot ISO on which my ISOs will reside) but the 'Emulation Type', 'Boot Image' , 'Platform Id' , 'Load segment' and 'Sectors to load' fields offer no guidance to what values are needed. I've left 'Emulation Type', as default, though there is a 'Hard Disk choice, which I will try. The boot image is from the Windows 11 Insider Preview install ISO. I've chosen to use 'efisys_noprompt.bin' rather than 'etfsboot.com', which I understand doesn't work with a UEFI boot image. 'Platform Id', I've changed to UEFI. 'Load segment' I've left to its default. and 'Sectors to load' I've changed to 8. This combination does not produce a bootable ISO. The message I get from attempting to load the ISO that I make for use with Ventoy is as follows: "No boot file found for UEFI. Maybe the image does not support x64 EFI" I know that Ventoy is working properly, because those bootable ISOs in the Ventoy USB load without problem. I'm running out of configuration ideas for making an ISO bootable. Can anyone offer any guidance, tips or observations? I'd welcome any replies.

Regarding CloneBD, since BD-R SL are stable technology, I've been debating just compressing my remaining BD-50's to BD-25. At least those will "always" work. I already have CloneBD. So, others may want to invest the cost of 1 or 2 lots of BD-R DL's and get a lifetime license for CBD. Then, compress your BD-50's to BD-25's.

Only one standalone player will read TL / XL discs. If you are interested in burning larger movies they need to be shrinked to 50GB e.g. with CloneBD. So- if you are interested in your burning results, flash the MK firmware. BTW- I moved to store ISO files and play from hard drive. No burning discs anymore.

UHD reading never interested me. I have no 4K Blu-Rays and even if I did, the cost of TL and XL media is prohibitive. If the DL media is this unreliable, I can only imagine how TL/XL will be!

You can also perform your own quality tests. Flash your WH16NS60 or any other full size LG /ASUS drive with the MT1959 chip to WH16NS58 1.V5 and use Qpxtools. https://github.com/speed47/qpxtool The scan results are much more meanigful compared with what you do currently. You can always flash the drive back to WH16NS60 or to the ASUS firmware. Be aware that the MK firmware from Makemkv is NOT recommended for burning but it reads UHDs. There is another firmware version I can recommend if you want to burn with that drive but this doesn't allow to read UHDs.

I knew it was there somewhere, just not where. I'd never had need to use it before but since 2x seems to be the only reliable speed for Verbatim DataLife Plus BD-R DL's, I wanted to take advantage of it as every other MID I have in my arsenal can be written at Max speed fine. And a few times, I've already gotten to change the Write Speed back manually.

Thanks! For others, it's also under Tools.

Yes, there is. To the right of the Write speed setting is a little green button called Change Automatic Write Speed...

windows 7 supported formatting it as fat32. im assuming modern windows did away with that. though theres nothing wrong with using udf to use dvd-ram as a flash drive.

Isn't there a feature in ImgBurn where you can tell the software at what Write speed to write a particular medium based on its MID? How do I enable and configure this? Thanks!

The Pioneer I was referring to was the 2213, which I think was the last model they produced. After getting failure on my first playback test of burning at 2x/4x in the NS60, I performed similar Forward Scan 4x test on two others and they passed where as the first disc failed that Forward Scan 4x playback test. I may try out some Ritek BD-R DL's and see if they are better than the Verbatim DataLife Plus ones. The problem with the Ritek DVD+R DL double layer media I tested about 15 years ago was 2/3 of them were unreadable after a year. However, they're cheap enough to throw the dice on. About half the price of the Verbatim DataLife Plus BD-R DL. https://www.amazon.com/RiData-50GB-Dual-Layer-Blu-Ray-Writable/dp/B018640FNI/ref=sr_1_1 Don't know the MID on them, though.

My Pioneer drives S12U and S11 will write the DVD+R DL with MID CMC MAG-D3-64 (Verbatim) with 2,4x, 4x, 6x and 8x. No idea about which Pioneer drive you are talking. The discs with the MEI MID are not available anymore. Only with MID VERBAT-IMf-000 which are much worse and they will benefit from the spare areas as they often fail at the layer break. The Riteks which perform better than those are the 50GB DL with MID RITEK-DR3-000. And slower burning at e.g. 4x (2x with spare areas effectively) will improve the burn quality. All LG drives are lousy burners for 50GB discs. They are OK for 25GB discs and these can be burned at full speed w/o any issue.

Don't have a Pioneer to test with and they no longer make drives, either. The last time I used their latest BD-R drive, it would only write 8x DVD+R DL at 2.4x, despite the previous firmware revision working at writing 8x DVD+R DL at 8x. And they have even fixed the borked firmware for 8x DVD+RW which HAD been fixed BEFORE after 15 YEARS but Pioneer BROKE AGAIN! Don't have any Japanese Verbatim/MEI MID BD-R DL's to test with. Will try the formatting with spare areas settings eventually. After I try the NS60 in the VanTec Gen 2 enclosure at 2x.

Try it. Today's discs are all mostly crappy. The last good ones where those Verbatims made in Japan with the MEI MID. Manufacturing was transferred to Taiwan and since then they are bad. Riteks still work somehow. At least with this method. Like mentioned in the link we tested with VPTools.

Most of the time, yes, but I got my fair share of crapping out writing/verifying in Layer 0 nowhere near the layer change.

No. It's also for BD-DL. It reserves the spare area and if the read back during the burn is bad the data is written to the spare area. The defects appear most of the time at the layer break.