dbminter

If you're trying to create a bootable USB, as I said, ImgBurn won't do that.

When you say the TOC message appears in the bottom left, I'm not entirely sure where you're talking about. Does this happen when you try to insert a disc or when you're actually performing a Read operation? If it's a Read operation, copy and paste the entirety of the failed Read operation log. And does this happen on all game discs or just this one? Also what game discs? PC? Some kind of proprietary system like a PS2 or XBox? Never mind, I think I see where you're talking about now. The bottom left corner of the top window, the main window. Where certain output messages appear. So, you're not actually performing a Read operation, just inserting discs. Do you get this same TOC message on other types of discs? Non game CD's or DVD's? If you get the same message repeatedly on other types of discs, I'd blame the slim model drive you got. Try another different manufactuer's one or buy a half height model and put in it an external enclosure.

I am guessing you're wanting to use ImgBurn to create a bootable ISO from or to a USB flash drive? If so, you can't do that with ImgBurn. ImgBurn only reads/writes to optical discs for images.

Hm, unfortunately, it saying SPTI is really less helpful than it seems on the surface. I was hoping it was saying something other than that to explain how ImgBurn can read the discs. I would have hoped that enabling SPTI would fail to read discs in ImgBurn, but one of the other interfaces like ElbyCDIO was working.

If you are going to use my method, you'll probably need a USB HDD. I have 4.6 TB of Reflect backups. That was probably why I needed GPT. To format a partition larger than 4 TB just for Reflect backups.

I'm rather paranoid in my imaging schedule. An image is done every day at 9:45 AM, one image set for each of all the 7 days of the week. Then, a Weekly image is done, 4 of those on Day 7, 14, 21, and 28. Then there are the 12 Monthly images done on Day 1 of each month. Each of those Monthly images is then copied as a backup to a USB SSD. Then, on Day 1 in January, the Yearly image is done, which is also copied to a USB SSD as well as a flash drive. That way, I have a fairly decent range of times I can restore back to without losing too much info. Then, twice a year, with the new Windows 10 Refreshes, I restore down Basic Systems Re-Installs, update Windows 10 to the latest version, update all software from my TO-DO.TXT file, install any new software, and make any configuration changes. Then, I make a new Basic Systems Re-Installs image, copying the old one to an archive folder on a USB SSD. When I get a new computer, the first thing I do before starting Windows for the first time is to boot my Macrium Reflect Rescue Media on it and image the entire PC drive(s) contents. That way, I've got a factory default image. Then, my comprehensive INSTALL.TXT file tells me what to install when and how to configure it. At approximately 15 different places along the way, temporary Re-Installs images are done. This way, if I later discover a problem occurred between X steps, I can restore back to X, fix the problem, and continue on with the set up.

The very nature of the beast that is Windows means you can just be sitting there and something goes wrong in the background. Often times, you will never notice one of these failures until you actually encounter it. Meaning, you won't know how long its been there. So your images, depending on your schedule, may have backed up these changes without your knowing it. If you have to do the drastic thing and reinstall Windows, do what I do. After you've reinstalled it and every piece of software and made all your configuration changes, take an image of Windows. This way, you may not need to reinstall everything if something like this happens again. You can just restore this, what I call Basic Systems Re-Installs Image, and you can just update it with new software updates and installations and configuration changes. Since you said you do take system images, might as well take advantage of doing so so you won't have to reinstall everything again.

It must be some kind of Windows problem. Maybe a configuration one. If ImgBurn can read the discs to image files, then the problem lies with Windows itself. When you first start ImgBurn, at the end of the log, there should be something that resembles this: I 11:28:28 Initialising SPTI... I 11:28:28 Searching for SCSI / ATAPI devices... I 11:28:28 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (N:) (SCSI) I 11:28:28 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (L:) (SCSI) I 11:28:28 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (Q:) (SCSI) I 11:28:28 Found 3 BD-ROM/HD DVD-ROMs! What do you have for the Initialising line? Do you have something other than SPTI? SPTI is Microsoft's driver. If you don't have that one enabled, that might explain while ImgBurn works and Windows isn't. If you don't have SPTI and have something else, I wonder if changing the driver to SPTI would cause ImgBurn to fail to read discs.

LUK, you know how sometimes I send logs of ImgBurn crashes on closing down of the application? I've been paying closer attention and this seems to happen at the Cleaning Up phase listed in the application on closing. Don't know if that's actually when it's crashing, but it could be a clue. You remember those crashes where you couldn't find anything out of the ordinary, but they've been randomly happening for years?

When you say pre-recorded, do you mean pressed DVD's like movies you buy in a store or Amazon or do you mean discs you've already written yourself in a burner?

OIC, by double density, you meant a double layer DVD. A DVD+R DL. (Possibly DVD-R DL, but those are less common, and they were uncommon to begin with.) Yeah, Windows 10 will natively read a double layer DVD as long as the USB DVD drive you get supports reading DVD+R. And almost all DVD burners today support both DVD-R and DVD+R, and even DVD-RAM. So, any DVD burner should do. A relatively inexpensive drive should do the trick. Avoid really older ones because they may not support double layer discs. I still install ImgBurn on new systems. Every one I get. Of course, I beta test the software. But, even then, I still use it a lot for data archiving. Mostly BD-R now.

I can't see Microsoft dropping support for ISO9660. It would pretty much kill backwards compatibility. Plus, older install discs may be ISO9660 and not UDF. I decided to create an ISO9660 image and burn it to a test DVD+RW to see if my Windows 10 2004 build can read it. I burned it and was able to load a .LOG file and read it fine from the ISO9660 disc I created from an image I wrote in ImgBurn. So, it's not that Microsoft removed ISO9660 backwards compatibility in Windows 10 2004.

First, I don't know what you mean by a double density CD. I don't believe I've ever heard of such of such a thing. Double density floppy disks, yes, but those are ancient history. Second, I don't see why you feel the need to install ImgBurn on the Windows 10 system to get it to read a CD. As long you have a CD drive somewhere connected, internal or external, Windows should read that disc natively. I'd just recommend getting a cheap USB CD drive, connect it up, let Windows 10 detect it, insert this CD you want to get the files off of, and copy them over from the CD drive with File Explorer. Beyond that, I don't see what issue you'd be having here.

I would say the drive is probably not the problem because, from what I gathered from his post, File Explorer shows no inserted disc, but ImgBurn can read discs to image files fine. Have you tried restarting the computer? When I get a case where File Explorer fails to see inserted discs, a reboot usually fixes that. And does File Explorer show any inserted disc and when you try clicking on it, File Explorer shows an empty directory?

Starting with Windows 8, I think (Definitely Windows 10.), Microsoft removed native playback of DVD's from Windows. So, all modern PC's will need some kind of software installed. My Dell came with a version of PowerDVD, but I don't use it to play my DVD's. I use a freebie called Media Player Classic Home Cinema.

Uh, that's precisely what you do want. DVD Video discs contain in their root directory a VIDEO_TS folder. (Not all DVD's contain an AUDIO_TS one.) VIDEO_TS contains the contents of your DVD. All the audio, video, and menus.

Have you tried powering off the PC and powering it back on? If it's an external drive, power off the enclosure and power it back on. It seems you're already in a loop where you can't use the drive, so you don't have much to lose at this point. And you're going to have to restart your PC at some point in the future anyway.

It's not that it has 2 videos on it. It has more than 1 track. I was thinking, when you first posted, you were probably trying to copy a DVD made with a DVD video recorder like one Panasonic used to make. Those cannot be copied with Read mode. You will need Build mode. First, put the disc you want to copy into a DVD drive on your PC. Next, in File Explorer, copy the AUDIO_TS (If it exists.) and VIDEO_TS folders to some temporary location on your hard drive. Then, in ImgBurn, go into Build mode. Drag and drop the AUDIO_TS folder (If it exists.) and VIDEO_TS folders into a Build job. ImgBurn will then ask you if you want to set the necessary attributes for playing a DVD. Accept ImgBurn to make these changes for you. Then, build the image file after you've done this. Then, in Write mode, burn the image file you just built in Build mode. This guide should be the one you're looking for:

Possibilities: 1.) The disc itself has a bad sector at that part near the end of the disc that's trying to be read. Have you tried reading other PS2 discs and see if you get the same behavior? 2.) Some drives just have certain problems with some discs. For instance, back in 2001, I got a CD release of the Hitchhiker's Guide To The Galaxy complete (At the time.) radio series. The CD's played fine in my CD player; I listened to them in their entirety before trying to make copies. However, one of the discs in my PC drive simply failed to read properly. And it, too, failed near the end of the read process. However, when I got a different PC CD drive, I tried reading that same disc again later. That time, it successfully read and copied the disc. The copy played. So, if this is the case for you, I'd try seeing if another DVD drive would read your PS2 game disc.

I believe that UME DID for DVD+R DL is not M-Disc. I believe that DID is for BD-R, but I'm not sure. Anyway, there are some questions about whether those are quality Verbatim discs or not. They're Chinese made, so who knows? I'd be willing to bet the problem is those UME discs. MKM is the only DVD+R DL quality disc. Try the Verbatim DataLife Plus (NOT the Life Series you find in stores.) or AZO DVD+R DL discs and see if you get better results. You'll only find the MKM stuff in online stores.

Good to know for there, too.

They do! Cool! I had never heard of them before until the Macrium Reflect tech support board. Pretty handy little feature.

Do Mentions work on this board forum? Meaning if I add an @ next to a user name, they'll know they've been Mentioned to bring their attention to a particular post? Thanks!

That will help some, but we'll need more. Post the log of the entire burn process, including the failure. Under Help, choose the ImgBurn log option. The folder with the log opens. Open the .LOG file, find the part with the failed burn, and post the entire burning and failing process log. Say, in your Avatar, is that Hank Henshaw, the Cyborg Superman?

As far as I know, Handbrake doesn't create Blu-Ray Video compliant discs. It creates containers, which is most likely why your Blu-Ray doesn't play. It doesn't have a BDMV and CERTIFICATE folder in its root. Just a container file. Check in File Explorer and see if you just have a single file in the root directory of your BD disc or if you have the BDMV and CERTIFICATE folders there.