Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Interfacing

Persistent mass storage is handled by the EPROM file area. It is interfaced by the :EPR device (OZ 4.7 and above). This device follows the DOR conventions with the major type DM_Epr ($84). Internal EPROM file area is accessed with :EPR.0 device name. :EPR.1, :EPR.2, :EPR.3 refer to the EPROM file area in slot 1, 2 or 3 when a formatted EPROM or flash card is available. Accessing the file requires opening with GN_Opf, followed by i/o operations (OS_Gb, OS_Pb, OS_Frm, OS_Fwm, OS_Mv...) and is closed with GN_Cl. All usual read and write operations are performed just like standard RAM files, thanks to the temporary ram files stored in :RAM.-. This functionality is transparent to the end user, the temporary files are deleted after closing the file.

Saving a file to the EPROM file area writes the complete file again. The previous copy (if it still exist) is marked as deleted. EPR device can be used as default device in the Panel. If this mode is chosen, keep in mind that the available free space can quickly be wasted by the deleted files generated. 

Wildcards

Wildcards has been implemented on EPROM filenames. Supported wildcards are '*' and '?'. Thus :EPR.* or :EPR.? browses all available file areas. Filenames are automatically expanded in GN_Opf filename buffer. This feature is useful in applications like Pipedream. After loading a file using wildcards, the filename is expanded when using <>FC or <>FS filename displaying the first file it finds.

 

  • No labels