Issues with ANSI art and FreeBSD reddit / bbs ---------------------------------------------------------------------- ImageJPEG · 2023-05-21 02:03 I’ve done a little research and it seems that the terminals don’t like the ANSI escape sequences; at least with regards to Linux OSes; but I’m having similar behavior on FreeBSD. I’ve tried dialing into a few BBSes and I just receive a bunch of random characters. This behavior occurs in SyncTerm natively AND with Banana Com running in DOSBox. Any suggestions? I’ve tried dialing into a few BBSes and it happens with all. When I connect, it does say it’s connected at a certain speed but that’s the only thing that I can make out. I’ve tried dialing into The Keep, Diamond Mine Online, and the 2600 Network. ---------------------------------------------------------------------- TotesMessenger · 2023-05-21 02:11 I'm a bot, *bleep*, *bloop*. Someone has linked to this thread from another place on reddit: - [/r/freebsd] [Issues with ANSI art on BBSes](https://www.reddit.com/ r/freebsd/comments/13nfxld/issues_with_ansi_art_on_bbses/)  *^(If you follow any of the above links, please respect the rules of reddit and don't vote in the other threads.) ^\([Info](/r/TotesMessenger) ^/ ^[Contact](/message/compose?to=/r/TotesMessenger))* ---------------------------------------------------------------------- KookyWait · 2023-05-21 02:45 Have you set your terminal's width appropriately? I bet a lot of these assume 80 columns. ---------------------------------------------------------------------- digitlman · 2023-05-21 03:39 If you’re running SyncTERM in X or SDL screen mode, the terminal you ran SyncTERM from makes no difference at all. What Screen Mode are you running SyncTERM in? ---------------------------------------------------------------------- ImageJPEG · 2023-05-21 03:47 I’ve tried X, SDL, and ANSI with similar behavior. In ANSI, I get a lot of question marks though. ---------------------------------------------------------------------- ImageJPEG · 2023-05-21 03:48 SyncTerm and Banana Com are both set in 80 columns. ---------------------------------------------------------------------- opt_in_out_in_out · 2023-05-21 05:14 Could you post a screenshot? There's a number of things it could be. Edit: *yes, I am captain obvious* ---------------------------------------------------------------------- ImageJPEG · 2023-05-21 17:11 [https://drive.proton.me/urls/SRS5SWWMD4#UHotZSIU7PwR](https://drive.p roton.me/urls/SRS5SWWMD4#UHotZSIU7PwR) ---------------------------------------------------------------------- opt_in_out_in_out · 2023-05-21 21:36 Thanks. This looks like a line speed issue. That garbage is exactly what I get if I am using a serial connection where the two ends don't agree on the line speed. When you say 'dialled in', are you literally on a modem, or just using it metaphorically for the telnet connection? Assuming an actual serial connection, you could try all the other line speeds until you find the one that works. Some of your screen shots say 57600, and some say 115200, so this could be a clue (or a red herring). ---------------------------------------------------------------------- ImageJPEG · 2023-05-21 23:05 I’m using a real modem. It’s a USR Courier 3453C. It works on my DOS machine at 19200 (the highest rate my IBM P/S ValuePoint can go) but even if I set the rate to that it still gives me a garbled mess. ---------------------------------------------------------------------- digitlman · 2023-05-21 23:08 The issue demonstrated in those screenshots has nothing to do with ANSI ---------------------------------------------------------------------- ImageJPEG · 2023-05-22 00:34 You are correct. I had to do some tinkering with the serial ports on FreeBSD to force it into a baud rate. ​ [https://docs.freebsd.org/en/books/handbook/serialcomms/](https://docs .freebsd.org/en/books/handbook/serialcomms/) ​ For anyone interested, I had to issue (as root): stty -f /dev/cuau0.lock 115200 and now I can run SyncTerm at 115200 without issue. I'm still needing to set the baud rate at boot, however. ---------------------------------------------------------------------- ImageJPEG · 2023-05-22 00:35 Update: [https://www.reddit.com/r/bbs/comments/13nfto8/comment/jl3hz2f/?utm\_s ource=share&utm\_medium=web2x&context=3](https://www.reddit.com/r/bbs/ comments/13nfto8/comment/jl3hz2f/?utm_source=share&utm_medium=web2x&co ntext=3) ---------------------------------------------------------------------- opt_in_out_in_out · 2023-05-22 01:16 Excellent news ---------------------------------------------------------------------- ImageJPEG · 2023-05-23 05:41 I’m afraid I celebrated too early. It works IF my modern connection speed AND serial device are set at the sane baud rate. So if my serial port is set to 9600 and my BBS connection I’d 9600, all is fine. If I set my modern/serial port to 115200 and I get a 19200 baud connection (like dialing into the NIST ACTS time service), I get a jumbled mess like on the screenshots. ---------------------------------------------------------------------- ImageJPEG · 2023-05-23 05:42 https://reddit.com/r/bbs/comments/13nfto8/_/jl99gm3/?context=1 Celebrated too early. ---------------------------------------------------------------------- opt_in_out_in_out · 2023-05-23 07:49 Key here is locking the speed somehow - keeping the same speed between the computer and modem regardless of anything else. It used to be the norm, because like you say, you never know what speed the two modems are going to end up negotiating. Maybe it is a modem setting? Have you done a factory reset? (from deepest memory it was AT&F before any other initialisation) ---------------------------------------------------------------------- RealDeuce · 2023-06-11 15:32 It sounds like you're saying that when you set an entry to 115200, SyncTERM does not open the serial port at that speed? That sounds like a SyncTERM bug. EDIT: Just looked at the code and nothing jumps out... now I suspect it may be a modem init string issue. Can you paste your init string in here?