Thank you for your replies.
Been troubleshooting my BBS over the weekend, and things get a little bit strange when I try to do anything more than simple menu activities.
For older computers like this, I use a fossil driver that manages all communications to the COM port from Telegard. I managed to get one fossil driver to operate (BNU), but when I launch things like DOOR games, things tend to break down in communications.
For instance, I set up a LORD door game, and whenever I try to type in my name, as soon as I hit the carriage return (ENTER), it performs the carriage return and also adds a . (PERIOD), so it fails at the next prompt (which is a yes or no reply - . is not a valid reply).
I tried multiple fossil drivers, various settings with the LORD door game, but it seems that it is a bug somewhere that is causing the failure. I checked my terminal program by using another, and its the same behaviour. I have narrowed it down to either the WiModem232, or the LORD door software.
Been troubleshooting my BBS over the weekend, and things get a little bit strange when I try to do anything more than simple menu activities.
For older computers like this, I use a fossil driver that manages all communications to the COM port from Telegard. I managed to get one fossil driver to operate (BNU), but when I launch things like DOOR games, things tend to break down in communications.
For instance, I set up a LORD door game, and whenever I try to type in my name, as soon as I hit the carriage return (ENTER), it performs the carriage return and also adds a . (PERIOD), so it fails at the next prompt (which is a yes or no reply - . is not a valid reply).
I tried multiple fossil drivers, various settings with the LORD door game, but it seems that it is a bug somewhere that is causing the failure. I checked my terminal program by using another, and its the same behaviour. I have narrowed it down to either the WiModem232, or the LORD door software.