Cheshire Cat Computing

Which version of the source are you compiling?
I've posted v1.9.0 recently, this has a new set of source for vstudio which gets rid of many of the deprecated messages and also fixes a number of other type incompatibilities and compilation issues that come up when the 'check for 64bit compatibility' option is set.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

I think you'll need to recompile the mcrypt library in 64bit, that should get rid of the mcrypt-related problems. mcrypt is open source (its how I compiled it) so that should be OK - but I suspect I didnt ship the source for mcrypt with the package?

The linking erros with WSA and __imp_* seem to be related to the Winsock2 library function calls. Maybe they need to be defined differently under 64bit? I'll need to check to find out where they are defined in the code.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

You'll definitely need to recompile the mcrypt library (open source) for 64bit. http://sourceforge.net/project/showfile ... p_id=87941

Then make sure you're linking against the mcrypt library, and also the socket library - that should get rid of most of these messages.

Finally, the WSA* errors are Winsock functions - possibly there is a winsock library, or else these are included in the socket library. Otherwise it sounds like things have compiled and the problem is now only at linking stage.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11