The Programmer's Guide to TRSDOS Version 6 - Tim Mann's Home ...

More documents

Recommendations

Info

considered as non loadable comment records. It is thus possible to "un-yank" a yanked patch; however, this feature is not implemented in the PATCH utility. 8.4 ERROR MESSAGE DICTIONARY Any time a SuperVisor Call experiences a malfunction, it returns an error code to the caller. The error codes possible are in the range . The operating system associates a message string with each error code. Each string can be displayed or obtained via the @ERROR SuperVisor Call request. The words contained in the messages are stored in an error dictionary which is in a system overlay. This section of the appendix is a compilation of those error code messages and associated meanings. Error 00: No error A return code of zero indicates that there is no error. Error 01: Parity error during header read During a read request, the sector ID FIELD could not be satisfactorily read. Repeated failures would most likely indicate media or hardware failure. Error 02: Seek error during read During a read sector disk I/O request, a sector ID FIELD noting the requested cylinder was not located within the time period allotted by the controller. Either the cylinder is not formatted on the diskette, or the step rate designated is too low a value for the hardware to properly respond. Error 03: Lost data during read During a read sector request, the CPU was late in accepting a byte from the FDC data register and subsequently lost one of the bytes from the sector. For more information, consult the reference manual for the floppy disk controller used in your disk controller. Error 04: Parity error during read During a read request, the FDC sensed a CRC error. Possible media failure would be indicated. The Drive hardware could also be at fault. Error 05: Data record not found during read A disk sector read request was generated with a sector number not found on the cylinder referenced. Error 06: Attempted to read system data record A read request for a sector located within the directory cylinder was made without using the directory read routines. Directory cylinder sectors are written with a data address mark that differs from the data sectors data address mark. See chapter 4 and chapter 5 for additional information concerning address marks. Error 07: Attempted to read locked/deleted data record This error indicates that a request was entered which required a system overlay that had been purged from the system disk. 8-9
Error 08: Device not available A reference was made for a logical device that either could not be located in the Device Control Blocks or the hardware associated with the device was not available (for example, a printer that was off-line). Error 09: Parity error during header write This is the same type of error as error-01 except that the operation requested was sector WRITE. Error 10: Seek error during write This is the same type of error as error-02 except that the operation requested was sector WRITE. Error 11: Lost data during write The CPU was not fast enough in transferring a byte to the FDC during a sector write request so it could be written to the disk. Therefore, one or more of the sector bytes were lost. Error 12: Parity error during write A CRC error was generated by the FDC during a sector write operation. Error 13: Data record not found during write This is similar to error-05. The sector number requested for the write operation, could not be located on the cylinder being referenced. Either the request is erroneous, or the cylinder is improperly formatted. Error 14: Write fault on disk drive This error message results when the disk controller returns a "write fault" error. Consult your FDC or HDC reference manual. Error 15: Write protected disk A write request was generated to a disk which either had a write protected diskette or the drive was write protected via software (see the SYSTEM (WP) DOS command). On 5-1/4" diskettes, covering the notch will protect the diskette from being written. On 8" media, exposing the notch will perform the same thing. If you want to write on a diskette, you must observe the proper notch condition. Error 16: Illegal logical file number A Directory Entry Code was referenced that was invalid for the referenced drive. Error 17: Directory read error Any disk error sensed during the reading of directory entry record sectors will result in this error. It could be media failure, hardware failure, or program crashes. The system's directory read accesses replace any lower level error (such as parity error) with this code. 8-10
Page 1 and 2:
MISOSYS, INC. The Programmer's Guid
Page 3 and 4:
1. Introduction Many thousands of u
Page 5 and 6:
language (i.e. BASIC, C, PASCAL, ..
Page 7 and 8:
NAME START END DESCRIPTION LOWCORE
Page 9 and 10:
ackup utility provides exceptional
Page 11 and 12:
3. Device Input/Output Interfacing
Page 13 and 14:
3.2.2 VECTOR Field - This field in
Page 15 and 16:
FILTER *PR USING *S0 the operating
Page 17 and 18:
===================================
Page 19 and 20:
===================================
Page 21 and 22:
ENTRY JR BEGIN ;Branch around linka
Page 23 and 24:
DATA1 EQU $-DATA$ DB 0 ;Data storag
Page 25 and 26:
Offset Contents +0 Contains the las
Page 27 and 28:
image of the serial port UART statu
Page 29 and 30:
called TRACKs. Each track is then d
Page 31 and 32:
The DCT contains the information re
Page 33 and 34:
accessed a single-sided diskette, t
Page 35 and 36:
containing the disk's directory. Th
Page 37 and 38:
Command Purpose RESTORE Recalibrate
Page 39 and 40:
available from Logical Systems, Inc
Page 41 and 42:
exceeds this capacity, then it must
Page 43 and 44:
is two physical cylinders. Although
Page 45 and 46:
5. The DOS Directory Structure 5.1
Page 47 and 48:
===================================
Page 49 and 50:
5.2.8 PACK NAME - This field conta
Page 51 and 52:
The position of a file's hash code
Page 53 and 54:
5.4 THE DIRECTORY RECORD STRUCTURE
Page 55 and 56:
Bit 3 Specifies the visibility; if
Page 57 and 58:
the first granule in use is the sec
Page 59 and 60:
travels the turnpike. In this manne
Page 61 and 62:
The @FSPEC SVC will transfer the fi
Page 63 and 64:
A high level language permits you t
Page 65 and 66:
does exist, @RENAME should return e
Page 67 and 68:
Next, it would be very useful if th
Page 69 and 70:
LD HL,FCBX+9 ;Point to the LRL fiel
Page 71 and 72:
operating system for such a purpose
Page 73 and 74:
position where the last character i
Page 75 and 76:
ecord. If a file has more than four
Page 77 and 78: DE Contains a pointer to the File C
Page 79 and 80: @RENAM SVC-56 Rename a file on disk
Page 81 and 82: @FNAME SVC-80 Obtain filespec given
Page 83 and 84: @WRSEC SVC-53 Write a disk sector @
Page 85 and 86: 7.6 SUPERVISOR CALL DETAILS 7.6.1 @
Page 87 and 88: Note: @EXIT in SYS1 automatically r
Page 89 and 90: 7.6.10 @CLOSE SVC-60 This SVC will
Page 91 and 92: 7.6.18 @DCSTAT SVC-40 This SVC pass
Page 93 and 94: Directory to Buffer Entry: B 1; Fun
Page 95 and 96: 7.6.31 @FLAGS$ SVC-101 This SVC wil
Page 97 and 98: NFLAG$ This "network" flag is used
Page 99 and 100: 7.6.32 @FNAME SVC-80 This SVC will
Page 101 and 102: 7.6.40 @HEX8 SVC-98 This SVC will c
Page 103 and 104: 7.6.48 @KLTSK SVC-32 This SVC will
Page 105 and 106: 7.6.57 @OPEN SVC-59 This SVC will o
Page 107 and 108: Registers Affected: AF, BC. Entry:
Page 109 and 110: 0-14 FILENAME/EXT:D - left justifie
Page 111 and 112: 7.6.71 @REMOV SVC-57 This SVC will
Page 113 and 114: Entry: DE A pointer to the FCB cont
Page 115 and 116: Exit: A Error return code, if any.
Page 117 and 118: CURSOR CHARACTER Registers Affected
Page 119 and 120: Exit: A Will contain the error code
Page 121 and 122: esident routine into its execution
Page 123 and 124: CKPAWS LD A,@FLAGS$ ;Get Flags poin
Page 125 and 126: ===================================
Page 127: The TYPE=0A indicates that it is th
Page 131 and 132: Error 28: End of file encountered T
Page 133 and 134: 8.5 HEADER PROTOCOL OF MEMORY MODUL
Page 135 and 136: This is obviously an extremely usel
Page 137 and 138: LD (IX+2),15 JR TASKA By firmly und
Page 139 and 140: 8.7.3 Details of Low Memory Page 2
Page 141 and 142: actual bank switching. As previousl
Page 143 and 144: set. Thus, the Z-flag will be indic
Page 145 and 146: 8.10 SYSTEM DISK BOOT TRACK The ope
Page 147 and 148: 14 DEBUG 72 PURGE 1B VERIFY 71 DUMP
Page 149 and 150: 8.13 USING @PARAM The @PARAM SuperV
Page 151 and 152: DW LPARM+1 DB 'FEED ' ;Line feed pa
Page 153 and 154: ;*=*=* PPARM LD BC,0 ;Zero because
Page 155 and 156: 8.14 TRAP Filter Illustrated ;TRAP/
Page 157 and 158: 8.15 SLASH0 Filter Illustrated ;SLA
Page 159 and 160: 8.16 DMP-500 BOLDFACE Filter Illust
Page 161 and 162: NOMEM$ DB 'High memory is not avail
Page 163 and 164: @ @ABORT..........7-2, 7-4, 7-8, 7-
show all

The Programmer's Guide to TRSDOS Version 6 - Tim Mann's Home ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?