WiModem232 and ProTERM 3.1 for Apple II

[Kailef]

With Dura-Europos, most of the time ProTERM drops into Online mode after connection. When it does, Dura cannot detect my terminal emulation properly even though that is set in the Emulation entry on the Dial screen. Since Dura asks me during connection what kind of terminal I use, I will choose the proper one. Typically, I am using ProTERM Special. After I disconnect from the BBS gracefully ('T' for Terminal Connection at the BBS's main menu), ProTERM goes Offline properly.

In the case of Sanctum, the WiModem232 shows connected on the OLED display but ProTERM never goes online. It will sit there and re-dial forever. I can cancel and put myself online (option-T) and then interact with the BBS. Again, the emulation mode is set to ProTERM Special.

I just wanted to mention that I have a similar issue.  Proterm 3.1 somehow doesn't notice that we've successfully connected to Sanctum and I have to manually go into Online mode to actually interact.  Not sure if that's the fault of the modem or the software, though.  I also have the same problem you mentioned with Dura-Eurpos, it used to (but no longer) detects that I'm running Proterm Special emulation and I have to manually select it.  However, it's important to note that the Skip has been doing all kinds of stuff on his BBS lately including deploying new modem drivers and a 16 mhz accelerator, so those issues could be on his side rather than ours.

I find myself using Agate because just dialing from a raw terminal seems to be more reliable, and of course Agate has it's amazing ANSI emulation on an Apple 2, but I do miss the slick features of Proterm like the editor, scrollback, address book, macros, autologins, and Proterm special emulation.  If/when I find a way and/or a firmware update comes along that makes Proterm more reliable I'll go back to using it as my primary terminal program unless I happen to need to call an ANSI board.