--------------------------------- LDos V1(3) for AMOS1.3 and above. LDos is (C) Niklas Sjöberg 1992 --------------------------------- PART EIGHT - Errorcodes ----------------------- As mentioned before, errorhandling isn't perfect, but I'm working on it! Ldos Errorcodes : # Description - ----------- 0 Invalid Channel = Channel not >0 and <4 1 LFile already assigned to channel = Channel not free for use 2 LFile not found = File didn't exist 3 Invalid filename = To long or short filename or file/dir didn't exist (used by some commands because I felt it was unecessary to implement even more errorcodes. See docs for some of the commands) 4 Examine failed = Some files can't be locked. May be busy while another program is writing to it or even creating it!! 5 Invalid comment = To long or short comment (MAX 79 characters) 6 Unable to set protectionflags = See 4. May be diskerror 7 No more entries in this dir = Lcat First wasn't a directory or you keep on calling Lcat Next after it has returned an empty string. 8 Start is greater than max limit = Oops, check your addresses in Lstr-calls. Otherwise your string will be as long as all your memory installed. 9 Device already open = Use Ldevice Close before opening a new device. 10 Device not open = LDevice Open may have failed, or you have closed the device. 11 Unable to open diskfont.library = diskfont.library MUST be in libs: on the boot-disk (SYS:) in order to use Ldisk Font (also required by AMOS Get Fonts) 12 Host not created = Rexxhost.lib has been expunged or a host with the same name already exists. (LREXX) 13 Old message not replied! = You tried to read the next message before the last was replied to. (LREXX) 14 No message to reply to! = You replied to a already replied message. (LREXX) *- 15 You need dos.library 37+ = You tried to use a command which *- need a higher version of this library (Kickstart 2.0-only) *- 16 "To long pattern/overflow/or no pattern" = Either you used a *- wildcard which actually doesn't contain any wildcards, or you *- used a pattern >100 chars, or there was a bufferoverflow in *- the dos.library *- 17 Password to short. Lcrypt requires at least for chars as pass- *- word. (This is not because of the algorithm, but for your own *- safety) *- 18 You can not call with an empty argument = This command req- *- uires that you do not supply an "empty" argument such as "" *- or zero. *- 19 Stop is greater than start = Think twice when using Lback Hunt *- since START actually is greater than STOP. *- 20 No more devices in system! = Stop calling Ldev Next when it has *- returned an empty string. *- 21 Not enough words in string! = You tried to extract a word with *- Lword which didn't exist. Use Lwords to find out how many words *- the string contains. ++ 22 LLdir$ can't find directory! = You tried to change the current ++ directory to something that didn't exist. ++ 23 Command need NULL-terminated string! = You forgot to add Chr$(0) ++ to a string before you called a command which doesn't terminate ++ the string itself (saves both space and time). ++ 24 Missing part of ARexx (lib/server) = rexxhost can't work if it ++ can't find rexx*-libs and the server running. This error will ++ ONLY be generated when you call Lrexx Make Host so you should ALWAYS ++ try to make a port (host) before you try any of the other Lrexx- ++ commands All LDos errors are trapable so there is no excuse for not providing your programs with an errorhandling-routine. PART NINE - Disclaimer ---------- ---------- Even though I have tested Ldos as much as possible there may be some bugs left. Many of the Ldos-commands involve access to dos and are naturally dangerous to misuse. Ldos handles most kind of errors, but I have skipped some checking in order to make the code smaller and some functions faster. Because of this Ldos can crasch if you try to call some functions with totally wild arguments. For example Ldisk Font, Lset Comment etc. will behave very strange if you call with an empty string as argument (now, why would anybody want to do that?). If you use Ldos under normal circumstances calling with valid parameters it should be stable. If you use Ldos it is understood that : o You can not hold me responsible for any kind of damage like lost file or crashed disks. o You are using it on your own risk. o If you like to use LDos in a commercial product you should contact me first. o If you use it in a Shareware-program (or anything like that) I would like to receive a registered copy of your program. This won't cost you more than a disk and a stamp. o If you are using LDos in Licensware-programs I would also like to receive a copy of the program. o LDos may not be sold for money. ++ Yack! This must be the largest bugs of all!! This text was included ++ in V1 of Ldos. Of course registered users will have FULL rights to ++ use Ldos/Lserial in any way. OF COURSE I do not require that you ++ should send SW/LW-programs to me. Please forgive me for missing this ++ part when I released the manual for 2.0/2.1!! END.