Unfortunately the original EXDOS documentations still missing
but exist a leaked Hungarian documentation: text files which are talking about FISH and DISKIO calls, FAT table, and EXDOS error codes. Unknow people see the original documentation, and translated these parts. The error table contaion the original IS identifiers of the errors. (This is the right pharse for .WPROT, .NDOS and etc?)
I wanted to use error code table from this package, cleaned up the Hungarian texts, for talking about English error messages.
Then I noticed many errors are missing from this table! Probably are come from early documentation.
Missing the:
- File exists
- RAM disk already exists
- Invalid file attributes
- Invalid MAPDISK
- Data error
- No RAM disk
But exist the: File cannot be copied onto itself
The strange thing: version 0.3 ROM have all the missing errors from the list, but don't have File cannot be copied onto itself error! (And COPY FILE1 FILE1 are working
)
Another strange thing the: B1h .WDRV - Insert disk for drive x:
In all existing version (from 0.3) these removed from the error table and putted to other messages table.
The very early 0.0 documentations what we have talking about this as error messages!
I'm totally confused about guess which version are the original of the leaked documents. At the FISH calls the RAMDISK handler function also missing, and also some other calls.
Back to the error messages... What is the right in English: filename or file name?
At the A6h .IFNM - Invalid filename
in version 1.3 changed to "Invalid file name".
But at ABh .DUPF - Duplicate file name
all existing ROM version use "Duplicate filename".
And the story of B1h error very interesting: it is removed from error messages table, but the error code still used. In the "ask user when error occured" routine (Retry or Abort and etc) added a exception handler for B1h error: if B1h code then print message from messages table, else select right message from error messages table.
Why added this extra routines for B1h? Just for can't see "Insert disk..." message with EXOS 28 (Explain error code) function?
Then if any user program using own replacement handler for EXDOS errors, then it is can get B1h error code, but can't get message for it with EXOS 28.