I'm in need of a copy of the updated Rlogin client that supports the -D command. Can anybody direct me?
Thanks!
BlaZ
Rlogin client
Re: Rlogin client
I recommend sending daniel_spain a PM, from memory it was something he wrote.
-- Duckula
// Site admin
// Galacticomm IP owner
// Site admin
// Galacticomm IP owner
Re: Rlogin client
You can actually get a version of Daniel's rlogin from DoorParty.
Re: Rlogin client
As it turns out, I already have it. So my problem is my GameSrv configuration. I'm playing with it now. I need to get it to recognize the door code I give it with the -d option. I tested this with DoorParty and it worked fine, so the -d option does indeed work for me.
I'm guessing I need to change the logonprocess.ini file. We'll see...
BlaZ
I'm guessing I need to change the logonprocess.ini file. We'll see...
BlaZ
-
- Posts: 440
- Joined: Sun Aug 09, 2020 2:39 am
Re: Rlogin client
BlaZ wrote:
> As it turns out, I already have it. So my problem is my GameSrv
> configuration. I'm playing with it now. I need to get it to recognize the
> door code I give it with the -d option. I tested this with DoorParty and
> it worked fine, so the -d option does indeed work for me.
>
> I'm guessing I need to change the logonprocess.ini file. We'll see...
>
> BlaZ
also after command lines there can be no spaces, so:
YES: -d Usurper
NO: -d Usurper 0.07
but wait.... -d was synchronet door external -t was doorparty right? same rule applies though -t <tagid> not -t <tag id>
> As it turns out, I already have it. So my problem is my GameSrv
> configuration. I'm playing with it now. I need to get it to recognize the
> door code I give it with the -d option. I tested this with DoorParty and
> it worked fine, so the -d option does indeed work for me.
>
> I'm guessing I need to change the logonprocess.ini file. We'll see...
>
> BlaZ
also after command lines there can be no spaces, so:
YES: -d Usurper
NO: -d Usurper 0.07
but wait.... -d was synchronet door external -t was doorparty right? same rule applies though -t <tagid> not -t <tag id>
Re: Rlogin client
I got the DoorParty autolaunch to work testing it out using the -d option. I did not try -t. My BBS is down right now while I'm making a backup, but I'll do some more testing here shortly...
-
- Posts: 440
- Joined: Sun Aug 09, 2020 2:39 am
Re: Rlogin client
BlaZ wrote:
> I got the DoorParty autolaunch to work testing it out using the -d option.
> I did not try -t. My BBS is down right now while I'm making a backup, but
> I'll do some more testing here shortly...
i was working with the author of DP to make is so you could run both on the same machine. my newest rlogin stuff does
so you can run say a Worldgroup Server, Synchronet Server on same server but because of my dma test stuff i dont
release it yet, i will get around to getting a release out so you dont need multiple systems.
> I got the DoorParty autolaunch to work testing it out using the -d option.
> I did not try -t. My BBS is down right now while I'm making a backup, but
> I'll do some more testing here shortly...
i was working with the author of DP to make is so you could run both on the same machine. my newest rlogin stuff does
so you can run say a Worldgroup Server, Synchronet Server on same server but because of my dma test stuff i dont
release it yet, i will get around to getting a release out so you dont need multiple systems.
Re: Rlogin client
So I did some more testing with the rlogin client I've got.
I've got the version of the rlogin client that has the -d option, the -m option for setting the module name (which only seems to affect the /# user list which is also built into the rlogin client module and overrides the default WG /# command.) I tried it with -t, as you mentioned earlier, and that command is not supported on my version of the rlogin client. Using -d LORD or whatever with DoorParty connector works great. If anybody can tell me what I need to change in my GameSrv configuration so that it will recognize that -d command, that would be awesome! That's definitely where my problem is right now.
As far as running it all on one machine, I'm running Doorparty connector, Synchronet, Worldgroup and a MBBS DMA Server all on the same "computer" which is a Win10 VM in VMware. I just have to bind things to separate NIC cards to make it all work right.
I've got the version of the rlogin client that has the -d option, the -m option for setting the module name (which only seems to affect the /# user list which is also built into the rlogin client module and overrides the default WG /# command.) I tried it with -t, as you mentioned earlier, and that command is not supported on my version of the rlogin client. Using -d LORD or whatever with DoorParty connector works great. If anybody can tell me what I need to change in my GameSrv configuration so that it will recognize that -d command, that would be awesome! That's definitely where my problem is right now.
As far as running it all on one machine, I'm running Doorparty connector, Synchronet, Worldgroup and a MBBS DMA Server all on the same "computer" which is a Win10 VM in VMware. I just have to bind things to separate NIC cards to make it all work right.
-
- Posts: 440
- Joined: Sun Aug 09, 2020 2:39 am
Re: Rlogin client
BlaZ wrote:
> So I did some more testing with the rlogin client I've got.
>
> I've got the version of the rlogin client that has the -d option, the -m
> option for setting the module name (which only seems to affect the /# user
> list which is also built into the rlogin client module and overrides the
> default WG /# command.) I tried it with -t, as you mentioned earlier, and
> that command is not supported on my version of the rlogin client. Using -d
> LORD or whatever with DoorParty connector works great. If anybody can tell
> me what I need to change in my GameSrv configuration so that it will
> recognize that -d command, that would be awesome! That's definitely where
> my problem is right now.
>
> As far as running it all on one machine, I'm running Doorparty connector,
> Synchronet, Worldgroup and a MBBS DMA Server all on the same
> "computer" which is a Win10 VM in VMware. I just have to bind
> things to separate NIC cards to make it all work right.
so the rlogin client itself uses the -d option to send a "hack" to the synchronet system, what it does is sends a string of text to synchronet which in part directly enters an external program that has an internal code that matches the text. i have spoken with the gamesrv author and it is on his todo list but no idea when that will be.
Only difference in the version you got and a newer one is doorparty tag support, i am redoing the -m option later.
> So I did some more testing with the rlogin client I've got.
>
> I've got the version of the rlogin client that has the -d option, the -m
> option for setting the module name (which only seems to affect the /# user
> list which is also built into the rlogin client module and overrides the
> default WG /# command.) I tried it with -t, as you mentioned earlier, and
> that command is not supported on my version of the rlogin client. Using -d
> LORD or whatever with DoorParty connector works great. If anybody can tell
> me what I need to change in my GameSrv configuration so that it will
> recognize that -d command, that would be awesome! That's definitely where
> my problem is right now.
>
> As far as running it all on one machine, I'm running Doorparty connector,
> Synchronet, Worldgroup and a MBBS DMA Server all on the same
> "computer" which is a Win10 VM in VMware. I just have to bind
> things to separate NIC cards to make it all work right.
so the rlogin client itself uses the -d option to send a "hack" to the synchronet system, what it does is sends a string of text to synchronet which in part directly enters an external program that has an internal code that matches the text. i have spoken with the gamesrv author and it is on his todo list but no idea when that will be.
Only difference in the version you got and a newer one is doorparty tag support, i am redoing the -m option later.
Re: Rlogin client
*** UPDATE: Problem resolved successfully.
To fix this, I had to dump the old "updated" rlogin client that I had (the one with the -m option) and go with the one downloadable from the DoorParty website. Actually downloading the file was a pain, so if there's a place I can send it so it can be hosted here, please give me that information and I will send the good copy of the rlogin client.
Using this updated client, I can now get doors to autolanch in GameSrv, DoorParty and Synchronet by using the "-d doorcode" command. Synchronet requires a small modification to the modopts.ini file. Everything else works out of the box.
Thanks to everyone who helped me with this problem.
To fix this, I had to dump the old "updated" rlogin client that I had (the one with the -m option) and go with the one downloadable from the DoorParty website. Actually downloading the file was a pain, so if there's a place I can send it so it can be hosted here, please give me that information and I will send the good copy of the rlogin client.
Using this updated client, I can now get doors to autolanch in GameSrv, DoorParty and Synchronet by using the "-d doorcode" command. Synchronet requires a small modification to the modopts.ini file. Everything else works out of the box.
Thanks to everyone who helped me with this problem.