en:docs:fapi:dosopen

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
en:docs:fapi:dosopen [2021/09/29 10:12] prokusheven:docs:fapi:dosopen [2021/09/29 10:38] (current) prokushev
Line 61: Line 61:
 | ::: | This bit is not inherited by child processes. | | ::: | This bit is not inherited by child processes. |
 | 13 | Fail-Errors flag. Media I/O errors are handled as follows: | | 13 | Fail-Errors flag. Media I/O errors are handled as follows: |
-| ::: |      0 = Reported through the system critical error handler. | +| ::: | 0 = Reported through the system critical error handler. | 
-| ::: |      1 = Reported directly to the caller by way of return code. | +| ::: | 1 = Reported directly to the caller by way of return code. | 
-| ::: |     Media I/O errors generated through an IOCTL Category 8 function always get | +| ::: | Media I/O errors generated through an IOCTL Category 8 function always get | 
-| ::: |     reported directly to the caller by way of return code. The Fail-Errors function | +| ::: | reported directly to the caller by way of return code. The Fail-Errors function | 
-| ::: |     applies only to non-IOCTL handle-based file I/O calls. | +| ::: | applies only to non-IOCTL handle-based file I/O calls. | 
-| ::: |     This bit is not inherited by child processes. | +| ::: | This bit is not inherited by child processes. | 
-| 12 |       No-Cache/Cache flag: | +| 12 | No-Cache/Cache flag: | 
-| ::: |      0 = It is advisable for the disk driver to cache the data in I/O operations on this file. | +| ::: | 0 = It is advisable for the disk driver to cache the data in I/O operations on this file. | 
-| ::: |      1 = I/O to the file need not be done through the disk driver cache. | +| ::: | 1 = I/O to the file need not be done through the disk driver cache. | 
-| ::: |     This bit advises FSDs and device drivers whether it is worth caching the data. | +| ::: | This bit advises FSDs and device drivers whether it is worth caching the data. | 
-| ::: |     Like the write-through bit, this is a per-handle bit and is not inherited by child processes. | +| ::: | Like the write-through bit, this is a per-handle bit and is not inherited by child processes. | 
-| 11 |  Reserved and must be zero. | +| 11 | Reserved and must be zero. | 
-| 10-8 |    The locality of reference flags contain information about how the application is to access the file. | +| 10-8 |The locality of reference flags contain information about how the application is to access the file. | 
-| ::: |     Value   Definition | +| ::: | Value   Definition | 
-| ::: |      000        No locality known. | +| ::: | 000        No locality known. | 
-| ::: |      001        Mainly sequential access. | +| ::: | 001        Mainly sequential access. | 
-| ::: |      010        Mainly random access. | +| ::: | 010        Mainly random access. | 
-| ::: |      011        Random with some locality.| +| ::: | 011        Random with some locality.| 
-|  7  |      Inheritance flag: | +|  7  | Inheritance flag: | 
-| ::: |      0 = File handle is inherited by a spawned process resulting from a DosExecPgm call. | +| ::: | 0 = File handle is inherited by a spawned process resulting from a DosExecPgm call. | 
-| ::: |      1 = File handle is private to the current process. | +| ::: | 1 = File handle is private to the current process. | 
-| ::: |      This bit is not inherited by child processes. | +| ::: | This bit is not inherited by child processes. | 
-| 6-4 |      Sharing Mode flags. | +| 6-4 | Sharing Mode flags. | 
-| ::: |    This field defines any restrictions to file access placed by the caller on other processes: +| ::: | This field defines any restrictions to file access placed by the caller on other processes: 
-| ::: |     Value       Definition | +| ::: | Value       Definition | 
-| ::: |            001          Deny Read/Write access | +| ::: | 001          Deny Read/Write access | 
-| ::: |            010          Deny Write access | +| ::: | 010          Deny Write access | 
-| ::: |            011          Deny Read access | +| ::: | 011          Deny Read access | 
-| ::: |            100          Deny neither Read or Write access (Deny None). Any other value is invalid. | +| ::: | 100          Deny neither Read or Write access (Deny None). Any other value is invalid. | 
-|  3  |        Reserved and must be zero. | +|  3  | Reserved and must be zero. | 
-| 2-0 |       Access Mode flags. This field defines file access required by the caller: | +| 2-0 | Access Mode flags. This field defines file access required by the caller: | 
-| ::: |         Value           Definition | +| ::: | Value           Definition | 
-| ::: |            000             Read-Only access | +| ::: | 000             Read-Only access | 
-| ::: |            001             Write-Only access +| ::: | 001             Write-Only access 
-| ::: |            010             Read/Write access.  |+| ::: | 010             Read/Write access.  |
  
 Any other value is invalid.  Any other value is invalid. 
Line 109: Line 109:
  
 ==== Access Mode ==== ==== Access Mode ====
- 
                                                  
 Specify the type of access to the file needed by your process (access mode). Specify the type of access to the file needed by your process (access mode).