Jump to content

DosSMNotifyDD2: Difference between revisions

From EDM2
No edit summary
Ak120 (talk | contribs)
mNo edit summary
 
Line 1: Line 1:
{{Legacy
This will issue an ioctl to the registered DDs for an incoming screen event. The IOCTL that will be called is category 0x0b, function 0x41. In contrast to [[DosSMNotifyDD]], this is called directly (basically it will be called by the HARDERR.EXE daemon).
|RepFunc=
|Remarks=This page list the older version of the function for reference.
}}
This will issue an ioctl to the registered DDs for an incoming screen event. The IOCTL that will be called is category 0x0b, function 0x41. In contrast to DOSSMNOTIFYDD, this is called directly (basically it will be called by the HARDERR.EXE daemon).  


==Syntax==
==Syntax==
Line 9: Line 5:


==Parameters==
==Parameters==
; type : type of event. corresponds to the bitmap of DOSSMREGISTERDD.  
;type : type of event. corresponds to the bitmap of DOSSMREGISTERDD.
 
;newsgroup : screen group to be active next (after save)
; newsgroup : screen group to be active next (after save)  
;currsgroup : current screen group
 
; currsgroup : current screen group  


==Return Code==
==Return Code==

Latest revision as of 05:29, 9 November 2018

This will issue an ioctl to the registered DDs for an incoming screen event. The IOCTL that will be called is category 0x0b, function 0x41. In contrast to DosSMNotifyDD, this is called directly (basically it will be called by the HARDERR.EXE daemon).

Syntax

DOSSMNOTIFYDD2(short type,short newsgroup,short currsgroup)

Parameters

type
type of event. corresponds to the bitmap of DOSSMREGISTERDD.
newsgroup
screen group to be active next (after save)
currsgroup
current screen group

Return Code

APIRET16 Pascal far