Jump to content

New pages

New pages
Hide registered users | Show bots | Show redirects
(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)

25 July 2025

20 July 2025

  • 06:1606:16, 20 July 2025 KME8OS2.SYS (hist | edit) [1,142 bytes] Martini (talk | contribs) (Created page with "This is enabler for the supplied Interface Card. This file should be located after the Card manager(PCMCIA.SYS, IBM2SS01.SYS) in the CONFIG.SYS file and the following options are available. ==Parameters== ;/nobeep :Setting this option to turn off the beep sound that is generated when inserting or removing the supplied Interface card. ;/v :If you set this option, the following message will appear when starting the computer. +--------------------------------------...")

17 July 2025

12 July 2025

  • 00:3900:39, 12 July 2025 DEVESC SETUPBLITTERNOTIFY (hist | edit) [1,994 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_SETUPBLITTERNOTIFY}} GreEscape DEVESC_SETUPBLITTERNOTIFY is called by EnDIVE users to indicate whether the hardware can support the current image blitting parameters. ;Simulation support: None. ==Syntax== GreEscape(hdc, ICODE, lInCount, pbInData, plOutCount, pbOutData); ==Parameters== ;''hdc'' (HDC) - input: Device context handle. ;''ICODE'' (LONG) - input: DEVESC_SETUPBLITTERNOTIFY escape code. ;''lInCount'' (LONG) - input: Number...")
  • 00:3800:38, 12 July 2025 DEVESC SETMODE (hist | edit) [2,419 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_SETMODE}} GreEscape DEVESC_SETMODE sets the printer into a particular mode. ;Simulation support: This function is mandatory for hardcopy drivers, but may simply return a DEVESC_NOTIMPLEMENTED code. For other drivers, it is simulated by a handling routine in the graphics engine. ==Syntax== GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Parameters== ;''hdc'' (HDC) - input: Device context handle. ;''l...")
  • 00:3600:36, 12 July 2025 DEVESC SETJOBPROPERTIES (hist | edit) [17,920 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_SETJOBPROPERTIES}} GreEscape DEVESC_SETJOBPROPERTIES writes the specified job property types and values into the job properties structure that is passed in. ;Simulation support: This function is mandatory for all drivers and must be implemented in order to have a valid OS/2 hardcopy driver. ==Syntax== GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Parameters== ;''hdc'' (HDC) - input: Device context...")
  • 00:3400:34, 12 July 2025 DEVESC REGISTER (hist | edit) [1,699 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_REGISTER}} GreEscape DEVESC_REGISTER is called by EnDIVE users to register and unregister use with the driver. ;Simulation support: None. ==Syntax== GreEscape(hdc, ICODE, lInCount, pbInData, plOutCount, pbOutData); ==Parameters== ;''hdc'' (HDC) - input: Device context handle. ;''ICODE'' (LONG) - input: DEVESC_REGISTER escape code. ;''lInCount'' (LONG) - input: Number of bytes pointed to by pbInData. ;''pbInData'' (PBYTE) - inp...")
  • 00:3300:33, 12 July 2025 DEVESC RAWDATA (hist | edit) [2,791 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_RAWDATA}} GreEscape DEVESC_RAWDATA sends device-specific data directly to the spooler or device. ;Simulation support: This function is mandatory for hardcopy drivers and must be implemented in order to have a valid OS/2 hardcopy driver. For other drivers, it is simulated by a handling routine in the graphics engine. ==Syntax== GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Parameters== ;''hdc'' (HDC...")
  • 00:1900:19, 12 July 2025 DEVESC QUERYVIOCELLSIZES (hist | edit) [3,638 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_QUERYVIOCELLSIZES}} GreEscape DEVESC_QUERYVIOCELLSIZES obtains the details of the VIO cell sizes supported by the presentation driver. ;Simulation support: This function is mandatory for display drivers. For other drivers, it is simulated by a handling routine in the graphics engine. ==Syntax== GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Parameters== ;hdc (HDC) - input: Device context handle. ;lE...")
  • 00:1200:12, 12 July 2025 DEVESC QUERYSIZE (hist | edit) [12,177 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_QUERYSIZE}} GreEscape DEVESC_QUERYSIZE queries the size of memory (in bytes) required for the corresponding list of specified job property types. Refer to Dynamic Job Properties for related information. ;Simulation support: This function is mandatory for all drivers and must be implemented in order to have a valid OS/2 hardcopy driver. ===Syntax=== GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ===GreEsca...")
  • 00:0700:07, 12 July 2025 DEVESC QUERYJOBPROPERTIES (hist | edit) [23,639 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_QUERYJOBPROPERTIES}} '''GreEscape DEVESC_QUERYJOBPROPERTIES''' queries the specified job property types and values inside the job properties structure that is passed in. Refer to Dynamic Job Properties for related information. ;Simulation support: This function is mandatory for all drivers and must be implemented to have a valid OS/2 hardcopy driver. Refer to Dynamic Job Properties for related information. ==Syntax==  GreEscape(hdc, l...")
  • 00:0500:05, 12 July 2025 DEVESC QUERYFB (hist | edit) [1,488 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_QUERYFB}} '''GreEscape DEVESC_QUERYFB''' is called by EnDIVE users to get information describing the characteristics of the frame buffer. ;Simulation support: None. ==Syntax==  GreEscape(hdc, ICODE, lInCount, pbInData, plOutCount, pbOutData); ==Parameters== ;''hdc'' (HDC) - input: Device context handle. ;''ICODE'' (LONG) - input: DEVESC_QUERYFB escape code. ;''lInCount'' (LONG) - input: Zero (0). ;''pbInData'' (PBYTE) - in...")

11 July 2025

  • 23:5723:57, 11 July 2025 DEVESC QUERYESCSUPPORT (hist | edit) [2,417 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_QUERYESCSUPPORT}} GreEscape DEVESC_QUERYESCSUPPORT queries whether a particular escape code is implemented by the presentation driver. The presentation driver returns DEV_OK if the specified escape is supported. Refer to Dynamic Job Properties for related information. ;Simulation support: This function is mandatory for all drivers and must be implemented in order to have a valid OS/2 hardcopy driver. ==Syntax==  GreEscape(hdc, lEscape, cInCo...")
  • 23:5623:56, 11 July 2025 DEVESC NEXTBAND (hist | edit) [3,098 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_NEXTBAND}} '''GreEscape DEVESC_NEXTBAND''' indicates that there is no more data for the current band, and gets the coordinates of the next band. If there is no current band, the handling routine returns the coordinates of the first band. ;Simulation support: This function is mandatory for hardcopy drivers, but may simply return a DEVESC_NOTIMPLEMENTED code. For other drivers, it is simulated by a handling routine in the graphics engine. ==Synt...")
  • 23:5323:53, 11 July 2025 DEVESC NEWFRAME WPROP (hist | edit) [5,189 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_NEWFRAME_WPROP}} Based on the new job properties that are passed in, '''GreEscape DEVESC_NEWFRAME_WPROP''', will reset the device context information and presentation space information. This action should be equivalent to the result of a new DevOpenDC with the new job properties. Refer to Dynamic Job Properties for related information. ;Simulation support: This function is mandatory for hardcopy drivers and must be implemented in order to have...")
  • 23:5023:50, 11 July 2025 DEVESC NEWFRAME (hist | edit) [2,750 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_NEWFRAME}} '''GreEscape DEVESC_NEWFRAME''' indicates that there is no more data for the current page. ;Simulation support: This function is mandatory for hardcopy drivers and must be implemented in order to have a valid OS/2 hardcopy driver. For other drivers, it is simulated by a handling routine in the graphics engine. ==Syntax==  GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Parameters== ;''hdc'...")
  • 23:4923:49, 11 July 2025 DEVESC HWREQUEST (hist | edit) [1,831 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_HWREQUEST}} '''GreEscape DEVESC_HWREQUEST''' is called by EnDIVE users to take advantage of enhanced acquire functions. In addition to performing the same serialization functions, GreEscape DEVESC_HWREQUEST lets each using process find out if its video memory buffer has been relocated or if system memory could not be allocated. ;Simulation support: None. ==Syntax==  GreEscape(hdc, ICODE, lInCount, pbInData, plOutCount, pbOutData); ==Paramet...")
  • 23:4723:47, 11 July 2025 DEVESC GETSCALINGFACTOR (hist | edit) [3,116 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_GETSCALINGFACTOR}} '''GreEscape DEVESC_GETSCALINGFACTOR''' gets the incremental scaling factors for the (X,Y) axes of a hardcopy device. ;Simulation support: This function is mandatory for hardcopy drivers, but may simply return a DEVESC_NOTIMPLEMENTED code. For other drivers, it is simulated by a handling routine in the graphics engine. ==Syntax==  GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Par...")
  • 23:4623:46, 11 July 2025 DEVESC GETJOBID (hist | edit) [2,498 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_GETJOBID}} '''GreEscape DEVESC_GETJOBID''' (8160L) is called by an application to get the spooler job ID, print queue name, and print server name for the job the application is spooling. This escape is not metafiled and is allowed only when printing OD_QUEUED. ;Simulation support: This function is optional for hardcopy drivers. ==Syntax==  GreEscape(lInCount, pbInData, plOutCount, pbOutData); ==Parameters== ;''lInCount'' (LONG) - input: Not...")
  • 23:4523:45, 11 July 2025 DEVESC GETCP (hist | edit) [2,698 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_GETCP}} '''GreEscape DEVESC_GETCP''' gets a hardcopy data stream that would set the specified code page in the hardcopy device. '''Note:''' This escape code is used only by hardcopy drivers with built-in fonts. ;Simulation support: This function is mandatory for hardcopy drivers, but may simply return a DEVESC_NOTIMPLEMENTED code. For other drivers, it is simulated by a handling routine in the graphics engine. ==Syntax==  GreEscape(hdc, lEscape,...")
  • 23:4223:42, 11 July 2025 DEVESC GETAPERTURE (hist | edit) [2,649 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_GETAPERTURE}} GreEscape DEVESC_GETAPERTURE ;Simulation support: This function is mandatory for display drivers supporting software motion video. For other drivers, it is simulated by a handling routine in the graphics engine. ;Description: '''GreEscape DEVESC_GETAPERTURE''' returns the size and physical address of the video aperture. For example, it would return "0A000h" and "64KB" for most Super VGA adapters. Care must be taken to determine i...")
  • 23:3423:34, 11 July 2025 DEVESC FLUSHOUTPUT (hist | edit) [2,298 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_FLUSHOUTPUT}} GreEscape DEVESC_FLUSHOUTPUT flushes any output received for the current document. ;Simulation support: This function is mandatory for hardcopy drivers, but may simply return a DEVESC_NOTIMPLEMENTED code. For other drivers, it is simulated by a handling routine in the graphics engine. ==Syntax== GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Parameters== ;''hdc'' (HDC) - input: Device...")
  • 23:3123:31, 11 July 2025 DEVESC EXTQUERY (hist | edit) [2,598 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_EXTQUERY}} GreEscape DEVESC_EXTQUERY is called by EnDIVE users to get information describing the characteristics of the motion video accelerator. ;Simulation support: None. ==Syntax== GreEscape(hdc, ICODE, lInCount, pbInData, plOutCount, pbOutData); ==Parameters== ;''hdc'' (HDC) - input: Device context handle. ;''ICODE'' (LONG) - input: DEVESC_EXTQUERY escape code. ;''lInCount'' (LONG) - input: Zero (0). ;''pbInData'' (PBYTE)...")
  • 23:2923:29, 11 July 2025 DEVESC EXTPUT (hist | edit) [3,356 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_EXTPUT}} GreEscape DEVESC_EXTPUT is called by EnDIVE users to copy an image to the screen. ;Simulation support: None. ==Syntax== GreEscape(hdc, ICODE, lInCount, pbInData, plOutCount, pbOutData); ==Parameters== ;''hdc'' (HDC) - input: Device context handle. ;''ICODE'' (LONG) - input: DEVESC_EXTPUT escape code. ;''lInCount'' (LONG) - input: Number of bytes pointed to by pInData. ;''pbInData'' (PBYTE) - input: Pointer to IMAGEPAC...")
  • 23:2823:28, 11 July 2025 DEVESC EXTGET (hist | edit) [1,956 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_EXTGET}} GreEscape DEVESC_EXTGET is called by EnDIVE users to copy an image from the screen to system memory or to off-screen video memory. ;Simulation support: None. ==Syntax== GreEscape(hdc, ICODE, lInCount, pbInData, plOutCount, pbOutData); ==Parameters== ;''hdc'' (HDC) - input: Device context handle. ;''ICODE'' (LONG) - input: DEVESC_EXTGET escape code. ;''lInCount'' (LONG) - input: Number of bytes pointed to by pbInData. ;''p...")
  • 23:2623:26, 11 July 2025 DEVESC ENDDOC (hist | edit) [2,923 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_ENDDOC}} GreEscape DEVESC_ENDDOC ends the current document. ;Simulation support: This function is mandatory for hardcopy drivers and must be implemented in order to have a valid OS/2 hardcopy driver. For other drivers, it is simulated by a handling routine in the graphics engine. ==Syntax== GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Parameters== ;''hdc'' (HDC) - input: Device context handle. ;'...")
  • 23:2523:25, 11 July 2025 DEVESC DRAFTMODE (hist | edit) [3,283 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_DRAFTMODE}} GreEscape DEVESC_DRAFTMODE sets draft (text) mode ON or OFF. ;Simulation support: This function is mandatory for hardcopy drivers, but may simply return a DEVESC_NOTIMPLEMENTED code. For other drivers, it is simulated by a handling routine in the graphics engine. ==Syntax== GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Parameters== ;''hdc'' (HDC) - input: Device context handle. ;''lEsc...")
  • 23:2323:23, 11 July 2025 DEVESC DEFAULTJOBPROPERTIES (hist | edit) [7,924 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_DEFAULTJOBPROPERTIES}} GreEscape DEVESC_DEFAULTJOBPROPERTIES resets (or defaults) the specified job property types inside the job properties structure that is passed in. ;Simulation support: This function is mandatory for all drivers and must be implemented in order to have a valid OS/2 hardcopy driver. ==Syntax== GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Parameters== ;''hdc'' (HDC) - input: De...")
  • 23:2123:21, 11 July 2025 DEVESC DEACQUIREFB (hist | edit) [2,233 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_DEACQUIREFB}} GreEscape DEVESC_DEACQUIREFB releases the internal Presentation Manager driver resources acquired by DEVESC_ACQUIREFB. ;Simulation support: This function is mandatory for display drivers supporting software motion video. For other drivers, it is simulated by a handling routine in the graphics engine. ==Syntax== GreEscape(hdc, lCode, lInCount, pbInData, plOutCount, pbOutData); ==Parameters== ;''hdc'' (HDC) - input: Device contex...")
  • 23:1923:19, 11 July 2025 DEVESC DBE FONTMANAGEMENT (hist | edit) [3,162 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_DBE_FONTMANAGEMENT}} GreEscape DEVESC_DBE_FONTMANAGEMENT is the entry point to sub-functions to support DBCS device font. ;Simulation support: NONE. This function is mandatory for display drivers supporting the Double-Byte Character Set (DBCS). For other drivers, DEVESC_NOTIMPLEMENTED should be returned. ==Syntax== GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Parameters== ;''hdc'' (HDC) - input: D...")
  • 23:1823:18, 11 July 2025 DEVESC CHAR EXTRA (hist | edit) [2,739 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_CHAR_EXTRA}} GreEscape DEVESC_CHAR_EXTRA changes the width of all characters, including the break character on a hardcopy device. ;Simulation support: This function is mandatory for hardcopy drivers, but may simply return a DEVESC_NOTIMPLEMENTED code. For other drivers, it is simulated by a handling routine in the graphics engine. ==Syntax== GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Parameters== ;'...")
  • 23:1723:17, 11 July 2025 DEVESC BREAK EXTRA (hist | edit) [2,769 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_BREAK_EXTRA}} GreEscape DEVESC_BREAK_EXTRA changes the width of the break character on a hardcopy device. ;Simulation support: This function is mandatory for hardcopy drivers, but may simply return a DEVESC_NOTIMPLEMENTED code. For other drivers, it is simulated by a handling routine in the graphics engine. ==Syntax== GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Parameters== ;''hdc'' (HDC) - input...")
  • 23:1523:15, 11 July 2025 DEVESC ACQUIREFB (hist | edit) [3,382 bytes] Martini (talk | contribs) (Created page with "{{DISPLAYTITLE:DEVESC_ACQUIREFB}} GreEscape DEVESC_ACQUIREFB reserves a video adapter by acquiring the necessary internal Presentation Manager driver resources so that the calling routine has sole access to the video frame buffer and bank-switching registers. No use of the adapter by the Presentation Manager or any other process is allowed while the adapter is reserved. ;Simulation support: This function is mandatory for display drivers supporting software motion video....")
  • 23:0723:07, 11 July 2025 DEVESC ABORTDOC (hist | edit) [4,182 bytes] Martini (talk | contribs) (Created page with "GreEscape DEVESC_ABORTDOC ends the current document. ;Simulation support: This function is mandatory for hardcopy drivers and must be implemented in order to have a valid OS/2 hardcopy driver. For other drivers, it is simulated by a handling routine in the graphics engine. ==Syntax== GreEscape(hdc, lEscape, cInCount, pInData, pcOutCount, pOutData, pInstance, lFunction); ==Parameters== ;''hdc'' (HDC) - input : Device context handle. ;''lEscape'' (LONG) - inp...")

30 June 2025

  • 22:3822:38, 30 June 2025 Valery Sedletskiy (hist | edit) [218 bytes] Martini (talk | contribs) (Created page with "Goes by "valerius" on IRC. ==Articles== * L4 microkernel as the basis of the OS kernel [https://ru2-halfos-ru.translate.goog/core/articles/core003.html?_x_tr_sch=http&_x_tr_sl=ru&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp (Google Translate)] * Approaches to Designing an Operating System Kernel [https://ru2-halfos-ru.translate.goog/core/articles/core001.html?_x_tr_sch=http&_x_tr_sl=ru&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp (Google Translate] ==Software== * FAT32 * VirtualBox...") originally created as "Valery Valerius"

17 June 2025

14 June 2025

  • 06:1806:18, 14 June 2025 Peter Norton (hist | edit) [768 bytes] Ak120 (talk | contribs) (Created page with "Peter Norton (* 1943) ==Publications== * Robert Lafore; Peter Norton: ''Peter Norton’s Inside OS/2'' – Brady 1988, ISBN 0-13-467895-8 * Peter Norton; Richard Wilton: ''The New Peter Norton Programmer's Guide to the IBM PC and PS/2'' - Microsoft Press 1988, ISBN 1-55615-131-4 * Peter Norton, Paul Yao: ''Peter Norton's Windows 3.0 Power Programming Techniques'' - Bantam Books 1990, ISBN 0-553-34940-6 {{DEFAULTSORT:Norton, Peter}} Category:Author")

13 June 2025

9 June 2025

  • 04:2004:20, 9 June 2025 SBPCD2.SYS (hist | edit) [75 bytes] Martini (talk | contribs) (Created page with "Sound Blaster Pro's CD driver. Example: DEVICE=C:\OS2\SBPCD2.SYS /P:240")
  • 01:0701:07, 9 June 2025 MMProgRef - Data Types (hist | edit) [4,120 bytes] Martini (talk | contribs) (Created page with "{{MMProgRef}} This section describes data types in C language. A data type name beginning with "P" (for example, PMCI_CONNECTOR_PARMS) is likely to be a pointer to another data type (in this instance, MCI_CONNECTOR_PARMS). If no data type definition can be found in this section for a data type name "Pxxxxxx," it becomes a pointer to the data type "xxxxxx," for which a definition should be found in this section. The implicit type definition needed for such a pointer "Pxxx...")
  • 01:0501:05, 9 June 2025 MMProgRef - SHC Messages (hist | edit) [3,064 bytes] Martini (talk | contribs) (Created page with "{{MMProgRef}} Stream handler command messages are provided by each stream handler in the Sync/Stream subsystem. Stream handlers can be DLLs or device drivers. All SHC messages are synchronous and must be provided by both DLL stream handlers (as a DLL call) and by device driver stream handlers as an inter-device driver communication (IDC) call. SHC messages are issued only from the Sync/Stream Manager and are not used directly by an application media control device. The...")
  • 01:0401:04, 9 June 2025 MMProgRef - SHD Messages (hist | edit) [748 bytes] Martini (talk | contribs) (Created page with "{{MMProgRef}} The stream handler device (SHD) messages are provided by a stream handler through a single entry point, SHDEntryPoint, to a physical device driver. For this interface, all pointers are 16:16 pointers; this enables the current 16-bit device-driver model to be used for stream handlers. There are two SHD messages. The message number must be used in the ulFunction field, of the parameter structure passed in the call, to indicate which message is being requested...")
  • 01:0001:00, 9 June 2025 VSDEntry (hist | edit) [2,469 bytes] Martini (talk | contribs) (Created page with "This entry point enables communication between vendor-specific drivers (VSDs) and an application such as the user-level audio stream handler or amplifier mixer. For audio VSDs, be sure to define INCL_AUDIO_VSD before including the VSDCMDS.H header file. ==Syntax== VSDEntry(hvsd, ulFunc, ulFlags, pRequest) ==Parameters== ;''hvsd'' (HVSD) - input :This parameter is the handle to the VSD instance. ;''ulFunc'' (ULONG) - input :The VSD command to be issued. The following...")
  • 00:5700:57, 9 June 2025 VSD DDCMD (hist | edit) [2,296 bytes] Martini (talk | contribs) (Created page with "Stream handlers can communicate with their attached devices using the VSD_DDCMD calls. The DDCMD interface is the primary method of moving data to and from devices in OS/2 multimedia. This command is sent using VSDEntry as follows: VSDEntry(hvsd, ulFunc, ulFlags, pRequest) hvsd (HVSD) Handle to a VSD instance. ulFunc (ULONG) Set to VSD_DDCMD. ulFlags (ULONG) The following flags (subcommands) are defined for this command:...")
  • 00:5600:56, 9 June 2025 MMProgRef - VSD Commands (hist | edit) [1,076 bytes] Martini (talk | contribs) (Created page with "{{MMProgRef}} The vendor-specific driver (VSD) interface is a generic device-driver like interface that effectively decomposes the high-level media control interface functions into more fundamental operations. The VSD layer resides in Ring 3 and provides a low-level function set that can keep pace with demanding data control and transport requirements. A Ring 3 stream handler can use the VSD_DDCMD command (described in this section) for data transportation. For this...")
  • 00:5400:54, 9 June 2025 MMProgRef - DDCMD Messages (hist | edit) [1,769 bytes] Martini (talk | contribs) (Created page with "{{MMProgRef}} The device driver commands are an interface used by a stream handler to communicate with a physical device driver. This interface uses the inter-device driver communication (IDC) mechanism provided by OS/2 AttachDD DevHelp. The stream handler must attach to the device driver using AttachDD DevHelp to receive the DDCMD entry point address of the device driver. This must be done prior to issuing any DDCMDs. Some device drivers also might require that a DosOpe...")
  • 00:5100:51, 9 June 2025 MMProgRef - SMH Messages (hist | edit) [2,649 bytes] Martini (talk | contribs) (Created page with "{{MMProgRef}} The Sync/Stream Manager helper (SMH) messages, provided by the Sync/Stream Manager, are used by all stream handlers to do the following. * Register with the Sync/Stream Manager. * Report events and synchronization pulses to the Sync/Stream Manager. * Request or return buffers to the Sync/Stream Manager. The SMH messages are synchronous calls and available to both DLL stream handlers (as a DLL call) and to device driver stream handlers (as an IDC call). T...")
  • 00:4800:48, 9 June 2025 MMProgRef - Data Stream State Table (hist | edit) [1,861 bytes] Martini (talk | contribs) (Created page with "The following table identifies the data stream states during which a call to certain SPI functions returns an error to the application. Key: ;E:Function returns an error. ;OK:Function can be called. ;N/A:Not applicable. {| class="wikitable" ! SPI Function !! Running State !! Paused State !! Stopped State !! Flush Pending State !! Discard Pending State !! Destroy Pending State !! Pre-rolling State !! Pre-rolled State |- | SpiAssociate || E || E || OK || E || E || E ||...")
  • 00:4600:46, 9 June 2025 MMProgRef - SPI Functions (hist | edit) [1,964 bytes] Martini (talk | contribs) (Created page with "{{MMProgRef}} The Stream Programming Interface (SPI) contains functions exported by the Sync/Stream Manager to support applications that control real-time data streaming. These functions are used to create data streams, associate data objects, and for data streaming and synchronization. SPI functions also enable applications to query and install stream protocols and to query the current stream time. The following table lists the SPI functions: {| class="wikitable" ! F...")
(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://www.edm2.com/index.php/Special:NewPages"