dbminter

As I said, the only fault I found in the NS40 the last I used it years ago was it did not properly write to DL BD media, but firmware updates since then might have fixed the issues.

The first log you posted in this thread was for 2 MKM-001 burns.

That might work because the write strategy in the firmware for a Ritek DVD+R DL would be different than a Verbatim MKM DVD+R DL.

Oh, are you writing directly to disc and not an image file first? If so, then, opening and changing a file might cause a Verify to fail that way. Your logs posted were for 2.4x Verbatim MKM-001's.

Unfortunately, the only reliable DVD+R DL are the Datalife Plus/AZO series of MKM discs from Verbatim. So, burning Riteks, while they might pass, won't do me any good as I won't use those. If you can't Verify immediately, then make sure the file is closed and do a manual Verify. Although, I fail to see why an open file would prevent a Verify.

I would be interested to see your MKM-003 results. See if you get the same results I did. Admittedly, I only tested one before returning it. Plus, the MKM-003 are the only DVD+R DL you can get new and cost effective. 2.4x discs are still available on the aftermarket but are nowhere near cost effective. My memory was I did test the Verbatim BD-R in the ASUS and it was fine. BD-R SL only, though.

Here's probably why your burn was successful: I 12:03:26 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00) You were using the 2.4x speed discs. I was using the 8x discs. Disc ID: MKM-003-00.

Unfortunately, if you intend to write to DVD+R DL, that ASUS will fail at the Verify at the layer change. It needs a firmware update to fix this, which I've TOLD them they need, but they refuse to update it.

I paid $115 for the last one I got on Amazon.com, back in November of 2021. So, I my memory was off as to how much I had paid for it last time. I believe the current prices reflect the state of the market. That LG has probably discontinued the NS60. Even LG's Where To Buy page, when you click on it, shows no one selling it.

Well, the 40K is overpriced at $150. That's about double the price of the NS60 when it was available, and that was a 4K capable drive.

From what I can tell, the main difference with the 40k is it's a triple and quad layer supported BD drive. The NS40 I had was not. The NS60's selling point is precisely that. The 40K appeared to be a 4K supported BD drive, which needs to be able to ready triple and quad layer BD.

I've never heard of a WH16NS40k.

Yes, I flew into the Denver International Airport. Then, was driven into Westminster.

Generally, the Windows version selling point is just that. The version of Windows generally doesn't matter. In one direction, it's more important than the other. A newer version of Windows is more likely to support older hardware than an older version of Windows is likely to support newer hardware. If it says it works on Windows 8, you're pretty sure it will work on Windows 10. What matters is the driver support included with the version of Windows you're putting the drive in. That's why it's more likely for older hardware to work on newer Windows than the other way around. Newer Windows would have older driver support. Pagosa Springs, Colorado. Is that anywhere near Arvada or Westminster? I've been there back in 1997.

Well, I haven't used the NS40 in years. What made me stop using it was despite it saying it supported double layer BD burning, 9 times out of 10, it fails. And it wasn't just me. Others on this board reported similar behavior. However, in the years since, firmware updates might have addressed this issue. So, if you're not ever concerned with burning BD-R DL or BD-RE DL, the NS40 was the drive I was using for a long time. I don't have a need to burn DL BD media anymore now that I've moved from BD-RE to flash drives and USB SSD's. So, the NS40 would probably meet my needs unless they borked the firmware for other media since, like Pioneer does.

As I said, the NS60 doesn't seem to be available anywhere. I couldn't find it on either Amazon.com or NewEgg.com when I last looked, but the NS40 was available on Amazon.com. Amazon's really good with their return policy. I recently tried out a Pioneer 213 and had to return it because Pioneer borked the firmware AGAIN! After a decade of borked DVD+RW firmware, they HAD fixed it on the 213, but BORKED BD-R, DVD+R DL, and CD-R. The latest firmware fixed all these issues but BORKED DVD+RW again! Amazon accepted my return with no issues.

Oh, that's my bad. I was going by the end of the log where it says this: I 12:04:57 Source Device: [3:0:0] PIONEER BD-RW BDR-212V 1.00 (G:) (SATA) I see later on you must have applied the 1.02 update. Another drive would isolate if it's the Pioneer's problem. That's why I recommended what I use. I know they "work" but that only means they "work" for me. They may not "work" for you. But, with a baseline, if they don't work for you, then that would probably help isolate if it's something else that is wrong.

You're currently on 1.00. You might as well try updating to 1.02. If it isn't firmware for your drive, it will most likely simply say it can't flash your drive, so nothing bad would have happened.

The BDR-212 is actually a BD burner. The 212V is not listed on Pioneer's firmware site, but the BDR-2212 has as its latest firmware 1.2.0.005. And other BDR lines have like 1.04 as opposed to your listed 1.00. You could try the firmware here: https://pioneer.jp/device_e/product-e/ibs/device_e/dev00001r_e.html#firmware1 Note if the firmware does not support your drive, the firmware update package will not alter your drive as it won't allow anything to happen to it. I recommended the LG line because it has the least amount of problems with it, and none fatal, except for the NS40 which didn't write to double layer BD media correctly.. Unlike Pioneer drives which for the past 10 years have had unaddressed firmware borks.

I would first check for a firmware update to the Pioneer drive. In Write mode, right click on the Pioneer drive and choose the last option in the context menu for checking for a firmware update. Apply that if found and see if that helps. You don't really have an apples to apples comparisons in all of these logs. You're using both good discs, the MKM's, and trash discs, CMC. However, you're getting it on good discs, which isn't normal. CMC errors are WAY too common. But, NOT on MKM's. Barring that, I can only recommend trying the LG WH16NS60, if you can find it, which is what I use. If not, try the WH16NS40, which you can probably still find, but note last time I tried it years ago, it did NOT write properly to double layer BD-R and BD-RE, even though it claims to support them. Note these two LG drives are BD burners.

Of course, LUK makes the final decisions regarding who is a beta tester, but I don't think we've had any new ones added in over 10 years. So, there probably aren't any openings for one right now. But, maybe you'll get lucky.

The current state is easier to answer. There was a beta released around November 16th of 2021. So, it's still being developed, just very slowly. As for why it doesn't appear to be updated, the answer is most likely the developer has a job. :)

Looks like you had a transient read error that ImgBurn recovered from. The image file is most likely okay. I'd only have worried if ImgBurn stopped reading all together. I can tell you what most likely caused the problem. This: I 06:28:52 Source Media Type: DVD+R (Book Type: DVD+R) (Disc ID: CMC MAG-M01-00) The disc being read is one CMC Magnetics's trash disc. CMC makes the worst discs out there. It is fairly common for read errors on those and to be completely unreadable after just a year or so.

Thanks! I'll try to remember that. Maybe add some text to the windows to mention CTRL+C can copy the message contents to the clipboard?

When an operation error occurs during an ImgBurn function, a pop up window opens with detailed error codes, etc. about the error. The way it stands now, the user must take a screenshot of these windows to gather troubleshooting information. I was thinking, if it's possible, to pipe these errors codes, etc. that appear in the pop up windows into the Log. That way, a person can copy and paste the error information from the Log, which is easier. As it stands, there is sometimes an error line in the Log, but if there is, it's nowhere near as detailed as the error windows that pop up. In lieu of piping the errors into the Log, I have another idea worth pursuing. Add some kind of button or function in the error pop up windows that display error information and let the user save a copy of the window/perform a screenshot from within the error window itself. That way, the user doesn't have to take the extra steps themselves to generate screenshots. Thanks!