forums.silverfrost.com

KennyT · Joined: 02 Aug 2005 Posts: 318

Got a wierd one. On a client W7-64 machine, our app fails to start. Using "depends", I can see that it is trying to use the 64-bit system DLLs in "c:\windows\system32" rather than the 32-bit system DLLs in "c:\windows\sysWOW64". Is there a setting on the users machine that might cause this or anything I can change in my link to force it to pick up the correct 32-bit system libraries?

TIA

K

PaulLaidler · Posted: Mon Sep 24, 2012 7:03 pm Post subject:

It might be worth looking at the "Compatibility mode" in the Properties dialog for the executable. Right click on the exe in the Windows Explorer and select the Compatibility tab.

BILLDOWS · Joined: 22 Jul 2005 Posts: 86 Location: Swansea, UK

Please excuse a probably stupid follow-on question / observation from an engineer - not a computer scientist..

I recently tested some of my 32bit fortran/clearwin code on a W7-64 machine (Core I5) and all worked fine - I always put salflibc.dll in the program folder. I had on the memory stick in the same single folder both my programs and all the files Silverfrost needed to re-compile / link them. I did a re-compilation on the W7-64 machine and once again all was fine.

On examining the .EXE back on my W7-32 machine while file sizes were identical for all the .EXE's the content differed somewhat on a 'compare' - but they all still run fine on the W7-32 machine.

I assume this is as would be expected and that regardless of whether the compilation was on W7-32 or W7-64 the resultant code (if sound) should run on either system??

Thanks

Bill