LIGHTNING UK!

If that 'crappy TV/DVD combo' player is the only one you're worried about and it played ok from start to finish (without skipping anything), I guess it's safe. Otherwise you'd have to build + burn a new image tailored for a double layer disc.

If that was your point, why didn't your initial post say the button shouldn't be there when 'output' is set to 'image file' ? Just say what you mean, I'm not a mind reader. Anyway, why shouldn't it be there? It can still display graph data from a previous read/burn/verify.

Expand the error box (show details or whatever) and see what it thinks has actually gone wrong. Please just confirm it also crashes if you simply load the program and then close it down again without actually doing anything in it.

Yes, it looks amazing. I don't want it doing that though (logging it), hence why it doesn't.

You haven't done anything with an optical drive and therefore it isn't supposed to work, it's supposed to display the message that you're getting.

I have no idea.

No and no.

You weren't clear in your initial post then, I figured you were already just trying to play the ISO.

No such thing exists for Blu-ray.

It doesn't look like you've got any crash dumps. Try manually pointing it to c:\windows\memory.dmp (assuming it exists). If it doesn't, your machine is probably unable to (or set not to) record crash data. You configure all that stuff in 'Start Menu' -> Right click 'Computer' -> 'Properties' -> 'Advanced System Settings' -> 'Startup and recovery' -> 'Settings'. You also need a large enough (size of physical RAM + a bit) page file on your system / boot drive.

Mount the ISO and see if you have the same problem with it when playing from a virtual drive.

Drivers cause crashes. Try this out... http://www.nirsoft.net/utils/blue_screen_view.html

ImgBurn isn't loading/using it, it's just loading itself or being loaded by another DLL. I've also had 310.70 on (no crash on that either) but it was preventing KProbe from displaying (drawing itself) properly and I was in the middle of doing some disc tests so I reverted to 306.97.

What version of the nvidia driver are you running? I'm using 306.97 and haven't seen that problem.

If anything like that ever comes about, it'll be from the guys at the MyCE forums. Keep an eye on the NEC/Optiarc forums over there.

If the ISO jumps and the disc (burnt from the same ISO) doesn't, that sounds like an issue with VLC.

It shouldn't do, but some enclosures and chipsets don't always work very well together.... sometimes you get spurious 'semaphore period timeout' errors from them.

That'll be why I couldn't see them then The PIE/PIF scans are just rough guides. You could scan a disc with the same drive / program one minute and scan again straight after and they'd be different - not massively different, but different. If two programs are drawing very different graphs (assuming scan speed etc is equal and the differences are beyond what you'd expect between 2 individual scans), it's probably because one of them is misinterpreting the values the drive is reporting. Sometimes you can write code based around the results from one drive and they're then wrong for another 'newer' one (from the same manufacturer).

Keep an eye on the buffer during verification. If it's full, the hdd is slowing it down. If it's empty, the optical drive is slowing it down (that would be normal).

I don't see any DVDInfoPro results. In any case, stick to using Lite-On drives for scanning. CD / Disc Speed doesn't really support scanning the oversized DL discs, notice the graph actually extends beyond the end of the window - but no PIE/PIF lines are plotted.

No that I know of, no. and currently, the MCSE tool doesn't support the 1.Z7 / 1.Z8 firmware.

There's nothing I can do about the 'Invalid floating point operation.' crashes, they occur due to a bug in the development environment I'm using. You should at least be able to cut down on the number you receive by turning off 'Capture Graph Data' in the Settings.

I've never used an Optiarc for scanning - I really have no idea what their scans look like or if they're even any good at scanning full stop. I would not expect a burn from an Optiarc on that media to look like that when scanned on a Lite-On.... unless there was something wrong with the drive/media. As you aren't scanning with hardware I know or trust, I can't really comment.

You want a queue for changing the volume labels of images? Never gonna happen.

Something about your USB drive and USB chipset combo is causing the early timeout that then leads to the drive going offline. Some just don't work very well together. I don't know of any quick fix, sorry.