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 5 Next »

Interfacing

Persistant mass storage is handled by the eprom file area. It is interfaced by the :EPR device (OZ 4.7 and newer). 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 eprom file area in slot 1, 2 or 3 if a formatted eprom or flash eprom 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 ended by closure with GN_Cl. All usual read and write operations are performed like standard RAM files thanks to temporary ram files in :RAM.-. This functionality is transparent for end user, temporary files are deleted after closure of the file.

Saving a file to the eprom file area implies a full rewrite of the file, the previous (if existing) is marked as deleted. EPR device can be used as default device in Panel, keeping in mind that available free space can quickly be wasted by deleted files. 

Wildcards

Wildcards have been implemented for eprom filename manipulation. 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 Pipedream. After loading a file with wildcards, its filename is expanded without wildcards in <>FC or <>FS filename.

 

  • No labels