Virtual Private Server (VPS) Hosting provided by Central Point Networking cpnllc.com
For some reason, the "Nodelist" and "Recent Callers" features are not working.
| Sysop: | Ray Quinn |
|---|---|
| Location: | Visalia, CA |
| Users: | 60 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 11:35:28 |
| Calls: | 12 |
| Files: | 12,930 |
| Messages: | 98,465 |
Check out the US 99 menu above for links to information about US Highway 99, after which the US 99 BBS is named.
Be sure to click on the Amateur Radio menu item above for packet BBSes, packet software, packet organizations, as well as packet how-to's. Also included is links to local and some not-so-local Amateur Radio Clubs.
I've posted several messages on the DOS echo.
The first one was (iirc) January 15 of this year.
Well I posted January 15, and March 5, on The Valley BBS.
I post regularly in the DOS Internet echo using that board.
Right now I am on Waldo's BBS which also has the DOS echo
and I posted here on March 7. Neither messages have gotten
to either board. Do you have any idea of a board where
I could use that echo? It doesn't seem like a very popular
one and I can't find it around except those two boards.
Could it be that the DOS echo is just not being distributed?
Hi Ole,
Monday March 08 2010 05:27, Ole Juul wrote to All:
I've posted several messages on the DOS echo.
The first one was (iirc) January 15 of this year.
Didn't get any messages from /you/ in that area. :(
Sometimes after long periods, I don't even pay attention
most of the
time, but every few months I check the synchronet guru
logs. People go
into chat with the guru. I sometimes end up on the floor
laughing so
hard. That poor little Guru gets abused horribly They don't
know if he
is real or not and when the people get mad at him... they
get mad!!! 8)
When you first log in, you are at the Main menu. The BBS shows you automatically all the areas that have new messages and if any are for you.<snip>
It is an old-fashioned bbs when you come in through the telnet interface.. but the telnet interface has more features than the Web interface.. The web interface really only has a few commands, like j to join, click with the mouse to read, who is online, directory list (for file area), etc.
Now I see something wrong. You are confusing the two echos.
hahahaha.. no, I think you are :) DOS is not on backbone.na anymore. It
was probably dropped for 'in-action'. It's still on my bbs because as I said, I don't remove echos that often.
I don't know how you saw that over here.. DOS is quite dead, and hasn't had a post on my bbs since September, 2009 :) :) :) DOS_INTERNET though still gets one or two or three messages a week.. :) Maybe when you were in the Main Board you thought that was the DOS echo? It wasn't <g>. you can see the area you are currently in by looking at the prompt:
hard. That poor little Guru gets abused horribly They don't
know if he
is real or not and when the people get mad at him... they
get mad!!! 8)
Oh, how I think I know what you guys are talking about.
One of the first boards I went to after I "came back"
had a page sysop option and i went for it, but someone
else came on. It took me about three lines until I went
"hey... waitaminnit!" and realized what was happening.
Thanks for the reply.
When you first log in, you are at the Main menu. The BBS shows you<snip>
automatically all the areas that have new messages and if any are for you.
OK, I read all that and will probably figure it out better now.
Thanks! The thing that I misssed was the movement of the cursor.
I thought I was supposed to type "fido:DOS". No wonder it didn't
work the way I expected, and subsequently ended up posting in
the local echo.
It is an old-fashioned bbs when you come in through the telnet interface.. >> but the telnet interface has more features than the Web interface.. The web >> interface really only has a few commands, like j to join, click with the
mouse to read, who is online, directory list (for file area), etc.
No mouse on this box. "Web" is text only here. <g> I have enough
trouble figuring out how my computer works let alone figuring
out some wierd GUI. I'll keep it simple until I grow some more
brain cells. :)
Not removing echos seems like a good policy. I guess
the problem that I ran into is that it is still on some
boards, but there is no indication that it isn't "live".
Regarding the echo being dead, I see by the other posts
from Mark et al, that all agree now. I do think there is
some general mixup about which is the "DOS" echo. I note
Kevin Klement said he was the moderator and he thought it
was live. Oh well, it would be nice to see it back.
I don't know how you saw that over here.. DOS is quite dead, and hasn't had >> a post on my bbs since September, 2009 :) :) :) DOS_INTERNET though still >> gets one or two or three messages a week.. :) Maybe when you were in the
Main Board you thought that was the DOS echo? It wasn't <g>. you can see >> the area you are currently in by looking at the prompt:
Got it. And who knows what I saw. hehe. I thought I was reading
posts from the DOS-Internet in the DOS section, ie "crossed wires".
Anyway, nevermind. :)
I'll be over on your board soon. I like the sparseness. It's
actually a bit like the ISCA BBS which to me is one of the best
interfaces of any board I've seen.
YOu might drop a note to the sysop of the other board you
use that carries it asking him to check his uplink's
linkages with it. HE might still have it on his board, but
the link up the chain from him (closer to main
distribution) no longer carries it.
YOu might drop a note to the sysop of the other board you
use that carries it asking him to check his uplink's
linkages with it. HE might still have it on his board, but
the link up the chain from him (closer to main
distribution) no longer carries it.
Haha, he hasn't been available for the two months since
I've been using it - and maybe never. It's a "ghost"
board. <vbg>
OK, when you mention the link to him being broken, I get
the idea of why it may not work there. However, here on
Waldo's it doesn't either, and this is certainly a well
maintained board.
but then again, i used to read upwards of 3000+ messages a da
back in the hey days... of those, i might write some 100+ replies... especiall
in the remoteaccess, frontdoor, and fastecho support areas... my replies would
be well over 200 a day after a new release came out :lol:
Understand... well things are a bit slower now, that's for
sure <g>
YOu might drop a note to the sysop of the other board you
use that carries it asking him to check his uplink's
linkages with it. HE might still have it on his board, but
the link up the chain from him (closer to main
distribution) no longer carries it.
Haha, he hasn't been available for the two months since
I've been using it - and maybe never. It's a "ghost"
board. <vbg>
FOund what seems most likely explanation.
About once a year, or at least the administrators of the
fidonet backbone audit the conferences distributed by the
backbone, and available. At that time conferences that have shown no coherent activity over a period of months are
dropped from backbone distribution, and must be again added
at the request of the conference moderator.
A conference moderator can help avoid falling into
distribution limbo by posting conference rules information,
etc. occasionally even.
I note from this last audit that the fidonet dos echo fell
into distribution limbo from the backbone.
coherent activity over a period of months are
dropped from backbone distribution, and must be again added
at the request of the conference moderator.
I suppose that makes some sense when it comes to keeping
things clean. I don't understand how that could sustain
an actual network though. It seems to me that things would
break on occasion.
A conference moderator can help avoid falling into
distribution limbo by posting conference rules information,
etc. occasionally even.
He posted hear a few messages back and said he didn't get
any posts from me. I posted on the only two boards that
I know has the echo and it didn't work. Waldo's was one
of them. I was hoping he would suggest a board that carried
a working DOS echo, but he hasn't responded to my request
yet.
I note from this last audit that the fidonet dos echo fell
into distribution limbo from the backbone.
My guess is that it's a gonner. :(
I note from this last audit that the fidonet dos echo fell
into distribution limbo from the backbone.
My guess is that it's a gonner. :(
Not necessarily.. relist it ;)
My guess is that it's a gonner. :(
Not necessarily.. relist it ;)
Hi Janis... Forgive my ignorance, but how does one go about doing that?
Whether it be this echo or any echo that seems to have died. Never
really got into that part of Fido before. What happens? The moderator
lets it fall off the backbone, and what? That leaves the echo dead until
or unless somebody else picks it up. If they want to, what do they do?
It's true, Ole, though there are systems like mine that don't update
their system to remove older echos that frequently. I just got
tired of deleting and re-adding echos <grin>. I just always hope
the echos that are deleted will get relisted... most do.
My guess is that it's a gonner. :(
Not necessarily.. relist it ;)
It is here on Prism as well - filegate.net on the standard
telnet port, or port 8080 on http://filegate.net:8080/bbbs
for the web interface.
My guess is that it's a gonner. :(Not necessarily.. relist it ;)
Ah I see my comment to you bore fruit eh?
It's true, Ole, though there are systems like mine that don't update
their system to remove older echos that frequently. I just got
tired of deleting and re-adding echos <grin>. I just always hope
the echos that are deleted will get relisted... most do.
YEp, I wrote some automation, compares backbone.dst with my
carried echoes list and warns me. I had it doing automagic
nuking, as well as sending areafix upstream to delink from
those nuked, pending human approval of course.
Disabled that though for same reasons you mention, but it
still sends me a report.
<snip>
My guess is that it's a gonner. :(
Not necessarily.. relist it ;)
YEp, echo mod will need to make sure it's submitted to the
echolist, and provide the confirmation msg to backbone
admins in the usual way I guess. Would like to see him do
that.
Thank you for commenting on this.
It is here on Prism as well - filegate.net on the standard
telnet port, or port 8080 on http://filegate.net:8080/bbbs
for the web interface.
Thanks, I'll try Prism for that echo then.
My guess is that it's a gonner. :(Not necessarily.. relist it ;)
Don't you have to run a BBS to do that?
Besides, The
Valley BBS doesn't have a sysop available, but is otherwise
about the best one I have encountered. Waldo's is competently
maintined by an active sysop, but the DOS echo has no
messages here.
I'll try Prism and hope. :)
Thanks, I'll try Prism for that echo then.
Don't you have to run a BBS to do that? Besides, The
Valley BBS doesn't have a sysop available, but is otherwise
about the best one I have encountered. Waldo's is competently
maintined by an active sysop, but the DOS echo has no
messages here.
I moderate DOS and no traffic this year yet so you're not getting
thru it would seem :(
About once a year, or at least the administrators of the
fidonet backbone audit the conferences distributed by the
backbone, and available. At that time conferences that have shown no coherent activity over a period of months are
dropped from backbone distribution, and must be again added
at the request of the conference moderator.
I suppose that makes some sense when it comes to keeping
things clean. I don't understand how that could sustain
an actual network though. It seems to me that things would
break on occasion.
A conference moderator can help avoid falling into
distribution limbo by posting conference rules information,
etc. occasionally even.
He posted hear a few messages back and said he didn't get
any posts from me. I posted on the only two boards that
I know has the echo and it didn't work. Waldo's was one
of them. I was hoping he would suggest a board that carried
a working DOS echo, but he hasn't responded to my request
yet.
I note from this last audit that the fidonet dos echo fell
into distribution limbo from the backbone.
My guess is that it's a gonner. :(
I see you posted this from Mark's system and it made it here.. so
it's not disabled over there... maybe he cleans out the traffic
more frequently than you'd expect..
Ok, it can be a little tricky at first if you're using the<lotsa snip>
Web interface... After you log in, click on [Join/Resign
No, you don't have to run a BBS to do that :) Anyone can
list an echo. You just have to be reachable "somehow"..
point address, email address, etc.
I see you posted this from Mark's system and it made it
here.. so it's not disabled over there... maybe he cleans
out the traffic more frequently than you'd expect..
but is easy enough to revive with a request or two and then
enough traffic to sustain it and keep it going ;)
In a Subspace Msg From Janis Kracht to Mike Roberts <=-
Hi Mike,
My guess is that it's a gonner. :(
Not necessarily.. relist it ;)
Hi Janis... Forgive my ignorance, but how does one go about doing that?
No problem Mike, it can seem daunting if you've never done it berore..
but it's not that hard. You essentially fill out a record for the
In a Subspace Msg From Janis Kracht to Ole Juul <=-
I suppose that makes some sense when it comes to keeping
things clean. I don't understand how that could sustain
an actual network though. It seems to me that things would
break on occasion.
It's true, Ole, though there are systems like mine that don't update
their system to remove older echos that frequently. I just got tired
of deleting and re-adding echos <grin>. I just always hope the echos
that are deleted will get relisted... most do.
I see you posted this from Mark's system and it made it here.. so
it's not disabled over there... maybe he cleans out the traffic
more frequently than you'd expect..
if you're talking about message base purging and the DOS echo, my system keeps >365 days of messages in all backbone areas... if there's no messages in an ech
at all, then it has been "dead" on my system for at least a year...
i just checked and DOS is set to retain for 365 days... soo... ;)
I just came from your board. Heheheh I should have come here
first because it took me almost an hour and still I couldn't
find a way to read messages on purpose. Yes, I am a bit
dense at times, but I persevere. <VGB> I really like the look
of the board, so I'll persevere. It looks a lot like the
way I like to set up my own computers, only I didn't do it
so I'll have to adjust. :)
Ok, it can be a little tricky at first if you're using the<lotsa snip>
Web interface... After you log in, click on [Join/Resign
Thanks, I'll be back shortly. The client I'm using is mTCP Telnet
which is the best I could find and after a couple of months of
doing this every day, it's holding up quite well.
No, you don't have to run a BBS to do that :) Anyone can
list an echo. You just have to be reachable "somehow"..
point address, email address, etc.
Aha, good to know. I'm real solid in the reachable department.
However, I just noticed that Mark is looking into it. I had
asked him yesterday if he would be so kind.
I see you posted this from Mark's system and it made it
here.. so it's not disabled over there... maybe he cleans
out the traffic more frequently than you'd expect..
Now I see something wrong. You are confusing the two echos.
I have seen that on another board, and it would appear to
be a problem on your's too. (I did read _some_ messages) :)
Specifically when I saw the "DOS" echo, it had messages from
this echo which is the "DOS/BBS Internet etc." echo. This
one is alive and welll but the "DOS" (nothing else) echo
is not.
I wonder if there could be some problem with crossed wires
in the network configuration. <g>
Hi Janis... Forgive my ignorance, but how does one go about doing that?
No problem Mike, it can seem daunting if you've never done it berore..
but it's not that hard. You essentially fill out a record for the
Hi Janis,
Thanks for taking that time and passing on that Information. I know it
took a lot of typing and I appreciate it. Saved for further review 8-)
Thanks again!
It's true, Ole, though there are systems like mine that don't update
their system to remove older echos that frequently. I just got tired
of deleting and re-adding echos <grin>. I just always hope the echos
that are deleted will get relisted... most do.
I am like You Janis. So many times I used to do that in the past. I
would delete because of no traffic and then get a bunch of msgs come
into my badmail area from the area I just deleted and then have to go
back and put it in or cancel it. So I have learned not to become so
hasty.
Exactly! The biggest bummer in that area is that when I add or removeechos,
the whole bbs has to come down in case someone logs in while you'reworking..
BBBS doesn't like that at all <vbg>
the whole bbs has to come down in case someone logs in while you'reworking..
BBBS doesn't like that at all <vbg>
BBBS is probably tough, but between You and I, I don't like that RoboCop Fella that is Lurking around. Lots of times when You're not looking he
gives me a whack up side the Head with that little nightstick of his.
For a Cop he is kind of a bully ;-)
BRoboCop* why?*BRoboCop* If you don't know, I'm not going to tell you.
On the serious side, I know what You mean, Changing and adding echos is
not simply an on the fly thing. Some software is harder than others.
I'm in the process of getting it re-listed on the bone, give it time
:)
Thanks for checking that out!
I see you posted this from Mark's system and it made it here.. so
it's not disabled over there... maybe he cleans out the traffic
more frequently than you'd expect..
if you're talking about message base purging and the DOS echo, my
system keeps 365 days of messages in all backbone areas... if there's
no messages in an echo at all, then it has been "dead" on my system
for at least a year...
Yeah, that's what I meant <g>.. Mine is set to hold for some
pre-set min-max number of messages.. some of the areas go back to
the year 2000.. kind of silly to hold on to messages that long but
disk space isn't a problem any longer :)
i just checked and DOS is set to retain for 365 days... soo... ;)
Understand :)
I'm in the process of getting it re-listed on the bone, give it
time :)
In a Subspace Msg From Janis Kracht to Mike Roberts <=-
BBBS is probably tough, but between You and I, I don't like that RoboCop Fella that is Lurking around. Lots of times when You're not looking he
gives me a whack up side the Head with that little nightstick of his.
For a Cop he is kind of a bully ;-)
Lol :) Well, I'll tell ya.. DON'T tell ol' brobocop to F-off.. he
will kick you off the BBS immediately.. yeah, I got really upset at
him one day hahaha I said, hey, wait, I'm the sysop :) :) Didn't
matter Lol
You are really right about him :)
Here's an example of his orneryness:
Read Command: msg brobocop
Message: why?
BRoboCop* why?
*BRoboCop* If you don't know, I'm not going to tell you.
hehe :) He's quite the bot :)
On the serious side, I know what You mean, Changing and adding echos is
not simply an on the fly thing. Some software is harder than others.
It's easy to add and remove things... but the BBS doesn't know how to
lock files, obviously.. at least not well enough to trust updating
things like msg. areas when things are running <g> I could set up
some semaphores but that's a pia because you have to remember which
ones do what Lol
In a Subspace Msg From Janis Kracht to Mark Lewis <=-
Yeah, that's what I meant <g>.. Mine is set to hold for some pre-set min-max number of messages.. some of the areas go back to the year
2000.. kind of silly to hold on to messages that long but disk space
isn't a problem any longer :)
system keeps 365 days of messages in all backbone areas... if there's
no messages in an echo at all, then it has been "dead" on my system
for at least a year...
Yeah, that's what I meant <g>.. Mine is set to hold for some
pre-set min-max number of messages.. some of the areas go back to
the year 2000.. kind of silly to hold on to messages that long but
disk space isn't a problem any longer :)
yup! that's why i went for keeping them for a year... i don't even do any of that min/max stuff... never saw a need for it... i mainly didn't want to fall
victim, like so many others, and loose newly arrived messages because the coun
went over the max... consider a setup with an area config'd for only 200
messages and there's a 400 message dump that comes in... you'd loose the first >200 of that dump and then start loosing more as more arrived if you didn't get >them all read...
but then again, i used to read upwards of 3000+ messages a da
back in the hey days... of those, i might write some 100+ replies... especiall >in the remoteaccess, frontdoor, and fastecho support areas... my replies would
be well over 200 a day after a new release came out :lol:
yeah, its also not on the backbone at this time... at least not at ross' system... looks like ben needs to get it carried again...
BBBS is probably tough, but between You and I, I don't like that RoboCop
Fella that is Lurking around. Lots of times when You're not looking he
gives me a whack up side the Head with that little nightstick of his.
For a Cop he is kind of a bully ;-)
Lol :) Well, I'll tell ya.. DON'T tell ol' brobocop to F-off.. he
I have felt like it, but don't really even look him in the eye as he is so free with that baton ;-)
will kick you off the BBS immediately.. yeah, I got really upset at
him one day hahaha I said, hey, wait, I'm the sysop :) :) Didn't
matter Lol
Hehehheheh, No respect!
You are really right about him :)
Here's an example of his orneryness:
Read Command: msg brobocop
Message: why?
BRoboCop* why?
*BRoboCop* If you don't know, I'm not going to tell you.
hehe :) He's quite the bot :)
Sometimes after long periods, I don't even pay attention most of the
time, but every few months I check the synchronet guru logs. People go
into chat with the guru. I sometimes end up on the floor laughing so
hard. That poor little Guru gets abused horribly They don't know if he
is real or not and when the people get mad at him... they get mad!!! 8)
It's easy to add and remove things... but the BBS doesn't know how to
lock files, obviously.. at least not well enough to trust updating
things like msg. areas when things are running <g> I could set up
some semaphores but that's a pia because you have to remember which
ones do what Lol
totally Understand, they need the locking, some when deleted are
totally deleted, some bbs's using like Jam, and You have to deal with
two softwares etc. Unless I am totally sure it is gone, I don't delete
it and hope the echo makes it back.
Yeah, that's what I meant <g>.. Mine is set to hold for some pre-set
min-max number of messages.. some of the areas go back to the year
2000.. kind of silly to hold on to messages that long but disk space
isn't a problem any longer :)
Hi Janis
It may be just Me, I like that kind of nostalgia, didn't do it on
purpose, but enjoy seeing some of those old msgs. I remember putting
back upof my old Telegard system in 2004 after being down for 4 years. It
had msgs going back to mid 90's in some cases and it was like raiding a
time capsule. I thought it was pretty neat!