============================================================================ E R R O R C O D E S ============================================================================ When EdPlayer gets an error, usually from an ARexx or telled command, it reports that error to the calling program. If you use "telled", you will not see an error message in your CLI window, although errors with numbers 10 or higher may cause your script to abort. If you use "cteled", a full error description should appear in your CLI window. And finally, if you use an ARexx script, the error number will appear in the script's window (the script may halt for errors >= 10), but no discription will appear. In ALL these cases, however, if the CD panel is open when the error occurs, an error number and description will appear in it. This is useful for debugging things like DVideoIII presentations which do not even return the error number from a failed ARexx message. If for some reason you can get an error number, but you would like a much fuller description, here are the codes: 0 = No error. 4 = Can't give response. You sent an ARexx query through telled or cteled, but EdPlayer can't answer your questions through those programs. You must use the AskEd.rexx script for queries. 5 = Incorrect PowerPacker Password. If you have a module that is encrypted, and you give a wrong password, you get this! 6 = No program! PREV or NEXT was called, but there is no program there to get the next songname from. 7 = Illegal JUMP. Someone tried to use the JUMP command to jump to a pattern that wasn't in the song, and the command had to be ignored. 8 = Can't continue. CONT was called, but the song was STOPped, and could not continue. 9 = Nothing to PLAY! Someone issued a PLAY with no filename and no song or program currently loaded. 10 = Syntax error. The first four letters of the message did not make a valid command. Perhaps there were quotes in "telled" parameters, or maybe you added extra letters to a command that didn't allow it. Or maybe it was just garbage... Note: This error also seems to be serving as my "illegal value" error for several commands. 11 = MIDI not available. If the MIDI command returns this, then your serial port is probably not free. If the MIDL command returns this, then maybe you don't have midi.library in your LIBS: directory or something. 12 = File not found. A very common error. Check spelling & path! You must use a FULL PATH with EdPlayer, because EdPlayer's current directory may not match the controlling program's current dir! ALSO: If you have two disks, both named "Empty" or both named "ST-00" or something, EdPlayer can't tell them apart! You will end up seeing this error a lot. RENAME your disks. Make them UNIQUE! Also, don't let req.library use "DF0:" instead of a volume name! If you do, EdPlayer will think all your disks can be found in drive DF0: all the time, and will report this error a lot. 13 = Need PowerPacker.library. EdPlayer came across a packed module, and you need to install powerpacker.library in your LIBS: dir. 14 = Disk error. Maybe the file is corrupt, or there was a read/write error or something. 15 = Out of memory. There is not enough CHIP RAM to load the module. I know I got MegaBall 2.0 to load songs into FAST ram, but that is ONLY because there are five songs, and the group of them go into FAST together and get buffered into CHIP one song at a time. This method will obviously not work with EdPlayer which only loads one song at a time anyway. So we're stuck with CHIP RAM again. :-( 16 = Unknown module type, or corrupt module. Perhaps you are trying to play a MED 3.00 module with the MED 3.0 bug in it, or perhaps you are trying to play an earlier format of MED modules, or even a song or something instead of a module. If the error happened because of a MED mutant, just load it into MED *3.21!* and save as a MODULE. This should fix it. If the tempo goes nuts, know that the MED author changed the tempo commands and it's not my fault. ;-) *** Please stop sending me email that EdPlayer won't load MED sng+samples format. I know this! It is VERY hard to load this format, and EdPlayer currently won't do it. SO, save your work as __MODULES__, not as __SONGS__! *** New for EdP 2.0: EdPlayer now range-checks mem writes during initialization of NT/PT mods. This should trap some semi-corrupt mods from destroying your mem list, but it will also make EdPlayer unable to play these mods. You can fix most such mods by loading them into ProTracker and saving them back out. 17 = Can't find LIBS:rexxsyslib.library. To use the ARexx queries, you _MUST_ have ARexx. You can't use queries without ARexx, because there is no other way for EdPlayer to answer you. Well?? What are you doing, just sitting there?? Go buy some ARexx! Go on!! Move it! Right now!! Whew. 21 = If EdPlayer returns this, then it is exiting (shutting down). However, this error is much more often generated by telled itself when it cannot find EdPlayer in the system. For instance, if you have a script file that starts EdPlayer, and immediately tries to send commands to it, without waiting for it to load and get ready (open it's port, etc.), then your script will probably die with this error code. You should wait for EdPlayer to start, and the best way to do this is with the "wport" CLI command that I distribute in this archive. Example: After starting EdPlayer, and before sending commands, have the CLI execute "wport EDPLAYER". * End of errors.