dbminter

If you're going to use the OWC enclosure with a WH16NS60, be aware there's a big drawback. If you power off the enclosure, Windows will not recognize the drive is connected again until you restart Windows. The OWC doesn't do this with Pioneer drives, but it does with the NS60. VanTec enclosures don't do this with the NS60, either. It's a peculiar bug in the OWC enclosure. I haven't used anything other than a Blu-Ray burner for like a decade, so I can't comment on DVD only burners.

Are you saying you have optical drives that are recognized by ImgBurn but are not recognized by it when you connect an external HDD? If you're not, then, it's as was said. ImgBurn does not image USB HDD's.

It's possible to get a VanTec enclosure that only partially works. My first VanTec made me thing the entire line was junk. While it initially appeared to work, eventually, it started dropping communication with the drive. I gave a 2nd VanTec a try and that's when I started to suspect inferior Chinese quality control because that unit worked fine. Then, I had another one where it would randomly not detect anything when a disc was inserted until the power was cycled. I would get an LG WH16NS60 if you're really looking for a BD drive. It's the best of the worst. The lesser of several evils. Pioneer is pretty much junk now. Hasn't properly written to DVD+RW for over 5 years. ASUS is also junk. Doesn't properly write DVD+R DL.

First, if you haven't, try power cycling the enclosure and then restart the PC. The second thing you could try is changing the Interface in ImgBurn. If SPTI was working before, this probably won't help, but it's worth a try. Tools --> Settings --> I/O --> Interface. Try all the other options and see if it helps. I'd have to say if ImgBurn worked before and you were able to read/burn many discs before, it would seem the drive needs replacing. However, you're also using one of those VanTec enclosures. They're 50/50 when it comes to quality control. You could have gotten one of those 50% clunkers. The only reason I use one is because the LG WH16NS60 only properly works in the VanTec. (And even then on the Version 2 one, you can't update the firmware of one in it.) You could try getting an Other World Computing enclosure and see if that helps. I'd say it probably wouldn't make a difference in this case, though.

It would be an interesting milestone for me. It would mark 10 years since I last spoke with a close friend of mine. He installed 2.5.8.0 after it came out, but did not heed my advice to not get click happy because of the PUP's at the time from other sites injecting installers into it. And he didn't regularly backup his system, so, ignoring all this, he installed something that replaced his bookmarks in his web browser with some collection of crap. He collected his entire porn library in his bookmarks rather than downloading it locally, so he "lost" "everything." He stopped talking to me after that simply because, I think, I was the one who told him about the new release. I think he blamed me even though I told him not to get click happy and told him many times he needed to backup his system. He completely disappeared after that and given his past of suicide attempts, I wouldn't be surprised if he did kill himself over something so petty as this.

Um, you're going to have be a bit more specific. "It doesn't work" doesn't give us any information to go on. What does that mean? Does the application not even start? What exactly isn't working? And why on Earth did you link an article about washing machines?! It doesn't appear to be selling anything, so it's not spam. It just seems incongruous.

Tried a 2212 with the new 1.02 firmware; STILL borked after 5 years plus! STILL can't properly write to DVD+RW without failing Verify. I noticed that Pioneer's web site displays some older models they apparently don't make anymore. On their products page, they list the 2212 and a USB half height model, but if you click on the links to buy them from the Pioneer store, the only model they offer on their web store is a USB slim. So, I doubt the BDR-213 will ever make it to North America.

It could be the CMC Mag discs. They're cheaper media, although that wouldn't generally explain away the failure on the same file on 2 different burns. Although the offsets are different, so it could just be coincidence that they happen to fail on the same file.

A simple conclusion of logic: if development has ceased, why were at least 2, possibly 3, I forget, betas released last year?

I've been half tempted to post screen shots of the latest beta log window showing the version and the About screen just to put an end to this.

I don't believe that's a user accessible variable. So, it's probably hard coded into the software at a 1 GB cap.

Although, I'm not finding any external models with that number. They're internal slim models. Is this external drive a slim one? It seems maybe someone put it in an enclosure because I don't think it originally was an external.

Every thing I find online about the UJDA750 is that it's a DVD-ROM and CD-RW drive. Meaning, it writes CD's but only reads DVD's. For example: https://www.aliexpress.com/i/2251832338157315.html?gatewayAdapt=4itemAdapt https://www.laptopspecialist.com.my/index.php?main_page=product_info&cPath=142_4579&products_id=2865 Notice in the specs of that 2nd link where it says "DVD-R (Read only), DVD-RAM (Read only)"

What are your trying to do? Read a disc to an image file? Burn an image file to a disc? A few other questions and suggestions. Have you tried different kinds of media to insert and always get Medium not present on everything? Is it a CD, DVD, or BD burner? Internal or external? If external, try powering off the device, restarting the PC fully, and powering the device back on. If it's internal, try shutting down Windows, powering off the PC, power it back on, and restart the PC. Has the Medium not present error just started showing up? Or is this the first time you've tried using this device?

Are the number of events cut off in the actual log itself? Under Help, open the Log and see if the log itself actually writes all the events.

Yes, it looks like you were responding at the same time I was typing. So, you probably found the solution just immediately before I was suggesting it.

The only 2 differences in my setup: under UDF, I have Disable Unicode Support checked. Try changing that and see if it works. And try changing the UDF Revision from 1.02 to 2.60. If that still fails, try loading the attached ImgBurn job Project IBB file. It's my defaults that are loaded on every time ImgBurn starts. Download the attached file, load it as an ImgBurn Project, add the stuff you want to add to it, and see if you have better luck. Set Default Options.ibb

Well, if it's a console game disc and if you downloaded it, that probably explains a lot. Most of those images found online are corrupt in some manner or another because whoever made the original image didn't know precisely how to process the source disc. Making images of console game discs always was a bit of a pain.

Except for the corrections made on the fly at burning, it looks okay. Those are unavoidable as those are errors present in the original image file. However, depending on what was corrected, I can't say how it will affect the final output. What is this image? CD Audio? Software installation disc? Console game disc? One thing you could try is installing some kind of virtual drive software like Virtual CloneDrive, mount this image as a virtual drive, use ImgBurn to create a new image from the mounted virtual drive image, and see if burning that new image to a disc causes any kinds of errors.

I believe you also have to take into consideration that the "file name" character limitation includes the number of characters in the path the file resides in. Not entirely sure about that. How many characters are in the folder path preceding the file name? Also, I saw you mentioned ASCII; did you try Standard character set? And Allow more than 255 characters in path under the ISO9660 settings?

I don't know why UDF wouldn't work as it has a maximum file name length of 256 characters as far as I know. Then again, it's been so long since I used Windows 7. Given its age, it may not support UDF 256 character file systems. Though I would think it would.

I do notice you're using CMC Magentics discs, so those are probably the cheap Verbatim discs. Do you have a log for a Taiyo Yuden burn? If they're CMC as well, that might explain the repeated failures even across multiple PC's and burners. You can rule out the hardware, probably, because you've tried multiple different combinations of those. The software can most likely be ruled out because many others use it just fine. So, what would be unique regardless of what you've tried? Either the images themselves are corrupt, since those could be used across multiple device combinations, or the discs you're using could be causing the problem if they're all CMC, which is the worst media out there. I also notice there is apparently something wrong with this image file in particular, it seems, as some error correcting was done on it. It does appear the drive corrected the errors present in the image file. I don't know about your second question, though.

Could be corrupt images. Did you download them off the Internet? If so, there's a higher likelihood the images themselves are corrupt.

Try changing the file system from ISO9660+UDF to just UDF and use the latest listed version. But, I don't know if Windows 7 supports reading from that.

It has been like a decade since I last tried to create a bootable image in ImgBurn. Plus, if the guide were CORRECT, I'd probably have had better luck...