Micronet decided to throw in a curveball.
For a couple of weeks now, this was working fine:
Listfile=micronet.###
UpdateFile=micronet.###
UpdateArchive=micronet.z##
DelUpdate=J
DoDiff=N
Format=1
zone=618
In otherwords, my bossnode was delivering micronet.zip with
micronet.### inside.
The last two updates processed automatically quite fine.
But I *just* received MICRONET.Z92, with micronet.092 inside.
At first, I thought this would be the solution:
Listfile=micronet.###
UpdateFile=micronet.###
UpdateArchive=MICRONET.Z##
DelUpdate=J
DoDiff=N
Format=1
zone=618
But that did NOT work in the automatic mode. :( Automatic mode
would normally kick in the NEXT TIME OpenXP is lauched. I was a
bit surprised by that. FSXNET.Z## which operates the same way
has not problem at all upadating automatically. I wondered..
WHY doesn't the MICRONET.Z## file cooperating?
The last FSXNET.Z## contains:
Archive: FSXNET.Z92
Length Date Time Name
-------- ---- ---- ----
36459 04/01/21 09:15 FSXNET.092
-------- -------
36459 1 file
Looking inside MICRONET.Z##:
Archive: MICRONET.Z92
Micronet Information Network nodelist for
02 April 2021 (day 92). A friendly
and active international BBS mail network.
Info on how to join is in the nodelist.
Length Date Time Name
-------- ---- ---- ----
26735 04/02/21 13:35 micronet.092
165 04/02/21 13:47 file_id.diz
-------- -------
26900 2 files
SO.. the difference is that the latter has TWO files inside.
Could it be that the presence of file_id_diz is throwing off the
automatic processing to work as expected?
Maybe, maybe not but I would say that micronet need to get their
act together with their filenaming convention for their nodelist
files before anyone attempts to offer a solution to your problem.
As things stand at the moment, I couldn't even hazard a guess as
to what the problem could be, sorry.
The last FSXNET.Z## contains:
Looking inside MICRONET.Z##:
Maybe, maybe not but I would say that micronet need to get their act together with their filenaming convention for their nodelist files before anyone attempts to offer a solution to your problem. As things stand at the moment, I couldn't even hazard a guess as to what the problem could be, sorry.
it should be noted that the micronet ZC's modem suffered from a lightning strike and they were down until a new mpdem was procured... during this time, the nodelist and ZC activities were transferred to the 2nd "in command"... the two systems are different which explains the filename
case differences as well as the appearance of the file_id.diz...
without knowing more about what the client software is doing, there's no way to even start to guess... from my side as an observer, i would say
the software is simply being too strict and needs to lighten up a little ;)
it should be noted that the micronet ZC's modem suffered from a
lightning strike and they were down until a new mpdem was
procured... during this time, the nodelist and ZC activities
were transferred to the 2nd "in command"... the two systems are
different which explains the filename case differences as well
as the appearance of the file_id.diz...
The temporary ZC activities is appreciated!
What modem replacement were you able to find? I have a modest
museum of old modems. I don't know what to do with them.
What modem replacement were you able to find? I have a modest
museum of old modems. I don't know what to do with them.
we're talking about an ISP modem... i know the story because sean is one of my links and he was keeping us updated... the ISP sent a zyxel...
I suppose your zyxel replacement was something provided under
a warranty or the rental program?
The only difference between FSXNET.Z## working and MICRONET.Z## not working is the presence of the 2nd file file_id.diz in the latter.
I suppose your zyxel replacement was something provided under
a warranty or the rental program?
idk... i'm not the micronet ZC... his name is sean whereas mine is
)\/(ark ;)
i have nothing to do with micronet other than being an outside
observer...
The only difference between FSXNET.Z## working and MICRONET.Z## not
working is the presence of the 2nd file file_id.diz in the latter.
Do you get MICRONET.Z## files? I've only ever received MICRONET.ZIP
files with a MICRONET.### (e.g. MICRONET.092) in it.
i have nothing to do with micronet other than being an outside
observer...
No problem. It sure sounded like you had the inside story to
the micronet problem though,
and then I mistakenly carried on as if you were involved with
its operations.
"idk" - I had to look that one up! :D
"idk" - I had to look that one up! :D
hehehe, i've been spending a lot of time with gamers and
streamers... i'm tending to use more and more of their
shorthand mnemonics like IDK, WDYM, ISWYD, and similar O:)
Looks like I receive an uppercase MICRONET.ZIP file (not .Z##) with a lowercase micronet.### inside of it:
"idk" - I had to look that one up! :D
hehehe, i've been spending a lot of time with gamers and
streamers... i'm tending to use more and more of their
shorthand mnemonics like IDK, WDYM, ISWYD, and similar O:)
Those are new to me too. So.. is there a new generation of
these things now?
Those are new to me too. So.. is there a new generation of these
things now?
mainly new common phrases for the most part... there are moar but i
think urban dictionary and similar cover them better than i/we could
here ;)
mainly new common phrases for the most part... there are
moar but i think urban dictionary and similar cover them
better than i/we could here ;)
Re: nodelist curveball
By: Martin Foster to August Abolins on Sun Apr 04 2021 11:33:00
Maybe, maybe not but I would say that micronet need to get their
act together with their filenaming convention for their nodelist
files before anyone attempts to offer a solution to your problem.
it should be noted that the micronet ZC's modem suffered from a lightning strike and they were down until a new mpdem was procured... during this time, the nodelist and ZC activities were transferred to the 2nd "in command"... the two systems are different which explains the filename
case differences as well as the appearance of the file_id.diz...
mainly new common phrases for the most part... there are
moar but i think urban dictionary and similar cover them
better than i/we could here ;)
I wrote a reply to this in CHAT.
I wrote a reply to this in CHAT.
no clue what fido echo that is...
I wrote a reply to this in CHAT.
no clue what fido echo that is...
Echo Successfully Updated.
I wrote a reply to this in CHAT.
no clue what fido echo that is...
That's a long time fido echo although I don't know who the moderator is or if there is one and the area is not on the backbone.
I wrote a reply to this in CHAT.
no clue what fido echo that is...
Perhaps it is one you missed:
i don't see it in either of my backbone.na or backbone.no lists...
actually, i do remember seeing that echolist update...
the area is not on the backbone, though, so i just don't have it here... probably one of the ones that get send here by others and is just deleted because it is not in any of my lists... oh well...
I wrote a reply to this in CHAT.
no clue what fido echo that is...
That's a long time fido echo although I don't know who the moderator
is or if there is one and the area is not on the backbone.
You can connect here if you like.. :)
I'm connected to this echo via Nick but the last message I see in there is Nov 2020.
... I have a dream... C:\ 999,999,999,999 Megs free!
... I have a dream... C:\ 999,999,999,999 Megs free!
That works out to...
999999TB (Terabytes)
-Or-
999PB (Petabytes)
-Or-
0.999EB (Exabytes)
So we still have to keep dreaming! LOL
actually, i do remember seeing that echolist update...
Yes, it is August's area, I remember now!
I am not sure if August had asked the area be added to the backbone but I did request the MUSIC area be added a while back in the Z1_BACKBONE area but so far it has not been added.
How do we add areas to the backbone today?
I'm connected to this echo via Nick but the last message I see in there
is Nov 2020.
That's a long time fido echo although I don't know who the moderator is
or if there is one and the area is not on the backbone.
i don't see it in either of my backbone.na or backbone.no lists...
... I have a dream... C:\ 999,999,999,999 Megs free!
That works out to...
0.999EB (Exabytes)
So we still have to keep dreaming! LOL
Yep, that was my dream in the 90's and today.. it's still a dream!
How do we add areas to the backbone today?
Let me know if you find out anything.
How do we add areas to the backbone today?
i don't see it in either of my backbone.na or backbone.no lists...
Janis has it though:
Re: shorthand mnemonics like IDK
By: Alan Ianson to mark lewis on Tue Apr 06 2021 06:41:44
I wrote a reply to this in CHAT.
no clue what fido echo that is...
That's a long time fido echo although I don't know who the moderator is
or if there is one and the area is not on the backbone.
i don't see it in either of my backbone.na or backbone.no lists...
... I have a dream... C:\ 999,999,999,999 Megs free! Yep,
that was my dream in the 90's and today.. it's still a
dream!
I have a 20TB NAS downstairs with 6.8TB free, I'm not sure
what I'd do with a petabyte let alone an exabyte.
Janis has it though:
that doesn't mean it is on the backbone, though...
remember, the backbone.na and backbone.no lists of echo
files are what determines if an echo is on the backbone or
not...
I have a 20TB NAS downstairs with 6.8TB free, I'm not sure what I'd
do with a petabyte let alone an exabyte.
Wow. Hard to let go of stuff even when it's digital, eh?
i don't see it in either of my backbone.na or backbone.no lists...
It's listed in ELIST.NA, if that's of any use.
that doesn't mean it is on the backbone, though...
remember, the backbone.na and backbone.no lists of echo
files are what determines if an echo is on the backbone or
not...
Ok. But the new elist guy isn't distributing the those
like Ben Ritchey did.
I just noticed that Vince (new Elist guy) posted some
instructions in z1_backbone on how to accomplish a backbone
listing.
the same way as has always been done... post in the Z1 backbone echo a *copy* of the echolist reply with the proper subject line... that method hasn't changed in well over a decade... the only thing right now is that we don't currently have an official admin person to handle the actual updates to the na/no lists and there's been no discussion of such between the stars...
Wow. Hard to let go of stuff even when it's digital, eh?
A lot of is is ripped DVDs. Several years ago I just HAD to have every
TV show I watch on DVD, which was awesome at the time, but then..
i don't see it in either of my backbone.na or backbone.no lists...
It's listed in ELIST.NA, if that's of any use.
yeah, that's from the echolist... nothing to do with the
backbone but the backbone does use the echolist for certain
things...
ben was wearing two separate and distinct hats... one for
the echolist and one for the backbone... i suspct he also
tried to combine some things but none of it was ever
discussed with the backbone stars...
I just noticed that Vince (new Elist guy) posted some
instructions in z1_backbone on how to accomplish a
backbone listing.
i've not seen it yet... i'll take a look...
I am working on a reply. Will post it to CHAT echo.
I'm connected to this echo via Nick but the last message I see in there
is Nov 2020.
Something broke. Here are just a few back to the beginning of
March:
06.04 August Abolins All Case against another
US intelligence offi 05.04 August Abolins mark lewis
-shorthand mnemonics like IDK 05.04 August Abolins Wilfred van
Could you post some of the kludge lines for these messages?
I'd be interested in knowing there the break in the link is betwen
point A and 1:229/426 where I get my messages from.
I am working on a reply. Will post it to CHAT echo.
I don't get any new messages in there, last messages was in Nov 2020.
Yes.. I read that you mentioned that before. Hopefully your feed
will re-supply it and then you can %rescan.
Could you post some of the kludge lines for these messages?
I'd be interested in knowing there the break in the link is betwen point
A and 1:229/426 where I get my messages from.
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 66 |
Nodes: | 4 (0 / 4) |
Uptime: | 15:57:49 |
Calls: | 718 |
Files: | 7,654 |
Messages: | 293,898 |