LORD error reddit / bbs ---------------------------------------------------------------------- njburchett66 · 2020-08-23 17:52 Anyone have this issue with running LORD under WWIV? [https://imgur.com/gallery/S1uyovj](https://imgur.com/gallery/S1uyovj) Every time I enter my name in, when I hit Enter it automatically enters a period where I should be answering Yes or No and doesn't let me go any further. Anyone have a fix? ---------------------------------------------------------------------- veeb0rg · 2020-08-23 18:48 I had this error with using SyncTerm for Lord on my WWIV bbs. Are you using syncterm? Try another terminal program if you are. ---------------------------------------------------------------------- WWIVPENGUIN · 2020-08-23 21:30 This is due to LR/CR set wrong in term program. If you can change the setting in your term, play with it. ---------------------------------------------------------------------- njburchett66 · 2020-08-23 22:11 Yeah, I am using SyncTerm. I'll check the settings and if no luck I i'll try another. Thanks! ---------------------------------------------------------------------- WWIVPENGUIN · 2020-08-27 12:47 What version of Lord are you running? Is this running under linux? windows? are you using dosbox? did you compile lord native? ---------------------------------------------------------------------- njburchett66 · 2020-08-27 13:31 It was running at the time of this post on Linux. I switched to Windows 7 and it worked. ---------------------------------------------------------------------- WWIVPENGUIN · 2020-08-27 17:37 Getting DOS apps running under Linux is getting harder and harder as time goes by. The way DOS apps access CPU instructions, and memory are very dangerous from a stability and security standpoint, and these methods simply no longer exist in the Linux kennel. Windows is probably not far behind in this. The common method in the past for BBS doors was using dosemu. Which is not virtualization but on the fly code/instruction translation. The app still executes in the native cpu instruction stack. Since this can be easily exploited the methods are being removed from the kennel. Dosemu has not actively been developed in a long long time, and although the program could be rewritten to get around this, I don't think anybody will take that on. Dosbox is a hybrid, it does on the fly code/instruction translation when possible for performance, and true virtualization when not. The problem with Dosbox (an awesome app however) is it's not designed with any good ways to chain to it, it call it within a sandboxed environment like the BBS. Qemu is the closest thing to dosemu that exists. I'm sure it's 100% possible to replace what we used dosemu for, but the process needs to be perfected and documented. The next problem we hit with running these old apps outside of virtualization is modern 64 bit processors. As commuter processors advance it's become nesicary to flat out remove old instruction sets that are no longer used in modern computing. This is done to reduce cost, complexity, transistor count, heat, and power consumption. This is usually fine because 99.999% of the population will never need or miss them, and for the small number that do, fill virtualization software fills that gap, leaving us weird retro dorks hanging.