View previous topic :: View next topic |
Author |
Message |
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7925 Location: Salford, UK
|
Posted: Sat Jan 28, 2017 9:20 am Post subject: |
|
|
I think that you should be able to use HtmlHelp.dll in place of HHCTRL.OCX.
Please check that UPDATE@ is the name of a routine that is missing.
I am looking again at GETCL@. I will keep you posted.
Note that dbos.ins must be INCLUDEd in some 64 bit compilations that use old DBOS routines. |
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Sat Jan 28, 2017 11:39 am Post subject: |
|
|
Hi Paul,
I meant UPCASE@ instead of UPDATE@. |
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Sat Jan 28, 2017 11:47 am Post subject: |
|
|
Hi Paul,
I can't find HtmlHelp.dll in my Windows system directory. HHCTRL.OCX is existing. |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7925 Location: Salford, UK
|
Posted: Sat Jan 28, 2017 12:49 pm Post subject: |
|
|
It looks like the Microsoft documentation that refers to this DLL is incorrect and maybe the Microsoft HtmlHelp.lib is a "stub" library for hhctrl.ocx. I will log this as needing investigation.
The following code works OK for me so perhaps UPCASE@ has recently been added as an export from clearwin64.dll.
Code: | character*80 str
str = "hello"
call upcase@(str)
print*, str
end |
|
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Sat Jan 28, 2017 1:06 pm Post subject: |
|
|
Hi Paul,
is there any chance to get an intermediate version of clearwin64.dll? |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7925 Location: Salford, UK
|
Posted: Sat Jan 28, 2017 1:50 pm Post subject: |
|
|
Unfortunately the current developer version of clearwin64.dll is not entirely compatible with the last release of FTN95.
Here is a link to the most recent pre-release of the DLLs but
a) the next full release is expected very soon so perhaps you should wait
b) make sure that you backup the existing DLLs before installing the new ones from the link.
https://www.dropbox.com/s/auq9iun0eetwx4h/newDlls18.zip?dl=0
The following code will now work in the next full release...
Code: | CHARACTER*80 line
INTEGER*2 lc
CALL GETCL@(line,lc)
print*, lc
print*, ":"//trim(line)//":"
END
|
|
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Sat Jan 28, 2017 2:26 pm Post subject: |
|
|
Hi Paul,
these new DLLs lead to a message of my antivirus program:
It has found HEUR/APC (Cloud) and removed salflibc64.dll from the installation directory.
So I will restore the original dlls of FTN95 8.05. |
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Mon Jan 30, 2017 10:32 am Post subject: |
|
|
Subroutine CMNAMR seems also to be undefined to 64bit. |
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Mon Jan 30, 2017 10:54 am Post subject: |
|
|
The UPCASE problem is solved. In my project I had used CALL UPCASE as well as CALL UPCASE@. Subroutine UPCASE was known for the 32bit linker, but not for SLINK64. I have now changed everything to CALL UPCASE@. |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7925 Location: Salford, UK
|
Posted: Mon Jan 30, 2017 11:08 am Post subject: |
|
|
Does CMNAMR@ work? On my machine it is exported by clearwin64.dll. |
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Mon Jan 30, 2017 11:11 am Post subject: |
|
|
Yes, CMNAMR@ is working! |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7925 Location: Salford, UK
|
Posted: Thu Feb 23, 2017 11:29 am Post subject: |
|
|
SLINK64 has now been extended in order to accept .ocx and .drv files.
Users of version 8.10 of the compiler can download and try the new SLINK64 from...
https://www.dropbox.com/s/h415kgbt92zq5tm/Slink64.zip?dl=0
Please keep a backup of the original SLINK64.
When linking hhctrl.ocx use something like...
SLINK64
lo c:\windows\sysnative\hhctrl.ocx |
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Mon Mar 06, 2017 6:30 pm Post subject: |
|
|
I have installed the FTN95 Personal Edition 8.10 now, but SLINK64 does not accept HHCTRL.OCX:
SLINK64 D:\FORTRAN64\NETDRAW3\MAKE\NDRW_LI64.LNK
[SLINK64 v1.8, Copyright (c) Silverfrost Ltd. 2015-2017]
***SLINK64 does not know what to do with file D:\FORTRAN64\NETDRAW3\LIBRARIES64\HHCTRL.OCX
Also the following symbols are still undefined:
RELEASE_BITMAP_DC@
CLEAR_BITMAP@
FILL_RECTANGLE@
NEW_PAGE@ |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7925 Location: Salford, UK
|
Posted: Tue Mar 07, 2017 8:40 am Post subject: |
|
|
v8.10 does not include the SLINK64 that accepts .ocx files. You still need to use the download mentioned above.
The 64 bit hhctrl.ocx is normally available in the standard system folder accessed using "sysnative" as recommended above.
RELEASE_BITMAP_DC@ is in clearwin.ins
CLEAR_BITMAP@ is in clearwin.ins
FILL_RECTANGLE@ is in dbos.ins
NEW_PAGE@ is in dbos.ins |
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Tue Mar 07, 2017 9:35 am Post subject: |
|
|
In my source code I have called USE MSWIN ans I thought this would include also clearwin.ins and dbos.ins. All these functions where found with FTN95 7.xx. |
|
Back to top |
|
|
|