Jump to content

dbminter

Beta Team Members
  • Posts

    8,597
  • Joined

  • Last visited

Everything posted by dbminter

  1. Well, I won't know that until my next nearly full BD-R burn. Until I perform my next nearly full BD-R burn to see if it scratches discs, ruining them, I won't know. Usually, when that happens, a replacement drive works for a few months before it starts up all over again! I just swapped it in, have configured its proper drive letter, and am doing a read of some DVD-RAM contents, which appears to all be going along smoothly... for the moment.
  2. FINALLY got my PROPER LG WH16NS60 replacement today!
  3. Have you tried booting into Safe Mode and see if ImgBurn still misbehaves? Also, given how your WinZip installation may also have been corrupted, you could have some kind of massive Windows problem on your hands.
  4. Thanks! I wasn't sure if, somehow, choosing an IFO might place a layer break pause somewhere in the video referenced in the IFO. I didn't think it did; particularly why I always choose BUP if offered.
  5. I still say don't use the cheap CD media. If LUK hasn't replied back, most likely, there is nothing discernibly wrong with the CUE sheet. Failed to send CUE sheet errors are not necessarily generated by the CUE sheets themselves being bad. It's an error communicating with the drive, which could be media incompatibility or a hardware error of some kind.
  6. What exactly happens when you set a layer break for a DVD Video on an .IFO/BUP file? For example, if you set a layer break on an .IFO and didn't use a seamless layer break, would you still get a layer break playback pause anywhere in the video? What if you set a layer break on a BUP? Thanks!
  7. Multitracks are not supported, as the error message says, by ImgBurn. Is this disc you're trying to copy, perhaps, a DVD made by a DVD video recorder like a Panasonic model? You will get issues trying to image those, too. The only solution for ImgBurn is to use Build mode to create a new disc. Drag and drop all the contents from the root directory of the disc you're trying to copy into Build mode. When you add the VIDEO_TS folder for a DVD Video, if that's the disc you're trying to copy, ImgBurn will ask you if you want to make all the appropriate settings changes for you.
  8. Ritek has generally been mostly 2nd tier quality media. It is known to have a few compatibility issues for people on the board. Particularly the DVD+R DL, but, generally, only the Verbatim are any good to begin with. Sony DVD-R is now made by Ritek after they stopped making their own media. Ricoh/Ritek were the last manufacturer of 8x DVD+RW, but even they have stopped production. FINALLY got LG to send me that replacement NS60. Let's HOPE they get it right this time!
  9. Well, believe it or not, unfortunately, the WH16NS60 IS the best of the worst. You've got basically 4 choices: LG WH16NS60, WH16NS40, Pioneer BDR-212, and the current ASUS model. The NS40 can't properly write DL BD media. The BDR-212 can't properly format 8x Ritek DVD+RW and only Verifies Memorex BD-RE at 2x, but mostly at 1x instead! The ASUS model destroys rewritable media! I tried both Ritek 8x DVD+RW and Memorex 2x BD-RE.
  10. Yeah, don't necessarily believe in the 1,000 years thing. While they will almost certainly outlast your lifespan, I doubt they'll last a millennium. You were supposed to get hundreds of writes out of DVD rewritable media, but it's more like 25 to 50 before they die.
  11. Actually, it's not as crazy as it seems. Different disc manufacturer and different disc type further indicates your drive has a compatibility problem with Verbatim BD-R. My experience with Sony BD-RE was they're cheap, though. The one I had died before its 5th write, but that's typical of the junk Sony has almost exclusively produced since 2002.
  12. LUK is Lightning UK who replied earlier. He's the author of the software.
  13. I am guessing the option to Verify against the image file is enabled by default BUT the user must select the Verify box in the Write menu to enable Verifies to begin with. Unless you actually went in to the Settings at some point and set Verify Against Image File, then it was the default behavior all the time, even if Verify wasn't checked in the Write interface menu. I don't know much about the default settings because I never "configure" ImgBurn. I set all my desired user options and changes years ago and exported the saved settings from the Registry to a .REG file. So, when I install ImgBurn on a new PC, I just run the installer and then double click the .REG file to import the settings. LUK will have to say whether it's a default option or not.
  14. Well, that's something I admit I don't know about the default behavior of the Verify check box on the Write page. Does that mean automatic Verify against image file contents? If you go into the Verify page, there's a specific option to check if you want to Verify against the image file. LUK, does the Verify check box on the Write interface mean automatic Verify against the image file being burned? I'd say it is, but I'm not sure. In the meantime, go into Tools --> Settings --> Write --> Page 1 and make sure Verify Against Image File is checked. If it's not, enable it. If it's enabled, which may be the default, then your previous burns were automatically Verified against the file contents, so they should be fine.
  15. Oh, if it's the guy I'm thinking of, I don't think it's the same person, unless he's using a different user name. We'll know if it's him IF he keeps asking the same questions already answered to him again and again ad infinitum.
  16. There are 2 kinds of Verify in ImgBurn. One is just a read test to see if the data can be read from the disc. The other, the Verify against the image file contents, compares the data written to the disc against the data in the image file to make sure the data was correctly written to the disc. A write can complete successfully but it doesn't mean it's "right." DiscSpeed would, I'd think, just do the ImgBurn Verify first option, the read test. I forget if the Verify against image file is an option set by default or not. It's been a while since I used Kaspersky, and that was a bundled A/V engine from them that ZoneAlarm used. So, I don't know how to disable anything in Kaspersky, sorry. As LUK said, since you said you had written some compressed contents to the disc, the overhead of the OS reading from an admittedly slower optical medium device might be causing it, too. If the read speed from DVD is too slow for you, this MIGHT help. Install Virtual CloneDrive, read the DVD to an image file with ImgBurn, mount the image file to a virtual drive in CloneDrive, and copy the contents from the virtual drive to another location. You will be doing some extra reading and steps, but if the copying from DVD is too long, you might save some time doing it this way.
  17. I wouldn't think so. And I wouldn't really be worried about the metallic layer, but the organic dye layer in the disc might be affected by such chemical gas. I don't know about that aspect.
  18. Depends on what you used. If you used a standard DVD-R, I have some I first burned in 2002 that are still readable. If you used MDisc, the expected life span is like 100 years and those will have a higher life. They don't use organic dyes, which decay, like DVD-R do. I wouldn't be too worried, particularly if the discs passed a Verify against the file image contents. Slow reading is most likely not a condition of the quality of the burnt discs. If you still have the original image file you burned and didn't do a Verify against image contents, you can enable that option and use the manual Verify option to load the image file and compare contents against. If you're really concerned, you could open a Command Prompt and do a COMP of the original contents against the files on disc. However, given the slow reading in Windows you're experiencing, it would probably take more than an hour to complete.
  19. You may want to try an external burner as that would be easier to replace than an internal one. Easier to test with, too, to see if it resolves the problem.
  20. The fact that ImgBurn has no read speed caps but your copying from Windows/File Explorer would indicate it's something in Windows that is capping the copying read speed. Like I said, could be the A/V software scanning the files as they're written to the source destination. Or some kind of Windows configuration error, which, as I said, good luck in tracking those down.
  21. Definitely if you've got a 10 year old DVD burner, I'd blame that. The best performance I ever got out of a drive was over 2 years before it needed replacing. I've found most drives need replacing after 7 to 9 months of use. But, I do use mine a lot.
  22. Is the LiteOn internal or external? Was this disc an MDisc you were copying? I've rarely used those so maybe they take longer to read back. I wouldn't throw the discs away. As I said, the discs are most likely not the culprit. One thing you could do is get some kind of software installation DVD disc and try to copy the contents from it and see if it takes a long time, too. If it does, you know the problem is not the discs you burned. Do you happen to remember if the Verify you performed took an hour? If it didn't, then ImgBurn is reading that disc at a "normal" speed. So, it would be something in Windows that would be the problem. You could try to temporarily disable your A/V and see if copying gets faster. Be sure to turn it back on when you're done, of course.
  23. Hm, never seen a CD Control Error before. W 07:42:16 Failed to Write Sectors 2816 - 2847 - Reason: CD Control Error Is this BD burner internal or external? If it's external, you could try a different USB port or replacing the USB cable and see if that helps. I've also never heard of the model # of the drive you're using. It could be a cheaper model and doesn't like those Verbatim discs. You appear to be using the good Verbatim stuff, so it's not like you're using cheap discs. You could try getting a different manufacturer and model of BD burner and see if that improves your chances. Given that other software has returned failure errors, it's down to the drive, most likely. It probably has a compatibility problem with Verbatim BD-R. You could try and see if there's a firmware update for your burner. In Write mode, right click on the drive in the target on the left side and choose the update firmware check option near the bottom of the options. I would try first getting an external BD burner. A different one than the make and manufacturer you're currently using if your BD drive is already external. In the meantime, maybe LUK can better explain what a CD Control Error is. By its description, it does sound like a hardware issue going on.
  24. Taking 1 hour to read a single layer DVD-R, even if completely full, is DEFINITELY not normal behavior. On my slowest Blu-Ray burner, I can copy an entire 25 GB, about 5 times the size of a DVD-R, in like half an hour. So, what's causing this? Most likely, the disc itself is not the culprit. Your drive may simply be a slow reader. There are cases I've seen where some drives, like LG, are generally slower readers than others. But, an hour? When I first started burning DVD-R in 2002, it used to take an hour to WRITE the disc, but not to read it. Could be the SATA cable or the port the drive is connected to. Swapping ports or the cable might help. Could be some kind of Windows configuration error or some sort of other error. Good luck troubleshooting something like that. Could be your A/V software slowing things down, too. Short of replacing your drive with some other manufacturer and model, there's really not much else I can think of to try. You could try and see if you had another computer where you could try to copy the DVD-R to. If it's still an hour and it's a different DVD drive being used, then it is the disc that is most likely the problem. Oh, should have asked. Is this drive connected by USB or internal?
  25. Just because the data can be read from a burned disc, doesn't necessarily mean the data was copied 1:1 successfully to the disc. That's why if you have an image file, Verification against it is the easiest way to be sure the data was written properly to the disc. As LUK said, you could use some other software or the DOS COMP command to compare your source files against the contents written to the disc.
×
×
  • Create New...

Important Information

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