LIGHTNING UK!

I see similar reports on Google about nvinit.dll crashing on application close - with other apps I mean. Maybe this will help? http://www.9bis.net/kitty/?action=forum&id=0320&PHPSESSID=61b4e0e814a1280363dcb6684cbbfaec

This is the only idea of yours that I don't hate. I'll think about it. Now please don't spam my forum with loads of others. You could have combined your suggestions into 1 thread, you didn't need to make 10 or whatever with 1 line in each - that just wastes my time.

Load the previous session's log when you open ImgBurn again? That'll just confuse things - so the answer is 'No'.

Beyond the scope of ImgBurn

I've no interest in LightScribe I'm afraid.

This is beyond the scope of ImgBurn.

You'd have to burn the VIDEO_TS folder/files directly to the DVD+R DL disc, you wouldn't be able to make an image first as it would know the files fit on a single layer disc and just build a single layer image. *ok, that isn't 100% true, you could adjust the single layer media size right down so it exceeds that and then builds an image for a DL disc. Just don't forget to revert the single layer media size when you're done.

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).