All Activity

No, not necessarily. Verbatim is owned by CMC Magnetics, which makes the worst optical discs out there. If you're using Verbatim Life Series sold in brick and mortar stores, they will be CMC Magnetics trash. Only Verbatim DataLife Plus, NOT Life Series, are high quality discs because they're made by Mitsubishi.

The disc has to be a high quality disc because the company who made the discs "Verbatim" has high quality discs.

I can't explain the first problem off the bat, but it could be related to the 2nd. Settings both areas of eject settings should have worked, but if the drive is failing, as it may be being unable to read that disc, that could explain it. However, being unable to read that CD-R could be an issue with that CD-R. Unless it's repeatable with other discs, it could just be a CMC Magnetics cheap CD-R.

*** NEW UPDATE! *** ImgBurn is failing to read the disc. (it is a CD Recordable (CD-R)) I'm getting a error (or info) (you can view it in the file) I don't know why is happening, but its probably a drive failure, it may recover sometime. The disc is vaild.

I disabled both of them already.

Did you disable BOTH eject settings? Somewhat oddly, there are 2 separate Settings sections with eject options. Under the Settings, there's a Cycle Tray Before Verify option you can disable under Write. Then, under the Settings, there are the various Eject options you can deselect under Device.

can someone help me*

I've disabled the settings but it still opens the tray. I'm burning on a laptop, and it opens the tray after it completes operations and on failures too. I don't want it to open the tray because the laptop is very bad it may not read the disc after its removal, and have to wait hours for it to make it work again. Please cansomeone help me?

As for the first question, there's a Create MDS option under Tools. As for the second question, I don't think there is a direct way to do that in ImgBurn, but there is probably a roundabout way, though. You load an ISO for burning and change the Labels so they are in all caps. Then, mount that ISO as a virtual drive and use ImgBurn to create a new image file from the virtual drive by reading it into a new image file.

How do I make .mds files that accompany my .iso ones? Also how do I make both .ISO and .MDS files in all caps?

No. As I say though, sometimes it makes things better, sometimes it makes things worse. Obviously I had to choose if the program asked the drive to perform opc before write by default or not, and I defaulted to not doing it. There’s no correct setting that works for everyone. Some drives may do it automatically, it’s all down to the firmware. If media has changed from what the manufacturers originally tested with and designed the firmware to handle, it could be a useful setting to play with - assuming the drive isn’t playing nicely with the media to begin with.

Looks like the biggest problem is that I was hacked somehow as I just tried to look into a bunch of files on one drive and they are bad! At least I have the backups. thanks for all your time! Charles

Yes, this ISO is totally borked. Attempting to load it in DVDShrink returns Invalid UDF Image File System. UltraISO returned Invalid Image File Type Or Unsupported. So, there's no salvaging this as far as I know. This explains why the image could successfully be burned but not read by any hardware. It's technically "data" but without a valid file system, Windows can't access the Table Of Contents to determine what's on the disc. Which means the disc is "blank" as far as hardware in concerned. This also explains why the physical hardware players won't play the discs. There's technically "nothing" on the discs because they can't be "read." So, there's no need burning any more copies to DVD+R DL as they will all be just as useless.

The ISO MAY be salvageable, but I doubt it. I'll see what may be possible.

Yes, I just figured that out for myself!! Fortunately I have backups of everything and will check that!!! Charles

Got it. The problem is the source file is corrupt. I tried mounting it as a virtual drive. It took 5 minutes for anything to happen after double clicking on the ISO, and instead of mounting the ISO as a virtual drive in Virtual CloneDrive, Windows asked me if I wanted to open the file or not. I tested a known good ISO for mounting and it mounts immediately in Virtual CloneDrive, meaning the problem is with your ISO file. It was not authored correctly. I will need to investigate further, but this ISO is, most likely, useless.

Here is a link to the file from Google. https://drive.google.com/file/d/18R3s_dNInlm_8qjYgGaM_Dvo9q350in1/view?usp=sharing Let me know that you were able to download it. Thanks, Charles

Well, it's something to try. I don't think I've ever changed that setting before. Does this Perform OP before write option increase burn time by a significant amount?

If you're going to do either of those options, let's start with the cheapest, fastest, and most secure way. Upload the ISO somewhere online such as Google Drive and send me a link to it by private message on the forum and I'll take a look at it. What Lightning UK! just said backs up what I was saying about ISO9660 options.

If you provide me your address I will send you the discs I have tried to burn and you can look at them and see where I have gone wrong. I can also send you the ISO file I was using but it is 8gb and would need to upload it so you can use that to try yourself so need an email from you. Thanks, Charles

By now, I assume you’ve removed power from the drive completely and powered it back on again. Same issue with the drive not being able to see the disc? Can it read original / pressed / silver discs? Sounds like it might have just died. I’m afraid that’s just bad luck, things do randomly just break.

ImgBurn would need to have been closed before you modified anything in the registry or the invalid values would have just been written back to it when it was closed rather than new default values being used next time you opened it. You only have to delete the setting when the window size or location on the screen has really been messed up for some reason. Otherwise, if you’ve simply closed the log window, just open it again from the View menu.

“Perform opc before write” is pretty much the only setting that could make a difference here. The drive’s firmware controls the burn, the software just sends data. I couldn’t make the drive produce an unreadable sector on BD if I tried, so it’s causing the problem itself for one reason or another. Forcing OPC may work around the issue for you, but can also cause the issue, which is why it’s optional in the first place.

All of the iso files I see listed in your log files have no file system in them, that’s why the discs don’t work. Whatever method you’re using to create them in the first place, it’s wrong.

You might want to check out this post I just recently made: Scroll down to the end, where I made my most recent post. BD-R DL are generally unreliable in ImgBurn, it seems. However, Windows own burning engine, ISOBurn, seems to work fine. So, I will be using it going forward to write BD-R DL discs. I won't be using ISOBurn's Verify option, as I said in that last post I made, and instead use ImgBurn's manual Verify option with the option to check against the ISO file I burned with ISOBurn.