dbminter

I think LUK meant for you to attach the .CUE file to a reply. That would be easier, but I suppose he can take the CUE text and create his own CUE file.

I was thinking it was Mixed Mode. Which makes verifying the burn a little more difficult as there's no way to ensure the data on the data track is not corrupt. Without an original disc to compare the source files to, you've no idea if the data files in the data track are corrupt in the original image.

Since it's an audio CD, it would be relatively easy to determine if it's a working burn. However, it would take some time. Listen to the CD. If there are no skips, hisses, pops, or pauses, then it probably burned correctly. Is there a data track on the disc? e.g. a Mixed Mode CD?

Never heard of AnyBurn before, so I've no idea how differently it handles images versus ImgBurn. Probably not a bug in ImgBurn. Just that AnyBurn is probably not performing as thorough a check on the contents as ImgBurn is. But, I'll have to let LUK reply further on that point.

Given you're using the high quality CD media in the log and given that you've tried different media, CD-R and CD-RW, and given that you tried this same image in different burners, I'd say the problem is in the image file you have. It's corrupted somehow. Particularly if you downloaded this image file, it's most likely the problem. Lots of images posted online are corrupt. Although the log itself doesn't show any error near as I can see.

TI was doing this USB forgetting or not finding them over a decade ago, which was the last time I used it. I've never done it with TI so I can't say, but particularly if you're cloning from one type of hardware to another, you may even to run ReDeploy in Reflect. I've never used the cloning feature of Reflect, but there are several posts I've seen on its forums regarding people needing help with it.

Did you try the Fix Boot Problems in the Reflect Rescue Media? There are a few posts on the Macrium support forums right now from some who are having cloning issues. They keep getting Error 9 trying to read, though. I moved away from True Image a long time ago because the recovery media either never recognized the external HDD or, worse, DID BUT, AFTER DELETING the target partition for restore, the software conveniently FORGETS the USB HDD was there, rendering you with an unbootable system! After that last fiasco where it HAD SEEMED TI was FINALLY viable again, I left it far behind. As you said, TI is now some kind of cyber security bloatware.

I've seen you over there. I use the same name, too. You also introduced me to Macrium Reflect, which I've been using ever since and became a beta tester for them for their Version 8 they released earlier this year.

Well, maybe LUK will make you a Beta Team Member. Aren't you a beta tester for Redfox? Or are you just a knowledgeable user on their forum?

Can't explain that one. Seems to be a Windows issue, beyond the scope of ImgBurn. I know I import a .REG file with all of my preferred ImgBurn settings when installing the software for the first time and any changes that get made afterwards are saved later.

Any particular settings you can name off the top of your head? One of the betas addressed the window positions not being saved, but I think that was a bug introduced as a result of the first beta from this year and some arcane Windows issue.

Well, they were beta releases, so they're only available for beta team members. Your avatar just says you're a member, so you wouldn't have had access to the links or topics.

Ever since the introduction of UAC up until some point this year, I always disabled UAC. I have good security practices, don't visit sketch sites, don't download software cracks, etc. But, I enabled it earlier this year because I got to thinking. I also never used to use seat belts until about 10 years ago. I hadn't been in an accident, but that's not a reason why you SHOULDN'T wear seat belts. You SHOULD wear them because you COULD get into an accident.

To be fair, in just the last half year alone, we have had 2 new beta releases.

I once had a cable modem that eventually needed replacing because every time I moved my mouse, it vibrated the desk area where the modem was standing. The cable port was apparently going bad and each movement of the mouse caused the modem to disconnect.

Could have been a loose cable or a cable that is going bad. Or a USB port on either the PC or the burner that is going bad.

Oh, I thought you had copied and pasted it from the log rather than typed it out. Well, let's start with the basics. ImgBurn may not recognize the drive connected, so we've got to start with checking if Windows detects it. Does it show up as a drive letter in Windows/File Explorer? If it doesn't, that's the reason why ImgBurn doesn't detect it because Windows doesn't. If it does show up in Windows, try changing your Interface. In Settings and Tools, under /IO Page 1, try selecting the different Interface options and see if that helps.

Well, I've had 2 NS60's die on me. One was older; forget the age of the other, but I'd just purchase one to replace the first dead one a month ago. Waiting on LG to get back to me, but they rarely respond at Christmas time. Have to keep pestering them into the new year when drives die around Christmas. Waiting to try out Pioneer's 213 line which I've heard might be released soon. It's hard to get 212 lines because it seems they've stopped manufacturing those. Which lends more credence to a 213 model coming out soon. While I fully expect Pioneer will not have addressed the old Ritek 8x DVD+RW issue, which they haven't for years, they may have no problem with the Imation Ritek 8x DVD+RW they currently make. While I don't have a cure for your problem, I am taken aback by one thing. I can see why a drive with TWO drive letters in its drive letter designation might be problematic. I've never seen that before.

I thought that maybe the command line switch might pre-date the creation of slim model optical drives which removed the ability to power load the tray. But, if you are using a slim model drive, it wouldn't matter.

I'm not familiar with the command line switches, but is there not something like /LOAD that would do the opposite of the /EJECT?

Hm, it sounds like you've got a bit of a Frankenstein here. I'd suggest you start all over. Unfortunately, we're not allowed to discuss methods of decrypting copy protected DVD's on this board. So, you'll have to do some searching on your own to find out how to do that. I do find it extremely odd you had a copy protected DVD where the resulting movie VOB's are fine but the menu VOB's are all black. Generally, without decrypting the source DVD, you'd get all black movie content VOB's but usually scrambled content VOB's. It's a movie encrypting affair and not a menu encrypting one because there are ways to make movies without menus. So, just encrypting the menus is extremely weak copy protection. Now, disregarding the copy protection issue here, I can't see a way to take an existing DVD and add subtitles to it. You can take the movie stream from a disc and add subtitles to it with something like ConvertXToDVD, but you don't get to keep the original menus. CXD makes entirely new menus.

I may have missed something, but I thought you eventually settled on the solution that the ISO itself was the problem. If the problem is in the ISO when the ISO is played back on VLC, then the problem will almost assuredly be replicated on the DVD you burned the ISO to. Try loading other .VOB files from the ISO in VLC. If they're all black, then the problem is with the ISO. I'd have to think it's whatever you used to inject the new subtitles into the DVD. Whatever you used probably didn't do it right. VIDEO_TS.VOB being black is actually fairly common. But any .VOB that is 2 GB or about being black is definitely a problem.

You replied while I was typing. I would guess it's a problem down to the discs you're using then. Post a burn log from the burn to DVD that is failing. My guess is it's probably a CMC disc and isn't reading correctly because they're cheap discs. Or weren't burnt well because they're cheap discs. Also, just to make sure, make sure the VIDEO_TS folder is in the root directory of the DVD disc you burned when you load it in File Explorer.

I just tried the double clicking a DVD Video ISO method I mentioned earlier. It does work for playing back DVD's. Just double click on the ISO and it if isn't assigned to something else in Windows, Windows will mount the ISO as a virtual drive. You can then open File Explorer, open the new virtual drive you'll find there, and go into the VIDEO_TS folder. Load the VIDEO_TS.IFO file there in whatever DVD player software you use. I'm guessing VLC can play VIDEO_TS.IFO files. Just be sure to use the Eject function in File Explorer before trying to delete the ISO. Otherwise, I doubt the file can be deleted while it's mounted because the file is in use.

You will need some kind of virtual drive software. I use Virtual CloneDrive. There are other options out there, though. Although, this might work, though I've never tried it. If you double click an ISO in Windows and ISO is not assigned to anything else, Windows will mount it as a virtual drive so you can access its contents in File Explorer. As a virtual drive, it might be possible to play the VIDEO_TS.IFO file from the VIDEO_TS folder in some DVD software.