I have no idea on this. Some Guru that is better versed isnah leave them out if there's no modem. I don't think
any software will choke on a line with no flags...
modem capability flags are needed IF there is a modem answering the line... if it is telnet or some other network protocol, then other
flags may be needed but not modem flags... unless we develop some
"dual meaning" flags... one thing if modem, another if a certain
The important thing is to have the order. The current
Nodelist has the major flaw or being disorganized at the
end. It's ok at the first... as you read the current list,
you know that field one is "A", two is "B", three is "C",
four is "D" and co on. Then you get to the flags and it
falls apart. If a Node is CM, but not MO, the order is
all messed up and hard to translate.... at least to me.
the thing to remember here is that the flags after the speed field are
all grouped together as a(nother) comma seperated field... and it is possible (of course) to have an additional comma seperated field in
there known as U(ser) flags...
I often laugh at the thought of putting a user flag in
yes, but that one shouldn't be allowed by the *C processing that
segment because it is frivilous and doesn't serve any technical function(s)...
The conversion program could use a configuration file to
set what sections of the new list are used in what order
for the old list.
uggg... that leave too much open to go wrong... someone could adjust
that line in the config file and then that row or entire segment might
be dropped by the processing software due to something being
If the flag IBN, ITN or some other "I" flag exists, the
node would be at least Internet capable.
that might be possible but it could also be restricting in the
future... better to have a complete new field similar to my proposal
of an additional leading field containing the connection type for the row...
|Location:||Riverside County, California|
|Nodes:||15 (0 / 15)|