Nick,
Just a frivolous idea ... whatt about an "ET Phone Home" function where every D'Bridge implementation sends you a monthly message indicating they're still there?
I know of one who is still there. I'm thinking of renaming my BAD_AREA
to Allen_Prunty.
Nick,
Just a frivolous idea ... whatt about an "ET Phone Home" function where eve D'Bridge implementation sends you a monthly message indicating they're stil there?
Just a frivolous idea ... whatt about an "ET Phone Home" function where every D'Bridge implementation sends you a monthly message indicating they're still there?
I know of one who is still there. I'm thinking of renaming my BAD_AREA to Allen_Prunty.
I know of one who is still there. I'm thinking of renaming my
BAD_AREA to Allen_Prunty.
D'Bridge does not accept such long directory names.
[I couldn't help it 8-)
On 06 Jan 17 07:19:00, Roger Nelson said the following to Ward Dossche:
Just a frivolous idea ... whatt about an "ET Phone Home" function
where every D'Bridge implementation sends you a monthly message
indicating they're still there?
I know of one who is still there. I'm thinking of renaming my
BAD_AREA to Allen_Prunty.
Sounds Mystic-al...
Sounds Mystic-al...
That's better than what I wrote. (-:
I know of one who is still there. I'm thinking of renaming my NA>RN> BAD_AREA to Allen_Prunty.
Sounds Mystic-al...
That's better than what I wrote. (-:
Its amusing to me to see all of these problems with duplicates, when
the duplicate-checking code in D'Bridge has not been changed since the early 90's.
I even get my own messages back through path's like these.
Its amusing to me to see all of these problems with duplicates, when the duplicate-checking code in D'Bridge has not been changed since the early 90's.
Well it could use an update for the modern fidonet, to also check the syste in the path line, when it does seen-by checking... Because paths like these
he undoubtably was aware that a large Zone 2 hub used D'Bridge
exclusively (Ward),
The original author supported D'Bridge well into 2000, 2001 I believe...
No complaints, no nitpicking... no noise... not even ranting from Mark Lewis.
eitherI even get my own messages back through path's like these.
And is that because of D'Bridge or because of some other sysop using
crooked software or not knowing what he/she is doing?
wasWell it could use an update for the modern fidonet, to also check the
syste in the path line, when it does seen-by checking... Because
paths like these
There WAS some work done with the PATH in the duplicate-check code, but
commented-out by the original author, most likely because at that time, he wasn't quite sure what to make out of FSC-0052 or parts of FTS-0004.001, and/or he undoubtably was aware that a large Zone 2 hub used D'Bridge exclusively (Ward), along with major Net hubs in Zone 1.
No complaints, no nitpicking... no noise... not even ranting from Mark Lewis.
It is a misconception that code that has worked for decades needs to be updated to support some new "modern" Fido technology...
On 06 Jan 17 11:41:23, Roger Nelson said the following to Nick
Andre:
I know of one who is still there. I'm thinking of renaming my NA>RN> BAD_AREA to Allen_Prunty.
Sounds Mystic-al...
That's better than what I wrote. (-:
Its amusing to me to see all of these problems with duplicates,
when the duplicate-checking code in D'Bridge has not been changed
since the early 90's.
Sounds Mystic-al...
That's better than what I wrote. (-:
+1
The original author supported D'Bridge well into 2000, 2001 I believe...
Actually ... "no" ... after some of us twisted his arm at some
point he released a Y2K-version which missed the mark completely.
It had been a while since there had been an update and what he
released was obviously to satisfy the questions, but it wasn't
stable at all ... after less than an hour I deleted it, went back
to the previous version and started working around the problems up
to the point of even making my own IP-implementation for D'Bridge
so I could run binkd... and then you showed up ...
No complaints, no nitpicking... no noise... not even ranting from
Mark Lewis.
That's because you use capital letters.
I'm not so certain about that. I used D'Bridge since 1989 and it wasn't unt late-1994 that I rose to some kind of prominence. His Z2 business was handl by Tom Ordelman, a person that gives you the creeps, and Chris' parents wer his business managers ... everything went via them and I think they didn't even know the on/off-switch of a PC.
When there were still duplicate nets in fidonet, zone-gates and seen-by stripping was needed. And this wasn't a good idea. But fidonet has changed.
It is a misconception that code that has worked for decades needs to b updated to support some new "modern" Fido technology...
Yes please, put your fingers in your ears, close your eyes, and keep repeat the mantra "fidonet is not changing" for as long as you can. Maybe it will have become a reality when you're done... ;)
When there were still duplicate nets in fidonet, zone-gates and
seen-by stripping was needed. And this wasn't a good idea. But
fidonet has changed.
I still see no reason to enable the PATH detection code... on the basis that nobody in the last several years has complained about it.
It is a misconception that code that has worked for decadesneeds
to b
updated to support some new "modern" Fido technology...
Yes please, put your fingers in your ears, close your eyes, and keep
repeat the mantra "fidonet is not changing" for as long as you can.
Maybe it will have become a reality when you're done... ;)
Do you honestly think ANY of the existing kludge or packet formats are going to be changed? :)
When there were still duplicate nets in fidonet, zone-gates and
seen-by stripping was needed. And this wasn't a good idea. But
fidonet has changed.
I still see no reason to enable the PATH detection code... on the
basis that nobody in the last several years has complained about it.
Yes please, put your fingers in your ears, close your eyes, and keep
repeat the mantra "fidonet is not changing" for as long as you can.
Maybe it will have become a reality when you're done... ;)
Do you honestly think ANY of the existing kludge or packet formats are going to be changed? :)
Sounds Mystic-al...
That's better than what I wrote. (-:
+1
That's good, right?
I stand corrected then...
I was amazed how many people jumped-up when D'Bridge started its life when became clear it was a commercial product. Lots of people figuring they were going to make money with Fidonet ... some probably even did ... for a short while.
I still see no reason to enable the PATH detection code... on the basis that nobody in the last several years has complained about it.
is that path detection code for CPD (circular path detection)? if so, it wo help with the problem wilfred is trying to describe where one message takes multiple paths from the origin to the receiver...
I still see no reason to enable the PATH detection code... on the basi that nobody in the last several years has complained about it.
Some people are complaining now about an excess of dupes. What's wrong with catching a few extra? You said the code is already there, so it would be ea for you to enable it!
I still see no reason to enable the PATH detection code... on the
basis that nobody in the last several years has complained about it.
is that path detection code for CPD (circular path detection)? if so,
it wo help with the problem wilfred is trying to describe where one
message takes multiple paths from the origin to the receiver...
From what I can gather, there was probably a good reason why it was
not done.
Some people are complaining now about an excess of dupes. What's
wrong with catching a few extra? You said the code is already there,
so it would be ea for you to enable it!
The people complaining are those seeing effects of this "modern" BBS software you speak of... Mystic, Synchronet, HPT etc. All three,
whether buggy or just improperly configured, have caused these
problems you want me to change code in D'Bridge to handle... code not touched in decades. :)
From what I can gather, there was probably a good reason why it was not done.
i'm sure... and there's really nothing in fidonet that can prevent all thes dupes, either... not with the way that one distribution system has set itse up... especially since their only real method of detection is not a require part of messages flowing in fidonet ;)
i just can't see how this was allowed to get out and into use for this long someone's doing something very wrong... that's for sure... it isn't you or rob, either...
Sounds Mystic-al...
That's better than what I wrote. (-:
+1
That's good, right?
Yups.
If you're referring to Fido-Web, none of that has impacted my system,
in both directions, as I have links that use my system as a "backup"
feed for certain echoes. Lots of folks from both Zone 1 and 2...
I see the duplicates being logged; but they just get zapped.
Its a non-issue here...
I thought Mystic was open source, why don't you or someone just fix whatevers wrong with it? I know nothing about Mystic or how it tosses mail.
i'm sure... and there's really nothing in fidonet that can prevent
all thes dupes, either... not with the way that one distribution
system has set itse up... especially since their only real method
of detection is not a require part of messages flowing in fidonet
;)
If you're referring to Fido-Web, none of that has impacted my system,
in both directions, as I have links that use my system as a "backup"
feed for certain echoes. Lots of folks from both Zone 1 and 2...
I see the duplicates being logged; but they just get zapped.
Its a non-issue here...
I've exchanged messages with James a few times, he's fantastic... puts
up with way more crap than he should; and it would not surprise me if
he is not exactly thrilled to return to working on it. He gets props
but he also takes a lot of crap that even I would "just say no" to.
I thought Mystic was open source, why don't you or someone just fix whatevers wrong with it? I know nothing about Mystic or how it tosses mail.
exactly sure on the details but i know that they greatly influenced me to my software place the MSGID as close to the beginning of the control lines possible so that db would not detect messages posted within one second as dupes... this was especially important when testing at 100+ posts per second... are you willing to share information about how db does its dupe detection so others can understand more? please?
I do the same in regards to dupes (ie: "zap" or delete them), and have a feeling the people that are beginning to worry about it the most don't do this, and actually move their dupes to an area where they can be seen by themselves. They see that their DUPE area is growing at a much faster rate lately than it ever has in the past, and start freaking out.
Obviously with this option you're giving in to the possibility that once i bluish-purple with pink polka-dots friggin moon there may be a "false positive" that may slip by and never be seen.
I thought Mystic was open source, why don't you or someone just fix whatevers wrong with it? I know nothing about Mystic or how it tosses mail.
Only briefly. It became even more of a problem when people were updating sources in the middle of his projects and wondering why their shit wasn't working as they expected. With that there was the added headaches of compilation dates in between alphas. So he ended up going back to alpha releases only.
On 08 Jan 17 09:16:24, Mark Lewis said the following to Nick Andre:date
exactly sure on the details but i know that they greatly influenced me
to my software place the MSGID as close to the beginning of the control
lines possible so that db would not detect messages posted within one
second as dupes... this was especially important when testing at 100+
posts per second... are you willing to share information about how db
does its dupe detection so others can understand more? please?
Its not that hard to understand. A CRC is computed from the header and
of the tossed message. I would have to dig into the code and I'm not sure how many bytes are being included from the start of the message.
Each Echomail area has a cache database file. In the case of *.MSG,
this is called DBRIDGE.DUP and resides in each area and for
Hudson/QBBS there is one database segmented slightly different. The
CRC's are kept in there. I believe the code sets the cache database
size at 1,024 entries.
Interestingly it appears that there is a "reputation" method for the
cache database. It appears as it is loaded into RAM during a toss, any time a CRC match is encountered, that CRC is pushed up the cache
table, while CRC's of legitimate messages end up being pushed down.
The CRC table is saved into that cache file every time the Echomail
area changes in the toss cycle; or there are no more packets to toss.
I know... but in this case, what it appears people are freaking about
is a system is running software with a bug or in a way where it could
be fixed by changing versions, but the operator of that system refuses
to do so.
Obviously with this option you're giving in to the possibility
that once i bluish-purple with pink polka-dots friggin moon there
may be a "false positive" that may slip by and never be seen.
How come I'm not seeing you in the DR echo?
Only briefly. It became even more of a problem when people were
updating sources in the middle of his projects and wondering why
their shit wasn't working as they expected. With that there was
the added headaches of compilation dates in between alphas. So he
ended up going back to alpha releases only.
I remember times just reading some of that stuff and cringing when a
Sysop would explain this lengthly problem that apparently was the
fault of Mystic (and the author)... yet when James did his usual troubleshooting-101, the problem was revealed to be some weird bizarre
way that the Sysop had installed and configured the thing in the first place.
i remember the different dup cache files... i didn't know they were limited a paltry 1024 entries, though... i never dug that deep ;)
Interestingly it appears that there is a "reputation" method for the cache database. It appears as it is loaded into RAM during a toss, any time a CRC match is encountered, that CRC is pushed up the cache table, while CRC's of legitimate messages end up being pushed down. The CRC table is saved into that cache file every time the Echomail area changes in the toss cycle; or there are no more packets to toss.
that's pretty interesting... i guess that's so that messages with more dupe can be detected faster with their CRCs at the top of the queue... interesti idea and i'm sure one that was important back in the day of slower machines
You may even be misunderstanding that whole ordeal. Allen Prunty is not running Mystic, yet both are seemingly being blamed at the same time. If it indeed a fault of Mystic causing all of Roger's dupes, then it is not Allen Prunty. If Allen Prunty is causing all of Roger's dupes, then it is not Mys
How come I'm not seeing you in the DR echo?
What's the DR echo? I may vaguely remember you netmailing me about this. Wasn't it originally local to your system? Sorry, it's been an unfortunate busy end to 2016 and beginning to 2017 so far and I haven't had much time t do anything productive in this hobby.
I haven't added many new echos to my system (maybe besides Fidonet's UTF-8 echo) in quite some time. In any case, I've actually been pondering removin bunch, rather than adding more. :)
Yeah. There was definitely a lot of that. Probably moreso than real problem unfortunately. So much that the work in blocking any attempt at stupidity o the operator's part in the software would probably have required a complete rewrite in some cases.
Unless he picked up more work recently that requires a lot of travel (whic he's been in and out of for years), I'm guessing he's just hesitant to come back to the idiocy. Usually programmers are fairly level headed, but there' no way I would be able to deal with some people you guys run into without ripping all my hair out and completely losing my mind.
The size of the mailer's configuration also takes
away from conventional memory... especially the Netmail routing table.
The size of the mailer's configuration also takes
away from conventional memory... especially the Netmail routing table.
Do you have "me" in mind? ... 8-)
Hello Nick,
On Sun Jan 08 2017 10:42:28, Nick Andre wrote to Nicholas Boel:
I know... but in this case, what it appears people are freaking about
is a system is running software with a bug or in a way where it could
be fixed by changing versions, but the operator of that system refuses
to do so.
You may even be misunderstanding that whole ordeal. Allen Prunty is
not running Mystic, yet both are seemingly being blamed at the same
time. If it is indeed a fault of Mystic causing all of Roger's
dupes, then it is not Allen Prunty. If Allen Prunty is causing all
of Roger's dupes, then it is not Mystic.
That's why I stayed out of the whole ordeal in the first place.
People pointing fingers in every direction and not actually taking
the time to figure out what the actual problem is. :/
Obviously with this option you're giving in to the possibility
that once i bluish-purple with pink polka-dots friggin moon there
may be a "false positive" that may slip by and never be seen.
How come I'm not seeing you in the DR echo?
What's the DR echo? I may vaguely remember you netmailing me about
this. Wasn't it originally local to your system? Sorry, it's been
an unfortunate and busy end to 2016 and beginning to 2017 so far
and I haven't had much time to do anything productive in this
hobby.
I haven't added many new echos to my system (maybe besides
Fidonet's UTF-8 echo) in quite some time. In any case, I've
actually been pondering removing a bunch, rather than adding more.
:)
Even though
most of the naysaying, anti D'Bridge troublemakers have faded into the past, there are still a few around who want to cause trouble for 2
reasons. 1) they can, and 2) they don't have an inkling of what D'Bridge is about.
I may very well be misunderstanding; and I'm not pointing fingers,
ever, at Mystic. I'm a fan of that software, but I did somewhat-cringe when I saw the progress on its mailer/tosser or whatever that MIS
module is, because James is venturing into Fido-standards territory
which has a lot of minefields. As I posted before; it would not
surprise me if that ends up being a de-motivational factor for him.
Just the constant complaints about the Fido stuff, if that makes
sense.
DR is chat originating from my system, [D]ark[R]ealms, but really it
just exists as my own echo. No rules whatsoever, aliases/anonymous messages allowed.
I more or less created that echo as a total free-for-all; an
alternative to the Fn_sysop/Fido-Sysop typical nonsense.
I haven't added many new echos to my system (maybe besides
Fidonet's UTF-8 echo) in quite some time. In any case, I've
actually been pondering removin bunch, rather than adding more. :)
I know! How many Linux echoes do we really need?
Let me say this about that and I'm not writing this to cause friction
or to be mean, but want to point out the facts as I remember them: I
don't recall ever placing the blame on anyone's software. I read a
regardless of what system it is. What I did was point out that there
were dupes and printed the paths along with the headers and in many
cases, the MSGID was exactly the same. Naturally, some took afront to this and blamed D'Bridge simply because they don't know better.
I haven't added many new echos to my system (maybe besides
Fidonet's UTF-8 echo) in quite some time. In any case, I've
actually been pondering removing a bunch, rather than adding
more.
:)
Most of mine are gone simply because I tired of reading the same old stuff.
I thought Mystic was open source, why don't you or someone just fix whatevers wrong with it? I know nothing about Mystic or how it tosses
mail.
DR is chat originating from my system, [D]ark[R]ealms, but really it just exists as my own echo. No rules whatsoever, aliases/anonymous messages allowed.
I stuck with a particular version of Renegade because I didn't like the direction the developer was taking it. Changing database structures and adding lightbars and all that... actually IMO he was copying from Searchlight and TBBS in how the menus work. Meanwhile, bugs I pointed out never got fixed.
I know! How many Linux echoes do we really need?
Even though
most of the naysaying, anti D'Bridge troublemakers have faded into the past, there are still a few around who want to cause trouble for 2
reasons. 1) they can, and 2) they don't have an inkling of what D'Bridge is about.
I find this a perfectly valid analyses.
I think I got my license KEE in 1988 ... Eewwhhhh ... I'm in my
29th DB-year. Back in those days there was a pre-configured
setting that made a rescan the first time someone linked-in to an
echo but due to some bug it also mirrored the complete content of
that or these echo[es] back up the path with a fresh header and everything.
So you knew a new D'Bridge-customer had popped-up when massive
rescans of echoes were posted. This could be avoided and people
with a brain were not affected.
In those days the usage of D'BROKE or D'BUG became fashionable. The problem was fixed, the myth persisted, especially among
Frontdoor-users. JoHo had assembled a fanclub and I remember a
Eurocon where he had a group of followers that were on his trail
all the time as if he were a guru of some kind. So when he
mentioned D'BUG, they all started doing that. He stopped doing that
when I had a private talk with him July 2nd 1995.
On Mon Jan 09 2017 04:56:34, Roger Nelson wrote to Nicholas Boel:
Let me say this about that and I'm not writing this to cause friction
or to be mean, but want to point out the facts as I remember them: I
don't recall ever placing the blame on anyone's software. I read a
I never said you did.
You mentioned what your DUPE base was filled with, is all. It was
others who brought the software into the equasion, which
intensified the discussion and meshed the two together somehow. I
was simply pointing out the two have nothing in common at this
time besides they may /separately/ be causing some similar
problems.
regardless of what system it is. What I did was point out that
there were dupes and printed the paths along with the headers and
in many cases, the MSGID was exactly the same. Naturally, some
took afront to this and blamed D'Bridge simply because they don't
know better.
I hadn't seen a message here recently blaming DB for any of the
recent dupes, although I may have skipped over some messages.
However, I remember a query for a feature request (which was
denied) and someone pointing out something about a /specific/ DB
system. I guess I'm just hazy as to why DB is still involved in
this conversation regarding Allen and/or Mystic at all. :)
I haven't added many new echos to my system (maybe besides
Fidonet's UTF-8 echo) in quite some time. In any case, I've
actually been pondering removing a bunch, rather than adding
more.
:)
Most of mine are gone simply because I tired of reading the same old stuff.
That's exactly where I'm at now.
I realize that, but I wanted to share those facts here that I
presented elsewhere and they were not aimed at you, but about the naysayers in other echoes when I began posting those headers, seen-bys
and paths. I didn't do it long because it soon dawned on me that I
was dealing with some stoneheads that were too busy blaming D'Bridge
and defending themselves to look at their own setups. With those
guys, it is always someone else's fault. I look over my setup every
time Nick puts out a new release just to be sure everything is as it should be. It doesn't take much time and I am speaking only about my setup, which is about as simple as I can make it.
So, we were saying the same thing using different words. That can
happen.
regardless of what system it is. What I did was point out that
there were dupes and printed the paths along with the headers and
in many cases, the MSGID was exactly the same. Naturally, some
took afront to this and blamed D'Bridge simply because they don't
know better.
You won't see it here. It only appears in some other echoes.
D'Bridge has caught over 4400 dupes since July 31, 2016. Those are
what I consider legitimate dupes. Remember a few months back when
(here) I received 3MB of mail? I think we all got an even number or
more depending on the areas carried.
I'm still waiting for my ISP to enable IPv6. I have a temp address,
but it's one-way only. My IPv4 address is static.
I haven't added many new echos to my system (maybe besides
Fidonet's UTF-8 echo) in quite some time. In any case, I've
actually been pondering removin bunch, rather than adding more. :)
I know! How many Linux echoes do we really need?
Well, one for every friggin distribution out there, DUH! :)
RA support echos and OS2 echos too. Along with the various technical areas software is not even being used anymore (TUB and TORNADO come to mind right off the top of my head, but I'm sure there are plenty others) Seriously, there's like 5+ of each of them and they're lucky to get one post a month besides the moderator's robot postings. Yet nobody has any kind of urge whatsoever to knock these down and combine them into one message base that could possibly get 2 posts per month instead of that lonely one.
At one point it must have just became a chest pounding thing to show how ma echos you moderated and how many you have collected over the years, and it doesn't seem like anyone ever wanted to give up that feeling. Now we have a wasteland of a bunch of dead echos and consolidation is definitely not something people want to come to terms with until /maybe/ the day one reali the only one seeing the robot postings are themselves. Even then there's a good chance it won't be realized.
I thought Mystic was open source, why don't you or someone just fix whatevers wrong with it? I know nothing about Mystic or how it tosses
mail.
Mystic isn't open source, unfortunately. I can certainly see how a single person writing code and supporting a software program can cause burnout. Needing breaks now and then to regroup is healthy.
If more coders were around the BBS world, that would certainly help.
DR is chat originating from my system, [D]ark[R]ealms, but really it just exists as my own echo. No rules whatsoever, aliases/anonymous messages allowed.
I like it! Where do I sign up?
I stuck with a particular version of Renegade because I didn't like the direction the developer was taking it. Changing database structures and adding lightbars and all that... actually IMO he was copying from Searchlight and TBBS in how the menus work. Meanwhile, bugs I pointed out never got fixed.
Similar situation with me an my "classic" modded WWIV 4.24a. I have the source code and can modify and do some coding in "C", where other languages I'm not as well versed.
It takes me a million more steps to complete the same task that could be do in minutes with Mystic, but somehow it all works. Like a classic car, ther are quirks that I try to deal fix now and then but I keep her running.. :)
I know! How many Linux echoes do we really need?
One for every single application.
I know! How many Linux echoes do we really need?
Well, one for every friggin distribution out there, DUH! :)
You mean for every distribution, every application, every possible configuration scenario... akin to the comp hiarchy on Usenet.
Well because you know that would just be the kiss of death of Fido, if
any echoes started vanishing like that...
I think I got my license KEE in 1988 ... Eewwhhhh ... I'm in my
29th DB-year. Back in those days there was a pre-configured
setting that made a rescan the first time someone linked-in to an
echo but due to some bug it also mirrored the complete content of
that or these echo[es] back up the path with a fresh header and
everything.
That wasn't DB130, was it? That's the version I began with.
Hero worship. I remember a bunch of guys (okay, maybe a few) telling
Chris that they could break his security and make their own kee, but no
one that I know of succeeded.
I think I got my license KEE in 1988 ... Eewwhhhh ... I'm in my RN>WD> 29th DB-year. Back in those days there was a pre-configured
setting that made a rescan the first time someone linked-in to an RN>WD> echo but due to some bug it also mirrored the complete content of RN>WD> that or these echo[es] back up the path with a fresh header and RN>WD> everything.
That wasn't DB130, was it? That's the version I began with.
Before 130 I think. But that's a long time ago.
Hero worship. I remember a bunch of guys (okay, maybe a few) telling
Chris that they could break his security and make their own kee, but no
one that I know of succeeded.
I think the KEE-generator got hacked and unlimited numbers of KEE's could b made.
There was code in the mailer that caused two systems with the same KEE numbers
to crash upon connection. I'm not sure if the modem would be disconnected ;)
There was code in the mailer that caused two systems with the same KEE numbers
to crash upon connection. I'm not sure if the modem would be disconnected ;)
Putin would not have been amused.
Putin would not have been amused.
I wonder how popular D'Bridge is in Russia.
I know Benny and Alexey keep pestering me for a Linux version...
Putin would not have been amused.
I wonder how popular D'Bridge is in Russia.
Not a chance, I'm pretty confident.
I know Benny and Alexey keep pestering me for a Linux version...
Benny has trouble remembering his own name, he's not interested at
all.
On 10 Jan 17 15:07:46, Ward Dossche said the following to Roger
Nelson:
I think the KEE-generator got hacked and unlimited numbers of KEE's
could b made.
There was code in the mailer that caused two systems with the same
KEE numbers to crash upon connection. I'm not sure if the modem
would be disconnected ;)
That wasn't DB130, was it? That's the version I began with.
Before 130 I think. But that's a long time ago.
I think the KEE-generator got hacked and unlimited numbers of KEE's
could be made.
I think the KEE-generator got hacked and unlimited numbers of KEE's
could b made.
There was code in the mailer that caused two systems with the same
KEE numbers to crash upon connection. I'm not sure if the modem
would be disconnected ;)
If D'Bridge crashed, which I now remember that it would under that circumstance, wouldn't the modem be disconnected automatically?
Putin would not have been amused.I wonder how popular D'Bridge is in Russia.
I know Benny and Alexey keep pestering me for a Linux version...
Benny has trouble remembering his own name, he's not interested at
all.
Benny has trouble remembering his own name, he's not interested at BP>WD> all.
you dont know me yet then
Hello Nick!
11 Jan 2017 08:12, Nick Andre wrote to Ward Dossche:
Putin would not have been amused.I wonder how popular D'Bridge is in Russia.
+1
I know Benny and Alexey keep pestering me for a Linux version...
atleast a raspberry pi version would do, remember it have its boot on fat :=)
On 11 Jan 17 11:23:17, Roger Nelson said the following to Nick Andre:
KEE numbers to crash upon connection. I'm not sure if the modem NA>RN> NA> would be disconnected ;)
If D'Bridge crashed, which I now remember that it would under that NA>RN> circumstance, wouldn't the modem be disconnected automatically?
Not necessarily. A system crash, or more specifically a DOS program that just decides to give-up... does not automatically drop the carrier signal on a COM port unless its told to do so or a hard-reset is done.
I have an archive of the source code for 1.60 I believe, I can take a
look.
I know Benny and Alexey keep pestering me for a Linuxversion...
atleast a raspberry pi version would do, remember it have its boot
on fat
:=)
Does anyone have their drives formatted FAT anymore or is that because
it raspberry pi?
Does anyone have their drives formatted FAT anymore or is that because
it raspberry pi?
Not necessarily. A system crash, or more specifically a DOS program that just decides to give-up... does not automatically drop the carrier signal on a COM port unless its told to do so or a hard-reset is done.
It just seems to me that if the program that was using the modem crashed, there would no reason for the modem to continue the carrier.
atleast a raspberry pi version would do, remember it have its boot onfat
:=)
Does anyone have their drives formatted FAT anymore or is that because it raspberry pi?
I know Benny and Alexey keep pestering me for a Linux version...
atleast a raspberry pi version would do, remember it have its boot on
fat :=)
atleast a raspberry pi version would do, remember it have its boot on
fat :=)
Does anyone have their drives formatted FAT anymore or is that because
it raspberry pi?
Not necessarily. A system crash, or more specifically a DOS program
that just decides to give-up... does not automatically drop the
carrier signal on a COM port unless its told to do so or a hard-reset
is done.
It just seems to me that if the program that was using the modem
crashed, there would no reason for the modem to continue the carrier.
Hello Roger,
On Thu Jan 12 2017 06:51:22, Roger Nelson wrote to Benny Pedersen:
Does anyone have their drives formatted FAT anymore or is that because
it raspberry pi?
And sorry. The last message should have been directed to Benny, and
not you.
On 12 Jan 17 06:59:08, Roger Nelson said the following to Nick
Andre:
Not necessarily. A system crash, or more specifically a DOS program that just decides to give-up... does not automatically drop the carrier signal on a COM port unless its told to do so or a hard-reset is done.
It just seems to me that if the program that was using the modem crashed, there would no reason for the modem to continue the carrier.
The modem doesn't know that. Its job is just to keep carrier until
its told not to. Either by the other side dropping carrier or due
to a software procedure call or a hardware reset.
atleast a raspberry pi version would do, remember it have its boot on RN>BP> fat. :=)
Does anyone have their drives formatted FAT anymore or is that because it raspberry pi?
Most likely he boots from an SD-chip ...
On 2017 Jan 12 06:51:22, you wrote to Benny Pedersen:
atleast a raspberry pi version would do, remember it have its boot on
fat :=)
Does anyone have their drives formatted FAT anymore or is that because
it raspberry pi?
it is because it has to boot using the old DOS boot style to get
the loader in place and then make the jump... this is the same type
thing that we used to have to do when making bootable CDs back in
the day when that first started...
On 2017 Jan 12 06:59:08, you wrote to Nick Andre:
Not necessarily. A system crash, or more specifically a DOS program
that just decides to give-up... does not automatically drop the
carrier signal on a COM port unless its told to do so or a hard-reset
is done.
It just seems to me that if the program that was using the modem
crashed, there would no reason for the modem to continue the carrier.
if the modem is internal, it may very well shut down... an external
one, on the other hand, may not... it depends on how it is
configured with the serial control lines and what happens to them
when the software or system goes down... this is one of the reasons
why i always use external modems and not internal ones... externals
i can just turn off and rest but internals have to have the machine rebooted and maybe even hard rebooted or powered off instead of
just a soft boot...
Most likely he boots from an SD-chip ...
I was surprised at the size of those cards. I have a 32Gb SDHC card
in my phone and it's about the size of my little fingernail. I use it
for backups.
Hello Roger,
On Fri Jan 13 2017 07:11:18, Roger Nelson wrote to Ward Dossche:
Most likely he boots from an SD-chip ...
I was surprised at the size of those cards. I have a 32Gb SDHC card
in my phone and it's about the size of my little fingernail. I use it
for backups.
The size and capacity even. I'm currently using a 128gb SDXD card
in both of my Raspberry Pis. They have 256gb cards, but they were a
little pricey, especially when the Pi you're putting them in costs
half the price. :)
Tell me your name ...
Does anyone have their drives formatted FAT anymore or is that because
it raspberry pi?
Hello Roger!
12 Jan 2017 06:51, Roger Nelson wrote to Benny Pedersen:
Does anyone have their drives formatted FAT anymore or is that because
it raspberry pi?
rpi have fat as the only boot partion supported, so yes you can
install freedos on it :=)
atleast a raspberry pi version would do, remember it have its boot
on fat :=)
Does anyone have their drives formatted FAT anymore or is that
because it raspberry pi?
it is because it has to boot using the old DOS boot style to get the
loader in place and then make the jump... this is the same type thing
that we used to have to do when making bootable CDs back in the day
when that first started...
I wonder if I could run D'Bridge on my Android?
Most likely he boots from an SD-chip ...
I was surprised at the size of those cards. I have a 32Gb SDHC card in
my phone and it's about the size of my little fingernail. I use it for backups.
rpi have fat as the only boot partion supported, so yes you can
install freedos on it :=)
+1
I wonder if I could run D'Bridge on my Android?
if you can get a DOS emulator on there, sure... if not, then a DOS VM
is the only other way i know of... i'm not going to try it on either
of my android tablet (finally got one) or my iOS phone (hand me up)...
I thought Mystic was open source, why don't you or someone just fix whatevers wrong with it? I know nothing about Mystic or how it tosses mail.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,049 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 52:52:32 |
| Calls: | 236,052 |
| Files: | 60,364 |
| D/L today: |
25 files (8,007K bytes) |
| Messages: | 289,618 |