LIGHTNING UK!

How fast something fast forwards is down to whatever player you're playing the disc on. The file system being used on the disc should have nothing to do with anything.

This could be something simple like rip lock - a feature in the drives firmware.

No, like I said above, ImgBurn just burns what you give it. If you're seeing a menu that you say wasn't there in the first place, it must be coming from your player. What sort of files are you actually burning?

ImgBurn burns exactly what you give it. So if your source file(s) don't already allow for / do that, what ends up on the disc won't do it either.

Ah, I see you have an nvidia chipset motherboard... I'm not a fan of anything non-Intel really! All I can suggest is that you try some different motherboard/chipset drivers - or possibly try to revert to the standard Microsoft ones built into Windows. You may even like to try switching your controller into AHCI mode via the BIOS and see if that makes a difference - you may need to make a quick registry edit in order to make the machine boot up in AHCI mode (do it when back in ATA/IDE mode). Try it and see.

Yeah this is a drive/firmware/media combo issue. I'm sure the LiteOn should be able to handle that MID ok. Assuming the discs are up to the normal standards expected, it could be that there's something wrong with your drive. You should probably take it up with LiteOn.

Ok, load the program again and switch to Write mode. Then right click the drive selection box and pick 'Family Tree'. Close the prompt and copy + paste the contents of the log window again please.

Try burning at 4x instead of 2.4x. If that fails, try cleaning the drive with a cleaning disc. Perhaps try with discs from another spindle (rule out a bad batch of discs). If all else fails then you have to assume your burner is at fault here. That isn't something you can fix, so you just buy a new one.

The disc is just unreadable in your drive(s). Maybe it was a low quality burn in the first place - start burning to different/better media if this keeps happening. Are they the same make/model of drive? PL05 is the latest so that isn't strictly true. http://www.firmwarehq.com/Lite-On/iHBS112%2B2/files.html

That question is covered by http://forum.imgburn.com/index.php?showtopic=12200

Read the pink box at the top of the support forum.

The ISO isn't a RAR file, you've just associated WinRAR or whatever with ISO files. Go into its settings and turn that off.

It's probably due to the controller your drive is attached to. Just copy + paste everything from the log window once it has got stuck - or if you don't have that info, just get us what's shown when you start the program.

Read the thread I linked you to. If your drive doesn't support your discs, buy a new drive or buy new discs.

You try all of the 'Supported Write Speeds' (listed in the disc info text on the right of the main window) until you find one that works. Start with the slowest.

Update the firmware on your drive. http://www.firmwarehq.com/Lite-On/DH-16AYH/files.html At the moment, it doesn't support the discs you're trying to use. That's not to say the firmware update will add support for the 'RITEK-S04-66' MID/dye, but it might do. You should also read this. http://forum.imgburn.com/index.php?showtopic=8000

Reading a disc makes use of error correction and a drive generally doesn't report success at reading a sector unless everything checks out ok.

It looks like an API command is getting stuck - and that's out of my hands. What I'd probably do here is uninstall the controller from within Device Manager and reboot (i.e. the DMA fix from the FAQ).

It's still having trouble burning to those discs. You may have more luck with the 2.4x speed Verbatim discs (MKM-001-00 MID/dye) Otherwise, it's probably new drive time.

http://forum.imgburn.com/index.php?showtopic=59&&do=findComment&comment=972

Your drive is probably 7 years old now. It may not even support the MKM-003-00 MID/dye properly. It may help if you cleaned it with a cleaning disc. Failing that, invest in a new drive.

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

IsoBuster must be lying to you. If the drive reports the logical block address you're requesting is out of range, it'll be saying that no matter which program or operating system use.

As expected, the drive won't read anything beyond 1237 as that's where it thinks the data ends.

As the following thread states, if it burns and verifies ok, you're on your own. http://forum.imgburn.com/index.php?showtopic=12200 In answer to your questions... You use whatever speed the drive does the best job at. You probably aren't in a position to know what that is (no scanning drive), so just accept that 2.4x produces a disc that verifies ok - it could be worse! Advances in the ways things are done mean that, yes, it's wrong to truncate. Do some research. No.