Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
titleDR_OP ($0B), open explicit filename (OZ 5.0 and newer)
IN:
     C = number of segment to parse (0 for all, default)
     DE = filename buffer (always local, in S0 or S1)

OUT, if call successful:
     Fc = 0
        IX = handle (device type, always)
        A  = DOR type (device, file, directory, EPROM)
        B  = segment count in explicit filename
        HL = last character parsed in filename (separator or null terminator)

OUT, if call failed:
     Fc = 1
     	A  = RC_Fail, buffer not in S0 or S1
        A  = RC_Onf, filename does not exist

Registers changed after return:
     ...CDE.. / ..IY same
     AFB...HL / IX.. different

...

Notes

  • This call is the optimized equivalent of GN_Opf / OP_DOR. It is used by GN_Opf itself and allows a faster file open.
  • It is recommended to use this call before using making file DOR header operation like reading filename, timestamp...
  • It always create a device type handle ($01) which is required to perform DOR header operation. Type can be changed by calling OS_Fn / FN_CH (in order to perform file I/O).
  • API call implemented in OZ 5.0

...

Code Block
titleDR_FRR ($0C), file record read (OZ 5.0 and newer)
IN:
     B = record type letter (Name, Creation, Update, eXtent, Efs, Attribute)
     DE = user buffer address (to store information of read, always local, in S0 or S1)
     IX = DOR handle (device or file type)

OUT, if call successful:
     Fc = 0
     original IX DOR handle is still valid

OUT, if call failed:
     Fc = 1
     original IX is still valid
     A = error code
          RC_BAD ($04), bad argument

Registers changed after return:
     A.BCDEHL/IXIY same
     .F....../.... different

Notes

  • This call is the optimized equivalent of DR_RD for file record. It is used by operating itself.
  • It is recommended to use this call to perform file DOR operation like reading filename, timestamp...
  • It accepts any handle type (device or file type). It can be called after a handle given by GN_Opf or OS_Dor / DR_OP.
  • API call implemented in OZ 5.0


Code Block
titleDR_FRW ($0D), file record write (OZ 5.0 and newer)
IN:
     B = record type letter (Name, Creation, Update, eXtent, Efs, Attribute)
     DE = user buffer address (to store information to be written, always local, in S0 or S1)
     IX = DOR handle (device or file type)

OUT, if call successful:
     Fc = 0
     original IX DOR handle is still valid

OUT, if call failed:
     Fc = 1
     original IX is still valid
     A = error code
          RC_BAD ($04), bad argument

Registers changed after return:
     A.BCDEHL/IXIY same
     .F....../.... different

Note

Read notes about DR_FRR.


Code Block
titleDR_USE ($0E), handle in use (OZ 5.0 and newer)
IN:
     IX = DOR handle

OUT, if call successful:
     Fc = 0
     handle or device is NOT already in use

OUT, if call failed:
     Fc = 1
     original IX is still valid
     A = error code
          RC_USE, already in use

Registers changed after return:
     ..BCDEHL/IXIY same
     .F....../.... different

...