LIGHTNING UK!

This sounds like a problem with your source files / reauthoring. Assuming it's all valid/correct, ImgBurn burns exactly what you give it.

PIE and PIF levels look fine in that but the Jitter is way higher than it should be. Burn (AND verify) a disc at 8x in ImgBurn's Discovery mode and then another at 16x. Post logs from both please. Then scan them both in Opti Drive Control (@ 4x) and post screenshots.

Verify as part of the burn (check the 'Verify' box on the 'Write' mode screen), not after it. Put the read speed back up to 'Max' for data (the left box of the 2) - this has to be done on the 'Verify' mode screen. Did you actually download and take a look at Opti Drive Control? Without explaining it step by step, I pretty much told you everything you needed to do. Load it up, click the 'Disc Quality' button on the left. Change the 'Speed' box to 4x and then click the 'Start' button just below it. For the screenshot you can press the floppy disc icon at the top of the program window (or use the generic method of pressing 'Print Screen' on your keyboard and 'pasting' the picture that's now in your clipboard into something like Paint).

I see no verify log there. Don't skip it! Burn at 8x, it's a better speed. In theory, that drive should be supported by Opti Drive Control for Disc Quality scanning. Give it a try and scan the disc at 4x. Then post a screenshot of the scan. Do the new discs you say are skipping still skip if you play them on the PC? Maybe it's a problem with what you're burning.

The stuff you're burning is about 6GB in size. The disc is 8.3GB or whatever, hence the bar shows the disc is (will be) 75% full.

No idea, it's nothing to do with ImgBurn itself. A quick Google search suggests it's possibly related to DAEMON Tools.

http://lmgtfy.com/?q=Duplex+Secure%27s+SPTD+driver+can+have+a+detrimental+effect+on+drive+performance

Copy + paste into a text document (use notepad or similar) and then copy it over via the network or using a USB stick etc.

I can assure you it's not a BD burner. The iHBS112 is the BD burner, the iHES112 is what's known as a 'combo drive'. It can write to CD and DVD but only read the superior BD format.

Copy + paste the disc info from the box on the right of ImgBurn's main window. DVD Flick isn't doing anything whilst ImgBurn is open (ImgBurn does the actual burning).

The iHES112 can't burn Blu-ray discs, it can only read them.

Your drive is too old to support that MID/dye. You'd do well to buy Verbatims AND invest in a new drive.

Yup, he was on our 'Top Gear' TV show a few weeks ago talking about it.

It's not related to your hdd or where the files are stored. This is a problem between your drive, its firmware and the discs you're using. The drive might need cleaning or you could have ended up with some lower quality discs - you can never be sure when buying those 'repacked' discs - which is what I assume you're getting - from ebay or whatever? You'd need to try your discs in another of those drives, and try your drive with some other discs to perhaps narrow down where the problem is coming from.

Do you have all the updates installed for the Win 95 machine? I don't know what else you've installed but ImgBurn runs just fine for me in 95 when I try it.

That's the log rather than the disc info Disc info come from the box on the right of the main window when you're in Write mode - like what I posted above. Anyway, if the disc size is showing up correctly now then there's no problem. As to where the problem came from in the first place, I have no idea. ImgBurn just displays / uses what the drive tells it.

Post the disc info as your drive sees it now please.

It opens in whatever 'input mode' you had selected the last time you closed the app down. If it's not remembering any of your settings then you need to figure out why that is. It could be because you've told it not to or because it doesn't have permission to update the registry (or ini file if you're using that instead). This would be a global issue though, not just a problem with that one setting. You might also like to check the Settings (Tools menu) -> Events tab. There's an option on there to control the initial Build Input Mode. As for the path issue, it sounds like you've enabled 'Preserve Full Pathnames' on the Options tab. It's off by default.

The order for files burnt as a data disc comes from the name of the file - and you're in charge of that. Use double digits for all track numbers in the name and you'll be ok. ...and by that I mean 01, 02, 03... 10, 11, 12 etc.

Mine is ok with that MID. Maybe you could post your discs info too (from when you're in Write mode), so we can see what else is different? The likelyhood of your project and disc both having that exact size figure are pretty slim... so you might want to double check the discs you're using really haven't ever been put in the drive before.

It's not a driver as such, it's built into the OS - therefore, there's nothing to reinstall. Post the log of your drive failing to burn a NEW disc. The one you've posted there doesn't show/tell us what the real problem is.

Use a new disc, it looks like you've already tried and failed to burn that one.

You should run Memtest86+ for a few passes to check for memory issues. http://www.memtest.org/

Again, it doesn't sound like something ImgBurn would do. For starters, you're in Build mode by the sounds of it and there's no 'source' drive in that mode for it to remember and keep checking itself. Source drives also have to say they're 'Ready' before ImgBurn tries to access them. So what screen were you on *exactly* when this popped up? Were you in the 'Disc Layout Editor' window? Had you clicked a 'Browse for files' or 'Browse for folder' button? (which then brings up a standard windows dialog box) Had you closed and reopend the program between builds? (i.e. since you'd used the drive that had the disc in it but then didn't) Maybe you could repeat what you did before and post a screenshot of the everything on your screen when the eror pops up.

Does anything get added to the log window?