MysticBBS on Linux - terminal output from doors reddit / bbs ---------------------------------------------------------------------- que_two · 2023-12-22 23:20 I've been in the process of migrating my old BBS that was still running on OS/2 to Linux. I got just about everything moved over successfully, but I'm having an issue with doors under Linux. It seems that in 1.12 A48 the default option when you launch a door with DD or D3, it will pump any terminal output to the telnet/ssh/modem. I've got my doors working with FOSSIL drivers within dosemu2, but what's happening is that the caller is picking up the raw game content via the FOSSIL driver /and/ output on the terminal... essentially they are seeing the content twice on the screen. Is there a hidden parameter somewhere that disables that terminal echo? Or, is there something else people are doing to get this to work right? I guess a backup option is to disable all the FOSSIL and COM routines in the doors and just go with local mode (which for some of them also shows local stuff like status bars and chat options which I'm not a fan of). ---------------------------------------------------------------------- Call_Me_Mauve_Bib · 2023-12-23 01:50 You could cat stdout to /dev/null as a temporary measure, I guess. ---------------------------------------------------------------------- ten-oh-four · 2023-12-23 18:09 How are you currently launching a door? Show me what you're using and I can help get it to where it needs to be :) ---------------------------------------------------------------------- que_two · 2023-12-23 19:54 Thanks for the offer! Here is where I'm at, for the moment... MysticBBS 1.12 A48, running on Ubuntu 2022 LTE, Dosemu 2 installed via the packages. Nothing else really special other than kvm support is disabled on the host. Have a very basic BNU Fossil driver installed. Mystic Menu config : [https://s3.us-east- 2.amazonaws.com/assets.s8700.net/Snag\_283598b5.png](https://s3.us- east-2.amazonaws.com/assets.s8700.net/Snag_283598b5.png) Bash Script to launch dosemu, called from Mystic : [https://s3.us-east -2.amazonaws.com/assets.s8700.net/Snag\_283598b4.png](https://s3.us- east-2.amazonaws.com/assets.s8700.net/Snag_283598b4.png) Dosemu2 "autoexec" batch file (userhook.bat) : [https://s3.us-east- 2.amazonaws.com/assets.s8700.net/Snag\_28359885.png](https://s3.us- east-2.amazonaws.com/assets.s8700.net/Snag_28359885.png) Dosemu user config file (primary in /etc/dosemu/dosemu.conf is default) : [https://s3.us-east- 2.amazonaws.com/assets.s8700.net/Snag\_28359886.png](https://s3.us- east-2.amazonaws.com/assets.s8700.net/Snag_28359886.png) L2 node config : [https://s3.us-east- 2.amazonaws.com/assets.s8700.net/Snag\_28359895.png](https://s3.us- east-2.amazonaws.com/assets.s8700.net/Snag_28359895.png) ​ Essentially, if I run the config above, the l2.exe won't launch at all. No errors or logs. If I take out the *-q -tde* from the bash script to launch dosemu, the door runs as expected, but the end user sees the content 2x (you see the stuff written to the screen, plus what is sent via the FOSSIL driver). This happens pretty much for all the doors I've been trying with, including Lord2, Lord, BTE, King of the Board and TW2002 (which I know has had some problems in the past). ---------------------------------------------------------------------- que_two · 2023-12-23 19:57 Tried that earlier on. For some reason, the TP compiled doors (which ends up being most of them) throws a Runtime 201 error.... Running theory I have on that is they are trying to access the tty and failing, but not quite sure. ---------------------------------------------------------------------- ten-oh-four · 2023-12-23 21:25 Interesting - you and I don't really differ anywhere as far as I can tell. Strange. I don't use the `-q -tde` args so I think you're probably safe to skip that. I also have `2>/dev/null` on the end of the line that launches the dosemu binary. Maybe this can help get you somewhere, not sure. Let me know how it goes.