Anyone ever see this? Last thing I was editing was some textblocks (WG textblocks, not MUD). I feel like if I revert them back it fixes but then it happens again so not sure. If I try to telnet in, it just sits there, connected but with no response. As soon as I press F7 on the console, the logon screen loads on the telnet client.
edit: Actually, I don't even have to press F7, it can be any key. Telnet to box -> connects but shows nothing -> press any key, e.g. just press "A" on console window -> screen loads on remote telnet client
WG not allowing logons until key pressed on the console
Re: WG not allowing logons until key pressed on the console
make sure the textblock you edited is saved???? must of used a bad variable or misspelled it never seen the prob you mention so really dunno
Re: WG not allowing logons until key pressed on the console
Well before I went to bed I disabled dialsoft control and it started working again. Control is proving to be a royal pain in the ass with all of its bugs. I have to do more testing to make sure it's actually the culprit and to see why all of a sudden it started happening.
- BearFather
- Posts: 668
- Joined: Sun Feb 09, 2014 6:27 pm
- Location: Portland, OR
- Contact:
Re: WG not allowing logons until key pressed on the console
I remember from old days how much it was a pain and why I never loaded it up when I started my board again. We really need to find someone who can write a new one.
Re: WG not allowing logons until key pressed on the console
I re-enabled it after doing a couple days of random WG and MMUD tweaks and it's working fine again. No clue.
Re: WG not allowing logons until key pressed on the console
So I think this was actually just a problem of using the old style console window. It started doing some weird shit today where it would pause all input to the board until I pressed keys at the console. And after a second it would stop again. I would have to sit there hitting tab over and over to keep it running. I tried disabling control (and reloading board) and it didn't help. Then I disabled the old console (on a hunch) and it worked. And immediately the other person helping me test the board at the moment said his connection to the board was way faster now.
So is there some sort of fix for the console window performance? And this leads me to another question: http://www.mudinfo.net/viewtopic.php?f=44&t=2093
So is there some sort of fix for the console window performance? And this leads me to another question: http://www.mudinfo.net/viewtopic.php?f=44&t=2093