------------------------------------------------ --- Version History of the BaudBandit.device --- ------------------------------------------------ Version 1.0 ----------- -First public release. -I dropped my plans to program a shareware requester and a time limit in order to get more shareware donation. But still, this software is shareware. Pay or die! ;-) Version 1.1 ----------- -The OS1.3 crash bug has been fixed. The level 1 and level 5 interrupts do no longer use EXEC's ExitIntr() because there is an incompatibility between OS1.3 and OS2.0 which caused the crash. -Version information has been corrected. You will now get the correct version string if you enter "version BaudBandit.device" in a shell. Version 1.2 ----------- -Fixed a bug in programming the timer device. This caused problems with RTS/CTS handshaking on some systems. VBlank timer is now used instead of CIA timer. Version 1.3 (not released) -------------------------- -The CTS timer abort-check was broken. This possibly caused hazardous problems. Fixed now. -The device no longer crashes if there is no memory for a preferences structure to get the default baudrate and buffersize. -Trying to eliminate the nasty receive-error bug, I reworked the read and write routines and improved safety in interrupt disabling/enabling. This had NO positive effect. Argh. -Another attempt to kill that bug: The RBF bit in INTREQ is now cleared AFTER the byte is fetched from SERDATR. Smashed that bug! ;-))) Finally, no more transmission errors! Version 1.4 ----------- -I decided to completely rewrite the request queuing. Read and write requests are now queued using real list structures, similar to serial.device. Since this is a major change, it is now version 1.4. -Found an incompatibility to serial.device: The IO_FLAGS were not cleared before executing any IO function. This caused many unexpected side effects like e.g. unanswered IO Requests and more. -Since there is such a big discrepancy between the number BaudBandit REGISTERED USERS and BaudBandit ILLEGAL USERS, I decided to include a little text that will be displayed on your terminal screens. It just reminds people to register. Nothing too disturbing, though. -I reworked the BaudBandit.Doc file, so better read it again. Version 1.4a ------------ -Fixed a bug in AbortIO: The request was always replied, even if it couldn't be aborted! (e.g. because it was neither active nor queued) -From now on GvpFix, a modified GvpPatch, will be included in each BaudBandit release. It will patch in before gvpscsi.device to prevent transmission errors at higher baudrates when using BaudBandit. Version 1.4b ------------ -Fixed a nasty little bug in the timer device code. tv_Secs was not cleared before sending the IORequest to timer.device. On some systems, this caused long delays in RTS/CTS handshaking. -Improved shareware reminder text output. It is now displayed on the TrapDoor and NComm terminal as well, hehehe... Plans for future releases ------------------------- -Include Break support -Include XOn/XOff support -Include shareware requesters and a time limit, if nobody registers. Important note to users of Enforcer ----------------------------------- If you have your VectorBase located in FastRam and if you use BaudBandit and Enforcer simultaneously, your system will crash. This is Enforcer's fault. Enforcer itself copies the VectorBase to FastRam. But it will always copy the contents of address 0-$400 instead of looking where the VectorBase was located before. Please tell the author to fix that. Before you start Enforcer, make sure that your VectorBase is located at address 0, even if you are not using BaudBandit!