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.
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
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.
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?
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.
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.
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".
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.
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.
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.
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.
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
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.
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.
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...
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.
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.
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.
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.
You and many others.
Even those who were successful weren't any help...
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.
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^(
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.
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.
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 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.
In setting up a new node, REX tries to use the old
z.n.?.@fidonet.org(net) reading from the nodelist.
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...
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>)
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...
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.
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.
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.
Linux users seem to have the most problems configuring Irex.
I would like to fully register irex, but I would like to get theseI wouldn't bother, since this program is no longer actively supported by
issues fixed first,
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.
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...
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.
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.
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.
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
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>
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 ;)
*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.
Nothing can be so bad as Wild Kitty <G>
IMO it's not the software per se as much as the developer.
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.
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>Which developer <G>? Rob is pretty good.
Oh, thought we were talking about Internet Rex here :)
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.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,042 |
Nodes: | 15 (0 / 15) |
Uptime: | 145:10:57 |
Calls: | 500,263 |
Calls today: | 1 |
Files: | 95,201 |
D/L today: |
123 files (66,139K bytes) |
Messages: | 464,630 |