> When setting the directories for the Platform SDK for Windows Server
> 2003 R2, I originally clicked on the Start Menu Shortcut "Register PSDK
> Directories with Visual Studio".
>
> This had the effect of corrupting my VC++ 2003 directory entries. So
> for VC6, I did it manually. ie. select Tools, then Options, then
> Directories, then
> set appropriate directories at the top of the list, as per your
> installation.

I tried the above (with minor differences), and it seems to work.

It produced what looks like a Portable Executable 64, although it has dependencies on a number of what look like 32 bit dll e.g. kernel32.dll

This is hardly surprising, given that the project includes the following object modules:-

kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib

This highly experimental version is available from:-
http://binnie.id.au/Downloads/TFC64.zip

The good news is that the SDK did not clobber the existing (I did this on an old sacrificial machine), but, as expected, I was no longer able to compile 32 bit versions, and got the following error : fatal error LNK1112: module machine type 'AMD64' conflicts with target machine type 'X86'