dbminter
-
Posts
8,372 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by dbminter
-
-
To be fair, that disc it failed on was a bit beyond the norm. It was a mixed mode CD created by Nero Burning ROM. The 2nd attempt to burn the disc worked but failed to read it one sector based on an illegal mode for the track.
-
To be fair, that disc it failed on was a bit beyond the norm. It was a mixed mode CD created by Nero Burning ROM. The 2nd attempt to burn the disc worked but failed to read it one sector based on an illegal mode for the track.
-
Had another failure. This time high quality AZO DataLife Plus Verbatim branded CD-R. Hopefully, it's another fluke, but I am worried about these numbers of "flukes" that are now appearing. I have to wonder if the tests that PASSED were flukes.
-
Had another failure. This time high quality AZO DataLife Plus Verbatim branded CD-R. Hopefully, it's another fluke, but I am worried about these numbers of "flukes" that are now appearing. I have to wonder if the tests that PASSED were flukes.
-
Plus, there's also a speed factor to take into consideration. It takes about 20 minutes to write 25 GB to a BD-R at 12x. Unless these Super DVD discs make a quantum leap in write speeds, I can't fathom the amount of time it would take to write a petabit of data.
-
How practical would it be for ImgBurn to support something like that? To store 1 petabit of data per disc, you have to have 1 petabit of data on standard storage media to begin with. How many people are going to have 1 petabit of information readily available to write to these discs? And it would be impossible to write an ISO for these before burning because there are no such things as petabit hard drives/SSD's. Even if you didn't use the entire 1 petabits, you'd be wasting a lot of potential space. The highest capacity HDD is something like 26 TB so you could copy the entire contents of a 26 TB HDD to a petabit disc, but you're wasting a lot of viable space. Even with a RAID set up, you'd still only be using 52 TB. And the issue of creating ISO's before hand still exists.
-
Generally, issues with freezes on Analysing Tracks are down to the device itself. As was said, about your best bet is to try another drive, but there's no guarantee it will work, either.
Another possible solution is to not use ImgBurn, which kind of defeats the purpose. I know I've encountered PS 1 games that ImgBurn wouldn't read but Alcohol 120% Free would. You could try Alcohol and see if that works for this disc.
-
Hopefully, it was just a fluke. The next disc in the stack was fine. And the previous disc was one of 3 at the bottom of the stack. And this was a newer stack. I won't know for sure unless it repeats with regularity.
-
Hopefully, it was just a fluke. The next disc in the stack was fine. And the previous disc was one of 3 at the bottom of the stack. And this was a newer stack. I won't know for sure unless it repeats with regularity.
-
Just had my first write failure. On Layer 0 of an MKM 8x DVD+R DL. And it wasn't even a full Layer 0. The failure wasn't at the layer change.
Could be a fluke. Won't know until 2 more failures in a row followed by swapping in the known working LG WH16NS60 and a disc from the same cake stack.
-
Just had my first write failure. On Layer 0 of an MKM 8x DVD+R DL. And it wasn't even a full Layer 0. The failure wasn't at the layer change.
Could be a fluke. Won't know until 2 more failures in a row followed by swapping in the known working LG WH16NS60 and a disc from the same cake stack.
-
I read a similar article about 24H2. It indicated any CPU made within like the last 10 years supports that instruction set.
-
ImngBurn can create such an ISO, but whether that ISO will backup all files is questionable. And whether that ISO can be made "bootable" in a virtual machine or run as a Windows installation I wouldn't know. I've never done any virtualization, so I know nothing about VirtualBox.
-
It appeared to be a fluke centered on the authoring of those 5 discs on which it ultimately happened to. I then processed 3 more BBC Audio CD's followed by 5 more and then 5 more again, all 10 also from BBC Audio. No issues with those.
Of course, the only discs it happened to were 5 of the 14 discs in the boxed set that I bought the set for! The story of my life...
-
It appeared to be a fluke centered on the authoring of those 5 discs on which it ultimately happened to. I then processed 3 more BBC Audio CD's followed by 5 more and then 5 more again, all 10 also from BBC Audio. No issues with those.
Of course, the only discs it happened to were 5 of the 14 discs in the boxed set that I bought the set for! The story of my life...
-
nlat, would you do me a favor? Would you provide the current firmware revision # for the ASUS USB drive you got? The easiest way is to open ImgBurn and check out the main startup text in the Log window. You'll see something like this:
I 12:39:21 -> Drive 3 - Info: ASUS BW-16D1HT 3.11 (R:) (USB 3.0)
That's the value for my internal ASUS BW-16D1HT in a USB 3.0 enclosure. It's firmware is 3.11. You should find the firmware # after the drive ID string.
Thanks!
-
It happened a 3rd time. All these discs were in the same boxed set from BBC Audio. So, it could be isolated to just this boxed set. I have another boxed set coming up BUT it's ALSO from BBC Audio. Plus, there's no guarantee this incompatibility is limited to JUST the ASUS drive. It may be a case of incompatibility between the ASUS and the OWC enclosure it's in. With a VanTech enclosure, this issue may not be present.
-
It happened a 3rd time. All these discs were in the same boxed set from BBC Audio. So, it could be isolated to just this boxed set. I have another boxed set coming up BUT it's ALSO from BBC Audio. Plus, there's no guarantee this incompatibility is limited to JUST the ASUS drive. It may be a case of incompatibility between the ASUS and the OWC enclosure it's in. With a VanTech enclosure, this issue may not be present.
-
It happened again. So, it looks like one of the faults of this drive has to do with playing audio CD's. It may not be a good candidate for that.
-
It happened again. So, it looks like one of the faults of this drive has to do with playing audio CD's. It may not be a good candidate for that.
-
Thought I'd better pass this along. I had an audio CD where when I inserted it into the ASUS, ImgBurn got stuck in an infinite loop of Adding Devices and Removing Devices attempting to read it. When I put the disc in my Pioneer, it was fine.
-
Thought I'd better pass this along. I had an audio CD where when I inserted it into the ASUS, ImgBurn got stuck in an infinite loop of Adding Devices and Removing Devices attempting to read it. When I put the disc in my Pioneer, it was fine.
-
I've never had to follow Cynthia's guide for an End Of The World problem, but I would guess you do as normal and select one of those layer break positions and burn it.
-
I would only ever use a slim drive for reading, never for any kind of writing, as they generally tend to be junk. They tend to be good enough readers, but that's all I'd trust them for.
VERBAT-IM BD-R
in Media
Posted
I've got a somewhat concrete value of how high quality the Verbatim VERBAT-IM BD-R are. I've burned over a thousand probably over the last 10 years. Out of those, I've just encountered my first one that failed to read data back properly on it. However, this was most likely because the disc was not written properly back in 2016. On Verify of this disc, there was an unable to read sector error that was corrected. Immediately after this, I swapped out the LG WH16NS60 for a new one. A manual Verify of that disc passed, but it was most likely not written properly to begin with.
All other failures were either immediate burn errors or failure on Verify which were caused by dying NS60's. Once swapped out with new ones, write and Verify problems ceased.