Recent content by PaulSp

I did. Anyway, I think I figured out what is happening. Another piece of poker software had the directory opened and apparently interfered with the update. After rebooting the handhistory directory disappears, which explains what happened last time. I just need to remember to exit the...

ok. my poker software did another update and the same thing has happened. the handhistory directory is not owned by me and I can do nothing with it. I tried the "takedown" command and got the following: ERROR: Access is denied. The last time I did this, the directory somehow had...

Yes. The PokerTracker folks say that it was done on purpose for "security" reasons. I fail to see what I could obtain from PokerTracker using procmon that would be a security problem.

No it was not a hidden directory. I tried to delete it yesterday and of course couldn't. Now I've deleted the americascardroom directory so everything is good. I just don't know what happened to make handhistory disappear. As you can see, it existed as of 12:06 AM. I don't believe I've...

The handHistory directory is gone! Very weird. So the problem has gone away... I don't understand this at all.

Searching the internet has provided other users with similar problems. According to some reports, these tools load a "kernel mode driver" which remains after the program (in this case procmon) exits. WinLicense is apparently a tool used by some developers to manage their software...

Ok. Another data point. I tried running a different program requesting privilege and didn't get the error dialog. So there must be something about the program itself (PokerTracker) that is generating this error. So unless you play poker, you're not likely to encounter this, I suspect. I will...

Ok, I ran procmon and then performed a File-> Exit. Then when I tried to run a privileged program I got the attached error.

Attached is a screenshot of a dir/q of the directory. handhistory doesn't appear to have an owner.

ok, if you say so. I will experiment further and report my results.

I will experiment a little further. It has occurred to me that perhaps I clicked the "X" to close it rather than using its "exit" function. This could possibly result in procmon not cleaning up as it should. I will post results after I try this.

I have run into an interesting situation. I have a directory that I cannot do anything with always receiving an "access denied" response. Going into the security tab of properties gives me the message "You must have read permissions to view the properties of this object". Then "click advanced...

Clearly some remnant of procmon has remained after its termination, else I wouldn't get the error that I did.

I recently downloaded the procmon tool. I've noticed that after stopping it a subsequent attempt to run a privileged program gets an error dialog saying that a system monitor is running and to remove it. This prevents the privileged program execution. Rebooting cures the problem. The two...

These entries are apparently coming from Windows Live Mail when starts. This is anecdotal.