Hi!

Im using the NeroCOM - "NeroFiddlesCOM.NET" example to burn an Image. I took the BurnProgress Dialog from this Example to use in a C# application I have to write. The burning process itself and the generated Image are OK. But after using the BurnProgress Dialog, the Application does not close anymore. After closing the MainForm the exe still remains in the Process List of Windows. This happens with my Application and also with the Sample itself and only after burning something. Just opening the Application to get the Drives List and Information does not lead to the Problem. It seems to be something with the Progress Dialog. The Debugger of VS does not report any Problems. I checked the Code many times now and cant find the reason. Might anyone here have an idea?

Many thanks and greetings!
Remo

Oh, by the way! I cant use the Search Function of this Forum. The Dropdown disapears behind the Comercials. Im using Opera.

I just tested my Application with an older Nero Version (6.3.1.20) and I did not have this Problem. I dont know how other Version react, but it does occur with the newest.

Well, I have ecountered the same problem ( with the same version ), It seems as if this is a DeadLock of the NeroCOM DLL as upon application termination all threads hang with the unmanaged 'WaitForSingleObject', following is the stack-traces of the suspected thread as provided by WinDbg@kb:
ChildEBP RetAddr Args to Child
0012fc78 7c90e9c0 7c8025db 00000310 00000000 ntdll!KiFastSystemCallRet
0012fc7c 7c8025db 00000310 00000000 00000000 ntdll!ZwWaitForSingleObject+0xc
0012fce0 7c802542 00000310 ffffffff 00000000 KERNEL32!WaitForSingleObjectEx+0xa8
*** ERROR: Symbol file could not be found. Defaulted to export symbols for E:\Program Files\Nero\Nero 7\Core\NeroErr.dll -
0012fcf4 04117df6 00000310 ffffffff 04117f1f KERNEL32!WaitForSingleObject+0x12
*** ERROR: Symbol file could not be found. Defaulted to export symbols for E:\Program Files\Nero\Nero 7\Core\CDROM.DLL -
WARNING: Stack unwind information not available. Following frames may be wrong.
0012fd54 0501e1cc ffffffff 00000000 031687a0 NeroErr!IsWinME+0x4c
0012fd78 0501e23a 05037c30 0501e576 00000001 CDROM!CNeroErrorList:perator=+0x814c
0012fda8 0501f4fd 0501f5c0 05000000 00000000 CDROM!CNeroErrorList:perator=+0x81ba
0012fde8 7c9011a7 05000000 00000000 00000001 CDROM!CNeroErrorList:perator=+0x947d