I just resumed work on kph after an extensive down time and noticed i am have some serious problems getting it running now. The problem mentioned above is also one of them. I think its something to do with the fact I am on win7 x64... wait let me test it in my win xp x86 vm...
ok it gives me some shit in uoai.net wrapper source... says:
"A first chance exception of type 'System.Runtime.InteropServices.COMException' occurred in UOAINET.dll"
on line 43 of UOAI.cs
which reads:
"return m_UOAI.LaunchClient();"
I guess thats really vague though. I'm sure this doesn't require an explanation because Arul and you could probably extrapolate more information from that than I would, due to your familiarity with the code.
Upon further investigation I am having the exact same issue as "diff" since the latest uoai update. Can you at least post the UOAI 7.0.0.0+ code so I can debug it myself?
and if it helps, I am also getting the following error if there is already a client running when kph starts up and tries to hook it.
An error occurred creating the form. See Exception.InnerException for details. The error is: Retrieving the COM class factory for component with CLSID {C27D1F35-5001-4B97-A467-1868A5BE19A9} failed due to the following error: 800703e6.
using 2d client 7.0.4.3 (patch 80)
So based on what I know so far it's something that happens as soon as UOAI tries to hook the client, i doubt it has trouble finding the executable since that location hasn't changed so far. So the problem is definitely with UOAI, not the wrapper.
After more research I found that error means "Invalid access to memory location". So UOAI is either accessing the wrong chunk of memory when hooking due to recent changes in the client or doesn't have the right permissions. And since this error hasn't come up in the past and I see no reason for any change in method used to access the memory for the client, I would have to say you just need to update the points for UOAI to hook for 7.0.4.3.
GL and I hope I helped, unfortunately for you, (/me looks at diff), we will all have to wait for Artaxerxes to fix this stuff or post the source.
one more thing i just noticed: the client.exe opens and shows up in task manager but no gui shows up.