forums.silverfrost.com

StamK · Joined: 12 Oct 2016 Posts: 152

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

PaulLaidler · Posted: Fri Dec 11, 2020 2:21 pm Post subject:

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.

StamK · Joined: 12 Oct 2016 Posts: 152

We are currently using them (but not recently tested!) so please reinstate them when you can. Thanks

PaulLaidler · Posted: Sat Dec 12, 2020 2:19 pm Post subject:

StamK

Please find a link to a new set of DLLs in your forum message box.

StamK · Joined: 12 Oct 2016 Posts: 152

Thanks Paul - by the way I haven't received anything in my Messages inbox yet.

DietmarSiepmann · Joined: 03 Jun 2013 Posts: 279

We use these routines, too, however, for ftn95 version 8.70 they are unresolved when linking with slink64.

Regards,
Dietmar

John-Silver · Joined: 30 Jul 2013 Posts: 1520 Location: Aerospace Valley

Paul scribe-led ...

John-Silver · Joined: 30 Jul 2013 Posts: 1520 Location: Aerospace Valley

astute observations aside, will the re-instatement 'fix' be made generally available ?
_________________
''Computers (HAL and MARVIN excepted) are incredibly rigid. They question nothing. Especially input data.Human beings are incredibly trusting of computers and don't check input data. Together cocking up even the simplest calculation ... Smile

"

JohnCampbell · Joined: 16 Feb 2006 Posts: 2505 Location: Sydney

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.

PaulLaidler · Posted: Thu Jan 21, 2021 8:21 am Post subject:

These routines have been reinstated and new DLLs are available on request for users of v8.70.

DietmarSiepmann · Joined: 03 Jun 2013 Posts: 279

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

JohnCampbell · Joined: 16 Feb 2006 Posts: 2505 Location: Sydney

perhaps you could create dbos_64.ins with the following adjustments

PaulLaidler · Posted: Thu Jan 21, 2021 2:21 pm Post subject:

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.

DietmarSiepmann · Joined: 03 Jun 2013 Posts: 279

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

PaulLaidler · Posted: Thu Jan 21, 2021 5:33 pm Post subject:

There is no known problem with the new DLLs.