All Activity

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.

Your hardware must be the problem. If it says burn completed but Windows says the disc needs formatting, then nothing was written to the disc or your drive doesn't recognize anything was written to it. That would also explain why your player doesn't play it. There's nothing actually on the disc. Try this next. With one of those discs you burned inserted into the drive, use ImgBurn's manual Verify mode to see if ImgBurn can read the disc. Or try the Read mode to see if that disc can be detected and read. Verify is basically a Read operation without an image file being written from the read data. You could also see if you get a needs formatting message by taking that disc to another PC with a different kind of drive. Or you could try getting a different USB drive and see if that happens again. However, I believe the issue is nothing is actually written to the discs, which would explain why your player doesn't play anything. But, to troubleshoot such an issue is nearly impossible to do remotely. One would need to be on site with the discs and all the hardware in question to know for sure. BUT, none of that explains why you weren't given an ISO9660 message or a layer break setting option. Wait, did you actually create this ISO you're trying to burn or did you get it from another source? If you didn't create it yourself, you'd not get an ISO9660 settings message. You may not get a layer break setting option either. If you didn't actually create this ISO in question, then the ISO may not have been authored correctly for DVD Video settings.

Disk is in the drive, opened File Explorer, clicked on the drive and File Explorer tells me the disc needs to be formatted! No other info is available for that disc or any of the others I've attempted to burn. I have VLC Media player on my PC and it won't open the disc either. Since when does an ISO file have a VIDEO_TS in it? I just put a regular dvd I burned recently from an ISO file and there is no VIDEO_TS file on it. My hardware is not the problem. I found these insrucions online... Open ImgBurn and select "Write image file to disc" from the main menu (or go to Mode > Write). Under the Source section, click the Browse for a file icon (the small folder/magnifying glass) and select your movie ISO file. Under the Destination section, ensure your dual-layer DVD drive is selected. On the right-hand panel, change the Write Speed to a low setting like 2.4x or 4x. Note: Burning dual-layer discs at high speeds often causes write errors or playback freezing. Check the Verify box if you want ImgBurn to double-check the disc for errors after burning. Click the large Write button (the image-to-disc icon) at the bottom left to start the process. Once the process reaches 100%, your dual-layer DVD is ready to play.

You put one of the burned discs in the PC drive, open File Explorer, and open the root directory of the disc by double clicking on the drive icon represented in File Explorer. If it is a DVD Video standard DVD and your PC is configured to automatically start DVD movies, your PC software player will open it. That proves it's a DVD Video compliant disc, which means your Sony, I think it was?, DVD player is the culprit. Otherwise, if the disc actually has contents burned to it, double clicking on the drive will open its root directory. Then, you look for a VIDEO_TS folder in File Explorer. However, since you were not asked to set a layer break or any ISO9660 settings, you're almost certainly not making a DVD Video disc, which explains why your player isn't playing it. Since you seemed unaware of what a VIDEO_TS is, let me ask you precisely what you're doing. What guide did you follow? Are you just adding files that play on your PC like MP4 or MKV to the DVD+R DL, popping that disc in your DVD player, and expecting it to play the files? If you are, that won't work. You need a DVD Video compliant disc with a VIDEO_TS in the root directory.

I thank you for all your help so far, but I am just an end-user, not an expert. I've followed all the online instructions, bought the DVD+RDL discs you said to buy (for $65) and have already wasted five of these discs. I can't tell you what is on any of the discs as I can't open them to see. I've burned numerous "regular" sized ISO movies onto standard DVD+R discs with your program with no trouble but this is the first time I've tried to burn an ISO file so large onto a double layer dvd. No, I was not asked to set a layer break or the ISO9660 file system settings and no mention of a VIDEO_TS folder. That's all I know. How can I open a burned dvd+rdl to show you the root directory of a failed burn? Please guide me and I will provide everything I can! If you send me step-by-step burning instructions I will keep trying! Here is a screenshot of my latest attempt underway. Charles

I have tried three different drives and none of them worked. Got it to write on two of them, but it stopped at 11 and 23%. Just going to burn it to two 25gb drives, so no rush. ImgBurn.log

As I said before, show me a screenshot of the root directory contents of the disc that won't play. I've got a feeling it's not a DVD Video compliant disc. When you created the image file in ImgBurn, were you asked to set a layer break? If you weren't, then there's most likely not a VIDEO_TS folder in the root directory of that disc. Also, were you asked to set the ISO9660 file system settings for a DVD Video disc by ImgBurn when you added a VIDEO_TS folder?

I got the new dvd's you suggested and tried to burn the same large iso file with no success as it was not playable on my Sony dvd player. Still at a loss as to what the problem is after following all the steps. Charles

I finally got a test candidate to try out ISOBurn with for BD-R DL. I tested a Ritek BD-R DL and I would recommend using it going forward as opposed to ImgBurn for BD-R DL's. With ImgBurn, only 2x burning properly works. With ISOBurn, it takes about less than 90 minutes, the total burn time for 2x, to write 6x BD-R DL and Verify it in ISOBurn. ISOBurn also works on my VanTec Gen 1 USB enclosure and the LG WH16NS60. With ImgBurn, the VanTec Gen 1 enclosure never worked on my setup for either the NS60 or my ASUS BD burner. I would recommend not using ISOBurn's Verify option. While it is servicable, since you must have an ISO file to get it to work, I would save time and use ImgBurn's manual Verify operation against the image file's contents after successful burn. The major drawback to ISOBurn is it only works as a command line driven tool. So, I created a shortcut to run it with I've only just made the basic tests to my Ritek burn thus far. I've only performed 4x Forward Scan tests on all of the extras. I'm in the process of watching the 2.5 hours of the main feature right now. I've finished the first 25 minutes episode of 6. No playback problems thus far. However, until I get a Blu-Ray BD-50 that I need to watch all of its contents on, I can't for 100% certain say ISOBurn "works." Thus far, though, it seems to be the superior option to ImgBurn for burning BD-R DL. So, I thank you for pointing out this alternative option!

I had ImgBurn 2.5.8 installed and encountered the problem that the Logging Window is NOT showing up, so I followed the instruction from the Forum as shown: "To resolve this, you can reset the window position by closing ImgBurn, opening the Registry Editor (regedit), navigating to HKEY_CURRENT_USER\Software\ImgBurn, and deleting the LogWindow entry." I deleted the registry entry for "HKEY_CURRENT_USER\Software\ImgBurn", closed ImgBurn and restarted it again. Again, the ImgBurn Log Window would NOT display. I do keep 2 versions of ImgBurn which is 2.5.7 and 2.5.8 and I never trusted 2.5.8 and have always used 2.5.7 since 2001 in my old PC's. I totally uninstalled ImgBurn 2.5.8 and re-installed ImgBurn 2.5.7 and the ImgBurn 2.5.7 install did not even created a shortcut for 2.5.7 but I easily created the 2.5.7 shortcut since the ImgBurn 2.5.8 shortcut I previously created was still existing in the desktop and ImgBurn 2.5.7 and 2.5.8 executable is named the same as "ImgBurn.exe". When I clicked the 2.5.7 shortcut named as "ImgBurn 2.5.7", the Log Window now appears. I believe this has to do with me closing the prior ImgBurn 2.5.8 Log Window and even following the advice to delete the Registry entry for "HKEY_CURRENT_USER\Software\ImgBurn" could NOT solve the problem. Now with ImgBurn 2.5.7 working with the Log Window opened up, I will use my new method of running a simulation first so the log is created and then a real backup with the contents plus the previously created simulation log. "EVEN IN SIMULATION mode, the LOG File SHOULD ACT the same way as a real backup process is performed" - I stated this because I need to verify this after successfully installing ImgBurn 2.5.7. Suggestion: Why not improve ImgBurn as 2.5.9 such that a C:\ disk drive log is created in "C:\Program Files (x86)\ImgBurn\Logs\......." every time ImgBurn is opened up and a new log is created with the log file name with stating "CCYY-MM-DD HH:MM:SS AM" or "CCYY-MM-DD HH:MM:SS PM" . Since the log is a Text file, logging can be done by just adding new records to the very end of the text file when ImgBurn is NOT closed and a new set of backup is created using the same log that was originally created when ImgBurn was first started. When ImgBurn is closed and a new session was initiated, then a new log with a different "CCYY-MM-DD HH:MM:SS AM or PM" is created. My reason for this I can perform a final burn which will include the previously created log file. I wanted the log file because ImgBurn renames the file being backed up if the maximum file length is exceeded and the log will show the new renamed name in the log file together with the CD/DVD or BD-R real backup contents for future reference.

The dvd's you recommended will arrive today and I will try burning one and let you know my results. Thanks again for your help! Charles