LIGHTNING UK!

Google / search.

I'd certainly go for the 1GB splitting if I were you. Don't leave it making large VOB's now that you know it's doing it and shouldn't be.

I guess in practice it doesn't make much difference because even though the vob files are normally limited to 1GB in size, once they're on the disc they're accessed as one virtual large chunk of data and not really as individual files. I haven't every actually tested ImgBurn with them like that though so you're kinda lucky that it just worked

Start again. If the process you're following leaves you with a single vob file thats larger than 1GB in size then your process is flawed. So basically, you can't burn what you have now and as we only help with ImgBurn related burning issues you're pretty much on your own I'm afraid.

You can't. It burns from an existing tree - and it burns the entire thing. If you don't want those folders there then you have 2 choices. 1. Move them someplace else for a second (or make a new folder tree of the stuff you DO want to burn) 2. Don't use ImgBurn

Is that not a single 4GB vob file? They're only allowed to be 1GB in size so you must have done something different and I'm pretty sure DVD Shrink wouldn't make a vob that big.

D+D from explorer has always been the solution, that's why I implemented support for D+D in the first place - it's not something that happens automatically.

Are you suggesting something that's already possible or have I misunderstood your point? Perhaps you're just letting other people know about it?

No chance.

Why wouldn't you just turn it off in the settings?!

www.svp.co.uk

It's a drive thing, you could learn to speak 1's and 0's and ask it if you like?

Well you actually got a non standard error there (hence why it says 'Close Track Failed! - Reason: Unknown') so there might not actually have been any problem at all. I don't know if your drive is actually on an nvidia controller or not but we do know there's a bug in their drivers whereby random nonexistent errors are reported. Should the error be a real one, your drive return error codes in the 'Write Error' family - meaning it ran into a problem writing to the disc. Whilst that's unlikely to happen with Verbatim media, anything is possible and BD is such a new format that it's going to take a while for the media / firmware to reach a nice stable level.

Check with philips and see if there are any firmware updates for the drive. This is a drive/firmware/media combo issue and is nothing to do with the software as such.

and yes, try 8x or 12x. Max speed burning on crappy media is never going to end well

Don't forget to verify, it's especially important when you're having problems.

Burn at 12x and fix DMA is recommended by LOCOENG. You can read the FAQ to tell you how to do that.

Well at the moment something is blocking the proper error codes that come from the drive. You either have to update the controller drivers or roll back to olders one because the one on there now isn't working properly.

It is if you're having problems!

I'm afraid it's just an odd thing that happens with some usb drives and usb controllers. It's been going on for years and nobody ever really got to the bottom of it. Search google and you'll see what I mean.

Well they *should* be good but we've seen some really bad batches from India. Don't forget to try burning at other speeds. Your drive supports them at 2.4x, 4x, 6x and 8x. So if 2.4x isn't working (which your log shows it isn't), try 4x, 6x or 8x. If none of them work then it's a case of do you blame the Indian spindle of discs or do you just say the drive's faulty when it comes to burning DL media?

The Sony branded drives aren't actually Sony drives. That particular model is really an Optiarc AD-7200A, which in its own right is a perfectly decent drive. I personally just prefer not to buy the rebranded models because it's harder to get firmware updates - i.e. I would buy a real Optiarc AD-7200A over a Sony branded version of it. But hey, if that's all you can find (easily?) and the price is right... go for it. Oh and yes the Pioneer drives a good burners too. The difference between the 116 and 216 is that the 116 is PATA and the 216 is SATA. If that number then has a 'D' stuck on the end of it (i.e. 116D / 216D) it means it's the cheapo cutdown version and doesn't support DVD-RAM (at least not in the standard firmware).

Oh well, it was worth a shot.

Ok, time to give up and buy some Verbatims.

Get your chipset drivers from nvidia.