Jump to content

dbminter

Beta Team Members
  • Posts

    8,362
  • Joined

  • Last visited

Everything posted by dbminter

  1. 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.
  2. 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.
  3. I read a similar article about 24H2. It indicated any CPU made within like the last 10 years supports that instruction set.
  4. 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.
  5. 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...
  6. 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...
  7. 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!
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. 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.
  15. 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.
  16. That unit you linked is the external version ASUS offers of the BD drive I am currently using in an enclosure. So, I would say it's the same drive internally as what I've been using. You can read my review, which spans a few years, here:
  17. Semaphore timeout errors are generally the fault of an incompatibility between the USB bridge in the external drive and the USB controller on your motherboard. Unfortunately, there's generally little you can do to fix this other than get a different drive. You could try and see if there are any USB controller driver updates for your system or firmware updates for your Pioneer drive (Verbatim doesn't actually make their own drives but farms out to Pioneer.). However, these rarely help, especially the firmware updates. I can say that on my Dell system, that kind of drive has never displayed a semaphore timeout problem, but I've never burned a 100 GB M-Disc before, either. I've actually never burned anything beyond a 50 GB BD-RE DL in any drive. So, what would I do? I'd try a new drive. And I'd avoid a slim unit. Slim model drives generally aren't very good, but my slim Verbatim Pioneer in the black version of your drive and it's worked fine for what I've thrown at it thus far, which has primarily been only as a reader. And I'd avoid Pioneer as they have had lots of issues for over a decade. What I'd get is the ASUS BD drive. I believe it supports 100 GB M-Disc. I think it comes in an external variety, but what I did was I bought the internal model and put it in an OWC USB 3.0 enclosure. The only other enclosure option is VanTech. And if you're going the enclosure route, you will need USB 3.0 to support BD speeds. (You will notice the log says your Pioneer drive is a USB 2.0. It's actually a USB 3.0. USB 3.0 hadn't been widely available at the time of the last ImgBurn release, so that's just a cosmetic error that has been addressed in beta releases since.)
  18. I do feel the need to pass this along. It appeared to be a fluke, but it did happen, so it's worth noting. I had a DVD-R of home movies converted to DVD Video. I know this disc was playable because after I created it just the other day, I read it to an image file with ImgBurn, loaded the image file in DVDShrink, and wrote a new VIDEO_TS output to test it. It passed. Sunday, I put the same disc back in and copied the VIDEO_TS folder in File Explorer, but it would not play or load in anything, even DVDShrink. I put the disc back in today and read it back into an image that did read properly in DVDShrink. So, I haven't quite figured it out yet. It may have just been a fluke. It may have been a issue with the USB enclosure. On the LG WH16NS60, you have to sometimes turn off the enclosures and turn them back on before Windows will recognize data from DVD's. Some kind of Windows bug. A similar one may have happened in this case. Plus, I've been unable to reproduce the issue. Sunday, I copied another DVD-R of home movies the same way without issue just before the one I described above.
  19. I do feel the need to pass this along. It appeared to be a fluke, but it did happen, so it's worth noting. I had a DVD-R of home movies converted to DVD Video. I know this disc was playable because after I created it just the other day, I read it to an image file with ImgBurn, loaded the image file in DVDShrink, and wrote a new VIDEO_TS output to test it. It passed. Sunday, I put the same disc back in and copied the VIDEO_TS folder in File Explorer, but it would not play or load in anything, even DVDShrink. I put the disc back in today and read it back into an image that did read properly in DVDShrink. So, I haven't quite figured it out yet. It may have just been a fluke. It may have been a issue with the USB enclosure. On the LG WH16NS60, you have to sometimes turn off the enclosures and turn them back on before Windows will recognize data from DVD's. Some kind of Windows bug. A similar one may have happened in this case. Plus, I've been unable to reproduce the issue. Sunday, I copied another DVD-R of home movies the same way without issue just before the one I described above.
  20. Was it ONLY those two files? If it was only those two, I would concur that it was user "error" and those 2 files alone got name changes in the DLE.
  21. No, the Read speeds are set on the media regardless of the maximum write speed used to burn a disc.
  22. A write of a full BD-R should take about 15 to 20 minutes at 12x and a read operation is faster than a write.
  23. Being on BD-R shouldn't matter as to what app opens the files. Unless the files on the BD-R do have a different extension and you were asked what to open these "new" file types with. And your standalone player not showing the files also makes me think the files have a different extension on them on BD-R. One way to check and make sure is to open a Command Prompt and do a DIR on the BD-R drive contents to make sure the files still have their proper extension on them.
  24. Oh, that explains why the extensions were missing. What this doesn't explain is how the files not a BD-R can play in VLC when you double click on them but the files on the BD-R do not. That would be almost as if the .MKV extension WERE missing from the files on the BD-R.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.