dbminter

Well, it's not the USB cable. I connected a new cable, but it was the 2nd enclosure and a LG drive that were the problem of the drive not showing up. Whenever the drive is powered off, it doesn't show up again in Windows until the PC is restarted (Logging off Windows doesn't work.) or the USB cable is removed and reinserted at either end. It seems to be something with this 2nd enclosure or the LG drive and a recent BIOS update that cause this. Because, before, this drive always was detected without issue when powered off and on each time before September 1st, when this BIOS update was installed. So, this means the issue has to be 1.) the other enclosure 2.) the Pioneer 2209 in the enclosure 3.) something with the September 1st BIOS update or 4.) something in Windows causing the device to drop communication. It's not #2 because I tried swapping in different 2209's in the first enclosure and it still wouldn't write correctly. It has to be either the first option or the 3rd. I say it's the enclosure. I was getting the 0.0x problem on a different Dell PC with this enclosure and the 2209.

Hm, well, it's always possible you just happened to get a bunch of decent burns out of junk media before the real junk hit you. It's highly unlikely, though. Especially given if it also happens on Sony media, too. However, you really shouldn't be using the CMC media, anyway. Just because cheap media burns and plays doesn't mean it should be used. It will have a higher tendency to be unreadable before the quality media does. Now, if you're getting another ISO with no errors, it's probably a corrupt ISO file that was causing the problem.

It appears to be exactly what I thought. Notice this line of the log: I 15:09:58 Destination Media Type: DVD-R (Disc ID: CMC MAG. AM3) (Speeds: 3x, 4x, 6x, 8x) CMC MAG tells me you're using Verbatim's Life Series of DVD-R, which are junk. I am guessing you have never tried these discs before? Or have you used them before and suddenly you're getting failures? Either way, it can be the case where you get some good burns and then all of a sudden you get bad ones with CMC Magnetics media. As I said, try Verbatim DataLife Plus DVD-R, which you will only find online. Although you said you tried Sony before, too, and it failed? With the same error message? Sony isn't the best quality media, either, so that could be a problem, too. Anyway, my first step in troubleshooting an issue like this would be to try known high quality media first. If you still get an error message with 3 different media types, and you're getting the same error message, then something else is up.

Help us help you. Post the log of the failed burn. Under Help choose ImgBurn logs and copy and paste the appropriate section (The entire log of the whole burn.) with the failed burn. My initial guess? You're using Verbatim Life Series DVD-R, which is junk, and not the DataLife Plus Series, which is the only quality media they make. The log will tell me that.

Wait, could this issue be caused by a bad USB 3.0 cable? I put in the other enclosure, but upon connecting and powering on, ImgBurn nor Windows recognized the device as connected. So, I tried a different USB cable on a different port and the drive was recognized. So, I put this new cable in the port where the old cable was, and Windows recognized the device. This leads me to believe the issue was a bad USB cable. Could a bad USB cable cause a semaphore timeout issue like this?

Yes, I'm not sure if it's the enclosure, the drive, the media, or some combination of them. Given this has happened on my oldest and newer 2209's, I'm more inclined to believe it's the enclosure. Yeah, it's most likely the enclosure. I just put in my newest 2209 and on the first attempt to burn another BD-R, it dropped to 0.0x. It's either that or these BD-R's, which I'm highly less inclined to believe. Does the attached screen shot of a failed burn help? It's taken right after the drive drops communication and writes plummet to 0.0x. I notice this time it says something about a semaphore timeout issue. So, that indicates to me it's the enclosure dropping communication, but I don't know.

What exactly does the Reason: Not Ready To Ready Change - Medium May Have Changed mean? I ask because in this one enclosure I've put a Pioneer 2209 in, I get some really bad results. The drive seems to drop communication. Write rates will drop to 0.0x and never resume. This time, I actually got an error message in an aborted write. I 17:38:00 Operation Started! I 17:38:00 Image Contents: 185 Files, 15 Folders I 17:38:00 Image Sectors: 7,809,504 (MODE1/2048) I 17:38:00 Image Size: 15,993,864,192 bytes I 17:38:00 Image Volume Set Identifier: 4D278CBD007728D3 I 17:38:00 Image Application Identifier: ImgBurn v2.5.9.0 I 17:38:00 Image Implementation Identifier: ImgBurn I 17:38:00 Image File System(s): UDF (2.60) I 17:38:00 Destination Free Space: 82,462,683,136 Bytes (80,529,964.00 KiB) (78,642.54 MiB) (76.80 GiB) I 17:38:00 Destination File System: NTFS I 17:38:00 File Splitting: 4 GiB I 17:38:01 Writing Image... I 17:41:56 Operation Successfully Completed! - Duration: 00:03:55 I 17:41:56 Average Write Rate: 66,463 KiB/s (15.1x) - Maximum Write Rate: 178,957 KiB/s (40.8x) I 17:42:31 Operation Started! I 17:42:31 Source File Sectors: 7,809,504 (MODE1/2048) I 17:42:31 Source File Size: 15,993,864,192 bytes I 17:42:31 Source File Volume Set Identifier: 4D278CBD007728D3 I 17:42:31 Source File Application Identifier: ImgBurn v2.5.9.0 I 17:42:31 Source File Implementation Identifier: ImgBurn I 17:42:31 Source File File System(s): UDF (2.60) I 17:42:31 Destination Device: [0:0:0] PIONEER BD-RW BDR-209M 1.51 (R:) (USB 3.0) I 17:42:31 Destination Media Type: BD-R (HTL) (Disc ID: VERBAT-IMe-000) I 17:42:31 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8x, 10x, 12x, 16x I 17:42:32 Destination Media Sectors: 12,219,392 I 17:42:32 Write Mode: BD I 17:42:32 Write Type: DAO I 17:42:32 Write Speed: MAX I 17:42:32 Hardware Defect Management Active: No I 17:42:32 BD-R Verify Not Required: Yes I 17:42:32 Link Size: Auto I 17:42:32 Lock Volume: Yes I 17:42:32 Test Mode: No I 17:42:32 OPC: No I 17:42:32 BURN-Proof: Enabled I 17:42:32 Write Speed Successfully Set! - Effective: 71,920 KB/s (16x) I 17:42:32 Advanced Settings... I 17:42:32 BD Optimum Writing Speed: Not Supported I 17:42:32 BD-R High Speed Recording: Not Supported I 17:42:32 Optimal Writing Speed: No I 17:42:32 Filling Buffer... (40 MiB) I 17:42:32 Writing LeadIn... I 17:42:43 Writing Session 1 of 1... (1 Track, LBA: 0 - 7809503) I 17:42:43 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 7809503) W 17:47:13 Failed to Write Sectors 4507008 - 4507039 - Reason: Not Ready To Ready Change - Medium May Have Changed W 17:47:13 Retrying (1 of 20)... W 17:47:15 Retry Failed - Reason: Invalid Address For Write W 17:47:15 Retrying (2 of 20)... W 17:47:15 Retry Failed - Reason: Invalid Address For Write W 17:47:15 Retrying (20 of 20)... W 17:47:15 Retry Failed - Reason: Invalid Address For Write E 17:47:20 Failed to Write Sectors 4507008 - 4507039 - Reason: Not Ready To Ready Change - Medium May Have Changed E 17:47:20 Next Writable Address: 4506080 / 1001:23:05 I 17:47:20 Synchronising Cache... W 17:47:23 User opted to skip the 'Close Track/Session/Disc' functions. E 17:47:23 Failed to Write Image! I 17:47:27 Exporting Graph Data... I 17:47:27 Export Successfully Completed! E 17:47:27 Operation Failed! - Duration: 00:04:51 I 17:47:27 Average Write Rate: 32,659 KiB/s (7.4x) - Maximum Write Rate: 48,416 KiB/s (11.0x) I've had this drive for 6 months, since around March. I once had to replace a 2209 within 7 months, so, could it be that the drive is dying? I wonder if it's the enclosure because I believe I had this occur on my newer 2209, too. Plus, the Medium May Have Changed message leads me to wonder if the drive dropped communication and resumed. I've wondered if this enclosure is simply dropping communication with the drive. Then again, I've had several write failures in this same 2209 in a different enclosure, but those were bombed out writes with error messages. None of this 0.0x crap. But, that could be a batch of not as quality BD-R's even though they are Verbatim. I think I'll try putting in the newer 2209 I got in May in this same enclosure and see if the process improves. In the meantime, any advice anyone can follow up on would be appreciated. Thanks!

Yes, Ritek media can be iffy. It's not as cheap as CMC, but it is a lesser tier media. It's been known to cause issues with some drives. Try Verbatim DataLife Plus DVD-R which you can only find online. NOT the Verbatim Life Series you'll find in stores. That will be CMC garbage.

Under Help, choose ImgBurn logs. Open the log and find the appropriate burn where it failed and copy and paste that part of the log. If I had to hazard a guess, you're probably using Verbatim Life Series CMC media or some other cheap discs that is causing the problem. The log will tell us that.

I wasn't sure if that still worked. Under Firefox, the Print function has no listed associated keyboard shortcut under the hamburger icon. It just says Print. I have a button to Print on my toolbar so I just use that.

I'm guessing you mean one of the guides in the Guides section of this forum? You'd use your web browser's Print function, wherever it's hidden away. It varies depending on browser and user browser configuration. Generally nowadays, Print is usually found under some kind of "hamburger" icon in the upper right of the browser window.

You can't mount multiple image files to the same virtual drive. What you'll have to do since you're limited to one virtual drive on your system with Daemon Tools is to mount each image one at a time and copy each drive's contents from each image file one after the other into 6 separate temporary folders. Alternatively, you could somehow convert the MDF files to ISO and install Virtual CloneDrive. It's free software and lets you create multiple virtual drives. It also mounts ISO files. That might work, but the conversion from MDF to ISO might not work right. I don't know. Another idea that might work. Virtual CloneDrive lets you mount what are called .DVD files. ImgBurn has a Tool option to Create DVD file. I don't know if .DVD files support .MDF image files or not, but instead of trying to convert from MDF to ISO first, it would be easier, if it works, to create a .DVD file and mount those in 6 separate Virtual CloneDrive drives. I don't know if there's a limit to how many drives you can have beyond the maximum 26 that would be allowed. And that number would be reduced by how many drives you have that show up in Windows/File Explorer.

Verbatim makes a DataLife Plus series of CD's, too, in addition to DVD and BD. I don't know if they use AZO on the CD like they do with DVD. And I don't know of their availability outside of the United States, where I get mine.

Look online for CD's called Verbatim DataLife Plus. They're probably the best out there now that Taiyo Yuden doesn't make media anymore. However, I had difficulty finding them on Amazon.com last time I looked and could only find them on Verbatim's web store. Don't get the Life Series from Verbatim; they're junk.

Let me guess. You put this CD in a stand alone physical CD player that displays track names and it isn't displaying them correctly? If so, that's a common issue seen here. It's generally down to the player not physically being compatible with reading CD Text from a CD-R. Have you tried playing this CD in some PC software player and see if you get CD Text information?

Depends on how you're burning the CD. If you just use Read mode to read in a CD and then Write mode to burn the image of the disc you just read, you can't add track names as far as I know. The only way I know is to Create a CUE file and burn your own CD from MP3/etc. tracks. That way you can add the metadata, either imported from the track files or you can manually add it.

Can't say why you'd end up in an infinite loop installing Alcohol. I haven't installed it like 10 years, so I don't know how well the software still works. And I was using a licensed version, so I've never tried installing the free version to see if it works. Back then, there wasn't a free version. I can't think of anything it might install that you'd need to reboot for, anyway. There's nothing like Daemon Tool's SPTD that hooks into the system, as far as I know.

Try Alcohol 120% Free version. I don't know if it supports mounting MDS or not, but it's worth a try. And I think it's free version will let you mount images, but I've never tried it. In fact, I haven't used Alcohol in like a decade. I know Virtual CloneDrive, which I use, doesn't mount MDS files. You could try creating a new .DVD or .MDS file under ImgBurn's Tools and point the new file to the .MDF file. .DVD, I believe, is supported by Virtual CloneDrive. Although a new .MDS file probably doesn't matter in this case.

Also, is the ISO the same file name, just different extension, as the MDF/MDS files? I wonder if, what happened, is you saved one of your Build jobs, either on purpose or by accident, to the same folder as the 6th CD image file set. I still think the 6th CD image file is corrupt, too. Mounting it as a virtual drive would help prove if it is or not.

I would make sure that 6th CD that isn't installing actually works to begin with. Burn the 6th CD image to a disc and try running Setup from that burned disc. I would think that the 6th CD image you downloaded might be corrupted and can't be used to run the setup from. But, I don't know that for sure. Are you getting that single track image error when trying to burn the 6th disc image? If that's the case, then you can't burn it with ImgBurn probably as it seems multi-track image files aren't supported for burning by ImgBurn. Wait, are you saying there are 2 different disc image files for the 6th CD? An ISO and an MDF? Given the file sizes you mention, they would, to me, not appear to be the same contents. I don't know if converting an MDF to an ISO would result in such a smaller file size. Try burning ISO on its own by loading the ISO in write. If that can't burn, try opening the MDS in Write mode. If that doesn't burn correctly, try opening the MDF and writing it.

Build mode doesn't burn anything to disc. It creates ISO image files that you use the Write mode to burn the ISO files to disc. There is a Write files/folders to disc option that is similar to Build that does burn contents to discs. It uses the same interface as Build mode.

Actually, there may be a simpler way, now that I think about it. Since you don't apparently need the actual install CD's and just the PDF files in the Testi folder, what I would do is this. Burn each MDS/MDF disc image set to a rewritable CD or DVD. Either one at a time and reuse rewritable discs or burn all 6 to 6 discs. Then, from each disc you burn, open the Testi folder and copy all the PDF's to a temporary folder. Add that temporary folder to a Build job and burn to a CD or DVD. This way, you'll have all the PDF files for reading without having to install the Adobe Reader to read them. Plus, you can use your Sumatra PDF reader as you normally would.

The MDS and MDF files you already burned to DVD are only good for burning as image files to disc or loading as virtual drives in a virtual drive program. That's how you'd access the contents on each CD. You could copy them from the DVD to a hard drive or just load them from the DVD, but you'd need 2 burner drives for that second option, one to read and one to write. Did you already burn 6 discs with the MDS/MDF files? If not, you'd need to burn them, preferably to rewritable discs, temporarily so you can copy the contents of each disc, e.g. that long list of files and folders that had the SETUP file in it, from each disc. These 6 individual discs are what you'd need to copy to 6 temporary folders in another temporary folder. And it would be these 6 temporary folders in a temporary folder itself that you would add to a Build job and burn to ISO and then to DVD. You will only ever be asked to erase a disc if it is rewritable. You'll never be asked to erase a CD-R, DVD-/+R, DVD-/+R DL, BD-R, BD-R DL, BD-R TL, or BD-R QL. Build mode is not batched. It will only queue image files to burn in a batch it creates. And, thus, you'd have to create more than 1 before burning one to queue. Unfortunately, I can't make it much clearer than what I've already done because, and I don't mean to sound condescending, but there are certain basics in navigating PC use that just can't be taught in a forum like this.

What you apparently did was simply copy all 6 CD image files to the ISO. While this isn't a total failure, all you can do with that disc is load each CD image file from the DVD in ImgBurn and burn them to CD's. Or mount them in virtual CD drives from the DVD. What you need to do is burn the CD image files to disc or mount them as virtual drives and copy the contents from the CDs, not the CD image files, to 6 temporary folders. You were probably asked for a 2nd DVD because you burned the job twice, putting the burned ISO file into ImgBurn's queue for burning. MDS is just a pointer to another file. So, in your destination folder, the MDS was actually pointing to the ISO file that ImgBurn created. For instance, with your original 6 CD image files, the MDS files point to the MDF file, which is actually the CD image file. MDS just tells ImgBurn how to burn the MDF/ISO.

Yeah, I was wondering if, given the small file size, the resulting Synchronizing cache might take a long time because it has more to pad out. I just wasn't sure.