LIGHTNING UK!

Sorry, no.

Tools -> Settings -> Device -> Eject Tray After.... -> Write

Have you tried with another spindle of Verbatims?

Use the drive advanced settings feature to clear opc data. Then disable the online hyper tuning option in the same area and try again. Burn the .dvd file, not the .iso.

I assume you've tried just powering the machine off and on again?!

If it's showing 2x as the write rate during the burn, there's no problem here. That world be about 8xxx KB/s for 2x BD speed. 2x DVD would be more like 28xx KB/s

ImgBurn already sets the process priority to high at the start of the burn.

You don't need to do anything for the drive you've got, the program does it automatically. Oh and of course you can only change the book type on DVD+R discs, not the DVD--R ones. Don't buy DVD-R DL discs, always get DVD+R DL instead.

If the drive works properly and supports those discs, sure. You'll have to try it and see.

If you've done everything that thread tells you to do, you're out of luck. Get yourself a decent drive that works with the media you're using.

It would help if you posted the disc info I asked for earlier. I can't suggest anything else until I know what I'm dealing with.

Read the pinned 'double layer' thread at the top of the forum and linked in the pink box at the top of the page.

Bin/cue is the only supported format for non basic/ data discs so that question is null and void for ImgBurn. By all means try a other program if you want to. If they don't analyse the tracks like ImgBurn does and write out to something other than an ISO then you might be ok. You can't damage a disc by reading it, no.

I don't know offhand which write type those 2 programs would be using by default for that task with your drive. The write type could provide a workaround for the issue but that's something you'd have to test and find out for yourself. I have no access to any hardware until next week - so I can't test things until then.

If it's getting stuck in a loop on that disc in your drive, you're out of luck.

It could be a result of burning in SAO mode or just something your drive is doing (as audio samples are offset slightly by the drive).

Copy + paste the disc info text from the box on the right when you're in Write mode please. If the program is asking you to format it, the drive is misreporting something (i.e. it doesn't understand the disc). A firmware update for the drive may fix the problem.

That is no doubt the issue here. 3rd party controllers (apart from Silicon Image chipset ones) often have problems with optical / ATAPI devices. I/O commands should either succeed or fail... they're not meant to get stuck so that's purely a driver/controller issue. I have a Z68 motherboard at home myself and that too has an (unused) Marvell controller on it (I made sure to connect my optical drives to the SATA2 ports on the Intel controller). I'll give it a spin when I next get a chance and see if mine has the same problem (with various drives). That won't be for a week or so though.

You should try burning at the remaining supported speeds if you haven't already done so. Maybe the firmware is just bad at 4x on the discs you've got. Where does it say your Verbatim discs were made? (look on the packaging) The ones from Singapore seem to be the best.

You've already been pointed in the direction of the answer/possible solutions. Making new threads asking the same question isn't going to get your a different answer. If your drive errors out during the burn then that's a problem between your drive/firmware/media combo.

Given any sort of choice, I'd never buy a slimline drive like that.

That log shows you trying reuse a disc that has previously failed. Don't do that.

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

When verifying audio data, ImgBurn doesn't compare the actual data - it's not possible due to the way the drives ofset audio samples. So all it's doing is checking the sectors are physically readable.

Here's how it works... It sorts the files in alphabetical order using their original file names (and that's probably alphabetical in character by character sense, not the 'logical' sense like in Vista+'s Explorer so 10 would come before 2 because 1 comes before 2) and then looks at each name in that sorted list and cuts so they fit in the restricted file name length (be that 8.3 or 64 characters etc). If the cut name matches one that already exists, it drops a character from the name and appends a number. That number is increased until the name is unique. The way it works is/was the standard way of doing it at the time of implementation.