actually, the problem is the builder running natively in 64bit on 64bit OS. Builder is written in .NET, and .NET is similar to java - it's not native machine code and its run in a virtual machine. So it runs in 32bit on 32bit OS and 64bit on 64bit OS. Problem is, the real emulator binary is an 32bit binary, and you can't simply call parts of 32bit binaries from 64bit application.
The solution is, on the other side, quite simple. There's an easy way to set a 32bit flag in the Builder .EXE file and then it will run in 32bit environment, and so that it can call the 32bit emulator library.
You need to get this utility:
http://msdn.microsoft.com/en-us/library/ms164699(VS.80).aspx
i think it's a part of some MS .NET SDKs (Visual Studio?)
I think this is the link:
http://www.microsoft.com/downloads/details...;displaylang=en
and use the parameter /32bit+, for example ""corflags /32BIT+ MyApp.exe" where MyApp.exe is the Builder binary. After you do this, everything will work fine.
and of course, the Wherigo people should be told about the issue, because they can very simply set this flag during the build process.
