Welcome to our forums
Morning, these calls used to work - just had to use include <dbos.ins> instead of <clearwin.ins>. But has something changed now? Thanks
__win_get_screen_block __win_restore_screen_block __win_close_vscreen __win_open_vscreen __win_vscreen_to_screen __win_create_screen_block
StamK
These routines have been removed from the latest clearwin64.dll on the assumption that they would not be used. Also the interface was not coded correctly so it was also assumed that they were not in current use.
They are very old DBOS routines but if they were actually doing something useful in your 64 bit code then they could easily be restored.
We are currently using them (but not recently tested!) so please reinstate them when you can. Thanks
StamK
Please find a link to a new set of DLLs in your forum message box.
Thanks Paul - by the way I haven't received anything in my Messages inbox yet.
We use these routines, too, however, for ftn95 version 8.70 they are unresolved when linking with slink64.
Regards, Dietmar
Arn't these F77/DBOS routines that predate FTN95 and clearwin+ ? I would think that updating to new routine names, that are documented, would be preferable.
These routines have been reinstated and new DLLs are available on request for users of v8.70.
For your information: symbols __win_get_screen_block etc. are unresolved in our compiles for the 64 bit executables (via ftn95 version 8.70) because they are contained in file **dbos.ins **and we need to include dbos.ins in special situations to get rid of other problems in our 64 bit build. We do **not **use these symbols 'directly' in our code base.
For ftn95 version 8.63 these symbols were resolved in the link step.
Dietmar
perhaps you could create dbos_64.ins with the following adjustments ! C_EXTERNAL GET_SCREEN_BLOCK@ '__win_get_screen_block'(REF,REF,REF,REF,REF) ! C_EXTERNAL RESTORE_SCREEN_BLOCK@ '__win_restore_screen_block'(REF,REF,REF,REF,REF) ! C_EXTERNAL CREATE_SCREEN_BLOCK@ '__win_create_screen_block'(REF,REF,REF,REF) ! C_EXTERNAL CLOSE_VSCREEN@ '__win_close_vscreen'() ! C_EXTERNAL OPEN_VSCREEN@ '__win_open_vscreen'(REF,REF) ! C_EXTERNAL VSCREEN_TO_SCREEN@ '__win_vscreen_to_screen'(REF,REF,REF,REF)
I think that there is something wrong here.
If a C_EXTERNAL interface is provided but not called then it should not be listed as a missing external at link time.
Sorry, my mistake, I searched for the wrong string in my last post.
We use e.g. GET_SCREEN_BLOCK@ when building a 64 bit GUI app and that's why we included dbos.ins and as a consequence __win_get_screen_block needs to be resolved.
Are the new dlls a problem?
Regards, Dietmar
There is no known problem with the new DLLs.
Have thes DBOS calls been removed from the 32 bit saflibc.dll as well? I need them!
Ian
These routines have not been removed for 32 bits and they have been restored for 64 bits.
This simple program links in 64bit but has missing symbols in 32bit winapp program dbostest include <dbos.ins> call new_page@ end I'm not expecting it to run I was only looking for the linker unresolved references.
64 bit: Compiling file: Dbostest.for Compilation completed with no errors. Linking... Creating executable file C:\Users\Ian\Documents\Projects\Debug\x64\dbostest.exe Linking completed.
32 bit: Compiling file: Dbostest.for Compilation completed with no errors. Linking... WARNING the following symbols are missing: __win_new_page C:\Users\Ian\Documents\Projects\Debug\Win32\Dbostest.obj (C:\USERS\IAN\DOCUMENTS\PROJECTS\DBOSTEST.FOR) Creating executable: Debug\Win32\dbostest.exe Linking completed.
All dlls dated 17/11/2020.
What am I doing wrong?
John,
Users Ian Documents Projects Debug Win32 also have capital letters! (and John of course)
May be an object file counts as a human and needs a capital letter and an executable is no longer human after execution!
Or may be there are some things in this world which do not have an answer!
This issue is addressed here https://forums.silverfrost.com/Forum/Topic/3966.
The deprocated calls issue, not the capitalisation variability.