en:docs:fapi:dosdevioctl

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:docs:fapi:dosdevioctl [2021/09/17 09:27] – prokusheven:docs:fapi:dosdevioctl [2021/11/28 10:33] (current) – prokushev
Line 15: Line 15:
   * ParmList ([[PVOID]]) - input : Address of the command-specific argument list.   * ParmList ([[PVOID]]) - input : Address of the command-specific argument list.
   * Function ([[USHORT]]) - input : Device-specific function code.   * Function ([[USHORT]]) - input : Device-specific function code.
-  * Category ([[USHORT]]) - input : Device category.+  * Category ([[USHORT]]) - input : [[Device category]].
   * DevHandle ([[HFILE]]) - input : Device handle returned by DosOpen or a standard (open) device handle.   * DevHandle ([[HFILE]]) - input : Device handle returned by DosOpen or a standard (open) device handle.
  
Line 40: Line 40:
 Values returned in the range hex FF00 through FFFF are user dependent error codes. Values returned in the range hex FE00 through FEFF are device driver dependent error codes. Values returned in the range hex FF00 through FFFF are user dependent error codes. Values returned in the range hex FE00 through FEFF are device driver dependent error codes.
  
-Refer to the ''IBM Operating System/2 Version 1.2 I/O Subsystems And Device Support Volume 1'' for a complete listing of control functions (DevHlp calls). +Refer to the [[http://www.os2museum.com/files/docs/os212pti/64F3959_OS2_V1_2_PTI_IO_Subsystems_and_Device_Support_Vol_1_Device_Drivers.pdf|IBM Operating System/2 Version 1.2 I/O Subsystems And Device Support Volume 1]] for a complete listing of control functions (DevHlp calls). 
  
 ==== Family API Considerations ==== ==== Family API Considerations ====