• Internet Rex

    From Gregory Deyss@1:266/512 to All on Wed Sep 26 17:51:00 2012
    My question is about internet rex under
    node manager --> in a users node entry
    connection information why is I can not edit any passwords
    that exist such as packet password, encryption password, or session
    password or even rexfix password, in fact all of these are grayed out.
    The only 5 options within this connection information menu that I can
    change is the the toggles yes or no.
    ╔═[■]╡ Connection information ╞═══════════════════╗
    ║ ║
    ║ Packet level password ******** ║
    ║ Encryption password ******************** ║
    ║ ║
    ║ Session password ******************** ║
    ║ RexFix password ******************** ║
    ║ Send notify messages Yes ║
    ║ Send help messages Yes ║
    ║ Secure connection No ║
    ║ Send acknowledgements No ║
    ║ ║
    ║ Accept resend requests No ║
    ║ ║
    ║ ║
    ║ ║ ╚═════════════════════════════════════════════════╝
    It would appear as if there is some password that does exist there
    but there is not because I deleted the node and I get the same result.
    The internet rex version that I am using is 2.29, shareware unreg.
    I would like to fully register irex, but I would like to get these
    issues fixed first, I do understand that the shareware has a limited
    number of nodes that would be functional, but certainly I should be able
    to modify the password selection.
    Thanks for your replies,
    - Greg

    --- QScan/PCB v1.20a / 01-0462
    * Origin: Christian Fellowship | cfbbs.dtdns.net 856-933-7096 (1:266/512)
  • From Roy Witt@1:387/22 to Gregory Deyss on Thu Sep 27 15:11:58 2012

    26 Sep 12 17:51, Gregory Deyss wrote to All:

    My question is about internet rex under
    node manager --> in a users node entry
    connection information why is I can not edit any passwords
    that exist such as packet password, encryption password, or session password or even rexfix password, in fact all of these are grayed
    out.

    If you use your 'arrow' keys to navigate these different levels, when you highlight one of them, press 'enter' and your cursor should be on that
    level. Whether you can see it or not doesn't matter. Begin typing and
    there should be some response to your input.

    The only 5 options within this connection information menu that
    I can change is the the toggles yes or no.

    Does that part work?

    as if there is some password that does exist there but there is not because I deleted the node and I get the same result. The internet
    rex version that I am using is 2.29, shareware unreg.

    You don't say which shareware version, DOS, WIN, OS2 or LINUX...

    Linux users seem to have the most problems configuring Irex.

    I would like to fully register irex, but I would like to get these
    issues fixed first,

    I wouldn't bother, since this program is no longer actively supported by
    the author. I've used Irex for years and it's still functional, even with
    its various quirks. Once configured, it will serve you well, but don't
    expect any help from the author.

    I do understand that the shareware has a limited number of
    nodes that would be functional, but certainly I should be able to
    modify the password selection. Thanks for your replies, - Greg

    My keyboard has a function key that allows the keys that don't work in
    Irex to be used as intended. You might try using one of the CTL, ALT or
    Shift keys to make changes in Irex.

    R\%/itt


    ... Mark Owen: "Hey, did you ever hear anything about that beer?
    ... Fellow SEAL: "You believed that shit, I bet you voted for change too,
    ... SUCKER."


    --- GoldED+/W32-MSVC and D'Bridge 3.82
    * Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)
  • From Roy Witt@1:387/22 to RJ Clay on Thu Sep 27 23:08:14 2012

    27 Sep 12 12:51, RJ Clay wrote to All:

    My question is about internet rex under
    node manager --> in a users node entry
    connection information why is I can not edit any passwords
    that exist such as packet password, encryption password, or session
    password or even rexfix password, in fact all of these are grayed
    out.

    I'm also seeing the same kind of issue...

    Linux?

    After not having it running for quite awhile I decided to try
    setting it up again, so installed the Linux version of it on a
    virtual machine running Debian v4 ('Woody').

    Debian does present a problem. Most Linux users have probably given up on
    using IREX by now. The older Linux libraries are obsoleted by the newer versions. (whatever that means to you, new libraries makes no difference
    to a WIN user)

    Attempted BinkP connects to it are failing;

    thought to check the session password setting but like Gregory, found
    that none of the passwords are accessible for editing.

    Use your keyboard up/down arrow keys to select the level you want to enter
    a password. Hit (enter key) and the ******** will go away and show you a
    blank line. Enter a password and hit enter key again to save.

    You can also use the up/down arrow keys to select Send notify, Send help, Secure and Send Ack (sometimes there is no response to Send Ack, as it
    depends on other things configed in the nodes config). Pressing the Enter
    key Changes Yes and/or No to its opposite status.

    i.e. Send notify messages; No changes to Yes with one hit of the enter key
    and vice versa for Yes to No...

    Escape key exits this window and you can then save the nodes settings by exiting REX or continue to config another node...

    Always exit REXCFG with the Escape key and answer Yes to any changes made.


    R\%/itt


    ... Mark Owen: "Hey, did you ever hear anything about that beer?
    ... Fellow SEAL: "You believed that shit, I bet you voted for change too,
    ... SUCKER."


    --- GoldED+/W32 with D'Bridge 3.82
    * Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)
  • From RJ Clay@1:120/544 to Roy Witt on Sat Sep 29 11:13:20 2012
    Roy,

    27 Sep 12 23:08, you wrote to me:


    27 Sep 12 12:51, RJ Clay wrote to All:

    My question is about internet rex under
    node manager --> in a users node entry
    connection information why is I can not edit any passwords
    that exist such as packet password, encryption password, or
    session password or even rexfix password, in fact all of these
    are grayed out.

    I'm also seeing the same kind of issue...

    Linux?

    Internet Rex version 2.29 (LInux 32-bit)


    thought to check the session password setting but like Gregory,
    found that none of the passwords are accessible for editing.

    Use your keyboard up/down arrow keys to select the level you want to
    enter a password. Hit (enter key) and the ******** will go away and
    show you a blank line.

    By "not accessible" I mean that I cannot do that: the password settings lines are greyed out and if I press the up arrow at "Send Notify messages", it just goes to "Accept resend requests".


    You can also use the up/down arrow keys to select Send notify, Send
    help, Secure and Send Ack (sometimes there is no response to Send Ack,
    as it depends on other things configed in the nodes config). Pressing
    the Enter key Changes Yes and/or No to its opposite status.

    That works...




    Jame


    --- GoldED+/LNX 1.1.5-b20110213
    * Origin: ftn.rocasa.net (1:120/544)
  • From RJ Clay@1:120/544 to Roy Witt on Sat Sep 29 11:41:05 2012
    Roy,

    29 Sep 12 11:13, I wrote to you:

    Use your keyboard up/down arrow keys to select the level you want
    to enter a password. Hit (enter key) and the ******** will go
    away and show you a blank line.

    By "not accessible" I mean that I cannot do that: the password
    settings lines are greyed out and if I press the up arrow at "Send
    Notify messages", it just goes to "Accept resend requests".

    And note, btw, that I have the same issue with the 'Password password' item on the "General information screen. The item is listed on that configuration screen but is greyed out and using the up or down arrows just ends up skipping over it.



    Jame

    --- GoldED+/LNX 1.1.5-b20110213
    * Origin: ftn.rocasa.net (1:120/544)
  • From Roy Witt@1:387/22 to RJ Clay on Sat Sep 29 17:09:49 2012

    02 Sep 26 15:09, RJ Clay wrote to Roy Witt:

    Use your keyboard up/down arrow keys to select the level you want
    to enter a password. Hit (enter key) and the ******** will go
    away and show you a blank line.

    By "not accessible" I mean that I cannot do that: the password
    settings lines are greyed out and if I press the up arrow at "Send
    Notify messages", it just goes to "Accept resend requests".

    And note, btw, that I have the same issue with the 'Password
    password' item on the "General information screen. The item is
    listed on that configuration screen but is greyed out and using the
    up or down arrows just ends up skipping over it.

    If you have previously set a password there, you'll have to 'start' your
    rexcfg executable with -p, which will allow you to view and modify all passwords throughout the config program.

    i.e. recfgL.exe -pcarrot - if your password is carrot, will allow you to
    view and modify all other passwords. Otherwise, the fields will be there,
    but the passwords will be starred out and unmodifiable.

    Leaving the Password password blank will not have this effect on the
    passwords used to config a node in the config program. They should be accessable and modifiable.

    At least that's how it works in the Windows version.

    I have no experience at all with the Linux version of REX, so all I can
    tell you is to get ahold of someone like Robert Wolfe (1:261/20), who has plenty of experience with Linux and REX.

    R\%/itt


    ... Mark Owen: "Hey, did you ever hear anything about that beer?
    ... Fellow SEAL: "You believed that shit, I bet you voted for change too,
    ... SUCKER."


    --- GoldED+/W32 with D'Bridge 3.82
    * Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)
  • From Gregory Deyss@1:266/512 to Roy Witt on Sat Sep 29 13:00:00 2012
    Thanks for your reply Roy.
    I still don't understand why I could not enter that area to indicate
    passwords. However the problem is now fixed. What I did was I obtained a
    fresh copy of irex 2.29 (windows version) where rex runs within my
    windows tray. This time when I went throught the config for Irex
    everything worked fine, including the password area under connection
    manager.

    I am re-doing my BBS system, I really wanted to use PX/DOS and wildcat
    4.20 but I can not seem to get any netmail or echo mail to toss into the correct directory so that irex can see it. I also use binkd. Netmail and echomail tosses into the BBS fine. So I am will now be setting up
    frontdoor and synhronet bbs for windows, from what I have seen of
    this so far it looks feature-rich. I just hope that it is not a
    nightmare to configure.

    - Greg

    --- QScan/PCB v1.20a / 01-0462
    * Origin: Christian Fellowship | cfbbs.dtdns.net 856-933-7096 (1:266/512)
  • From Joe Delahaye@1:249/303 to RJ Clay on Sat Sep 29 19:07:34 2012
    Re: Internet Rex
    By: RJ Clay to Roy Witt on Sat Sep 29 2012 11:41:05

    And note, btw, that I have the same issue with the 'Password password' item on the "General information screen. The item is listed on that configuration screen but is greyed out and using the up or down arrows just ends up skipping over it.



    Try seting your userlevel to Advanced. The Password password, might be a paid feature. I dont recall now. However changing to advanced mode, will let you do a bunch of stuff you could not before
    --- SBBSecho 2.12-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Rj Clay@1:120/419 to Roy Witt on Sat Sep 29 18:48:12 2012
    Roy,

    29 Sep 12 17:09, you wrote to me:

    02 Sep 26 15:09, RJ Clay wrote to Roy Witt:
    And note, btw, that I have the same issue with the 'Password
    password' item on the "General information screen. The item is
    listed on that configuration screen but is greyed out and using
    the up or down arrows just ends up skipping over it.

    If you have previously set a password there, you'll have to 'start'
    your rexcfg executable with -p, which will allow you to view and
    modify all passwords throughout the config program.

    Would I be correct in thinking that if it's greyed out and not accessible, I likely did set a password there? I don't recall and it's not in my notes but the basic configuration was copied over from other systems... (several times...<g>)


    i.e. recfgL.exe -pcarrot - if your password is carrot, will allow you
    to view and modify all other passwords. Otherwise, the fields will be there, but the passwords will be starred out and unmodifiable.

    I wonder if I should try setting it up from scratch (including the entry of the registration info) on a clean install...




    Jame

    --- GoldED+/LNX 1.1.5--b20111217
    * Origin: RJC eeePC (1:120/419)
  • From Rj Clay@1:120/419 to Joe Delahaye on Sun Sep 30 09:25:04 2012
    Joe,

    29 Sep 12 19:07, you wrote to me:

    Re: Internet Rex
    By: RJ Clay to Roy Witt on Sat Sep 29 2012 11:41:05

    And note, btw, that I have the same issue with the 'Password
    password' item on the "General information screen. The item is
    listed on that configuration screen but is greyed out and using the
    up or down arrows just ends up skipping over it.

    Try seting your userlevel to Advanced. The Password password, might
    be a paid feature. I dont recall now.

    Doesn't appear to be, as after I re-installed and reconfigured it simply comes up as accessible and blank. So I must've set it somewhere along the way on the previous install...


    However changing to advanced mode, will let you do a bunch of stuff
    you could not before

    I may go ahead and try that anyway, just to see what becomes available...




    Jame


    --- GoldED+/LNX 1.1.5--b20111217
    * Origin: RJC eeePC (1:120/419)
  • From Rj Clay@1:120/419 to Roy Witt on Sun Sep 30 09:30:31 2012
    Roy,

    29 Sep 12 17:09, you wrote to me:
    02 Sep 26 15:09, RJ Clay wrote to Roy Witt:

    i.e. recfgL.exe -pcarrot - if your password is carrot, will allow you
    to view and modify all other passwords. Otherwise, the fields will be there, but the passwords will be starred out and unmodifiable.

    I must've set that somewhere along the way (like I mentioned; the install I was testing had been moved from system to system several times...<g>), because after installing and re-configuring it again from scratch, there is no longer a problem.

    Testing does appear to be going well, though it needs 'a lot' setup and configuration; one of the main things I wanted to test with it on this version of the OS I'm using is if it can handle domain names instead of having to use IPs and that does appear to be working properly.



    Jame




    --- GoldED+/LNX 1.1.5--b20111217
    * Origin: RJC eeePC (1:120/419)
  • From Roy Witt@1:387/22 to Gregory Deyss on Sun Sep 30 16:14:12 2012

    29 Sep 12 13:00, Gregory Deyss wrote to Roy Witt:

    Thanks for your reply Roy.
    I still don't understand why I could not enter that area to indicate passwords. However the problem is now fixed. What I did was I
    obtained a fresh copy of irex 2.29 (windows version) where rex runs
    within my windows tray.

    Ahhh. So perhaps the REX executable was corrupt.

    This time when I went throught the config for Irex everything worked
    fine, including the password area under connection manager.

    Good.

    I am re-doing my BBS system, I really wanted to use PX/DOS and
    wildcat 4.20 but I can not seem to get any netmail or echo mail to
    toss into the correct directory so that irex can see it.

    Wildcat software is a real bear to work with in that regard.

    I also use binkd.

    You should be able to use that with your synchronet.bbs.

    Netmail and echomail tosses into the BBS fine. So I am will
    now be setting up frontdoor and synhronet bbs for windows, from what
    I have seen of this so far it looks feature-rich. I just hope that it
    is not a nightmare to configure.

    I can't say that I find anything good about synchronet, but there are
    people who're using it successfully. I'd classify it with wildcat
    software.


    R\%/itt


    ... Mark Owen: "Hey, did you ever hear anything about that beer?
    ... Fellow SEAL: "You believed that shit, I bet you voted for change too,
    ... SUCKER."


    --- GoldED+/W32 with D'Bridge 3.82
    * Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)
  • From Roy Witt@1:387/22 to Rj Clay on Sun Sep 30 15:54:12 2012

    29 Sep 12 18:48, Rj Clay wrote to Roy Witt:

    And note, btw, that I have the same issue with the 'Password
    password' item on the "General information screen. The item is
    listed on that configuration screen but is greyed out and using
    the up or down arrows just ends up skipping over it.

    If you have previously set a password there, you'll have to 'start'
    your rexcfg executable with -p, which will allow you to view and
    modify all passwords throughout the config program.

    Would I be correct in thinking that if it's greyed out and not accessible, I likely did set a password there?

    That or your REX install is running with corrupt files.

    I don't recall and it's not in my notes but the basic configuration
    was copied over from other systems... (several times...<g>)

    Hmmmm.

    i.e. recfgL.exe -pcarrot - if your password is carrot, will allow
    you to view and modify all other passwords. Otherwise, the fields
    will be there, but the passwords will be starred out and
    unmodifiable.

    I wonder if I should try setting it up from scratch (including the entry of the registration info) on a clean install...

    If you have preserved the reg info, that should be a good way to go.

    Use freshly unpacked files from a clean REX archive.


    R\%/itt


    ... Mark Owen: "Hey, did you ever hear anything about that beer?
    ... Fellow SEAL: "You believed that shit, I bet you voted for change too,
    ... SUCKER."


    --- GoldED+/W32 with D'Bridge 3.82
    * Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)
  • From Roy Witt@1:387/22 to Rj Clay on Sun Sep 30 16:00:31 2012

    30 Sep 12 09:30, Rj Clay wrote to Roy Witt:

    i.e. recfgL.exe -pcarrot - if your password is carrot, will allow
    you to view and modify all other passwords. Otherwise, the fields
    will be there, but the passwords will be starred out and
    unmodifiable.

    I must've set that somewhere along the way (like I mentioned; the install I was testing had been moved from system to system several times...<g>), because after installing and re-configuring it again
    from scratch, there is no longer a problem.

    Cool.

    Testing does appear to be going well, though it needs 'a lot'
    setup and configuration; one of the main things I wanted to test with
    it on this version of the OS I'm using is if it can handle domain
    names instead of having to use IPs and that does appear to be working properly.

    In setting up a new node, REX tries to use the old z.n.?.@fidonet.org(net) reading from the nodelist. Having used it and being frustrated with that
    (since that @fidonet method went bellyup a while ago), I always tried to
    use a dynamic or static address there.

    However, I have wanted to test if editing the extension to @binkd.net,
    which is the new lookup now being used in BinkD. I wonder if it would
    resolve as before and not have to rely on ip input during config...


    R\%/itt


    ... Mark Owen: "Hey, did you ever hear anything about that beer?
    ... Fellow SEAL: "You believed that shit, I bet you voted for change too,
    ... SUCKER."


    --- GoldED+/W32 with D'Bridge 3.82
    * Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)
  • From Joe Delahaye@1:249/303 to Roy Witt on Sun Sep 30 15:29:00 2012
    Re: Internet Rex
    By: Roy Witt to Gregory Deyss on Sun Sep 30 2012 16:14:12

    I can't say that I find anything good about synchronet, but there are
    people who're using it successfully. I'd classify it with wildcat
    software.



    Nothing can be so bad as Wild Kitty <G>
    --- SBBSecho 2.12-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Roy Witt@1:387/22 to Joe Delahaye on Sun Sep 30 21:54:02 2012

    30 Sep 12 15:29, Joe Delahaye wrote to Roy Witt:

    Re: Internet Rex
    By: Roy Witt to Gregory Deyss on Sun Sep 30 2012 16:14:12

    I can't say that I find anything good about synchronet, but there are
    people who're using it successfully. I'd classify it with wildcat
    software.



    Nothing can be so bad as Wild Kitty <G>

    Tell ME about it! I attempted to install fidonet under Wildcat back in the early 90s and never got it going.

    R\%/itt


    ... Mark Owen: "Hey, did you ever hear anything about that beer?
    ... Fellow SEAL: "You believed that shit, I bet you voted for change too,
    ... SUCKER."


    --- GoldED+/W32 with D'Bridge 3.82
    * Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)
  • From Joe Delahaye@1:249/303 to Roy Witt on Sun Sep 30 22:41:14 2012
    Re: Internet Rex
    By: Roy Witt to Joe Delahaye on Sun Sep 30 2012 21:54:02

    Tell ME about it! I attempted to install fidonet under Wildcat back in the early 90s and never got it going.


    You and many others.
    --- SBBSecho 2.12-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Roy Witt@1:387/22 to Joe Delahaye on Mon Oct 1 17:58:02 2012

    01 Jan 70 00:00, Joe Delahaye wrote to Roy Witt:

    Re: Internet Rex
    By: Roy Witt to Joe Delahaye on Sun Sep 30 2012 21:54:02

    Tell ME about it! I attempted to install fidonet under Wildcat back in
    the early 90s and never got it going.

    You and many others.

    Even those who were successful weren't any help...

    R\%/itt


    ... Mark Owen: "Hey, did you ever hear anything about that beer?
    ... Fellow SEAL: "You believed that s**t, I bet you voted for change too,
    ... SUCKER."


    --- GoldED+/W32 with D'Bridge 3.82
    * Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)
  • From Joe Delahaye@1:249/303 to Roy Witt on Mon Oct 1 19:50:47 2012
    Re: Internet Rex
    By: Roy Witt to Joe Delahaye on Mon Oct 01 2012 17:58:02

    You and many others.

    Even those who were successful weren't any help...


    Most likely because the couldnt remember what it was they did to get it to work
    <G> I ran PCBoard clone at first, and then purchased PCB. My host was long distance, and at the time we could not do FTN, but we had Fido. QWK worked OK back then. Then Internail came to visit, and I purchased a copy of that. It did everything I wanted, including tossing the mail in native PCB format.
    --- SBBSecho 2.12-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Roy Witt@1:387/22 to Joe Delahaye on Tue Oct 2 16:53:11 2012

    01 Jan 70 00:00, Joe Delahaye wrote to Roy Witt:

    You and many others.

    Even those who were successful weren't any help...


    Most likely because the couldnt remember what it was they did to get
    it to work <G>

    Paul, the person I asked to help, already had Fidonet working under
    Wildcat. I was one of his users who was active in the one and only echo I
    was interested in at the time: Chatter. This was 1990 or so and I had the
    same version of WC with a lot of game doors, files and local msg areas on
    it, but no Fidonet.

    That was frustrating to say the least. But, in retrospect, that was
    probably a good thing I didn't get it working, as the PC running WC was in
    my office at my shop. I probably would never have gotten any work done.
    8^(

    I ran PCBoard clone at first, and then purchased PCB.
    My host was long distance, and at the time we could not do FTN, but
    we had Fido. QWK worked OK back then. Then Internail came to visit,
    and I purchased a copy of that. It did everything I wanted,
    including tossing the mail in native PCB format.

    Interestingly, host 202 wasn't the source of any echomail in that net. The entire group of net-nodes paid into a pool to buy a dedicated computer to
    run echomail. Dunno the source, but there were several hubs, all assigned 202/x00 numbers to distribute mail to their 202/909 like numbered nodes
    who were their downlinks. I recall having knock down drag out fights with 202/900 because his software was screwing up most of the time.


    R\%/itt


    ... Mark Owen: "Hey, did you ever hear anything about that beer?
    ... Fellow SEAL: "You believed that s**t, I bet you voted for change too,
    ... SUCKER."


    --- GoldED+/W32 with D'Bridge 3.82
    * Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)
  • From Joe Delahaye@1:249/303 to Roy Witt on Tue Oct 2 14:21:00 2012
    Re: Internet Rex
    By: Roy Witt to Joe Delahaye on Tue Oct 02 2012 16:53:11

    That was frustrating to say the least. But, in retrospect, that was
    probably a good thing I didn't get it working, as the PC running WC was in my office at my shop. I probably would never have gotten any work done.
    8^(

    LOL


    Interestingly, host 202 wasn't the source of any echomail in that net. The entire group of net-nodes paid into a pool to buy a dedicated computer to run echomail. Dunno the source, but there were several hubs, all assigned 202/x00 numbers to distribute mail to their 202/909 like numbered nodes
    who were their downlinks. I recall having knock down drag out fights with 202/900 because his software was screwing up most of the time.


    We had a local hub who called LD to get the mail, who then distributed it here.
    Still same net, and Cost Sharing of course. He eventually got a Planet Connect
    system and did it all himself.
    --- SBBSecho 2.12-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Rj Clay@1:120/419 to Roy Witt on Wed Oct 3 07:48:27 2012
    Roy,

    30 Sep 12 15:54, you wrote to me:

    29 Sep 12 18:48, Rj Clay wrote to Roy Witt:

    Would I be correct in thinking that if it's greyed out and not
    accessible, I likely did set a password there?

    That or your REX install is running with corrupt files.

    And either case can be resolved by starting from scratch.


    I don't recall and it's not in my notes but the basic
    configuration was copied over from other systems... (several
    times...<g>)

    Hmmmm.

    Yep.<g> The last working install (prior to where it is now) was on an old PC that I stopped using due to hardware problems. The hard drives were still accessible so I backed up their contents in various ways (images of the drive partitions as well as a simple copy of the their contents). Since then, I've copied the irex install from that to various other systems, attempting to get it working again. And of course, this happened over some time, as I wasn't devoting much time to it... Finally copied it over to the current system (Debian v3 in a VM) where it worked well enough to get me to decide to devote more time to getting it operational.


    I wonder if I should try setting it up from scratch (including
    the entry of the registration info) on a clean install...

    If you have preserved the reg info, that should be a good way to go.

    I've a print out of that somewhere, but in this case since the old install was working well enough otherwise I just went into rexcfgl in another window for the registration info.


    Use freshly unpacked files from a clean REX archive.

    That's what I ended up doing. It appears to be operational but I think needs a lot of configuration. (And more understanding, on my part...<g>)



    Jame


    --- GoldED+/LNX 1.1.5--b20111217
    * Origin: RJC eeePC (1:120/419)
  • From Rj Clay@1:120/419 to Roy Witt on Wed Oct 3 08:02:02 2012
    Roy,

    30 Sep 12 16:00, you wrote to me:

    In setting up a new node, REX tries to use the old
    z.n.?.@fidonet.org(net) reading from the nodelist.

    How does it do that?

    And keep in mind that they're used in two different ways. The fidonet.org domain is used only for email while the fidonet.net domain was used for connectivity.


    which is the new lookup now being used in BinkD. I wonder if it would resolve as before and not have to rely on ip input during config...

    Edit that where? If you simply enter a system domain name in that format and assuming that the domain name is actually defined, that should work...




    Jame


    --- GoldED+/LNX 1.1.5--b20111217
    * Origin: RJC eeePC (1:120/419)
  • From Roy Witt@1:387/22 to Rj Clay on Wed Oct 3 16:58:57 2012

    03 Oct 12 07:48, Rj Clay wrote to Roy Witt:

    29 Sep 12 18:48, Rj Clay wrote to Roy Witt:

    Would I be correct in thinking that if it's greyed out and not
    accessible, I likely did set a password there?

    That or your REX install is running with corrupt files.

    And either case can be resolved by starting from scratch.

    Absolutely.

    I don't recall and it's not in my notes but the basic
    configuration was copied over from other systems... (several
    times...<g>)

    Hmmmm.

    Yep.<g> The last working install (prior to where it is now) was
    on an old PC that I stopped using due to hardware problems. The hard drives were still accessible so I backed up their contents in various
    ways (images of the drive partitions as well as a simple copy of the
    their contents). Since then, I've copied the irex install from that
    to various other systems, attempting to get it working again. And of course, this happened over some time, as I wasn't devoting much time
    to it... Finally copied it over to the current system (Debian v3 in
    a VM) where it worked well enough to get me to decide to devote more
    time to getting it operational.

    I have a CD around here that has one of my first registered installs of
    Irex archived on it. That was a working model and I should be able to
    retrieve it at paste into a newer system and read the setup. Even if it
    was on a DOS 6.2 system.

    I wonder if I should try setting it up from scratch (including
    the entry of the registration info) on a clean install...

    If you have preserved the reg info, that should be a good way to go.

    I've a print out of that somewhere, but in this case since the
    old install was working well enough otherwise I just went into
    rexcfgl in another window for the registration info.

    That works...

    Use freshly unpacked files from a clean REX archive.

    That's what I ended up doing. It appears to be operational but I think
    needs a lot of configuration. (And more understanding, on my
    part...<g>)

    That will come with time and use of the software. I'm not a programmer or
    even a guru of Irex, just plenty of time and experience with using it.


    R\%/itt


    ... Mark Owen: "Hey, did you ever hear anything about that beer?
    ... Fellow SEAL: "You believed that s**t, I bet you voted for change too,
    ... SUCKER."


    --- GoldED+/W32 with D'Bridge 3.82
    * Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)
  • From Roy Witt@1:387/22 to Rj Clay on Wed Oct 3 17:06:45 2012

    01 Feb 12 15:10, Rj Clay wrote to Roy Witt:

    In setting up a new node, REX tries to use the old
    z.n.?.@fidonet.org(net) reading from the nodelist.

    How does it do that?

    My understanding is that it is hard-coded to read the nodelist and use the
    info found there to write the z.n. etc..

    And keep in mind that they're used in two different ways. The fidonet.org domain is used only for email while the fidonet.net
    domain was used for connectivity.

    The one in reference was used as a DNS lookup - when 'fidonet.net' was
    still around. It has since died and there's a BinkD.* DNS look up that has taken it's place.

    which is the new lookup now being used in BinkD. I wonder if it
    would resolve as before and not have to rely on ip input during
    config...

    Edit that where?

    In your node manager. Choose 'send to a BinkD' system and then enter the configure node that appears under that, the first line will already have
    the z.n. lookup entered by Irex.

    If you simply enter a system domain name in that format and
    assuming that the domain name is actually defined, that
    should work...

    It will. i.e. my lone-star.dyndns.org can and should used to replace that
    z.n. listing that Irex will put there...

    R\%/itt


    ... Mark Owen: "Hey, did you ever hear anything about that beer?
    ... Fellow SEAL: "You believed that s**t, I bet you voted for change too,
    ... SUCKER."


    --- GoldED+/W32 with D'Bridge 3.82
    * Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)
  • From Rj Clay@1:120/419 to Roy Witt on Sun Oct 7 08:58:27 2012
    Roy,

    03 Oct 12 17:06, you wrote to me:

    01 Feb 12 15:10, Rj Clay wrote to Roy Witt:

    Edit that where?

    In your node manager. Choose 'send to a BinkD' system and then enter
    the configure node that appears under that, the first line will
    already have the z.n. lookup entered by Irex.

    I don't recall it coming up like that but then I've only added a few local point systems since I got it somewhat working. I'll check that, the next time I add a system.




    Jame


    --- GoldED+/LNX 1.1.5--b20111217
    * Origin: RJC eeePC (1:120/419)
  • From Roy Witt@1:387/22 to Rj Clay on Tue Oct 9 20:50:37 2012

    13 Oct 15 15:10, Rj Clay wrote to Roy Witt:

    Edit that where?

    In your node manager. Choose 'send to a BinkD' system and then enter
    the configure node that appears under that, the first line will
    already have the z.n. lookup entered by Irex.

    I don't recall it coming up like that but then I've only added a
    few local point systems since I got it somewhat working.

    Irex reads the nodelist and inputs that info from there. I wouldn't expect
    it to do that with a pointlist, unless points are listed in the same
    manner.

    I'll check that, the next time I add a system.

    Just for grins, add some that are listed in the nodelist with an INA
    and/or IBN flag.

    R\%/itt


    ... Mark Owen: "Hey, did you ever hear anything about that beer?
    ... Fellow SEAL: "You believed that s**t, I bet you voted for change too,
    ... SUCKER."


    --- GoldED+/W32 with D'Bridge 3.82
    * Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)
  • From Robert Wolfe@1:116/18 to Roy Witt on Mon Oct 29 17:32:58 2012
    If you use your 'arrow' keys to navigate these different levels, when you highlight one of them, press 'enter' and your cursor should be on that
    level. Whether you can see it or not doesn't matter. Begin typing and
    there should be some response to your input.

    What user "experience" level do you have your IREX set to in REXCFG -> General Information -> User Level? If you have that set to "Expert" then you should have all options available to you.

    Linux users seem to have the most problems configuring Irex.

    Not necessarily. But yeah, the DNS resolution thing is a biggy.

    I would like to fully register irex, but I would like to get these
    issues fixed first,
    I wouldn't bother, since this program is no longer actively supported by
    the author. I've used Irex for years and it's still functional, even with
    its various quirks. Once configured, it will serve you well, but don't
    expect any help from the author.

    That's what this echo and Internet email are for. It seems that every time I have emailed Charles about how to do something, I've always gotten a timely response.

    --- BBBS/NT v4.10 Dada-1
    * Origin: Omicron Theta | Memphis, TN | Yes, We Are Still Here! (1:116/18)
  • From Robert Wolfe@1:116/18 to Roy Witt on Mon Oct 29 17:39:12 2012

    Tell ME about it! I attempted to install fidonet under Wildcat back in
    the early 90s and never got it going.

    You and many others.

    Even those who were successful weren't any help...

    Hmm, that's odd. I would be HAPPY to help anyone with WINS and PX set up Internet Rex with those packages.

    --- BBBS/NT v4.10 Dada-1
    * Origin: Omicron Theta | Memphis, TN | Yes, We Are Still Here! (1:116/18)
  • From RJ Clay@1:120/544 to All on Thu Sep 27 12:51:01 2012
    Hi All!

    26 Sep 12 17:51, Gregory Deyss wrote to all:

    My question is about internet rex under
    node manager --> in a users node entry
    connection information why is I can not edit any passwords
    that exist such as packet password, encryption password, or session password or even rexfix password, in fact all of these are grayed out.

    I'm also seeing the same kind of issue...

    After not having it running for quite awhile I decided to try setting it up again, so installed the Linux version of it on a virtual machine running Debian v4 ('Woody'). Attempted BinkP connects to it are failing; thought to check the session password setting but like Gregory, found that none of the passwords are accessible for editing.



    Jame


    --- GoldED+/LNX 1.1.5-b20110213
    * Origin: ftn.rocasa.net (1:120/544)
  • From Robert Wolfe@1:116/18 to RJ Clay on Mon Feb 25 08:43:44 2013
    And note, btw, that I have the same issue with the 'Password password' item on the "General information screen. The item is listed on that configuration
    screen but is greyed out and using the up or down arrows just ends up skipping
    over it.

    What user level do you have Internet Rex set to?

    Under IREXCFG -> General Information -> User Level

    I have mine set to "Expert" which makes all of the options available to me.

    --- BBBS/NT v4.10 Dada-1
    * Origin: Omicron Theta | Memphis, TN | Yes, We Are Still Here! (1:116/18)
  • From Robert Wolfe@1:116/18 to Roy Witt on Mon Feb 25 08:44:24 2013
    I have no experience at all with the Linux version of REX, so all I can
    tell you is to get ahold of someone like Robert Wolfe (1:261/20), who has plenty of experience with Linux and REX.

    *smiles* I am also at 1:116/18 in the nodelist now ;)

    --- BBBS/NT v4.10 Dada-1
    * Origin: Omicron Theta | Memphis, TN | Yes, We Are Still Here! (1:116/18)
  • From Robert Wolfe@1:116/18 to Joe Delahaye on Mon Feb 25 08:45:20 2013
    Try seting your userlevel to Advanced. The Password password, might be a paid
    feature. I dont recall now. However changing to advanced mode, will let you do a bunch of stuff you could not before

    It's also available in the non-paid version as well, IIRC.

    --- BBBS/NT v4.10 Dada-1
    * Origin: Omicron Theta | Memphis, TN | Yes, We Are Still Here! (1:116/18)
  • From Robert Wolfe@1:116/18 to Joe Delahaye on Mon Feb 25 08:48:58 2013
    I can't say that I find anything good about synchronet, but there are
    people who're using it successfully. I'd classify it with wildcat
    software.

    Nothing can be so bad as Wild Kitty <G>

    IMO it's not the software per se as much as the developer.

    --- BBBS/NT v4.10 Dada-1
    * Origin: Omicron Theta | Memphis, TN | Yes, We Are Still Here! (1:116/18)
  • From Roy Witt@1:387/22 to Robert Wolfe on Mon Feb 25 10:25:19 2013

    Robert Wolfe wrote to Roy Witt:

    I have no experience at all with the Linux version of REX, so all I
    can tell you is to get ahold of someone like Robert Wolfe (1:261/20),
    who has plenty of experience with Linux and REX.

    *smiles* I am also at 1:116/18 in the nodelist now ;)

    Hmmmm. Heard anything from Richard Webb lately? He's been missing for
    about a month now.


    R\%/itt


    --- GoldED+/W32 1.1.5-31012
    * Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)
  • From Robert Wolfe@1:116/18 to Roy Witt on Mon Feb 25 13:43:38 2013
    *smiles* I am also at 1:116/18 in the nodelist now ;)

    Hmmmm. Heard anything from Richard Webb lately? He's been missing for
    about a month now.

    No, actually.

    --- BBBS/NT v4.10 Dada-1
    * Origin: Omicron Theta | Memphis, TN | Yes, We Are Still Here! (1:116/18)
  • From Joe Delahaye@1:249/303 to Robert Wolfe on Mon Feb 25 15:57:29 2013
    Re: Internet Rex
    By: Robert Wolfe to Joe Delahaye on Mon Feb 25 2013 08:48:58

    Nothing can be so bad as Wild Kitty <G>

    IMO it's not the software per se as much as the developer.


    Which developer <G>? Rob is pretty good.
    --- SBBSecho 2.20-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Robert Wolfe@1:116/18 to Joe Delahaye on Mon Feb 25 15:40:06 2013
    Re: Internet Rex
    By: Robert Wolfe to Joe Delahaye on Mon Feb 25 2013 08:48:58

    Nothing can be so bad as Wild Kitty <G>

    IMO it's not the software per se as much as the developer.


    Which developer <G>? Rob is pretty good.

    Oh, thought we were talking about Internet Rex here :)

    --- BBBS/NT v4.10 Dada-1
    * Origin: Omicron Theta | Memphis, TN | Yes, We Are Still Here! (1:116/18)
  • From Joe Delahaye@1:249/303 to Robert Wolfe on Mon Feb 25 19:29:49 2013
    Re: Internet Rex
    By: Robert Wolfe to Joe Delahaye on Mon Feb 25 2013 15:40:06

    Re: Internet Rex
    By: Robert Wolfe to Joe Delahaye on Mon Feb 25 2013 08:48:58

    Nothing can be so bad as Wild Kitty <G>

    IMO it's not the software per se as much as the developer.


    Which developer <G>? Rob is pretty good.

    Oh, thought we were talking about Internet Rex here :)


    I thought so as well, but somebody brought Synchronet into the picture, and that is why I asked <G>
    --- SBBSecho 2.20-Win32
    * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
  • From Robert Wolfe@1:116/18 to Joe Delahaye on Mon Feb 25 18:58:22 2013

    Which developer <G>? Rob is pretty good.

    Oh, thought we were talking about Internet Rex here :)

    I thought so as well, but somebody brought Synchronet into the picture, and that is why I asked <G>

    Tee hee :)

    --- BBBS/NT v4.10 Dada-1
    * Origin: Omicron Theta | Memphis, TN | Yes, We Are Still Here! (1:116/18)
  • From mark lewis@1:3634/12.42 to Roy Witt on Mon Feb 25 16:07:40 2013

    I have no experience at all with the Linux version of REX, so all I
    can tell you is to get ahold of someone like Robert Wolfe (1:261/20),
    who has plenty of experience with Linux and REX.

    *smiles* I am also at 1:116/18 in the nodelist now ;)

    Hmmmm. Heard anything from Richard Webb lately? He's been missing
    for about a month now.

    richard is not missing ;)

    )\/(ark

    ---
    * Origin: (1:3634/12.42)