dbminter

One thing I noticed Pioneer updated in this firmware also relates to 8x DVD+RW. In the past, writing initially began at 6x for the first 2 and half minutes. That time has been cut down to one minute and 15 seconds.

As far as the 2209 goes, firmware updates make a lot of difference. For instance, when I first got the 2209, there were 2 Verbatim DVD+R DL media brands with the same Disc ID. One disc had an inkjet printable surface and one was branded. The 2209 had no problems with the branded discs, but would always fail Verify on the inkjet discs, even though they were the same DID. Internally, they should not have been different, but apparently, they were. The next firmware update to the 2209 fixed this issue. Then, when the 1.34 firmware came out, it caused Ritek 8x DVD+RW that would burn and Verify under 1.33 to fail Verifies until fully formatted in another drive. Hence why I started using the LG for my 8x DVD+RW. Then, the 1.50 firmware came out for the 2209 and 8x DVD+RW completes Verifies now. And now that my LG needs replacing and the 2209 appears to work again with 8x DVD+RW, I'm getting the Pioneer 209 BD that doesn't support BDXL and M-Disc since I don't need those. It has the same firmware revision number (In fact, the other, newer Ultra HD BD drive Pioneer put out also has the same firmware revision number.) as the 2209 does now, so it should write to 8x DVD+RW fine, too. I didn't know about the firmware update until today. I had checked a few weeks ago, but there wasn't one. Don't know what prompted me to check today, but I did, and there it was.

Now, IF you wanted to gamble the money on it, you could try some more Verbatim BD-R X/TL M-Disc with this new Pioneer BDR-2209 1.50 firmware. See if this new firmware handles those kinds of media better. However, as I said, it's a gamble. But, if you had any left, why got give it a throw?

Well, what do you know? After over a year of no new firmware updates, Pioneer updated the 1.34 firmware of the BDR-2209 to 1.50. I had thought that the 2209 would never receive another firmware update. I'm testing an 8x DVD+RW right now, in the Verify stage where it failed before, to see if they fixed the borked firmware from before. So, if the OP got the 2209 and has decided to keep it, there is a new 1.50 firmware released around March 2nd. It's dated December 2017, though, oddly enough. Surprisingly enough, the LG WH16NS40 also got a firmware update after like almost 4 years. But that was to plug a decryption hole in Ultra HD Blu-Ray's. Maybe that's why the 2209 got one, too. Simply to plug a Hollywood Hole, a goof that the big movie producers don't want. And nothing done to actually better the drive. And, the 1.50 firmware PASSED! They actually followed up on my e-mail and fixed the borked firmware, it seems!

I only use double layer discs when necessary. For DVD-Video jobs that require DVD+R DL and for BD-RE DL to make my monthly system and files backups to. I avoid using multi-layer media whenever I can. Even though it takes more BD-R to do a backup than it would BD-R DL, they're more likely to finish without errors and not have a problem reading back later on in years.

But, THUMBS.DB was abandoned after Windows Vista. The OP's original intention seemed to indicate he wasn't using that version of Windows. But, if you are using Vista, just do the steps as described above.

Which makes sense. After all, I believe long file/folder names are actually still 8.3 names with ~ in them and desktop.ini may just link the long file name with the 8.3 name. For reference, here are two related posts I made about this topic where I encountered this same thing: http://forum.imgburn.com/index.php?/topic/24759-imgburn-created-2-folders-in-the-same-directory-with-the-same-name/?hl=%2Btemporary+%2Bburn+%2Bfolder http://forum.imgburn.com/index.php?/topic/24760-drag-and-drop-from-optical-renames-target-folder-as-temporary-burn-folder-on-fall-creators-update/?hl=%2Btemporary+%2Bburn+%2Bfolder&do=findComment&comment=160787

As far as I know, what you suggested by about inserting the media and letting Windows generate the thumbnail data in the Users cache is probably the best and easiest way to go. I can't think of any way you could manually import that information with the switch over from THUMBS.DAT.

I had this happen once or twice before. I couldn't explain it either. Somehow, on the disc I burned, TWO folders in the same sub-directory were named the same thing, Temporary Burn Folder. I didn't think that was even possible under Windows's file structure. My folders were also supposed to be named Disc 1 Of 2 and Disc 2 Of 2. I also burned to BD-R. It was reproducable for a while but after I rebooted, it stopped doing that.

You're right. I just inferred the OP wanted to make an ISO of a bootable USB stick. However, the contents from the stick could be used to make a bootable recovery disc. I thought ImgBurn couldn't make an ISO of the stick, but I never thought about using its contents to Build an ISO until you pointed that out.

But, that doesn't make an ISO of the USB stick, though, does it? It just creates a bootable ISO of the installation media you can burn to an optical disc, right? I never had, well, any luck creating bootable discs with ImgBurn's Build options. But, I was trying to recreate WinPE rescue media from Macrium Reflect, so I had no idea what necessary settings were required or if any files were needed beyond the boot sector ones.

ImgBurn won't do this, I use USB Image Tool for such a task as the one you want to do. I think it saves to ISO, but I don't remember if that is the file output format or not.

A disk imaging program copies sector by sector of a hard disk drive partition. For instance, if you just backed up the Windows files, you can't just restore all of them and expect Windows to start. You have to restore a disk image of the Windows partition in order to get Windows to start if you need to restore Windows. ImgBurn doesn't do that. Now, if they're non-important non-system files, you could always copy them with ImgBurn. It depends on what you want to do. If you want to copy a Windows installation disc, ImgBurn can do that. If you want to backup Windows, ImgBurn can backup the files, but it cannot backup the various boot sectors, etc. that Windows needs to start.

Yeah, could have been, and seems to have been, the player. Depends on how old it is. Older age would play a factor. I had a Panasonic Blu-Ray player that after only 5 years, and about half of that it was never used, it started simply stopping playback in mid play of discs. And your player may have had a problem with Taiyo Yuden media. TY is generally pretty compliant, but not every player plays nice with all media. For instance, I had Memorex Ritek BD-R's that don't play back properly on my Playstation 3. Which was why I got the Panasonic at first before I discovered the PS3 has no problems with Verbatim BD media and just copied my Memorex BD's to Verbatim BD's.

Plus, what do you mean by "burning Windows 2010?" I didn't know there was such a thing. And do you mean copying the install disc? Or installation files? Or backup your entire Windows partition? If you're trying to backup your entire Windows installation, you're better off using a disk imaging program. You could backup the contents of your Windows installation to, say, a Blu-Ray or 2, but if you need to restore Windows, restoring individual files usually won't cut it. Plus, with disk imaging programs, you can generally restore individual files from images.

Before you invest in a new player, did you test to make sure it plays on a PC? If it doesn't play on a PC, then a new player won't help. It's either a faulty disc or a faulty processing of the original DVD. I'd also just try recreating the disc again from the source material. But, I'd make sure it plays first on a PC before attempting to burn it.

Also, I thoroughly tested the 2209 in that enclosure. I threw many discs at it and all tests passed with the 2209 in the vertical position. However, only a few double layer media tests were performed. A few DVD+R DL's and 1 BD-RE DL write test were done. So, I still think it's just the nature of the triple layer beast. Let's see how well you do with DL M-Disc. So, I don't see there being any real problem with the drive in the vertical position.

I don't understand the end of that log. What were you doing that took 0 seconds? How old is this drive? It may simply need replacing. How old is this standalone player? It may need replacing. It may not simply like Taiyo Yuden media. You need to try a range of drives/players and see what results you get. You could also put in a disc that fails to play and perform a Verify on it manually. While you probably don't have the image to compare it against, you can perform a read test in ImgBurn (Or just do a Read) and see if it finishes reading. Also, what are you feeding it? Are the VIDEO_TS's processed in any way before you burn them with ImgBurn?

Yeah, about the horizontal versus vertical orientation debate. At one time, PC case makers used to sell models where the optical drives were designed to be put in vertically. So, you could, if you wanted, fit 4 drives in the space of 2. So, did they stop doing this because drives were never meant to do this? Or did they stop doing it simply because it wasn't a feature people were using? That people weren't stuffing their cases with 4 drives. In fact, I never had more than 3 drives in a tower, and that one tower was the only one that ever had space for 3 5.25 inch drive bays. And one of those drives had to be PATA because there were only 3 SATA connections on the mobo, and one went to the HDD. I don't prefer vertical orientation because you have to make really sure you've secured the disc in the tray indentation before pulling your hand away. Just last week, I didn't do it well enough and a disc fell on the floor.

File size should have nothing to do with it. It depends on where it's failing on the disc. And, it's most likely failing at the layer change, where most common problems with multiple layer media exist. Well, I prefer horizontal, actually. I use vertical for external drives because I have to. I have little desktop real estate since I have an external HDD taking up a portion of it. So, I needed a vertical drive simply for a lack of space reason. I've read arguments that drives shouldn't be placed vertically, yet why then do they make external drives that orient vertically? It's sort of like the argument of whether you should leave your PC on all the time or not. Does turning it off and on wear it out sooner over time or is it better to leave it on all the time? I leave it on all the time simply because I don't want to miss Scheduled Tasks and that I think turning it off and on probably wears it out faster. But, there's little evidence for either side of the debate. I mean, as I said, if a drive was never supposed to be placed vertically, why did they make external burners that do? As for lasting a thousand years, I don't buy it. CD-R was supposed to last 100 years and doesn't. Besides, the problem is, in a thousand years, you won't be around. And, most likely, there will be no more readers available to read in your disc even if does last 1000 years. So, what's the point? Kind of like in the 2014 Godzilla movie. Someone had data stored on Zip disks and was able to freely read them. However, I don't think they make Zip Drives anymore in this day and age.

I've only ever burned BD-R SL M-Disc, but all of them burned fine in LG and Pioneer burners. The only BD DL media I ever burned were Verbatim BD-RE, but the Pioneer and my ASUS USB burn them fine; LG's do not. Maybe if there's a BD-R DL M-Disc, you might have better luck with those. I ran all of my burn and read tests with a 2209 in that enclosure with it oriented vertically, since that's what I need external drives for. Plus, I think that enclosure I recommended is designed to be oriented vertically as that's how I always used it. Don't know if it even orients horizontally, like drives are when put into PC's. (Well, some PC cases do orient internal drives vertically. Depends on the manufacturer, but they're few and far between now.) All read and write tests I performed to all media except CD-R (I have a limited number of those and they were getting hard to find on Amazon.com last time I bought them. But, CD-RW tests passed fine.) were with the 2209 in that enclosure oriented vertically.

It's probably just the nature of the multiple layer beast. Having never used anything beyond DL media, and that was only Verbatim BD-RE, I can't say how well any drive writes to even Verbatim BD-R DL media. Let alone triple or quadruple layer media. Also, how are you orienting the 2209 in the enclosure? Horizontally or vertically? If you've tried it in its horizontal position, try the vertical one. I've never actually tested that enclosure to see if it orients vertically, though. Some drives don't like being positioned horizontally. But, by this point, what else have you got to lose? You've tried everything else and nothing else gives you steady reliability.

I was creating a DVD Video project and exited the advanced Build mode. ImgBurn asked me if I wanted to use a label which I hadn't defined. I chose No and when ImgBurn returned to the main Build interface menu, the UDF field had, in fact, been filled with a label. But, here's the thing: the label was all in Japanese/Chinese characters! What could possibly have caused that? It eventually caused ImgBurn to "crash" on exit. Plus, before I closed, I couldn't drag and drop anything in in the Disc Layout Editor because the window of all drives and available sources in the upper left was just a blank window. This is what forced me to restart ImgBurn and get a "crash" on exit of application.

I thought of another situation where this might occur. If you read Mom to an image file and then Dad to one before you burned anything, ImgBurn probably queued up Mom for burning first. Then, after Mom's image file was burned, Dad's image came up next in the queue and that got burned.

So, you want 33 copies of each disc? 33 of Mom and 33 of Dad? As I said, the only way I can see what you describe is happening is if one disc is under 4 GB and the other is over 4 GB and you have image file splitting enabled. What would happen is you'd have 2 image files. 1 an ISO file and one an image file set with an MDS file. It's probably easier to just do a Read of Mom and write 33 copies in a row of Mom. Then, read Dad to a file and repeat. However, after each Read, be sure, under Write mode, you choose File and Recent Files. The most recent image file read to under Read mode will be at the top of the list. This way, you make sure you get the last Read image file to load under Write. I'd also make sure after you burn the first and 2nd copies before burning the remaining 30 plus that you make sure the contents of disc 1 and disc 2 are the same. You don't want to burn 30 plus copies only find some of them are different contents.