There is the cleaned error table, now need to create the missing messages.
BFh .NOUPBThis is happened when Unit Handler called for sector operations but the Unit Parameter Block not filled with boot sector parameters. Some disk errors also set status bit in UPB for set it is as invalid.
*** UPB not validare right?
BDh .ICMDThis is happened when the Unit Handler got a unknow function code.
It is will be important in the future because when the EXDOS updated for using big, FAT16 disks, then need to define new FISH and Unit Handler function codes for the 32 bit LBA sector transfers. These are will be unknow for the old handlers, and the new handlers will be reject the old 16 bit LBA commands for avoid file system damage.
This error have a message in the version 0.0 documentation:
*** Invalid unit handler commandProbably use "function call" or "function code" instead "command" like as EXOS error messages?
BCh .IUNUMIt is happened when used unknow internal unit number for operation, for example try to read from 5. floppy drive.
In the future this also can be more possible, with the removable SD Cards, if one card removed or replaced with less partitions, then less unit numbers will be valid.
From the 0.0:
*** Invalid unit numberBBh .ISECTIf sector number for read/write point outside to disk area then this error occured. For example on 720K disks sector are exist from 0-1439, from 1440-... generate this error.
It is usaly occured when the FAT table or directory entry damaged.
From 0.0:
*** Invalid sector numberB0h .ICALLFISH called with unknow function code. As I say before the Unit Handler calls, in the future this is will be important.
Following EXOS similar error (0FFh):
*** Invalid FISH function codeA3h .IFATThis is occured when FAT entry point outside the disk. (I found bugs, or least missing feature about this checking
It is not always checked, and when accepting the invalid value then will generate .ISECT error. 000h and 001h are also accepeted
)
My suggestion:
*** Invalid FAT entry9Bh .OV64kTry to transfer data over FFFFh Z80 address. For example read 200h bytes starting at FE00h. It is very frequent error because TAPE, NET and other EXOS devices not checking this problem.
Any good idea for the message?
9Ah .FILEEnd of file entry readed from the FAT before it is ending by the file size from directory
My suggestion:
*** Invalid end of fileAnyway good to talking about these, I see many more verification need to be added in my EXDOS expansions