-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frozen at "User logging in" step #3
Comments
Well for one, I'd probably use Turbo Pascal. NetFOSS/NetSerial is a
better option than ADF. Seems an issue of the rglng.txt not being updated
or compiled. 99% of the time the issue.
…On Sat, Dec 10, 2022 at 6:31 PM Robert Cadena ***@***.***> wrote:
Hi, I'm on commit 4004664
<4004664>
.
When attempting to log in, in either Local mode or via SyncTERM, both
regular and fast login, the screen gets stuck with the status bar message
saying "User logging in." (PASCAL.PAS:383
<https://github.com/leewoodridge/RenegadeBBS/blob/main/SOURCE/RENEGADE.PAS#L383>
).
It actually appears to stop (not crash or anything, just freeze at the
line) when inside the function GetUser
<https://github.com/leewoodridge/RenegadeBBS/blob/main/SOURCE/LOGON.PAS#L757>
while trying to call Get_Node. I didn't get much deeper than that and I'm
not sure how to do step-through debugging on Borland Pascal (been a while).
Anyway, I also commented out additional calls until I could get the
Renegade welcome screen rendered (LoadNode, SaveNode, Check_Ansi). Once I
finally got that Renegade Screen showing up, I don't see any character echo
but I do see this random stuff being rendered back
[image: syncterm_rg_junk]
<https://user-images.githubusercontent.com/73070/206879342-f26c5011-7342-4938-bca8-af97b6665973.png>
If i type a character, I get several lines of that last random-looking
junk near the bottom of the image.
System:
Compiled with Borland Pascal 7.0
Running under DosBox (os x)
ADF Fossil driver (for telneting)
I am able to succesfully run a pre-compiled version of Renegade v1.19.
I've no clue how to proceed. Happy to help if you can think of something I
can try myself.
Thanks!
—
Reply to this email directly, view it on GitHub
<#3>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2LMU2PGVVAN4JIFZOVMULWMUHETANCNFSM6AAAAAAS2SC6QQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@Renegade-Exodus - I went with TP because the BUILDBP.CMD used BP. I'll give TP a try. Thanks. |
Also, why aren't you using v1.30/DOS release from www.rgbbs.info? |
But, also, I just started this project a few days ago and I think the first google result I got for Renegade BBS was here: https://renegadebbs.info/ which only has 1.19. It wasn't until I got to your bbs that I learned about 3.0 - will definitely try that if I can't get it to compile, but, I'd love to be able to make changes if I want. Thanks again for the help. |
@rcadena
We're always looking to add people to the team. So if you got an idea,
change away and we'll how well it works on our roadmap. If you're willing.
…On Sat, Dec 10, 2022 at 6:51 PM Robert Cadena ***@***.***> wrote:
Also, why aren't you using v1.30/DOS release from www.rgbbs.info?
I wanted to try compiling from source.
But, also, I just started this project a few days ago and I think the
first google result I got for Renegade BBS was here:
https://renegadebbs.info/ which only has 1.19. It wasn't until I got to
your bbs that I learned about 3.0 - will definitely try that if I can't get
it to compile, but, I'd love to be able to make changes if I want.
Thanks again for the help.
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2LMU3FJ2HHM7EM7TDNHI3WMUJOZANCNFSM6AAAAAAS2SC6QQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
No dice. Things I tried:
Same problem. I tried just running locally ( I'll mess around some more and see what I can figure out. Screen.Recording.2022-12-10.at.4.53.19.PM.mov |
@rcadena
Are you sure you have the COMPLETE rglng.txt file and the most current
RGLNG.EXE compiled? That is more likely than the problem. You are
missing strings in the lng file and didn't compile it with the most current
rglng.exe file. Grab the full install from the real website and let me
know if that works okay. If it does, use the files from that full install
for your bbs setup and then try to compile renegade again and copy it and
the ovr over to your bbs dir. 99% sure that will fix the issue.
www.rgbbs.info
DO NOT trust anything on renegadebbs.info/renegadebbs.net ... I gave those domain away years
ago, and Mr. Professor is our resident squatter with it and adds his own
shit to everything on it.
www.rgbbs.info
is the ONLY Renegade BBS site for RG support.
Hope that helps! Later!
…On Sat, Dec 10, 2022 at 8:00 PM Robert Cadena ***@***.***> wrote:
No dice.
Things I tried:
- compiled with TP 7.0
- made sure to call RGLNG.EXE
Same problem. I tried just running locally (/L) in case it was the fossil
driver, but same problem.
Strange thing is some of the sysop screen menus work, like the System
Editor, but the User Editor will halt halfway through the display.
I'll mess around some more and see what I can figure out.
https://user-images.githubusercontent.com/73070/206881467-b0b90a37-0369-4a3f-948d-68466a2fbde7.mov
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2LMUZES4PACGDAY33N6L3WMURR7ANCNFSM6AAAAAAS2SC6QQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
man, you were so right. So, the thing I tried instead was to get the full V1.3 working local and via telnet. Worked. Tried local: worked. So, yeah. It's just the Thanks for the heads-up re: the other domain. Ok, thanks again for the help. |
Been down that road 1000 times. :) Sounds like something we should
probably add. :) If you come up with a cool way of doing so, merge it with
the master and we'll look it over. Glad it worked out for you. Later!
…On Sat, Dec 10, 2022 at 9:02 PM Robert Cadena ***@***.***> wrote:
man, you were so right. So, the thing I tried instead was to get the full
V1.3 working local and via telnet. Worked.
Then I compiled from source (made a tweak to make sure i was running my
compiled version) and replaced RENEGADE.{EXE|OVR} with the compiled
version. Tried local: worked. Tried telnet: WORKED!
So, yeah. It's just the RGLNG.TXT. Thanks for your patience. I'm gonna
look into this particular problem and see if there's a way to dump out an
error if the string is malformed or non-existent or something. Just for my
debug purposes.
Thanks for the heads-up re: the other domain.
Ok, thanks again for the help.
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2LMU2UW2LP7UZNWPMNOY3WMUY23ANCNFSM6AAAAAAS2SC6QQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi, I'm on commit 4004664.
When attempting to log in, in either Local mode or via SyncTERM, both regular and fast login, the screen gets stuck with the status bar message saying "User logging in." (RENEGADE.PAS:383).
It actually appears to stop (not crash or anything, just freeze at the line) when inside the function
GetUser
while trying to callLoadNode
. I didn't get much deeper than that and I'm not sure how to do step-through debugging on Borland Pascal (been a while).Anyway, I also commented out additional calls until I could get the Renegade welcome screen rendered (
LoadNode
,SaveNode
,Check_Ansi
). Once I finally got that Renegade Screen showing up, I don't see any character echo but I do see this random stuff being rendered backIf i type a character, I get several lines of that last random-looking junk near the bottom of the image.
System:
Compiled with Borland Pascal 7.0
Running under DosBox (os x)
ADF Fossil driver (for telneting)
I am able to succesfully run a pre-compiled version of Renegade v1.19.
I've no clue how to proceed. Happy to help if you can think of something I can try myself.
Thanks!
The text was updated successfully, but these errors were encountered: