Paul:

Thanks for the response.

I tried to download the 32 bit IVF, but we have had power outages all afternoon, but I just got it. I took off the X64 and loaded both back on. (Steve this is not beta, this is real Fortran)

Considering the various sources for this program , my own poor windows skills it is a wonder it runs at all, well actually it only runs because of much kind help here over the last few years.

It compiled and ran in 32 bit, so I need to go slowly through all of the calls and check the types against the IFWINTY module and the interfaces for the subroutines. It is not a trivial exercise, pretty much like writing it for the first time.

I am going to integrate the program into a 2012 SQL Server database using the German SQL Fortran routines, I am hoping they arrive tomorrow. Accountant type says they have paid for them, so fingers crossed. Out IT types do not like SQL Server.

Should be a lot of fun.

JMN

Dear Steve:

It has taken a while to get a small windows program that runs nicely and will start me to do some real Fortran programming, whilst feelling slightly younger than a DEC 32 computer. I have it running under 32 bit as noted above, but there are a few quirky errors which I was wondering if you would look at in 64 bit compiler to tell me I am at least headed in the right and true path.

This program comes from many sources, including great help by Anthony Richards, Petzold's book, the great CVF book by Lawrence and yourself. I am not sure how many copyright owenreships I am breaching by putting the code here, but I am happy if anyone wants to try it, if there are errors please let me know.

PS: The code has source control embedded, just ignore it.
PS1:I chose the colour as tribute to Trapper John who wanted a Robin's egg blue convertible.

JMN

Lorri:

It is ok, you are talking to a third string man, so you are still in front.

Yes, the warnings are interesting, but the error had me stuck.

As I liberated the code as I went I was hoping to put it back onto this site so other third stringers like me had a model that worked in IVF modern instead of CVF Olde Englishe for a simple Windows program that works in Fortran. It is not pretty, it could be turned into modules, but it doth worketh. Slowly like me.

thanks
JMN.

function HiWord (param)

import

integer(WORD) :: HiWord

!DEC$ ATTRIBUTES DEFAULT :: HiWord

!DEC$ IF DEFINED(_M_IX86)

!DEC$ ATTRIBUTES STDCALL, ALIAS : '_HiWord@4' :: HiWord

!DEC$ ELSE

!DEC$ ATTRIBUTES STDCALL, ALIAS :  'HiWord'   :: HiWord

!DEC$ ENDIF

integer(DWORD) param

end function HiWord

end interface

interface !lib=ifwin.lib

function LoWord (param)

import

integer(WORD) :: LoWord

!DEC$ ATTRIBUTES DEFAULT :: LoWord

!DEC$ IF DEFINED(_M_IX86)

!DEC$ ATTRIBUTES STDCALL, ALIAS : '_LoWord@4' :: LoWord

!DEC$ ELSE

!DEC$ ATTRIBUTES STDCALL, ALIAS :  'LoWord'   :: LoWord

!DEC$ ENDIF

integer(DWORD) param

end function LoWord

end interface

Dear Annalee:

I am not the world's best on pointers and such, but for the warning the LOWORD macro is defined with DWORD and LONG_PTR, in IFWINTY, LONG_PTR is variable but DWORD is fixed at 4. So it works at 32 but gives warning at 64, whereas there is a DWORDLONG, so why not use it?

Or am I completly lost?

JMN

Dear Repeat Offender:

Thank you for the comments. This is probably the most useful set from the Lawrence book, I am happy to fix it, just need to learn the X64 pointer stuff. Actually hating pointers does not help, but I will try.

Yes I know it is a long slog, it was a long slog to get this working in 32 as I had to learn Windows and C, whilst going deeply into the Fortran include files, and it was a long slog to get a Windows Driver to compile in Visual Studio 2010 instead of the WDK compilers, so now I can attach blinking lights to my programs to tell me there are high pressures in a system without having to look at the data.

I created a searchable PDF of all of the Fortran include files so I could get this working in 32 and then lost it. Looks like I am doing it again.

Thanks again.

JMN