LIGHTNING UK!

Have you tried burning at all of the supported write speeds? If none of them work, buy better discs. Something from Verbatim or Taiyo Yuden (Victor JVC).

The 8x discs will work fine. It's a technical limitation that it can't handle DVD+R DL any faster than 6x (slimline drives are rubbish), that doesn't mean the firmware won't support 8x discs at speeds below that (i.e. 4x and 6x). Give them a try

I assume the 'no seek complete' error is during the verify stage? That's probably due to the media you're using and/or the write speed chosen. If you're getting that in the old version, you'll be getting it in the new version too - only now it's probably having more of an impact on the track analysis phase.

What, you've got Verbatim discs now? Post a new log then please.

Yes, read the thread I posted in my last reply and do what it says!

When you buy DVD discs they're either single layer (DVD-R, DVD-RW, DVD+R, DVD+RW) or they're double layer (DVD-R DL, DVD+R DL). The single layer ones are marked up as 4.37 or 4.7GB usually and the double layer ones will be something like 8.5GB. Any amount of searching via Google etc will show you what they are and pretty much anywhere that sells single layer dvds will also sell double layer ones.

That image is meant to go on a double layer disc.

The problem isn't OS related, it's down to the drive being use and the disc in it. What format is the original image? How comes you're mounting it and making a new image rather than just burning the original - I guess the original one isn't supported or something?

Look in the 'Mode' menu at the top.

It's your antivirus program, which I asuume is 'Avast'. It's sandboxing the app.

Sorry, I haven't a clue. I know nothing about Macs, Parallels etc. Is Parallels up-to-date / the latest version? On the disc that failed with 'Peripheral Device Write Fault', try scanning it (PIPO / Disc Quality scan) in DVDInfoPro / CDSpeed / Opti Drive Control / kProbe etc and see what it's like. I can't tell if the write did actually error out for a good reason (the drive didn't like the disc) or it was just the virtual machine messing up. Are there any alternatives to Parallels? A quick Google suggests VMWare Fusion. Maybe give the trial a shot? Is there a way of running native Windows 7 on that physical machine? Again, I know nothing about Macs How about adding the drive internally - not via USB - is that an option?

The full erase is what would have done it, even if it got stuck. Quick erase does nothing except write zeros to the first few hundred sectors... which of course you'd be writing to anyway if you're trying to write an image.

Do you have the logs from the others? Brand names don't mean much (except with Verbatim and Taiyo Yuden), they could all be using rubbish MID codes/dyes like the 'RITEK-F16-01' shown there. That said, if the drive is failing with everything you throw at it, it's probably dirty (clean it with a cleaning disc) or faulty.

It's because the disc is (was) formatted with spare areas enabled - thus the drive activates 'hardware defect management' and verifies every 'write' operation on the fly as it goes. Doing so slows the burn down a lot. I can't see that a quick erase in ImgBurn would have made any difference to it... is that really all you did? A Full erase would have (if using default settings) formatted the disc again but turned off spare areas and therefore deactivated defect management. The other way to make it burn at normal speed (even when defect management is enabled) is to enable the 'FastWrite' option in the settings ('Write' tab).

The initial error - ASC: 0x09, ASCQ: 0x90 isn't documented anywhere, but here are some other errors from the ASC 0x09 series... 09 00 TRACK FOLLOWING ERROR 09 01 TRACKING SERVO FAILURE 09 02 FOCUS SERVO FAILURE 09 03 SPINDLE SERVO FAILURE 09 04 HEAD SELECT FAULT It all adds up to your drive not liking the discs you're using. Give it another go at 4x or something. Notice the speed you requested (12x) isn't supported so the drive used 8x instead. If it doesn't work at 4x, get yourself some better discs - Verbatim or Taiyo Yuden (Victor JVC).

Ah well, it was worth a shot. I guess the drive you have now just produces discs your player can't read. It's probably a firmware bug. I see it doesn't support the usual booktype/bitsetting commands and it doesn't automatically change the booktype to DVD-ROM (which is a bit weird)... but I'm sure the Sony players can't be relying on that - or can they?! Are you able to try some of the 8x Verbatim discs? MKM-003-00 rather than MKM-001-00

I only ask because for Vista+ they're disabled automatically It's probably a graphics card driver issue (perhaps something they've changed on purpose?) if it's not working in XP.

That's just the drive performing its own quality checks as it goes and adjusting the laser power accordingly - in order to achieve the best possible burn. Seeing as the 112 and 212 are basically the same drive, I don't know why it wouldn't be doing that too... weird. Different firmware perhaps?

How come the drive was USB one minute and then SATA the next?! When connected via USB, it would appear the real error messages from the drive are getting lost (in the drivers / translation between the actual drive -> your Mac OS -> Parallels -> Windows 7 -> ImgBurn). For that reason, I'd stick with SATA if I were you. That said, it looks like that isn't perfect either - it looks like you ran into some sort of timeout when performing OPC and the media somehow vanished! On top of that you had weird failures when performing the sync cache / close track / finalise disc commands. I don't know how this Parallels thing works but do they ever release updated versions / components? Is yours the most recent? It's hard to try and help out when the machine isn't doing what it's meant to.

Have a read... http://forum.imgburn.com/index.php?showtopic=8000

What OS are you running? I guess you must still be on Windows XP?

Have you tried burning at 4x instead of 2.4x? The drive might actually do a better job at that speed.

Yes, it's done using the normal quick/full erase method. ImgBurn gives you 3 options for the the amount of space you're left with on the disc after formatting/erasing. It defaults to 'Preferred' which then uses the size in the first 'Format Capacity' descriptor - these are listed in the disc info box on the right of the main window. It's called 'Preferred' because the drive lists them in order of preference (according to the manufacturer / firmware or whatever). You can probably guess what the 'Minimum' and 'Maximum' ones mean The 'FT: 0x32' ones are for formatting with spare areas enabled. So 'Preferred' would leave you with 11826176 usable sectors. 'Minimum' would leave you with 7369728 and 'Maximum' with '12088320'. There's no 'Format' command visible to the end user but it's called when you do a full erase (quick erase doesn't apply to BD-R).

I'd expect 24 bit files to be a problem in general. Certainly, the wav file created by decoding the flac file (using the flac command line tool) will not load either - because it's still 24 bit.

Ah I think it might be because they're 24bit. Maybe madFlac doesn't support 24bit flac files... or at least not when it's being asked to output in 16bit?