LIGHTNING UK!

Do you have any m4a files that do work ok? It could be something specific to the ones you're trying to burn - or neither of the filters have installed properly.

It's impossible to say without knowing the actual error your drive is returning. The error you're getting after a 'retry' (asc 0x30, ascq 0x0C) stands for - "WORM MEDIUM - OVERWRITE ATTEMPTED". That error code isn't meant to apply to optical drives, hence why it has not been added to the lookup in the program and just says 'Unknown' in the log. The ASC 0x30 group is all about incompatible discs though. As with most media related issues, I'd usually recommend trying different discs and possibly cleaning the drive with a cleaning disc. A quick Google shows you can find the IRST stuff here: http://downloadcenter.intel.com/Product_Filter.aspx?ProductID=2101 Picking the latest one (14.6.0.1029 at this time) takes me to the following link for the main driver: https://downloadmirror.intel.com/25165/eng/SetupRST.exe EDIT: The latest supported by series 7 chipsets is v13.1 and you can get that here: https://downloadcenter.intel.com/download/24006/Intel-Rapid-Storage-Technology-Intel-RST-RAID-Driver

I do it by the 'BD Read Feature' and looking at which versions of discs are supported.

Have you tried putting a newer Intel rapid storage technology driver on?

Assuming your PC is the one you've tried reading it on (as per the log file), I can guarantee it can't play it well. It might be able to play some of it, but when it gets to the sectors ImgBurn reports the drive can't read, your playback software will start to stutter and skip frames (or possibly give up). As you can see from the Log, ImgBurn has asked the drive to read certain sectors multiple times (default is 20) and the drive has reported a failure each time. There's nothing I (or anyone else) can do to make it read what it can't read (beyond infinite retries and hoping one works).

Your drive can't read the discs. Are they dirty / scratched? Your drive might just not be a very good reader. See if you can read them in a different one.

Yes, there's a guide on how to copy a disc in the guides forum.

The real error from your drive is being lost / swallowed up by something else. Go into the settings and put the I/O interface back on SPTI. When you've done that, right click the drive selection box when you're in Write mode and click 'family tree'. Close the prompt that comes up and then copy and paste everything from the log window.

That drive won't work. Buy the liteon drives or the optiarc 5280s-CB-Plus / Robot.

Opencandy is a plugin that offers 3rd party apps during the installation wizard - which you're free to decline. Beyond that, it does nothing.

Click the download link in the blue navigation bar at the top and then pick from one of the 7 mirror sites listed.

Post the log please.

You need the right hardware to burn the oversized images correctly. Normal sized ones are fine with any drive.

You will need the right hardware to do it.

Not all players will play BD content from a DVD discs, they only look for BD content on BD discs. Beyond that, I've no idea.

Your drive is reporting a write error as it tries to overburn those ritek discs. If it worked at all with those, you're lucky.

Bootable in what way? Is it an old dos based game?

How are you with editing the registry? You could look in hkcusoftwareimgburn and adjust it manually that way.

Can you post the log of you burning and verifying the disc please?

No, I meant when going from 1 / 2 layers to 3 / 4 layers. I'm sure it's all in the spec sheet somewhere if you can find it

And does it remember other settings ok between closing and reopening? I see no reason for it not to work.

They changed the layer size when going to triple / quad.

Are you loading ImgBurn directly or is another program doing it? You must load it directly. Many 3rd party apps that call it up will tell it not to save settings or override yours via the command line.

It would help if we could see the error and problem files in the log. I'm assuming it's just a file name length thing? Are you using UDF on the disc? You could just have UDF enabled and go from there.

If safe mode worked, it's more than likely your drivers for the controller are causing the issue - or a filter driver installed in the I/O chain somewhere.