/CHECK_WINIO problem(?) Compiler Version: 8.40.0

Added this option to my compile and will get a fault. Have included the crash dump here:

Runtime error from program:c:\program files (x86)\silverfrost\ftn95\ftn95.exe Run-time Error *** Error 29, Call to missing routine : ___winio_check_ex at 0x005685c5. 005684d9 do_winio_check(<ptr>structÄtree_record,enumÄlogical) [+00f1] [recur= 1] 00478abc do_function_rec(<ptr>structÄtree_record) [+019e] 005274f6 code_generator(<ref>structÄtree_ptr) [+46a7] 00537128 do_equals(<ptr>structÄtree_record) [+02c2] 005274f6 code_generator(<ref>structÄtree_ptr) [+46a7] [recur= 1] 00532182 do_if(<ptr>structÄtree_record,<ref>structÄtree_ptr) [+0281] 005274f6 code_generator(<ref>structÄtree_ptr) [+46a7] [recur= 1] 0047c5ef do_switch(<ptr>structÄtree_record) [+054c]

I checked a couple of these and they all appear to be identical.

Please check that you are using the latest version of salflibc.dll. You will need the version that goes with FTN95 v8.40. Perhaps there is a older version that is in the local folder.

Thanks, Paul. I'll do a system search and find them all!

I don't know if this is an issue, but it is a question.

In doing the system search, I found older versions of some files where I did not expect them. I wonder if this is an issue with the install?

This is what is in my FTN95 folder:

Directory of C:\Program Files (x86)\Silverfrost\FTN95

11/12/2018 12:24 PM 2,538,496 salflibc.dll

11/12/2018 12:24 PM 3,093,168 salflibc.lib 11/01/2018 09:45 AM 478,208 salflibc64.dll 03/13/2018 06:30 AM 2,562 salflibc64.lib 4 File(s) 6,112,434 bytes

while in the redist folder (from which I build my deliveries of DLL's):

Directory of C:\Program Files (x86)\Silverfrost\FTN95\redist

11/12/2018 12:24 PM 2,538,496 salflibc.dll

01/18/2018 09:52 AM 3,047,142 salflibc.lib 11/01/2018 09:45 AM 478,208 salflibc64.dll 10/30/2017 07:07 AM 2,562 salflibc64.lib

My date of 8 Jan 2018 in the redist folder was one of the test versions of the DLL.

salflibc.lib isn't part of the redist folder anymore. I am not sure why it was (puts on tin hat).

Thanks for the tin hat reference and the laugh that followed it!!

Paul, I have gone through my system and looked for all instances of the older salflibc.dll and gotten rid of them all. This included de-installing my software deliveries that included this DLL. Only the version of 12 Nov 2018 is still on my system.

And, I still cannot use the /CHECK_WINIO option. The crash is the same.

Is there some other DLL that may be the root cause?

One question: If salflibc.dll is in the registry as a registered DLL, would this be a potential cause?

The only advantage of this checking option is that you get the check done at compile time rather than run time.

So if this is the only problem then I would avoid using this option for now.

I have the same problem. Is there some way to reveal which version of salflibc.dll is being accessed? Using /VER indicates that I am using FTN 8.40.0, and I cannot immediately find any older version of salflibc.dll

Here is a link to a utility that you can use.

https://www.dropbox.com/s/hjs63upyab4r2tt/WHICH.EXE?dl=0

Just type the following from a command line (DOS box)...

which salflibc.dll

If you copy salflibc.dll to the folder where your exe resides, that version is used for preference.

The downside to this approach is that you may find old versions littering up old folders!

Eddie

which.exe confirms that I am using the latest version of salflibc.dll the error message disappears if I compile with /VER. I am compiling from within Plato.

I have managed to trace this failure to a fault in the build of the released version of FTN95. I apologise for not spotting this earlier.

/CHECK_WINIO does not work with v8.40 and users who have v8.40 and would like to use this option can download a new FTN95 via https://www.dropbox.com/s/zirhyc4d4vpea68/ftn95.exe?dl=0.

This new version includes a fix for Simon's report concerning a false error report about loss of precision.

Don't forget to keep a backup of v8.40 in case something goes wrong.