locked chm file.
-
Hi All, Hopefully someone can help me, if possible :) I have a problem with a locked chm file (htmlhelp file), it is launched from a printer driver so the process thats handling it is the explorer.exe, so when the help file is closed, explorer.exe still has a handle to the file. If I manual close the handle, using process explorer, then replace the file the html help window does not display the content. If I kill teh explorer.exe process and relaunch everything works OK. I believe the problem is due to the hhctrl.ocx not being unloaded until explorer.exe is closed and restarted, is there a way to unload hhctrl.ocx without killing the explorer.exe? Thanks!
-
Hi All, Hopefully someone can help me, if possible :) I have a problem with a locked chm file (htmlhelp file), it is launched from a printer driver so the process thats handling it is the explorer.exe, so when the help file is closed, explorer.exe still has a handle to the file. If I manual close the handle, using process explorer, then replace the file the html help window does not display the content. If I kill teh explorer.exe process and relaunch everything works OK. I believe the problem is due to the hhctrl.ocx not being unloaded until explorer.exe is closed and restarted, is there a way to unload hhctrl.ocx without killing the explorer.exe? Thanks!
Likely not - I believe that once a DLL is loaded into a process, unloading it is not possible (normally). How about this - instead of opening the file itself, try copying it to a temp location and open the copy instead. After having it opened, open/close it again (via code) with the
DELETE_ON_CLOSEflag and the file should clean itself up when it is finally closed. Peace!-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles -
Likely not - I believe that once a DLL is loaded into a process, unloading it is not possible (normally). How about this - instead of opening the file itself, try copying it to a temp location and open the copy instead. After having it opened, open/close it again (via code) with the
DELETE_ON_CLOSEflag and the file should clean itself up when it is finally closed. Peace!-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles