dbminter

When you say "multiple bootable files," I am guessing you mean can an ISO have multiple bootable sectors. And as far as I know, a bootable ISO can only have one boot track. Although, technically, you could extract, say, 10 boot sectors with ImgBurn as "files" and store those 10 files in an ISO, but they wouldn't do you much good. They wouldn't boot, just reside in a track in the ISO separate from the boot sector. I don't see a way to automate this, but what you could do is try this. You could make ISO files of these 10 installable discs and store those ISO's on a DVD/BD. You can then navigate into them from the disc natively via Windows and run the installers from them. Or copy the contents to a temporary location for execution. However, as I said, you probably can't automate this process. And each time you navigate the contents, you're mounting the ISO as a virtual drive, so you'll need 10 available drive letters, unless you Eject each one after each installation. So, the downside side, each installation must be performed on its own one after the other and I don't think it can be automated. And, I'm not entirely sure this process would work as I describe it. It's theoretical at this point, but it might work.

You could try changing ImgBurn's driver interface, but since you said even Windows Explorer doesn't recognize 2 connected burners as burners, that probably won't help. The cause does seem to be a deeply rooted Windows misconfiguration. You could try downloading and installing the Elby CD IO package. See if that "fixes" whatever the cause may be. That way, you could set Elby as the driver interface in ImgBurn.

What I have to wonder is given the age discrepancy between Windows 7 and modern burners, if Windows 7 doesn't have updated drivers and is just loading what it thinks will work. Which, in this case, is just a standard DVD-ROM drive driver. You could try going into Device Manager and check what driver is being loaded. If it's some kind of generic Microsoft driver, it's probably just loading a DVD-ROM driver.

To be honest, I have to think you probably can't Given the age of Windows 7, the driver being loaded for that device is probably so old that the driver doesn't recognize such newer drives as writers. You could try seeing if there's an updated Windows 7 driver from the manufacturer's web site, but there probably isn't one, given Windows 7's age.

Verbatim made the discs you used that failed. Check the log and it says this: I 01:31:47 Source Media Type: BD-R (Disc ID: VERBAT-IMf-000) The Disc ID says Verbatim actually made them. Hardly anyone actually makes their own media anymore. They farm out to a handful of manufacturers: CMC, which also owns Verbatim, Taiyo Yuden, which is also now owned by CMC! , Mitsubishi, and Panasonic/Matsushita. It could be your drive. A drive lasting a year before needing replacing is a good life span. In fact, it's above average. You could try replacing the drive and see if that helps.

How long have you had this ASUS burner? It may have just reached the end of its life. You're using quality Verbatim media, however Verbatim DL BD media can be very picky. Some drives don't like them at all, like the LG WH16NS40. CMC could also have changed the formula for those discs, introducing all new problems. In the interim, try to see if there's an update for your drive's firmware. That might help. In Write mode, right click on the drop down dialog with your ASUS burner in it. Choose the option near the bottom of the list about checking for firmware update.

PAR and PAR2 were still in use about a decade plus ago, when I last had access to newsgroups. They still even use NZB's to this day, from what I've heard.

Personally, I would see creating parity error recovery on a disc as a waste of time. If the disc has scratches, etc. that make it difficult to read files, then reading a smaller file like some kind of parity recovery would make it even more difficult as small data would be more affected by a larger scratch.

If Device Manager lists it as a "DVD-ROM," it's a DVD reader, not a burner. Unless Windows is not properly detecting the hardware type. I got something similar to this in store from an Office Depot: https://www.amazon.com/Verbatim-External-DVD-Writer-Compatible/dp/B01BY4PZLE/ref=sr_1_1_sspa?crid=2CLBSIX0KFPMD&dchild=1&keywords=verbatim+external+slimline+cd%2Fdvd+writer&qid=1606594366&sprefix=verbatm+externa%2Caps%2C159&sr=8-1-spons&psc=1&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUFIV0RMRUFLTE82M1cmZW5jcnlwdGVkSWQ9QTA5OTQzNTFQU05JV0lZQjdCVlQmZW5jcnlwdGVkQWRJZD1BMDU3NDI1MDNVNDBYT0FWMFFYSjgmd2lkZ2V0TmFtZT1zcF9hdGYmYWN0aW9uPWNsaWNrUmVkaXJlY3QmZG9Ob3RMb2dDbGljaz10cnVl It has worked well in what tests I threw at it. This listed model has M Disc capabilities, which mine didn't, so, as I said, it's not exactly the same one I tried out.

If you encounter this problem in the future, the best way you can probably tell if your drive is a read only drive and not a burner is to open ImgBurn and then go into Read mode. If it detects your drive in Read mode, but it's not detected in Write mode, it is most likely a read only drive and not a writer.

I always use UDF 2.60 for everything except DVD Video, which I accept ImgBurn's default changes for when I add a VIDEO_TS folder to the root directory of a Build job. And I guess whatever options are automatically set when you use ImgBurn to convert audio container files to a CD Audio.

I've got an idea of the culprit, which LUK is probably thinking of, too, but we'll need to see the log to determine it. ImgBurn probably thinks the disc is not empty because it isn't. Most likely, data was written to the disc but the burn failed. Even if the write fails to complete, data was still written to the disc.

Unfortunately, I've never found a consistent high quality BD-RE manufacturer. Most everything is either CMC or the lesser of two evils Ritek. So, I take Ritek, even though they don't play back properly on the PS3. However, I mostly just use BD-RE for data purposes. They write and read faster than CD or DVD media so I use BD-RE for things like bootable rescue media. Now, in the, past, Verbatim used to make their own quality BD-RE, but not anymore. I have 1 Verbatim BD-RE that is a quality one. It has a white surface with blue text on it. Panasonic, though, used to be something that wasn't CMC or Ritek. Some manufacturer who uses the DID MEI. Don't know if MEI is quality or not, though. However, I believe the M is short for Matsushita, if that means anything in terms of quality. I've got a stack of them, but haven't really had a chance to test them out. The drawback to them is they're only available in inkjet printable surfaces as far as I know. Panasonic used to make a high quality DVD-R. Back in the first days of DVD recording, in 2002, Panasonic made a DVD-R that was $15 a pop! But, they were quality; they're still playable 18 years after recording. Panasonic also made a quality DVD-RAM. I've got several DVD-RAM discs from Panasonic that are from 2002 that are still readable and still write! Best quality media in terms of write life I've ever seen.

Verbatim farms out to CMC for half of their output. One of the CMC products is their BD-RE, so I avoid Verbatim BD-RE. Now, Verbatm uses quality manufacturers for their BD-RE DL, not CMC crap. My guess is CMC doesn't make DL BD, otherwise, Verbatim would use that, too. Actually, CMC now OWNS Verbatim!

You can't put anything past God as to what he'll do. For instance, I recently got a new BD burner. It had a new firmware update that is only applied by the factory to new units. So, there was the uncertainty of new firmware borking up. In addition, the drive was put in a new USB enclosure I hadn't tested yet. So, my first burn to a DVD+RW failed! Knowing how it was most likely a trick, I put in a new, unformatted DVD+RW, and that worked! So, the failed burn just happened to be to a DVD+RW that just happened to have reached the end of its life on my first test. All subsequent burns have performed fine, except for an oddity. I was burning a BD-R which completed burn, ejected the disc for Verify,, but it got locked up at Waiting for device to become ready. A manual Verify worked fine. I'd never encountered such a thing ever before in my 15 years of using ImgBurn.

Another one of the problems could be this: I 09:14:30 Media Type: BD-RE (Disc ID: CMCMAG-CN2-000) CMC MAG media is the absolute worst. Results can widely vary with that kind of media. However, a reformat wouldn't explain away using CMC media. However also, a reformat can sometimes do the trick. For instance, if you have AnyDVD running and burn a DVD+RW disc, that disc will ALWAYS fail Verify after the burn and on every subsequent burn, even with AnyDVD NOT running, until you reformat the disc. At least, that's what it did about a decade ago.

No, it seems you got "genuine" TY media, as it says in your log: I 14:35:33 Destination Media Type: DVD-R (Disc ID: TYG02) CMC bought TY a few years back, and changed its "name" to CMCPro. I never tried CMCPro because of the poor reputation CMC has. However, any manufacturer can put anything in the DID label field, and I wouldn't put it past CMC to fake it. However, given you've had similar failures on different quality media, I'd be more likely now to think the drive is behaving badly. Try getting an external USB burner and see if you get the same results with these discs. If you do, you've got a problem somewhere deeper in Windows or a bad drive. Could also be a bad SATA cable or SATA port its connected to.

Under an hour is generally the burn time I've encountered on full 2x BD-RE. Do you have any other BD-RE you can try? Particularly one from a different manufacturer? It could be the BD-RE you used before is reaching the end of its life. As BD-RE approach end of life, they don't write at the maximum rated speed for that disc. Plus, it could be a fluke. Did you try a 2nd burn? Sometimes, for a variety of reasons, a drive will not write one particular burn at the maximum rate of speed.

Does this W 21:32:47 Session 1, Track 1 is smaller on the disc than it is in the image file. have anything to do with the error? I would, also, first try something other than RITEK media. Try Verbatim DataLife Plus/AZO DVD media. NOT the Life Series you find in brick and mortar stores. Those will be CMC, which are worse than Ritek. The DataLife Plus/AZO Verbatim DVD can only be found in online stores.

I've never used those Verbatim DVD+R you showed, but they do say AZO on the package, which is one of the things to look for. So, I'd say they're the good ones. Be aware if you're using the LG WH16NS60 Blu-Ray burner, there is a compatibility issue with Verbatim MCC DVD+R and that drive. They won't work. There are benefits and drawbacks to using both DVD-R and DVD+R. DVD-R is older so it has better compatibility playback for DVD players, particularly older ones. DVD+R is slightly larger than DVD-R so holds a bit more space. Plus, I don't think there's a write in lead in time on DVD+R like there is for DVD-R, so you'll shave off a little bit of time burning DVD+R versus DVD-R. I used to use exclusively DVD-R for its compatibility with older DVD players. I then switched to DVD+R for its slightly larger size and shorter lead in time, but CMC changed the formula for MCC Verbatim DVD+R and they no longer work with the WH16NS60. So, I switched to Taiyo Yuden DVD-R, since the MCC Verbatim DVD-R had the same problem as their DVD+R. TY doesn't make DVD+R with inkjet printable surfaces, so I had to go with TY DVD-R, which does.

About your previous luck statement. That can be the nature with CMC discs. You can go through a whole stack without issues sometimes. Sometimes you get like 50/50. Another problem with CMC is I had some DVD+R that burned and Verified correctly, but my DVD player wouldn't play them. That's also the nature of CMC and other cheap discs. Just because one burns and Verifies doesn't mean it did it "right."

Now, be aware there's no guarantee switching away from the cheap media will fix the problem. It may be something else. However, it generally solves most issues and it's where I'd always start with first. Plus, you're better off in the long run using the higher quality media. You'll have fewer playback problems with hardware and the discs will last longer.

Found exactly what I was expecting to find. This is most likely your culprit: I 21:27:15 Destination Media Type: DVD-R (Disc ID: CMC MAG. AM3) CMC is CMC Magnetics, the absolute WORST manufacturer of optical discs. 50% of the problems we see on this board are caused by cheap CMC discs and the problems generally disappear when you move up to higher quality discs. Try Verbatim DataLife Plus/AZO discs made by Mitsubishi. NOT the Life Series you find in brick and mortar stores; those are CMC. You can only find the good stuff in online stores. Or you could try genuine Taiyo Yuden DVD-R. Those are the top two quality disc manufacturers out there. You want to know the real kicker? Guess who now owns Verbatim: CMC!

Probably has nothing to do with the RAID setup. While it is unusual to configure optical drives on RAID, some manufacturers do ship them out of the factory that way. Dell does. I guess HP does, too. I think it's related to using Intel Rapid Storage Technology driver as the underlying I/O interface. Not sure. Anyway, we'd need to see a full log of a failed burn, not just the returned error code in the dialog. Open the ImgBurn log file. Under Help, choose the log file option. The .LOG file opens in your preferred text editor. Find a failed burn in the log and copy and paste the entirety of that failed burn log, and whatever may be in the Verify part of the log if the burn completed and just failed to Verify properly. I have a feeling of what may be the underlying cause, but I'd need to see a log of a failed burn/Verify.

Brand new drive doesn't necessarily mean anything. I've had several new drives that had to be sent back because they came bad from the factory. But, a newer drive does more easily rule out the drive being problem. However, I never really suspected the drive. It's the cheap CMC media that's the problem. However, a new drive could be the problem if the new drive came from the factory bad, which, as I've said, I have seen happen before. ImgBurn just sends commands to drives. It's up the drive and the media in the drive working together as to how well it behaves. Changing the ImgBurn software won't have any effect on that at all. One thing you could try is checking for a firmware update to the drive. An updated firmware might have better compatibility between media and drive. A drive's interactivity with media is based on the firmware it contains. While this may be a new drive and the user may have been using ImgBurn for years, have they always been using these same CD-R? And even if they were, there's no guarantee the CD-R manufacturer didn't change the formula for the discs so they no longer work with a drive. I've seen it happen to my WH16NS60 and Verbatim MCC DVD+R.