dbminter

That's why I miss those days.

So, you're using 2 WH14NS40 drives? Writing in a 1.03 firmware drive and verifying in a 1.05 firmware drive? If that's the case, I'd wait and see if it happens again, but this time use the 1.05 drive to write the BD XL disc.

Is this the first time you've tried BD XL media? I know one of the reasons the WH16NS40 is not usable, as far as I'm concerned, is it doesn't properly write to double layer BD media. 9 times out of 10, it writes it incorrectly.

See if this helps: Tools --> Settings --> Build --> Page 1 --> Advanced --> Check the box for Include Reparse Point Files. If it's already checked, don't change it as that won't help.

I did recommend M-Disc in my initial reply, but there is one mitigating factor that may turn someone off to using them: cost. M-Disc are a tad bit expensive, particularly when compared to the price for BD-R. However, there is the initial cost of having to pay out for a more expensive BD burner if you're going to use BD-R. And you will need a BD drive to read the discs back. With M-Disc, as long as your device supports DVD+R, it will read it. So, M-Disc is a bit more "universal."

I do prefer the old days when apps stored settings in INI files in the directory they were installed in. It made configuring applications on a new system much easier. Plus, INI is safe from when developers change the name of the Registry key they're writing to or change/add/delete branches from the key.

One oddity of the firmware in the Pioneer 212. It takes 35 seconds longer to write an 8x DVD+RW than it does on the WH16NS60. At one minute and 25 seconds into burning, the drive drops the write rate to 0.0x and it stays there for 35 seconds before resuming, climbing back up to 8.0x. It does this on "Ricoh" 8x DVD+RW from years ago and on the current 8x DVD+RW from Imation, made by "Ritek."

So, in Verify Mode, if a user unchecked Verify Against Image File, ImgBurn would just do a Read of the contents as if it were creating an image file?

In the Verify mode, there's an option the user can check to Verify Against Image File. When a Verify is automatically performed after writing an image if the user has the Verify option selected, is the disc verified against the image file that was written by default? Or is the Verify just a Read operation without comparison against the image file contents being burned? Thanks!

Yeah, as far as I know, there's nothing like a Like on this board's forum software.

I appreciate the compliments and I'm sorry I can't be of more assistance.

It sounds like the OP had a DVD-R DVD Video and used Handbrake to make an MP4 from the VIDEO_TS. They then tried burning that to a new recordable disc. As LUK said, DVD-R is a simple Read and Write operation: Read the disc to an image file and then Write it to a new recordable disc. However, be aware some DVD-R type movies from big studios have structural copy protection on them. Which means ImgBurn won't directly copy them; it will tell you if it can't Read the disc. Also however, if you got Handbrake to make an MP4, the disc either didn't have structural protection or you already circumvented it to make files Handbrake can process. DVD-R is simply a cheap ass way for studios to save money on production costs. Frankly, I'm surprised all studios haven't abandoned pressed discs in favor of DVD-R and DVD+R DL's. Most TV series are now released on DVD+R DL.

Unfortunately, your information just furthers my idea that there's no way to know what you're supposed to do with this X-Ray disc without asking who made it. The BIN file on that disc is not an image format you can burn, so ImgBurn has nothing to do with viewing the X-Ray on this disc. It appears to be some kind of proprietary format, so only its creator can tell you what you need to do with it.

Unfortunately, it's not immediately obvious what this disc is supposed to do in terms of behavior. BIN is a disc image format that ImgBurn recognizes, but BIN generally is associated with BIN/CUE, which is a file format pairing generally exclusively for Audio CD. BIN could also be shorthand for BINARY, but without knowing what the BIN file is supposed to do, I couldn't say. You could try copying the BIN file to somewhere temporary and loading that BIN file in ImgBurn's Write mode. If it is a disc image file, it will be available for writing to a recordable disc. If it isn't, ImgBurn will say it's not a proper disc image file. Oh, NOW I think I see why ImgBurn was called in this case. You may have had ImgBurn already installed before you received this X-Ray disc. Double clicking on the .BIN file would have invoked ImgBurn to try and burn it, which may have caused ImgBurn, when it opened, to check for an update. Then, it may have detected your ImgBurn was an older version. So, at this point, I'd do what I recommended before about copying the BIN file to some temporary location, loading it in Write mode, and see if you can burn it to a recordable disc.

I'm guessing Xray is a subfolder in the folder Study in the root directory of the disc? It depends on what Xray is. Is it a folder or a file? If it's a file, it will usually have some kind of . extension after it defining what program opens it. Unfortunately, probably only a screenshot of what you're seeing where it says Unknown in the properties would help here. And I don't know if you know how to create one.