11/6/2011
I've been playing around with 64bit builds of Scribe on windows. And it's been er... interesting to say the least.

• By default the Visual Studio 2005 installed doesn't install the x64 compiler and libraries. Nice...
• When you do get that installed, and then create an x64 profile in your solution you get the option to copy the settings from the 32bit profile. Which for the most part works, but when you try and compile said x64 profile, you discover this delightful error:

  fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'X86'

  Which in a nutshell means you are linking 64bit objects into a 32bit binary. However the standard response that people get on the forums is that you have to set your Linker- >Advanced->TargetMachine correctly. And you know what? Well it WAS set correctly to MachineX64. So what gives? Well if you click on Linker->CommandLine and look in "Additional Options" you'll see /MACHINE:I386. Sigh.
• When running Windows7 64bit and you put additional 32bit DLL's in C:\Windows\System32 you'd think... that since there is a "32" in that folder name that is where they go. Well no... the 64bit DLL's go in System32 and the 32bit DLL's go in "System". Gaaaaahhhhh.

But at the end of the day, there it is... 64bit Scribe: