Jump to content

dbminter

Beta Team Members
  • Posts

    8,359
  • Joined

  • Last visited

Everything posted by dbminter

  1. Had another oddity. Just burned a DVD+R DL that passed Write and Verify. Then, I went to Read the same disc I had just finished Writing and Verifying and the read rate plummeted to 0.01x at the layer change. I powered off the drive, powered it back on, and tried again. The 2nd attempt to Read the disc afterwards succeeded.
  2. Had another oddity. Just burned a DVD+R DL that passed Write and Verify. Then, I went to Read the same disc I had just finished Writing and Verifying and the read rate plummeted to 0.01x at the layer change. I powered off the drive, powered it back on, and tried again. The 2nd attempt to Read the disc afterwards succeeded.
  3. I do believe that first failed read was a fluke due to a behavioral "bug" either in the drive, Windows, or the OWC enclosure the drive is in. Unless you use the Eject context menu item to eject discs in File Explorer, the metadata of disc contents is NOT updated. The downside of this is if you don't do it, when you copy the contents of one disc in File Explorer without Ejecting, File Explorer is trying to copy nonexistent data from subsequent discs inserted into the drive.
  4. I do believe that first failed read was a fluke due to a behavioral "bug" either in the drive, Windows, or the OWC enclosure the drive is in. Unless you use the Eject context menu item to eject discs in File Explorer, the metadata of disc contents is NOT updated. The downside of this is if you don't do it, when you copy the contents of one disc in File Explorer without Ejecting, File Explorer is trying to copy nonexistent data from subsequent discs inserted into the drive.
  5. Interesting how that drive apparently supports DVD-RW DL reading and writing since DVD-RW DL was NEVER manufactured.
  6. If the Super DVD is to be a viable format, it has to make a quantum leap in write speed. However, it is based on 3-D memory and not optical storage. 3-D memory may be super fast at writes. Without it in consumer hands, we'll never know. And it's not even in enterprise hands yet as it's only just a recently announced technology. However, I think your math is off. If it takes 20 minutes to write 25 GB, 1 petabyte is 125 TB. 125 TB is 125,000 GB. (Well, let's just conveniently ignore the 1024 factor. ) So, 125,000 divided by 25 GB is 5,000 20 minute writes. That's 100,000 minutes / 60 minutes in an hour / 24 hours in a day is 69.4 days.
  7. One thing I noticed in your screenshots. I see the text CMC MAG, which means you're using CMC Magnetics discs, which are the worst quality out there. Over 50% of the problems we see on this board are caused by CMC Magnetics media and when people switch from them to the high quality media, their problems usually go away. Try to find Verbatim DataLife Plus DVD-RW. NOT the Life Series you find in brick and mortar stores. Those will be CMC. You can generally only find the DataLife Plus stuff in online stores.
  8. I would say so. PS1 games were on CD where layer breaks weren't a concern. However, I can't recall seeing .MDS ever associated with a PS 1 game CD image. Of course, I'm just going by ImgBurn, which I can't remember that it used MDS in its file set, but maybe it did.
  9. I think at one time, the bypass trick was even easier. You just entered in no account name and password and repeated it several times in a row. Each time, you'd be told to enter something, but after a handful of attempts, Windows setup would go to setting up a Local Account. Microsoft quickly removed that impediment, of course.
  10. Thanks for that Microsoft account workaround! I knew it existed, but I couldn't recall what it was. My setup is okay as it was a Windows 10 that I created back when local accounts were possible and upgraded to Windows 11. But, on my next new PC, I wanted to create a local account, but couldn't remember how to do it.
  11. It's hard to know which error you're specifically talking about as the log displays multiple different errors from different failed burns. However, it points out a few possible issues. You're using the MCC media, so you're using the high quality stuff. Not junk media, so we can rule that out. The thing that immediately leaps out is the combination of semaphore timeout errors and the drive's listed USB interface of USB 1.1. USB 1.1 is ancient and super slow. You could be getting semaphore timeouts because the drive is not reading/writing fast enough. If you're going to use USB BD writers, you need USB 3.0 to avoid drop outs of data. However, semaphore timeout errors can also be a conflict between the USB bridge in your burner and the USB controller on your motherboard. So, what can you do? 1.) If you want to keep using that same drive, try connecting it on a USB 3.x port. 2.) Try a different drive, however, there's no guarantee X drive will work properly with the USB controller on your motherboard. 3.) Replace the USB controller on your mobo. However, there's no guarantee the next one will be any better and it's often times just cheaper to replace the mobo. Which isn't, of course, a cheap option to begin with. If you're going to go that route, you're better off buying an entirely new PC. Again, though, there's no guarantee a different PC's mobo won't have the same issue.
  12. Most likely, if ImgBurn said Disc Not Empty, either your DVD-R actually isn't empty or your DVD "burner" is actually only a read only model. Or could be a firmware conflict with the drive and the type of DVD-R you inserted. I'd first start off with providing some information. When ImgBurn first starts, copy and paste everything in the Log window that appears on start into a reply here. I'll proceed from there. I don't understand what you meant when you said "when I use format with imgburn it doesnt show DVD-R option." You can't format DVD-R except as a giant floppy option in File Explorer. And format would only show up as an option in ImgBurn if you used DVD-RW or DVD+RW.
  13. dbminter

    VERBAT-IM BD-R

    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.
  14. 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.
  15. 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.
  16. 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.
  17. 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.
  18. 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.
  19. 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.
  20. 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.
  21. 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.
  22. 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.
  23. 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.
  24. 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.
  25. I read a similar article about 24H2. It indicated any CPU made within like the last 10 years supports that instruction set.
×
×
  • Create New...

Important Information

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