The VME supports the following OSFI drivers, defined in the file dm,hosts,, in addition to the standard drivers:
OSFI Windows Driver |
Access to the underlying host file system. This driver and some derivatives allow access to Windows. |
OSFI Remote Pick Files |
Access to remote D3 files through TCP/IP. This driver allows access to a remote D3 system. See the D3 Reference Manual for more information. |
FSI Driver |
Access to the distributed File System Interface. |
This driver allows access to the underlying Windows file system with the following conventions:
D3 file is represented by a directory, and the directory must exist.
D3 item is a Windows file.
Dictionary of a D3 file is represented by a subdirectory $DICT.
Examples of Windows driver names are:
NT |
Used for text records in which a line is terminated by a line feed. When copied into D3, the line feed is replaced by an attribute mark. |
DOS |
Used for text records in which a line is terminated by a carriage return / line feed. When copied into D3, the sequence carriage return / line feed is replaced by an attribute mark. Tabulation are also replaced by 4 spaces, and vice versa. |
NT_BIN |
Used for binary records or data which must not be translated in any way. WARNING—This driver should not be used to read items using the BASIC READ statement. |
Examples of valid Windows OSFI file names are:
NT |
/temp |
Directory /temp on the current drive. |
DOS |
D:/temp |
Directory /temp on the drive D:. |
NOTE |
The use of slash marks (/) instead of the usual MS-DOS backslash (\). |
The options in the host item are identical to the options of the UNIX driver with the following addition:
Lx
where x is a one letter code representing an MS-DOS drive letter. This option eliminates the need to specify an MS-DOS letter.
The entries A, B, C, and D in the host file are shortcuts to the MS-DOS drives A:, B:, C:, and D:. For example, it is possible to refer to the file A:/Docs, as a D3 file.
See Also