https://osfree.ru/doku/ 2026-04-21T18:33:04+00:00 https://osfree.ru/doku/ https://osfree.ru/doku/lib/exe/fetch.php?media=wiki:dokuwiki.svg text/html 2014-05-13T10:54:42+00:00 Anonymous (anonymous@undisclosed.example.com) https://osfree.ru/doku/doku.php?id=en:ibm:ifs:mechanism:calls&rev=1399978482&do=diff File System Function Calls The OS/2 Version 2.0 Control Program Programming Reference gives a detailed description of the 32-bit file system calls new for OS/2 Version 2.0 See the OS/2 Version 2.0 Programming Guide for a description of how to use these calls. For detailed descriptions of the 16-bit file system calls see the text/html 2014-05-12T02:54:31+00:00 Anonymous (anonymous@undisclosed.example.com) https://osfree.ru/doku/doku.php?id=en:ibm:ifs:mechanism:commands&rev=1399863271&do=diff IFS Commands An FSD is loaded and initialized at system start-up when an IFS= statement is encountered in CONFIG.SYS. The syntax of this command is as follows: IFS=drive:path\name.ext parms where drive:path\name.ext specifies the FSD to load and initialize. parms represents an FSD-defined string of initialization parameters. text/html 2014-05-13T10:55:02+00:00 Anonymous (anonymous@undisclosed.example.com) https://osfree.ru/doku/doku.php?id=en:ibm:ifs:mechanism:eas&rev=1399978502&do=diff Extended attributes Extended attributes (EAs) are a mechanism whereby an application can attach information to a file system object (directories or files) describing the object to another application, to the operating system, or to the FSD managing that object. text/html 2014-05-12T03:43:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://osfree.ru/doku/doku.php?id=en:ibm:ifs:mechanism:errcodes&rev=1399866237&do=diff Error Codes FSDs should use existing error codes when possible. New error codes must be in the range reserved for FSDs. The FS_FSCTL interface must support returning information about new error codes. The set of error codes for errors general to all FSDs is 0xEE00 - 0xEEFF. The following errors have been defined: text/html 2014-05-13T10:55:15+00:00 Anonymous (anonymous@undisclosed.example.com) https://osfree.ru/doku/doku.php?id=en:ibm:ifs:mechanism:image&rev=1399978515&do=diff FSD File Image An FSD loads from a file which is in the format of a standard OS/2 dynamic link library file. Exactly one FSD resides in each file. The FSD exports information to OS/2 using a set of predefined public names. The FSD is initialized by a call to the exported entry point FS_INIT. text/html 2014-05-13T10:55:24+00:00 Anonymous (anonymous@undisclosed.example.com) https://osfree.ru/doku/doku.php?id=en:ibm:ifs:mechanism:init&rev=1399978524&do=diff FSD Initialization FSD initialization occurs at system initialization time. FSDs are loaded through the IFS= configuration command in CONFIG.SYS. Once the FSD has been loaded, the FSD's initialization entry point is called to initialize it. FSDs are structured the same as dynamic link library modules. Once an FSD is loaded, the initialization routine FS_INIT is called. This gives the FSD the ability to process any parameters that may appear on the CONFIG.SYS command line, which are passed a… text/html 2014-05-13T10:55:36+00:00 Anonymous (anonymous@undisclosed.example.com) https://osfree.ru/doku/doku.php?id=en:ibm:ifs:mechanism:interfaces&rev=1399978536&do=diff FSD System Interfaces Overview Installable file system entry points are called by the kernel as a result of action taken through the published standard file I/O application programming interface in OS/2 Version 2.0. Installable file systems are installed as text/html 2014-05-12T06:57:49+00:00 Anonymous (anonymous@undisclosed.example.com) https://osfree.ru/doku/doku.php?id=en:ibm:ifs:mechanism:overview&rev=1399877869&do=diff Installable File System Overview System Relationships Installable File System (IFS) Mechanism defines the relationships among the operating system, the file systems, and the device drivers. The basic model of the system is represented in Figure 1-1. text/html 2014-05-13T10:56:04+00:00 Anonymous (anonymous@undisclosed.example.com) https://osfree.ru/doku/doku.php?id=en:ibm:ifs:mechanism:reqs&rev=1399978564&do=diff FSD Calling Conventions and Requirement Calling conventions between FS router, FSD, and FS helpers are: * Arguments will be pushed in left-to-right order onto the stack. * The callee is responsible for cleaning up the stack. * Registers DS, SI, DI, BP, SS, SP are preserved.