While trying to debug my code and monitoring file access, I noticed the first thing the compiled program does is look for RICHED20.DLL in the current directory. I'm not using any windows/gadgets at all but thinking this may be something to do with PB's debugger I put a copy of RICHED20.DLL in the directory. Now if I run my prog in debug mode there are a lot of accesses to this dll plus (possibly) a scan of the current directory. There does not appear to be any change to the debug window. Any idea what's going on?
Figured it out It's just a regular attempt to access a dll in the local path before checking system paths for it. What threw me is I had a filter on the file monitor to show accesses to my dev dir only.