2010-12-13, 07:31 AM
(2010-12-13, 06:36 AM)dmpdesign link Wrote:attached
Does the clog.txt file look right for you when you open it with Wordpad? The attached version seems mangled somehow. I can still make it out in a hex editor.
Anyway, it looks like everything is going normal, but Som itself is crashing before it even gets to reading its ini file.
SomEx goes on ahead and installs all the hooks first thing at this point, even though only the ini file read API needs to be hooked earlier than normal. So it's possible there are many other hooks being called before SomEx is properly initialized which might be causing trouble, because I hadn't even thought to look (because I haven't had any trouble)
So anyway, I will add some log stuff to the top of every hook and actually check to make sure the hooks install, though not installing shouldn't be fatal. If none of those log entries show up then there is something wrong with the hooking process itself. Which would probably be because of other something installed (or possibly not installed) on your computer.
UPDATE: I don't see anything that could possibly cause Som to crash before getting to the ini API (which doesn't show up in your clog.txt) so I'm pretty stumped. I'm attaching another SomEx.dll with some additional log information. I'm hoping there is just something stupid going on this might shed some light upon. However my guess is there is something installed on your computer that's getting in the way. So many things people install on their computers these days hook into every single process and muck around with stuff.... pretty much the same way SomEx mucks around with Som. Microsoft even provides an API for that.