View previous topic :: View next topic |
Author |
Message |
clint
Joined: 14 Jun 2006 Posts: 37
|
Posted: Mon Jun 26, 2006 10:15 am Post subject: DOSCOM@ |
|
|
DOSCOM@ does not appear to be in FTN95. What should be used instead?
thanks
Clint |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7927 Location: Salford, UK
|
Posted: Mon Jun 26, 2006 2:49 pm Post subject: DOSCOM@ |
|
|
Clint
See if START_PROCESS@ and/or CISSUE are relevant. |
|
Back to top |
|
|
clint
Joined: 14 Jun 2006 Posts: 37
|
Posted: Wed Jun 28, 2006 2:31 am Post subject: DOSCOM@ |
|
|
Unfortunately, neither are relevant.
DOSCOM@ is used to get DOSCOM buffers for interrupt handlers.
see page 140 of the FTN77 Library reference.
What is the work around?
PS: what should be used instead of
SET_ALARM_CLOCK@
GET_MEMORY_INFO@
|
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7927 Location: Salford, UK
|
Posted: Thu Jun 29, 2006 2:03 am Post subject: DOSCOM@ |
|
|
Clint
There is no equivalent to DOSCOM@ under Win32. CODE/EDOC sequences that use DOSCOM@ must be rewritten.
Similarly there is no equivalent to SET_ALARM_CLOCK@. In ClearWin+ you can use winio@ with %dl.
Again I cannot think of an FTN95 function for GET_MEMORY_INFO@, however, in this case there will be a simple API function that you can use. |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7927 Location: Salford, UK
|
Posted: Thu Jun 29, 2006 3:10 am Post subject: DOSCOM@ |
|
|
Clint
Please note that I have corrected my last posting.
Also the Windows API GlobalMemoryStatus may be useful. |
|
Back to top |
|
|
|