LIGHTNING UK!

If your drive is having trouble burning to 'MBIPG101-R12-00' discs, use something else. http://forum.imgburn.com/index.php?showtopic=8000

Click the 'Download' link in the blue navigation bar at the top and then pick any one of the seven 'Mirror' sites that are listed (they all host the exact same download, hence the term 'Mirror').

Do you have the wavpack directshow filter installed? http://www.wavpack.com/downloads.html Details of this and other filters can be found in the Audio CD guide. http://forum.imgburn.com/index.php?showtopic=5555

Nope, the optical drive screws have a finer pitch thread. Yes, those M3 thumbscrews look like they should do the job

http://en.wikipedia.org/wiki/Computer_case_screws M3 screws for optical drives.

Stick to using those then if they work. I can't say that I have ever heard of them.

Have you tried burning at 4x? If your drive can't burn MKM-003-00 (pretty much the best DL disc available) at either of the speeds it claims to support, it's probably time to invest in a new drive.

That's to be expected. The 'auto change booktype' code will be attempting to use the Plextor command set. If you add the drive id under the LiteOn heading within the 'Advanced' section of the booktype feature, it'll use the LiteOn ones instead.

What MID were the disc you've written ok in the past? Were they RICOH instead of RITEK? If your drive won't burn the RITEK ones, you'll have to go back to what you used before - or go with the tried and tested Verbatims as mentioned above.

Please post a log - as per the pink box up the top

So if you manually try to use the LiteOn tab for the booktype stuff it fails yeah?

I normally just Google it! i.e. 'PX-891SA LiteOn' My top result then shows it's a 'LiteOn iHAS124 C' clone. Plextor haven't made their own drives for years now.

No idea, sorry.

It's probably a LiteOn drive, use that tab instead of the Plextor one.

There's a modified firmware available for the 'iHASx24 B' drives that'll let you overburn. The special Vinpower Digital 5280-CB range of drives can also do it. Free Sectors: 4,267,040 Free Space: 8,738,897,920 bytes Free Time: 948:15:65 (MM:SS:FF) Can't you just rebuild the ISO and remove something from it so it's back down to normal size?

I think you forgot the log.

During testing, it worked best with just 'Force HT' and 'Smartburn' enabled. Disable the other 2 ('Online HT' / 'Overspeed'). You can also disable 'Perform OPC Before Write'. Don't forget about service pack 1 for Windows 7.

The LTH media isn't as well supported by drives, nor as reliable. It's cheaper for a reason There's a 1.30 firmware update available for the 207M, maybe it'll help? http://www.firmwarehq.com/Pioneer/BDR-207M/files.html You could also try burning at the other speeds the drive claims to support on that MID. (i.e. 2x and 6x) Maybe it'll do a better job at one of those rather than 4x.

Don't burn from that machine then, make an image on one with decent throughput and burn from that. You could also slow the write speed down so it doesn't need it to be so fast in the first place. Buffering an entire BD-R in memory isn't an option. ImgBurn is only a 32bit app and simply cannot address that much memory.

The format is an internal drive thing, so it's just your drive having a problem with the disc and getting stuck. If you turn off file certification, it might actually finish the erase (quickly too), then you'd have to do a few full disc 'Discovery' mode burns on it to see if you can actually burn to all sectors without errors.

Ok so just open the CUE in notepad and change the last line from INDEX 01 30:32:86 to INDEX 01 30:32:74 Whoever made the file, did so incorrectly.

There's nothing to remote assist with. Have you tried with 'Force Hypertuning' enabled now that you've done the firmware mod? Like I said before, if the drive isn't playing nicely with the cheapo discs, buy the ones you're meant to be using.

Your drive is attached to an SATA port on the motherboard (hopefully!) which is connected in one way or another to an SATA controller. The drivers for that controller (or some other 3rd party driver installed on your machine) are what's messing up and causing I/O to get stuck on your system. So look for updated chipset/SATA controller drivers for your machine. If you switch to 'Write' mode within ImgBurn and right click the drive selection box, you should see a 'Family Tree' entry. Click it. Now close the prompt and copy + paste everything from the log window.

You haven't done what I told you to. If you don't want to do what I said (modifying the firmware so it burns 'RICOHJPN-D01-67' at 2.4x instead of 4x, 6x, 8x), buy the media you're supposed to be using for overburning - i.e. Verbatim discs.

ImgBurn is just an exe. If it's not running, it can't possibly be doing anything. If your drive is also reporting errors in ImgBurn, tell me what it says and maybe I'll be able to help you.