LIGHTNING UK!

It wouldn't be a software thing, you'd have to rewrite the firmware in the drive.

I'm sorry but 'finalised' really does mean finalised... as in nothing else can be written to it.

Do you remember how you configured the options on the 'Bootable Disc' tab? I'm not really sure why you'd run into the issue you're having. Either the iso is bootable or it isn't - so I don't know where the inability to see your RAID drive comes into it.

That disc is done now, you can't burn anything else to it.

That isn't showing any sort of 'freeze', it's showing the drive is unable to read the disc that it just burnt - hence all of the 'unrecovered read error' error messages. As your drive claims to support burning those 'UME02' MID discs at 4x and 8x, try burning at 4x instead of MAX (8x). After that, if your drive still doesn't produce a working disc, invest in some better quality discs. The 'UME02' MID ones you're using at the moment aren't any good.

Can you post the log from where you built the ISO please.

Can you burn other discs? Perhaps try enabling the 'Perform OPC Before Write' option in the settings and give it another go. It's a shame you can't get the recommended MKM-003-00 MID Verbatim discs.

10 and 12 are very similar. With 12, you've a couple of extra options you can toggle. One is the 'streaming' bit, the other is the 'verify not required' bit. Neither are anything to do with layers.

For the entire duration of the burn, the programs would only issue 'write (10)' or 'write (12)' commands. That's it.

I can continue to deny there's any difference... I have the code!

I guess the drive had done just about enough before reporting the error.

There is no difference between on the fly and writing an ISO. It's all buffered internally and the same burning code does everything.

Yes, no doubt due to the write speed on the particular MID being too high and the drive performing badly on them.

My previous post covered everything thus far. There's no magical fix I'm afraid, you just need to mess around (troubleshoot) until it works. Without the proper error code, it's impossible to see what's actually happening. If your drive had thrown a 'Write Error', that would be easier. Yours is throwing 'invalid field in cdb'... which is nonsense.

As I said previously, I'm not convinced the software is getting the actual error code back from the drive. Can you try booting into safe mode and burning another disc? After that, I'd start looking at various drivers for your SATA controller. Is the bios up-to-date for your motherboard?

Hard to tell with this one as it looks like something is messing up the error codes your drive is actually returning and all the program is getting back is that 'invalid field in cdb' one. Right click the drive selection box and pick 'family tree'. Close the box that comes up and copy + paste everything from the log window please.

Your drive doesn't appear to like those disc. Try some different ones or get a new drive.

Not really, no. Once the data hits the drive's cache, the drive takes over. If it doesn't burn properly, it only has itself to blame.

Audio CD uses a specific format (44.1kHz, 16 bit, stereo) and is burnt as raw 2352 byte sectors. There are 75 frames per second for CDDA and 1 frame = 1 sector. So 1 second of audio = 75 frames = 75 sectors = 176,400 bytes. So 1 minute of audio = 4500 frames = 4500 sectors = 10,584,000 bytes (~10MiB). MP3 can vary greatly in size because of variable bitrates etc.

mp3 files are tiny in comparison to a track on an audio cd... so you can fit loads more songs (tracks) on an mp3 disc. A proper audio cd will normally contain a max of 74 or 80 minutes worth of audio. With an mp3 disc, assuming each file is around 4mb in size, you'd be able to fit about 160 on a disc. 160 songs lasting say 3:30 each would make over 9 hours of audio.

If you've burnt audio files with the program in Build mode, you've made an MP3 type disc (technically just a data disc with audio files on it). Playback of such discs is down to the individual player. Some will support them, some won't. Some may not support the type of audio files you've burnt either. When you follow the Audio CD guide and burn the audio files via the CUE method, the program creates a proper Audio CD that should be compatible with anything that'll play Audio CDs. There are no 'files' on such discs - even though Windows / Explorer might make you think there are, by displaying a .CDA file for each track.

Files, file system descriptors etc don't start and stop on 64KiB boundaries, they start and stop on sector boundaries. So you can hardly call that value useless! You only use the block size at the very end of the image for descriptor placement.

It would only read what the drive reports has been 'used'. Of course, when talking about this stuff, you have to ignore double/triple etc. layer discs. Unused space on those could be in line with used space on other layers - whereby scratches will render the disc unreadable.

bytes per sector

Maybe you'd like to try posting that again.... all you've done is copy and paste the 'forum rules' from the pink box.