dbminter

You may want to try more than 1 burn and make sure you get consistent results. It seems you got 1 good burn on the Traxdata and then none. So, maybe you just got 1 good Verbatim burn, but may not get other good burns. It's worth doing the test a few times to make sure you get good results each time.

Yeah, go ahead and see if that helps. Plus, you can always image the discs with Windows recovery files on them first. Then, you could burn the contents back after testing to "restore" them. Going back over your log again, it seems you did get a good burn on that Traxdata disc. So, I'm wondering if you just had a fluke and got a good burn that one time. A few tests to Verbatim should bear more info from their results.

This is probably your problem: I 22:51:15 Media Type: DVD+RW (Disc ID: RICOHJPN-W21-01) Since this seems to be the first write operation you've performed to this DVD+RW after formatting it, you've no experience with these media before? What's most likely the problem is your LG, and I think it's an LG burner, doesn't like those particular brand of Ricoh/Ritek DVD+RW. My LG had no problem with writing to 8x Ritek DVD+RW (It would Verify some discs that were obviously corrupt enough they wouldn't play properly, but that's another story.) but I don't know about your drive/media combination. Where I'd go from here is try some Verbatim DataLife Plus DVD+RW. I doubt Traxdata is of very high quality, as Ritek/Ricoh is a 2nd tier optical disc manufacturer. Don't get Life Series Verbatim. DataLife Plus Verbatim media can only be found online. I only use my Ritek DVD+RW because they're the only ones who made 8x DVD+RW, and now no one does.

I don't know, but I'd have to say no. In fact, you could probably only eject the drive using the pin hole eject. ImgBurn locks drives for exclusive access so nothing else can interfere with an operation. Thus, an eject command shouldn't work at all.

Maybe BIN/CUE can only be written to CD-R/RW. I know the Create CUE File function can only burn to those media. Doesn't even write to an image file. I don't use BIN/CUE as I have ImgBurn set to create .CCD files, which saves the BIN as a .IMG file. Standalone CD/DVD players generally check the type of media you've inserted to determine what to play. So, it won't play audio CD, generally, unless you insert a CD media. Thus, you'll want a CD-R/RW for this instance. Of course, the player has to support those functions/media and play nice with the media manufacturer you've burned to.

I would have thought ImgBurn would let you burn the CD-Audio image to a writable DVD, but warn you you're underburning, e.g. using the wrong media. I would have thought it should still would have allowed you to do it. I believe I tried writing a CD-Audio image to a BD-RE once because it was faster and I just needed to test playing it in Windows, not on a CD player. And that wouldn't work. Oh, wait, maybe that was .CUE files created from containers that wouldn't burn to BD-RE. Anyway, yeah, if you want a CD that plays in an audio CD player, you'll need CD-R/RW. And your CD player has to support CD-R and RW and support the particular brand you're using.

By "advice," I guessed he meant he followed a Guide. Now, you did use Read mode to create that BIN file, right? I mean, you have an audio CD you're trying to copy? In other words, just asking on the incredibly off chance you had a data CD that just happened to have the files format of an audio CD you read to an image file set in ImgBurn on the disc itself that you copied over. Most likely not. It seems you, most likely, read an audio CD using ImgBurn's Read function.

Yes, with Pioneer firmware, what you describe is not unprecedented. Two discs with the same Disc ID should be the same, but apparently aren't. Years ago, Verbatim DVD+R DL did the same thing on Pioneer burners. Verbatim's branded and inkjet printable DVD+R DL had the SAME DID, but the inkjet printable discs would ALWAYS fail Verify! The branded ones would always burn correctly. Pioneer eventually fixed this in a future firmware revision. So, it may be worth a support e-mail to Pioneer to let them know this. I let them know about their borking 1.33 to 1.34 for Ritek 8x DVD+RW and they apparently fixed it in 1.50. I also recently wrote them about their BD Drive Utility. If you have more than 1 kind (Multiple copies of the same drive don't do this.) of Pioneer BD drive installed on the system, the utility only recognizes the first connected Pioneer device as being available for configuration. They said this was normal behavior but that they'd forward it to the developers to see if they could do something about it. So, who knows if they actually will but, you never know.

I believe in witches, just not what they believe. There are such things as witches, in that there are women who practice magic. But, it doesn't mean what they believe is a fact. Same problem with gods. Gods exist because people have created them as a concept. Doesn't mean they're real, though, which they aren't.

You know? The sad fact of the matter is that some things just don't make sense. There's obviously a cause, but you'll be damned if you can find it. And the way I see it, as long as you get a working solution, go with it.

Those Primeon's you're burning appear to be Ritek. Ritek makes an OK single layer media for DVD, but don't use anything they make for DL DVD. So, I doubt their BD-R DL is going to be much better. Even if you had an improperly decrypted Blu-Ray movie you were attempting to burn, that wouldn't prevent the drive from starting writing to it. You'd get a burn that if it completed, it wouldn't play properly, most likely. Problems with writes that don't start or fail to complete are hardware related, generally. Either your drive needs replacing, it has a conflict with the media you're trying to burn to, or, in rare cases, some kind of software conflict is preventing the writing to media. However, it's not unusual for firmware updates to bork writing to particular media. There was the 1.33 to 1.34 bork I mentioned fixed by 1.50. I'd try Verbatim BD-R DL media and see if that works. If it does, then you know the issue is with Primeon discs. If Verbatim also fails, you have to consider the drive being the problem. If it's the drive, it may need replacing, there may be a bork in the latest firmware, or a software conflict going on.

Are there different read speeds for WORM media vs. their rewritable counterparts? I guess it's down to the rated read rate for a particular media dependent on the drive manufacturer. But, let's say, a drive is rated for 16x DVD-R/ROM read speed. Does this mean a read speed for a 4x DVD-RW will also be 16x? Probably not, but I don't know, hence why I'm asking. Thanks!

In fact, you won't find any good media in a store. Verbatim DataLife Plus media can only be found online. Even the Verbatim you find in stores is the Life series, which is junk.

Glad it worked!

It seems he was burning a CUE file that resulted in an about 700 MB image. But, as Ch3vr0n said, WAV isn't an image file. ImgBurn creates image files from WAV files, though, when creating CUE files. As for what's going on, I'd first suggest trying something other than Sony brand. I've found most Sony products since 2002 to be mostly junk. Since you've tried multiple drives on different PC's but used the same media each time, probably, I'd try using something like Verbatim DataLife Plus CD-R (NOT the Life series.) first to see if that does the trick. As for the cause, it's either a drive that isn't working right or, most likely in this case, an issue where the drive doesn't like Sony's CD-R's. I admit I've never heard of a Reason: Track Following Error before, so I don't know what it means.

By it's down to what the drive does means what it says on the tin. A disc can have a write descriptor of 16x but only write to 8x depending on the drive. The drive also has to have in its firmware the write strategy to support that maximum speed. If it doesn't, it will only write at the maximum speed the firmware dictates. Plus, many BD-R are rated at 6x but a lot of drives will write at 12x or even 16x for them. The drive basically does what it's told and does its best to interpret the instructions it's given. The drive sometimes doesn't always do what it's told. And you'll get random misbehavior, too. A disc may be rated 16x, ImgBurn says it will write at 16x, but the drive only writes at 8x for whatever reason. Some drives even have in their instruction set to do this. LG's, for instance, will write 6x BD-R Verbatim media at 12x, but if there's drive read threshold encountered, many times when the LG resumes writing, it's capped at 6x. The LG I got rid of was doing this. 16x DVD-R were said by ImgBurn to write at 16x, but were only writing at 8x.

As for the 2nd thing you're talking about, I don't know. As for the volume label, you can set that manually before you press the create/burn button. Then you won't be prompted to do so. You might be able to turn off these checks with these options in the Settings. I don't know, but you can always try. Tools --> Settings --> Build --> Page 3 tab --> Prompts --> Check the two boxes that say Don't.

Ah, now I see why you were trying to load an audio CD image in a game emulator. That's why I was thinking it was failing in RetroArch. Because it probably doesn't support audio CD images. Whoever made RetroArch probably didn't code in support for audio CD images, thinking there would never be a reason for them in the software. They were probably not aware of something like Monster Hunter being able to do that. Even though the old PS ROM supported playing audio CD's, it probably wasn't supported for playing back in RetroArch because Windows can natively play CD's on its own. So, the function was considered redundant. I admit, a lot of the time, I just thought this was human error. That you were trying to load audio CD's in a game emulator. But, there was actually a reason why you wanted to do that.

I could whip up a single track, really small audio CD with ImgBurn, but I'd have to burn it to a CD-RW and image that, since none of the virtual CD writers I tested ever worked. Which means my image files will be in CCD/IMG format, the only way I can test them with VirtualClone Drive. Which means you'd have to install VirtualClone Drive. And if you're going to do that, you might as well, before I do anything, read this disc to a new CCD/IMG format and test it in VCD yourself. To enable CCD/IMG creation, go into Tools --> Settings --> Read and check the CCD box under Image Layout File Format.

ImgBurn is fine for most disc reading, but certain instances and combinations of certain drives and discs aren't the best. For instance, some PS1 games can't be read in on certain hardware because they apparently have gaps in the audio tracks. Mega Man 8 is one of them that won't read in my Pioneer in ImgBurn but will in Alcohol 120%. I use Alcohol 120% for those cases where ImgBurn won't read a PS1 game disc. Other than that, I've never had a problem with other disc image formats. You sure it's an audio CD and maybe not a mixed mode CD, combining an audio track with a data track? Generally, those aren't a problem, but if it's a game disc instead, that might be a problem. You're doing it right, but there could be a wide variety of issues at play here. Your drive may be the issue. The disc may not be authored correctly or is some weird form of disc. Just to be sure you didn't get a bad read, try reading it again to a new set of BIN/CUE and attempt to mount again. Since I'm only familiar with VirtualClone Drive and Alcohol 120% as virtual drives, I couldn't say why WinCDEmu doesn't like that image set. You can't use BIN/CUE with VirtualClone Drive (Well, VCD will mount BIN files, but they don't play as audio CD's in VLC. I tested that out.) so you'd have to enable CCD creation in ImgBurn and read to a new image file set to mount it in VCD. I believe Alcohol 120% creates its own image file format, but it may support BIN/CUE already existent.

Never heard of WinCDEmu, so I couldn't say. As far as I know, ISO isn't for audio CD's or any CD format. As for why it may be a corrupt image, well, the image is corrupt or it isn't recognized as a compatible image for WinCDEmu. And that could either be a bad read or simply a bad disc. Maybe it wasn't authored correctly. Could be a lot of factors and my having no familiarity with WinCDEmu, I can't say.

Ah, that's what I did! I set ImgBurn to create.CCD files because VirtualClone Drive didn't appear to support .CUE files when I tried it out. But, it did mount .CCD (CloneCD) files because I think the same software company that makes VirutalClone Drive makes CloneCD. Which may explain why my CUE file didn't play in VLC. VLC may very well support BIN/CUE, but I only had IMG/CUE. I turned off CCD creation so I'd get a BIN/CUE image file set of the same disc to test again. VLC simply does not support playing CUE files.

Well, I've no idea why VLC associates CUE with itself because it does not support playing audio CD's from CUE/IMG file sets. I tried it just now. VLC does not natively support playing CUE/IMG files. I made an image file on a CD that VLC will play from (I tested it.) and VLC did not play the CUE file ImgBurn created. I tested a 2nd image file I made years ago for testing purposes and the CUE does not play. Now, it may work with BIN/CUE but without being able to create BIN/CUE to test, I can't say. I mounted the CCD file ImgBurn created with the IMG/CUE in VirtualClone Drive and VLC will play a CCD mounted IMG/CCD/CDT/CUE file set created by ImgBurn. What I don't understand is why ImgBurn is creating a BIN/CUE set when, for me, it created a CUE/IMG set of a CD.

As far as I know, no software player will natively read in BIN/CUE of audio CD's and play them. Now, if you mounted the image with, say, VirtualClone Drive, VLC, if it supports playing audio CD's (I don't know.), would play the image file as a virtual drive, if the image file isn't corrupt.

There are two ways to do that. First, use ImgBurn to burn the CUE file's BIN file to a CD-R or CD-RW and see if that disc plays. The second is to installing an optical disc emulator software like VirtualClone Drive or Alchol 120%. Both are either freeware or have a free version. You can then mount the CUE/CCD file, depending on the software you choose, and see if the mounted image plays.