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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

*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)

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)

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)

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)

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)

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)