Successfully burnt disc could not be read by Explorer. Problem ?

[LIGHTNING UK!]

Yup that's perfectly normal.

 

One is the handle is used for sending the I/O stuff. The other is for disabling MCN.

 

If you have autoinsert enabled on your pc, when you close imgburn it'll take those two handles out and the OS should spring into life and attempt to read the disc.

 

The two handles are actually also closed the second you click the 'ok' button after a successful burn / verify.

They're then opened up again straight away but normally that short moment is enough time for the OS to wake up and notice a change in the drive contents.

[Defenestration]

Would it be possible to have a test build with a small delay after clicking the OK button after a successful burn to see if that helps ?

[LIGHTNING UK!]

Opening / closing of handles is pretty much as single function that's common to everything. So if I delay it within the routine, it effects the entire program. I can't just delay it after a burn or whatever.

 

It's probably easier for you to just uncheck the option to disable MCN in the settings and test it that way.

 

Having any sort of handle open via SPTI methods seems to block the OS anyway. Especially if you put the disc in when ImgBurn is already open. How the OS responds to stuff actually changes based on what's open and when.

 

You might find you have less issues using ElbyCDIO or Patin Couffin. They work quite well asynchronously.

[Defenestration]

Any other ideas on trying to track down the cause of this problem ?

[LIGHTNING UK!]

Nope, but one of the above should work anyway.

[Defenestration]

I'll give the other interfaces a go along with trying a couple of other things and post back here.

 

BTW, if I install CloneDVD and then uninstall it, will I still be left with the Elby interface or do I have to keep CloneDVD on the machine ?

[LIGHTNING UK!]

I honestly don't know myself. Try it and see!

 

No harm in it just sitting there anyway is there?

[Defenestration]

No harm in it just sitting there anyway is there?

There is if you're a busy person with very important things to do...... and then there's me, so I'll guess I'll just install it and see what happens!

[LIGHTNING UK!]

I've had a little mess around with where the 'Disable MCN' stuff kicks in, and basically moved it to the places that count rather than being active from the second the program is loaded.

 

So now it just disables it during write/verify/erase.

 

Once re-enabled at the end of a burn/verify/erase, I also refresh then drive handle (close / reopen). That makes Windows spring into action and read the drive - hence refreshing it properly. This all happens just before you click the 'ok' button to the 'operation successfully completed' messagebox.

 

It all seems to work ok on my pc, now to let the beta team have a little play.

[Defenestration]

Thanks for taking the time to look at this issue. I would rather use SPTI if possible as you've mentioned this interface is used most of the time during testing.

[LIGHTNING UK!]

Well it's been an ongoing thing since dvd dec days and since you're not the first / only person to mention it, I figured what the hell!

 

It was more important to stop the OS butting in back in dvd dec days because we'd both be trying to parse the filesystem at the same time. That made it take ages and occassionally even fail.

 

As ImgBurn doesn't have to deal with that, I see no problem on just disabling it when it really needs to.