Scratch my last message. I have had it! What is going on? 
After successfully configuring Striketerm 2013 final for use at 9600 baud with the UP9600 driver I saved the configuration. I used the modem to connect to a BBS and then to SDF.ORG. After logging out of sdf.org I shutdown.
I restarted the computer, load and run Striketerm 2013. The software booted with the saved configuration.
I selected F3 for terminal. The terminal failed to respond to keyboard input.
I went back to the terminal menu and selected C= and the e key. The terminal responded by echoing keyboard input.
Striketerm did not respond to commands. I.E. atdt whateverbbs.dynu.net:6400 yielded nothing. The same with every other command that I input. No Response!
I have a basic modem that I bought for $20 bucks including S&H just to see if I would like going back to the old BBS system via wifi. It does run at 9600 baud flawlessly in Striketerm 2014 Final and CCGMS 2020.
After successfully configuring Striketerm 2013 final for use at 9600 baud with the UP9600 driver I saved the configuration. I used the modem to connect to a BBS and then to SDF.ORG. After logging out of sdf.org I shutdown.
I restarted the computer, load and run Striketerm 2013. The software booted with the saved configuration.
I selected F3 for terminal. The terminal failed to respond to keyboard input.
I went back to the terminal menu and selected C= and the e key. The terminal responded by echoing keyboard input.
Striketerm did not respond to commands. I.E. atdt whateverbbs.dynu.net:6400 yielded nothing. The same with every other command that I input. No Response!
I have a basic modem that I bought for $20 bucks including S&H just to see if I would like going back to the old BBS system via wifi. It does run at 9600 baud flawlessly in Striketerm 2014 Final and CCGMS 2020.