dbminter

Go to https://imgburn.com/index.php?act=download and download the installer from Mirror 7. That's the best way to get a working installer.

I do always use the same output folder and file name. This issue never arose before when I was using file splitting. It was only after I turned off file splitting to get single ISO files that it started.. Another factor that I haven't quite fully tested yet is sometimes the output folder is empty and sometimes it isn't. It appears, though I haven't determined it if is yet, when the output folder is empty, this does happen, though I don't know why that would matter.

I had wondered if that might be the cause. I do have that enabled. Should ImgBurn, though, be smart enough to know if you're generating MDS and DVD files along with the ISO based on the user options and load by itself the MDS or DVD file instead of the generated ISO?

Could be a few things going on here. Some PS1 discs simply cannot be read in by ImgBurn and certain hardware. For instance, on my rig, I cannot image Mega Man 8 from my collection with ImgBurn. Someone else posted a problem with the same disc. The solution I found was to try using Alcohol 120% to read to an image file and write that image file. I believe there is a limited free version of it. Your drive appears to be an LG one. In the past, LG drives have proven to be not as reliable readers as other drives. You could try getting a different kind of USB drive, preferably from some other manufacturer besides LG, and see if you have better luck. You probably won't, though. Your disc may simply have degradated with age. It may simply no longer be fully readable anymore. One way you can check, though it is not a foolproof method as this won't copy all of a PS1 game's contents, is to open the disc in File Explorer and attempt to copy and paste all the contents in the root directory to somewhere else. If it fails to complete, then the disc may be unreadable. Which trying a new drive would be recommended then, too.

I am starting to believe all those random crashes reports I used to send in were this issue. I had a crash just now and I'd been doing roughly the same thing. While I didn't notice the change to Chinese characters, this issue sometimes manifests itself as the ISO9660 Label field clearing itself out instead of changing the UDF Label to Chinese characters.

@LIGHTNING UK! This happened again after creating a new BD sized ISO. But, it wasn't anywhere near 100% full; it was only 79%. However, this time it said something different. I should have selected the DVD file instead.

If what LUK suggested doesn't work, try not using CMC Magentics junk discs. I 13:28:17 Media Type: BD-R (Disc ID: CMCMAG-BA5-000) CMC Magnetics makes the worst discs out there. Over 50% of the problems on this board are caused by CMC junk. Most of those are usually resolved by switching away from CMC media.

I was thinking of a Clone Disc button for real beginners. What Clone would do is read a disc to an image file, then automatically eject the disc, load the image for writing, and ask for insertion of a writable disc for burning. Thanks!

The only thing I could think of as to why an Audio CD might be saved as an ISO is it's not technically an Audio CD but a Mixed Mode CD, an Audio CD track with another track for data files. I'm not entirely sure, but that may be the case.

I'm not sure this is a bug, but given what I believe, I think it is. I was creating an image file in Build mode that was like 99% filling to a DVD-R. (Well, the Disc Layout Editor said it was 99%. Information said 100% with free space a little over 720K. So, that may be a bug in its own right.) Right at the end of the actual Build, ImgBurn tells me something I'd never seen before: "You should have selected the MDS file and not this one. I'll do it for you automatically this time, but don't do it again!" As I said, I don't know if that's a bug, but that kind of error I'd have expected on loading an image file for Writing instead of during Building an ISO. Thanks!

I don't have AnyDVD running at all when ImgBurn is open. So, I don't know if setting AnyDVD to Disabled is enough. The ImgBurn prompt does say to make sure it's disabled, but, @LIGHTNING UK! does that mean to completely exit AnyDVD or is disabling AnyDVD but it still resident enough? If it should be totally shutdown instead of disabled, maybe the AnyDVD prompt in the ImgBurn log should be changed to reflect this?

I noticed this in your log: W 13:07:30 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! Did you try shutting down AnyDVD first before attempting to read to an image file? It probably doesn't matter, but it should be tried to isolate it's not the problem. As for Windows 10 showing up as Windows 8, that's a cosmetic issue. Microsoft changed how Windows 10 identifies itself so newer versions afterwards show up as Windows 8. This will be fixed in the upcoming release, and, no, don't ask when it will be out.

Yes, that error message came as a surprise to me, too.

ImgBurn does no conversion. It just creates images/burns what you feed into it. ConvertXToDVD, last I remember, did have an unlimited 7 day free trial. So, you can test it out and give it a throw. See if it meets your needs and your level of ease of use. I find it extremely easy to use and intuitive. I think the only limitation on the free trial is the video may have a watermark on it. Still, it should give you a good indication of what you'll get even with a watermark. I've been using it for like over a decade, since version 4.x and it's now on 7.x.

That's the problem. Your players probably don't support natively playing container files. You are trying to play these video files like a DVD, correct? You will need to use some kind of conversion software to convert the two movie files to VIDEO_TS for DVD Video playback. I use a paid software called ConvertXToDVD. There are free alternatives but I don't follow those because last time I saw them years ago, they took too long to convert, the results weren't of the same quality, and/or the software was extremely buggy.