dbminter

I've got an idea, but I need to see the Log entry first for the burn in question.

Life happens. Yeah, the Initializing, Writing LeadIn, and Finalizing steps are somewhat random in terms of how long they can take from burn to burn. Sometimes they're quick, sometimes not so much. Just let them run, as you did.

Good! Glad it worked. That it was the drive in question and not the disc. I had figured it was, most likely, a drive issue, as opposed to the disc not being readable.

Depends on what you mean by "pull the file without corruption." Are you getting any kind of errors from ImgBurn? If so, what are they? And is this on the ASUS you said you had to try?

It's hard to say for certain. Could be a fault in the hardware or it could simply be the laser in the unit isn't very good to begin with. Since it can read some CD-RW but not most of the others you tested, that's more odds on average a fault in the device. However, you wouldn't be able to tell unless you got another one of these units and tested it. Otherwise, it would be down to the laser used in the device. It's having a reflectivity issue reading those CD-RW's. Which would mean if you wanted to use those particular CD-RW's, you'd have to try a different model of drive.

For anyone else looking for a similar solution, there's a Guide that explains this fairly well:

I did a little digging into your MATSHITA drive. It's a slim model drive, but it doesn't appear to be external. Did you put this drive in an external enclosure yourself? It could be just that someone put that model into an enclosure for you and sold it that way.

You're best off getting a different make and model USB drive. That way you have a better shot and of determining if the disc itself might have gone bad. Also, as I said, if you're not certain your drive is USB 3.0, although as a BD, it should be, you may want to check that it's connected to a USB 3.x port and make sure.

As I said, try a different drive. Since it's USB, you can always swap it out for another.

From those other screenshots, it's not an issue with G: so forget about that. If you're curious, it wouldn't be your Google drive but a physical drive connected to your system. If you wanted to fix it, it's not exactly a newbie issue. It requires reformatting G: for NTFS which would delete everything off of G. So, you'd have to copy all of G: contents to some sort of backup, format G: as NTFS, and then copy all of the G: contents backup back to the newly formatted G:. However, as I said, that's just FYI as it doesn't matter here. I've never seen a Track Following Error before, but it's indicative that your drive could not read the disc you put in into it. You'd either need to try a different drive or maybe the disc is damaged and cannot be read. Now, I did notice D:, your Blu-Ray drive, is listed as connecting at USB 2.0 speed. BD drives need USB 3.0 speed to properly work. However, you may actually have the BD drive connected by USB 3.0. There's a cosmetic bug in ImgBurn's last gold release related to its age where USB 3.0 speeds will display as being connected at USB 2.0 speeds.

Gonna need more than that. What exactly is "can't get the disk to load properly? entailing? ImgBurn does not recognize the disc is inserted? You can rip the game to an image file but the Steam deck won't play it? If it's that 2nd one, it's probably because you're forced to use file splitting. G: is formatted as FAT32, so it won't create single file ISO's, but split files at the 4 GB mark since the largest file size for FAT32 is 4 GB.

Well, there was a beta release about 3 years ago. So, the software is still "actively developed."

Whenever I have a source file trying to create a CUE that ImgBurn throws back an error on, the first thing I do is convert it to an uncompressed WAV file and try again with that WAV file. Do a web search for audio converter applications and see what looks best to you. I use freac Free Audio Converter, but I've also used something just called Free Audio Converter in the past.

I don't understand the question about VIDEO_TS at the end. It would only case playback problems on DVD players if you DIDN'T have a VIDEO_TS folder in the root directory of the disc you're attempting to play. However, if you're asking if you need to create an ISO first for VIDEO_TS contents to get to play on a DVD player and if you can just Write contents directly to a recordable DVD in ImgBurn, I can't see why that wouldn't work. But, if you don't want to waste a WORM disc testing that, you can attempt a test burn to a rewritable DVD disc first and test that on the player. It would have to be a DVD-5 to test, though, unless you compressed the DVD-9 first.

I had said it could possibly be a false positive for "data." I tried reading a data label side in my setup, but all I got was an expected unable to read anything return message.