search

trietptm / ospy

Automatically exported from code.google.com/p/ospy
0 stars 1 forks source link

oSpy does not support x64 OSes #10

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Load oSpy on Windows Vista Ultimate x64
2. Start oSpy, inject in to msnmsgr
3. Error shown - "Error, LoadLibraryW in remote process failed."

What version of the product are you using? On what operating system?
oSpy 1.9.6, Windows Vista Ultimate x64, Messenger 8.5

Original issue reported on code.google.com by pcj...@gmail.com on 9 Sep 2008 at 12:47

GoogleCodeExporter commented 8 years ago 
After clicking "All issues" I see that someone else has the same problem, and 
that it
is an x64 issue.

It seems a shame, this application appears to be written in .NET so with a 
little
tweaking and a build in x64 this seems possible.

Original comment by pcj...@gmail.com on 9 Sep 2008 at 10:50

GoogleCodeExporter commented 8 years ago 
Sorry, oSpy only supports x86_32 at the moment. It's not because of the UI, 
which is
.NET indeed, but the logging agent DLL that gets injected into processes to be
monitored is written in C and x86 assembly, and the assembly is currently 32-bit
only. I haven't got any 64-bit Windows OS installed so I haven't yet had the 
need or
time to port it, but if someone sends me a patch I'd be very happy. :)

Original comment by ole...@gmail.com on 10 Sep 2008 at 8:15

GoogleCodeExporter commented 8 years ago

Original comment by ole...@gmail.com on 3 Feb 2009 at 12:07

GoogleCodeExporter commented 8 years ago 
This issue makes me sad.

Original comment by ncol...@gmail.com on 19 Jun 2009 at 6:55

GoogleCodeExporter commented 8 years ago 
I've finally upgraded to Windows 7 64-bit. Expect a new oSpy release in the 
near future 
with x64 support. (I've already got it working at the alpha stage, limited to 
monitoring 32 bit processes for now.)

Original comment by ole...@gmail.com on 13 Aug 2009 at 12:14

GoogleCodeExporter commented 8 years ago

Original comment by ole...@gmail.com on 13 Aug 2009 at 12:14

GoogleCodeExporter commented 8 years ago 
About to release 1.10.0 with lots of fixes and improvements, this issue should 
now be 
fixed. (Tested it a lot on Windows7 x64 without any problems.) It's limited to 
monitoring 32 bit processes for now though, but I'm aiming to fix that in one 
of the 
next releases.

Original comment by ole...@gmail.com on 20 Aug 2009 at 12:15

GoogleCodeExporter commented 8 years ago

Original comment by ole...@gmail.com on 20 Aug 2009 at 12:15