New status bar?

I'm getting the message:

The procedure entry point __set_status_text could not be located in the dynamic link library C\ etc \lgotemp@.exe

Using 32-bit mode, 8.30PE and:

      WINAPP
      OPTIONS (DREAL, INTL)
      PROGRAM STATUS
      INCLUDE <WINDOWS.INS>
      COMMON IAR(10), Ihnd
      INTEGER, EXTERNAL :: StartFN
      IAR =10
      N1 = 300
      N2 = 200
      IA = WINIO@('%ca[Status bar test]&')
      IA = WINIO@('%sc&',        StartFN)
      IA = WINIO@('%gr[Black]&', N1, N2)
      IA = WINIO@('%5sb&',       IAR)
      IA = WINIO@('%lc',         Ihnd)
      END
      INTEGER FUNCTION StartFN()
      INCLUDE <WINDOWS.INS>
      COMMON IAR(10), Ihnd
      Call Set_status_Text@ (Ihnd, 0, 'Help')
      Call Set_status_Text@ (Ihnd, 1, '1')
      Call Set_status_Text@ (Ihnd, 2, '2.0')
      Call Set_status_Text@ (Ihnd, 3, '3 step')
      Call Set_status_Text@ (Ihnd, 4, '4.345')
      StartFN = 2
      END

Any ideas?

Eddie

The entry point __set_status_text is present in the SALFLIBC.DLL that came with FTN95 8.30.169, but not in the SALFLIBC.DLL of FTN95 7.20.0.

Please check if you have a mismatched version of SALFLIBC.DLL in the list of paths in %PATH%. You can, for example, use the command

WHERE SALFLIBC.DLL

Thanks Mecej4, I had checked that the path pointed at the correct Salflibc.dll, and that I did not have a local (outdated) copy, but something else is going on. I then made a local copy in the subdirectory I'm working in, and now it works. Actually looks quite nice, and is subtly different with and without the default.manifest. But why it didn't work before I can't guess. Probably because even though it was on the path, Windows has its own hidden path it checks first! Having a local copy puts it in the first place Windows looks!

Nice enhancement Paul.

Eddie