ÉÍÍÍÍÍÍÍÍÍÍÍÍÍ[ SPITFIRE Bulletin Board System ]ÍÍÍÍÍÍÍÍÍÍ» º º º Fool's Gold BBS º º º º Tricom Tornado Quin 42 º º º º 22nd August 1991 º º º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ I have had a lot of problems using a TriCom Tornado Quin 42 modem with the Spitfire Bulletin Board System V3.1 however I have found that the following settings solved all my problems. 1/ Modem would answer calls during maintenance routines when Spitfire had taken it 'off the hook', which meant that callers could get an answer from the board but then nothing. Solution Remove the Auto Answer by setting Front Switch 5 DOWN 2/ BBS Crash would not work over the modem but was fine in local mode. Modem users gat ntohing but garbage on the screen. Solution The modem was reporting a baud rate of 2400 which Spitfire dutifully passes to BBS Crash in the SFDOORS.DAT file but the modem is doing speed buffering so that the real baud rate from computer to modem is 9600. BBS Crash has its own serial routines which use the Baud rate in SFDOORS.DAT which gives garbage over the modem link. Set Rear Switch 8 UP, send \J1 in the initialisation string, and set Spitfire option to NO hardware Data Flow Control (ALT M menu). 3/ For modems running at less than 9600 there was intermittent corruption of long messages e.g. file lists. Solution The modem was running at 2400 but the computer link was set for 9600 so Solution to 2 above cured most of the problems but setting the modem for RTS/CTS flow control solved the remaining problems The combination works fine but I have only been able to test at 2400 Baud so it is just possible that there may be other problems at lower baud rates. TriCom Tornado Quin 42 Front Switches S1 S2 S3 S4 S5 S6 S7 S8 S9 S10 Up X X X X X X Down X X X X Rear Switches S1 S2 S3 S4 S5 S6 S7 S8 Up X X X X Down X X X X Spitfire V3.1 Initialisation String for Spitfire (Option ALT M menu) ATQ0V1E0M1%F0%L1\J1*W^M Hardware Flow Control (Option ALT M menu) NO /* End of file 22/8/91 */