Subj : Totally Confused... To : Martin Kazmaier From : Digital Man Date : Sun Dec 21 2025 03:13 am Re: Totally Confused... By: Martin Kazmaier to Digital Man on Sun Dec 21 2025 12:45 am > DM> > supposed to. In my case, it's the new user procedure that needs to > DM> > be disabled. Every time I connect, it's as a new user and the real > DM> > name > DM> isn't > DM> > accepted as the same as the handle (sbbs simply reports that it's > DM> either a > DM> > dupe or invalid) as I think it's only 1 word. > > DM> And I told you how to disable that real name prompt. > > Ok, I just went through every message from you to me and didn't see that. > Could you please tell me again? Here are those instructions again, verbatim: You can eliminate that prompt entirely by creating the file ctrl/text.ini and adding the following line: EnterYourRealName = "" > DM> If you connect a second time with the same name, that wouldn't be > DM> another new user either, so "every time" sounds incorrect as well. > > It is forcing me to create a new user each time I connect because the real > name is invalid or duplicate. It doesn't say which. I have multiple users > with the same handle and different real names... That on it's own is > confusing. That doesn't make sense - if the rlogin-supplied user name already exists in your BBS's userbase, the user will not go through another new user registration again. It sounds like you're specifying a different username for each new rlogin connection. Your BBS's terminal server log output would clarify what's happening. i.e. compare the server log output between 2 successive connections. If the first connection completes the new user registration process, then a second connection (with the same username) should not start a new user registration again. > DM> Cool. I've never heard of it. Looks like it's running Synchronet: > DM> a-net-online.lol -- digital man (rob) > Yep, he's got it working so I can use that until I can manage this. I would > love to work with you on this and will try to calm down my idiosynchracies > (sorry I couldn't remember how to spell that) so that I'm easier to deal > with. He spent about 2 years to get his to the state that it's at. Rob > McGee (x-bit) also has a game server. His just asks for username and > location as well as mouse reporting and ansi on new user connection. I was > hoping to get to that state. Exodus also has one set up so that people can > access sbbs games from his Renegade. If that many people can use it, it > shouldn't be as difficult as I've experienced. Perhaps they all used a newer > version. The "newer version" (actually *versions*) of logon.js just add some more options that some sysops requested and can enable, as documented, but aren't required for baisc game server functionality. The basic rlogin-game-server functionality has been in Synchronet's logon.js for a long time now and isn't that complex to setup. > I just went to the synchronet website, which seemed the logical > place to get the latest version. I did read the game server wiki (thanks to > Stringray for pointing me to that) and follow it's instructions before I had > my melt-down. The rlogin/game-server support in Synchronet is controlled via the exec/logon.js script. You can see the edit history of this script (and download the latest version of it) here: https://gitlab.synchro.net/main/sbbs/-/commits/master/exec/logon.js Or... you could upgrade to the latest development build of Synchronet (which includes an updated logon.js) by following the instructions here: https://wiki.synchro.net/install:dev That's also the *second* link on the "download" "Synchronet for Windows" option at "the synchronet website" (www.synchro.net). -- digital man (rob) Sling Blade quote #8: Karl Childers: I don't reckon I got no reason to kill nobody. Norco, CA WX: 50.6øF, 92.0% humidity, 0 mph NNE wind, 0.00 inches rain/24hrs .