I know that there is no weekly infopack or nodelist sent out. I
would be happy to assist with this, if you wish. My last one was in
2018.
Mike Dippel
--- Platinum Xpress/Win/WINServer v7.0
* Origin: ILink The Hobby Line! BBS hobbylinebbs.com (454:1/393)
I know that there is no weekly infopack or nodelist sent out. I
would be happy to assist with this, if you wish. My last one was
in 2018.
I know that there is no weekly infopack or nodelist sent out. I
would be happy to assist with this, if you wish. My last one was
in 2018.
Let me get back to you on that -- seems to have been a reason why we disontinued but not enough coffee in my system to remember.
@MSGID: 454:1/1@cfbbs.dtdns.net d5865084
Mike Dippel and Nigel Reed:
I checked with the other administrators just in case I was missing a
detail or it would be a good idea. They appreciate the thought but we
all agreed it was an unnecessary project.
The Fido nodelist is current even though dated February 2023; Michael
Luko will touch the date to make it current
There is no common file area so each BBS has their own dependent on the SysOp's interests.
Is there a current Nodelist that you can forward to my email address
at: mdippel@gmail.com
I know that there is no weekly infopack or nodelist sent out. I would be happy to assist with this, if you wish. My last one was
in 2018.
Let me get back to you on that -- seems to have been a reason why we discontinued but not enough coffee in my system to remember.
It might have gone something like "some sysops want a weekly nodelist, but there is no reason to update a nodelist that has not had any updates."
I am on another network where this issue came up. We get a weekly nodelist but it often doesn't change week-to-week which was causing some sysops with automated nodelist processing to run into issues... their processor would burp on the "new" old nodelist, and they expected the net coordinator to figure out the issue.
Mike
I can send you a current nodelist to your email a bit later.
I have the following batch file that gets executed if a change is made
to the nodelist:
cd \pcb\qfront
c:\pcb\qfront\qfutil /addr:454:2/1 /forward /file:c:\pcb\ilink\docs\il-list*.* /flags:hold
c:\pcb\qfront\qfutil /addr:454:1/393 /forward /file:c:\pcb\ilink\docs\il-list*.* /flags:hold
c:\pcb\qfront\qfutil /addr:454:1/5016 /forward /file:c:\pcb\ilink\docs\il-list*.* /flags:hold
c:\pcb\qfront\qfutil /addr:454:3/105 /forward /file:c:\pcb\ilink\docs\il-list*.* /flags:hold
cd %pcbdir%
starter.bat
If there are any system that would like to be added to the list let
me know. Also is there any interest in putting the batch file on a
scheduled event in addition to as changes are made? Weekly, monthly?
It would be almost impossible for me to send it directly to each node
using my tic hatcher since I would have to have a connection to each
node in my Platinum Express Data Processor.
What I could do is to compile the nodelist only when there are any
changes, and email it as an attachment to the various nodes.
I know that there is no weekly infopack or nodelist sent out. ILet me get back to you on that -- seems to have been a reason why we disontinued but not enough coffee in my system to remember.
would be happy to assist with this, if you wish. My last one was
in 2018.
It might have gone something like "some sysops want a weekly
nodelist, but there is no reason to update a nodelist that has
not had any updates."
I am on another network where this issue came up. We get a weekly
nodelist but it often doesn't change week-to-week which was
causing some sysops with automated nodelist processing to run
into issues... their processor would burp on the "new" old
nodelist, and they expected the net coordinator to figure out the
issue.
Is there a current Nodelist that you can forward to my email address
at: mdippel@gmail.com
I can send you a current nodelist to your email a bit later.
Right: one reason I didn't want to immediately say 'no' just because I thought we didn't need it. I use Wildcat! and that system doesn't need
but Syncronet systems are assigned to you because you're familiar with
its nuances. I figured if Sychronet (for example) needed a file it
would have been created and generated as needed.
Right: one reason I didn't want to immediately say 'no' just because I thought we didn't need it. I use Wildcat! and that system doesn't need
but Syncronet systems are assigned to you because you're familiar with
its nuances. I figured if Sychronet (for example) needed a file it
would have been created and generated as needed.
Synchronet doesn't need the nodelist but can use it. I suspect
some sysops may have their systems set up to use it.
| Sysop: | Martin J Mitchell |
|---|---|
| Location: | Scotland |
| Users: | 5 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 50:13:40 |
| Calls: | 127 |
| Files: | 29,254 |
| Messages: | 54,760 |