MikeGale wrote:I started running a test and loaded up SysInternals Process Monitor to see what is going on with file access (so that I could report more fully).
There seems to be something in the Beta that then intervenes. It shut the program and the Batch tool both. When I attempted to restart it kicked in with a message that there was a monitor running. (Message was from oreans.com, something called WinLicense.)
I've shut the monitor process and looked at running processes, it's gone as far as I can see. The oreans code still thinks it's running. Maybe it caches something! It sure seems to have it wrong.
So the Beta has stopped running altogether for me. I hope a reboot brings it back but that's not going to happen now. I'll report back later.
MikeGale wrote:I've just seen your message. Yep I'll a build without protection if that will still be valuable.
MikeGale wrote:If I last installed the Beta, which DLL is running when I use 9.03 batch tool?
Code: Select all
The problem is that those process monitors are loaded in memory till the system is restarted. That is, even if the user closes the process monitor,
the process monitor driver is still loaded in memory and that's why it's detected.
MikeGale wrote:That multiple try technique is the only one that came to mind. I'll gladly give it a try.
MikeGale wrote:The URI gave me a 404. (Tried a couple of variations, all failed.)
MikeGale wrote:It's still refusing to start because of the monitor in memory.
I'm not planning to reboot the machine soon. I'll reconsider that, but it does disrupt things.
Users browsing this forum: Yahoo [Bot] and 0 guests