dbminter

Well, now I don't know if my next tower model PC will be a Dell anymore. Dell has removed the full height 5 inch bays from the latest iteration of their XPS tower model PC's. It comes with 1 half height bay for a half height DVD burner. As far as I know, they don't even make half height BD burners and that's what I need. Even if they did make them, slim model external BD drives are junk, so I can't see internal half height drives being of any quality. So, I'd have to get an enclosure and buy full height drives for external use only. Plus, I preferred having 2 5 inch height bays in the Dell towers I've had before. I liked having 2 internal drives because I had some old DVD-9 images that were split across 2 DVD-5's. With only one drive, internal or external, I'd have to copy the parts from each disc to HD and create a new .DVD that way. I don't think I have too many more of these split images left anyway, but it was easier having 2 internal drives for this process. And I need BD drives. I've moved to BD for a lot of my dual layer DVD-9 needs. No more layer changes to worry about failing. So to Dell!

This may not actually be considered a bug. I can't replicate it with any frequency. It seems to be random, but it does happen randomly about 1 in 10 times. When I'm in Advanced Input mode, I drag and drop folders/files, create folders I want, etc. I X close the Advanced Input window, but instead of closing and ImgBurn doing its calculations on the input, the window sometimes goes minimized to the tray. I just open the minimized window, X close it again, and everything proceeds as it should, with the window closing and the calculations performed. It's actually been doing this for years and I just lived with it since I never could replicate it except randomly. But, after I got it just a moment ago, I thought I'd post it.

Well, there's probably some kind of intermediary at play, especially if it wanted to download a 4 GB file for the ImgBurn installer. The PUP "warning" used to be expected as some AV treated the bundled OpenCandy as an unwanted program. It was never a virus or anything malicious. It just offered free software downloads that you probably didn't want. However, nothing would be installed unless you blindly kept clicking OK without opting out. However, OpenCandy should have been removed from the ImgBurn download installers on the mirrors since the OpenCandy servers were taken offline. That PUP "warning" may be a false positive. It used to be flagged in the past for OpenCandy and Symantec's AV may just be flagging it based on its installer name. Without actually checking the file for anything internal. Or, who knows? Maybe OpenCandy has been replaced with something else that offers users an "alternate experience" when installing.

It's possible it could have just been fluke. That when plugged in the first time, inferring you never took the cable out until I suggested it, that it was "installed" incorrectly by Windows. Unplugging it and reinserting might have "cleared" the issue. It's rare, but it happens. Hence why sometimes people have luck switching USB ports to fix semaphore time out issues. Weird Windows issues just sometimes happen. I had one PC where I couldn't, out of the box, put a shortcut on the Desktop with the letter S in the name. Trying to name them with S in their names caused Windows to lock up. Considering, until you change the setting, Windows DEFAULTS to naming all new Desktop shortcuts with the words Shortcut To in their name, this issue was a deal killer for that PC, which went back to the store.

You've got some kind of reworked version that has been altered to access the Internet. Probably to download malware. Make sure you only download the installer from one of the mirrors here: http://www.imgburn.com/index.php?act=download ImgBurn installer no longer accesses the Internet at all, I don't think. It did before for targeted marketing, but that was removed, I think.

That's odd. Your original post did come through as that's what prompted me to reply about keeping the image and testing the ports with it after a burn. I was a bit confused at first seeing the same post, for the most part, again. Now, it makes more sense.

Now, if you still have the image you burned before where you were getting the timeout, you could try hooking the drive up to the "bad" USB port and perform a manual Verify against a disc you burned where it failed. If it fails again, change the port and try again. If it doesn't fail, you can pretty much rule it down to that one port has some kind of issue. If you don't have the image, then, when you burn again on that port, keep the image, switch the port, and perform a manual Verify on the disc.

You know, I've got to be honest. I've rarely seen that tip actually work! I've heard it mentioned before but have rarely seen anyone report back that that fixed the issue. I don't know the specifics. Could be the USB port is going bad? Or the connection of that port to the motherboard. Also, be aware it may not have actually "fixed" the problem. It may be random and you only just encountered a case where it didn't show up when you switched the port. Hopefully, it will work long term, and I say if you find a solution that works, be thankful.

I would expect you can't just copy Dreamcast game CD's and expect them to work without some kind of mod chip or bypass method. You do have something like that, right?

Optical Quantum is not a brand I'm familiar with, so they're probably cheap discs. Any cheap manufacturer will probably almost always fail on double layer media. They did in the past with DVD DL so I don't see why that trend wouldn't continue with BD. I have heard of Philips, but my only experience with them was some DVD-R that CMC made. CMC is the worst optical manufacturer out there. But, that's no reason that Philips would use CMC for BD media. If CMC even makes BD DL media.

Let's say we have a VIDEO_TS that will fit on a DVD-5. We add that VIDEO_TS to a job that includes some root directory folders that increase the image size from a DVD-5 to a DVD-9. Where does ImgBurn "place" the VIDEO_TS? Layer 0 or Layer 1? Is there something in the DVD standard that says VIDEO_TS has to be on Layer 0 or start at Layer 0 and can expand beyond to Layer 1? I guess it may matter depending on the size of VIDEO_TS and the size of the extra contents? Meaning if the VIDEO_TS fits on the smaller layer, VIDEO_TS could go to that layer and the bigger layer for the rest of the data? I'm guessing Layer 0 is larger than Layer 1? I know that one layer is smaller in size than the other and I just guessed that Layer 0 is the bigger of the two. Thanks!

Are you sure when you drag and drop the folders, you haven't changed the "focus" by selecting just one folder with the mouse? Are all the folders still highlighted when you try to drag and drop them and it only adds one folder? Also, be aware that this sometimes randomly happens, even in the Advanced input interface. If you drag and drop more than one folder and ImgBurn only adds one folder, try dragging and dropping again immediately afterwards, choosing to either skip the folder already added or replace the folder with the new drag and drop. I encounter similar behavior about 1 time in 10.

Can anyone recommend some kind of free software that converts audio files, like MP3, to video container files, like AVI and the like? I'd prefer something where I can set a still image for the video instead of a black screen. But something like an equalizer output that just shows random graphics in synch with the video would also do. I'm looking for something like Freemake Video Converter, but that "free" software adds black bars to the video and a watermark at the start and stop of the video. So, it's crippled, instead of "free." I really can't use any kind of online converter because I'm often converting entire CD's, which can be over an hour. Thanks! Looks like I found something that works. Something called Any Video Converter. I had it already, but didn't think, given its name, it would do what I wanted. But, on a whim, I tried it for this purpose and it works. Even lets me add a still image to the video, which is what I usually do with spoken word CD's. I rip all the tracks to 1 giant audio file, convert to a video file using a scan of the CD cover art for the still image, and then put all the CD's for, say, a book on CD, as a DVD Video. Allows me to replace 5 CD's, usually, with 1 DVD. Music CD's aren't prime candidates for this, but books on CD or Big Finish Doctor Who audio dramas fit this category very well. And, I can only play these books on DVD on a DVD player, so it doesn't do any good for playing in a car audio CD player. Well, Any Video Converter works but it doesn't do it "right." You cannot navigate to random points in the container file. It plays but only from beginning to end. If you try to jump around in the video, it just sits there doing nothing. However, I just need these containers to import into ConvertXToDVD. They do and preview so it should seem that they would work, but I won't know for sure until I come across a need to create one.

My best experience with Verbatim BD-RE DL has been Pioneer's BDR-209M, with a few caveats. The last firmware released for this drive borks writing to Ritek 8x DVD+RW. They won't complete Verifies until formatted by an earlier firmware or in another drive. So, it may require downgrading the firmware on if it borks writing to ALL DVD+RW. Pioneer also has a few quality issues. The Eject buttons will go wonky after about 7 months. Pressing the Eject button won't work the first time, requiring a 2nd press. Same with issuing an Eject command in ImgBurn. Happened on my first 2 models. However, if ImgBurn automatically ejects the disc like after a write before a Verify, it seems to work every time. And there may be a general decline in the quality of the drive itself. My first and 2nd ones still work after almost 3 years, save for the Eject button issue and having to downgrade the firmware. My third one stopped writing BD-R after 7 months. My 4th one was borked right out of the box, failing to Verify on BD-R's the 2nd Pioneer of the same model would write properly to. So, it went back to Amazon.com.

I know the WH16NS40 is terrible at writing BD-RE DL media. I've never used a Verbatim BD-R DL, but I have tried Verbatim BD-RE DL with my drive many times. It fails Verify more often than not at the layer change.

Yeah, you won't need a bootable disc for that type of program contents. You can always make it bootable, but you will always need some kind of boot image to tell ImgBurn how to make it bootable. ImgBurn can't just make a disc bootable based on what files and folders you tell it to include on the disc.

Yeah, if you got a disc that fails to Verify on USB, try taking that disc and Verify it in an internal drive. See if you get semaphore timeout errors. I've only generally seen them associated with USB drives. Oh, so you haven't tried the old discs on your external drive yet, then. If your old discs do the same thing, it's most likely your USB drive. Although, as I said, semaphore time out errors generally don't just pop up on Verify and not on Writes. You will usually get them at the start of a burn if that's the issue. Some people have luck with fixing semaphore timeout errors by switching USB ports or swapping out the USB cable for a different manufacturer

It's odd that semaphore timeout issues have suddenly started up. Semaphore time out issues are generally caused by an incompatibility between your motherboard's USB and the USB bridge in the external drive. Generally, semaphore time out errors will pop up right at the start of a write, resulting in a burn that doesn't start. I can't say what might be the issue with it suddenly turning up only on Verifies. Could be the current batches of Verbatim BD-R DL's. You say your old discs still work fine but not the new ones. There have been gradually and worryingly, for me, increasing reports of Verbatim BD-R DL that used to could be trusted are having more and more failure rates.

I didn't encounter an issue with Verbatim BD-RE DL at the layer change. However, despite the Disc ID's being the same, they obviously aren't the same media as one is WORM BD-R DL and one is rewritable BD-RE DL. So, it may just be that the ASUS doesn't like Verbatim BD-R DL. Or I've seen indications in other posts that Verbatim BD-R DL may not necessarily be of good quality anymore. In the days of DVD+R DL, Verbatim was the only quality choice IF you got DataLife Plus and not Life Series. TDK also seemed to make a good DVD+R DL, but that was the extent of my experience. So, it may be that the ASUS drive in question likes Verbatim BD-RE DL and doesn't like Verbatim BD-R DL. Or it could be as simple as Verbatim BD-R DL can't be trusted. I 16:22:51 Operation Started! I 16:22:51 Source File: E:\TEMPDIR\Temporary UltraISO Files\Temporary 01.iso I 16:22:51 Source File Sectors: 12,700,592 (MODE1/2048) I 16:22:51 Source File Size: 26,010,812,416 bytes I 16:22:51 Source File Volume Set Identifier: 593046D05930466F I 16:22:51 Source File Implementation Identifier: Microsoft IMAPI2 1.0 I 16:22:51 Source File File System(s): ISO9660 (Bootable), UDF (1.02) I 16:22:51 Destination Device: [0:0:0] ASUS BW-12D1S-U E401 (D:) (USB) I 16:22:51 Destination Media Type: BD-RE (Disc ID: VERBAT-IM1-000) I 16:22:51 Destination Media Supported Write Speeds: 2x I 16:22:51 Destination Media Sectors: 24,438,784 I 16:22:51 Write Mode: BD I 16:22:51 Write Type: DAO I 16:22:51 Write Speed: MAX I 16:22:51 Hardware Defect Management Active: No I 16:22:51 BD-RE FastWrite: No I 16:22:51 Link Size: Auto I 16:22:51 Lock Volume: Yes I 16:22:51 Test Mode: No I 16:22:51 OPC: No I 16:22:51 BURN-Proof: Enabled I 16:22:52 Write Speed Successfully Set! - Effective: 8,990 KB/s (2x) I 16:22:52 Filling Buffer... (40 MiB) I 16:22:52 Writing LeadIn... I 16:23:05 Writing Session 1 of 1... (1 Track, LBA: 0 - 12700591) I 16:23:05 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12700591) I 16:23:05 Writing Layer 0... (LBA: 0 - 12219391) W 17:06:13 Waiting for buffers to recover... (LBA: 11161536) W 17:06:18 Waiting for hard disk activity to reach threshold level... I 17:06:18 Writing Sectors... I 17:10:22 Writing Layer 1... (LBA: 12219392 - 12700591) I 17:12:21 Synchronising Cache... I 17:12:22 Exporting Graph Data... I 17:12:22 Export Successfully Completed! I 17:12:22 Operation Successfully Completed! - Duration: 00:49:30 I 17:12:22 Average Write Rate: 8,596 KiB/s (2.0x) - Maximum Write Rate: 8,827 KiB/s (2.0x) I 17:12:22 Cycling Tray before Verify... I 17:12:36 Device Ready! I 17:12:37 Operation Started! I 17:12:37 Source Device: [0:0:0] ASUS BW-12D1S-U E401 (D:) (USB) I 17:12:37 Source Media Type: BD-RE (Disc ID: VERBAT-IM1-000) I 17:12:37 Source Media Supported Read Speeds: 6x I 17:12:37 Source Media Supported Write Speeds: 2x I 17:12:37 Source Media Sectors: 24,438,784 I 17:12:37 Source Media Size: 50,050,629,632 bytes I 17:12:37 Image File Sectors: 12,700,592 (MODE1/2048) I 17:12:37 Image File Size: 26,010,812,416 bytes I 17:12:37 Image File Volume Set Identifier: 593046D05930466F I 17:12:37 Image File Implementation Identifier: Microsoft IMAPI2 1.0 I 17:12:37 Image File File System(s): ISO9660 (Bootable), UDF (1.02) I 17:12:37 Read Speed (Data/Audio): MAX / MAX I 17:12:38 Read Speed - Effective: 2.5x - 6x I 17:12:38 Verifying Session 1 of 1... (1 Track, LBA: 0 - 12700591) I 17:12:38 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 12700591) I 17:12:38 Verifying Layer 0... (LBA: 0 - 12219391) I 17:34:33 Verifying Layer 1... (LBA: 12219392 - 12700591) I 17:35:14 Exporting Graph Data... I 17:35:14 Export Successfully Completed! I 17:35:14 Operation Successfully Completed! - Duration: 00:22:32 I 17:35:14 Average Verify Rate: 18,801 KiB/s (4.3x) - Maximum Verify Rate: 29,702 KiB/s (6.8x)

I have started my own Verbatim BD-RE DL test. That won't complete for about an hour. I'll get back the results then. I overlooked you were using a BD-R DL. I haven't ever tried burning a BD-R DL on any drive. Only BD-RE DL. You could try using Windows to burn the ISO. However, if it fails, you probably won't get much of an error report. Never used PowerISO so I can't say. I don't know how well the ASUS handles Verbatim BD-R DL. Or the Pioneer or LG. Be aware that my results with Pioneer's XL burner have been going steadily downhill over the last few I've had. I've had 4 and they steadily declined in quality. The last one I had was borked right out of the box, failing to write Verbatim BD-R that the 2nd oldest version of that same model would, so it was the drive I had received and eventually sent back. However, the LG has its own problems. If you're looking to burn DL, I can tell you it's a terrible drive for writing BD-RE DL to. It fails at the layer change more often than it succeeds and Verbatim BD-RE DL formatted as a giant floppy in File Explorer write at half the speed of the Pioneer. So, I'd try the Pioneer before the LG. However, also be aware that you may need to regress to the 2nd to newest firmware for it. The latest firmware for Pioneer drives bork Ritek 8x DVD+RW so they will always fail Verifies until they are fully formatted in a different drive or a Pioneer drive with the 2nd newest firmware.

If you saw the original text of this post, disregard it. I had the wrong model number as I do have that drive you just mentioned as an external. I can't remember if I ever tested writing an image to BD-RE DL in my drive. I know I've written the disc to full contents as a giant floppy in File Explorer without an issue. Yeah, it was weird. The USB ASUS model, which I had first, passed every test I threw at it. I just don't remember if I ever tested writing an image to BD-RE DL. So, I had high hopes for an internal ASUS I tried later. However, it WAS junk. Destroyed rewritable media, BD-RE DL and DVD+RW, thrown at it. How long have you had this drive? If you've been using it for a considerable amount of time, say 7 months to a year, it may just need replacing. Problems at the layer change are down to generally 2 issues: 1.) your drive needs replacing 2.) your drive doesn't like that kind of DL media Now, it could be down to the drive itself simply not being a good DL writer. I know LG's aren't. They fail more often than not on Verbatim BD-RE DL at the layer change. And they write giant floppy formatted BD-RE DL at half the speed of the Pioneer. Is this your first attempt at trying to write to Verbatim BD-RE DL in that drive? If I can remember, I'll try a good test to my model. I have an image that's only just a little bit over the size of a BD-RE SL, so it will test the layer change without taking as much time.

Yeah, don't bother; I'm not going to. It's just something I was curious about if it was information you had readily available in your memory.

This may not exactly be an ImgBurn issue, but it's kind of related. Where does ImgBurn write the Table Of Contents on a disc? Is the TOC written to the inner most ring, outer most ring, or a random place on the disc? I realize it may not actually be down to ImgBurn, but to the standard of an ISO image. I just don't know. Thanks!

So, you're trying to burn an ISO file made by Sonic's application in ImgBurn? It seems Sonic made it incorrectly, but there's still a possibility you can fix this. You could try mounting Sonic's ISO as a virtual drive, go into ImgBurn's Build mode, and drag and drop all files and folders from the virtual drive into a Build project. Then, let ImgBurn build the DVD. It will ask you if you want to change all the various settings for DVD Video when you import the VIDEO_TS folder. If there's still some kind of problem, then Sonic did not author the VIDEO_TS folder correctly. The problem is beyond just the settings Sonic made for the ISO. And, are you use the ISO contents itself aren't actually larger than the size of a DVD+/-R DL?

When you CTRL+SHIFT+Q to bring up the queue, does it show more than 1 in Remaining images? Also, when you press the Write button, are you pressing the Write button in the View Queue view or the write button in Write mode? I've never burned a queue before, so, I'm only guessing, but maybe the write button in Write mode doesn't burn a queue. Although I've had images come up in a queue before when using Write mode that I never intended to queue. As I said, I'm only guessing. Maybe you can't queue CUE? I don't know.