ml>> you obviously don't have a clue what information is
 ml>> contained within the exitinfo.bbs file, then... for one
 ml>> thing, tell me if door.sys can carry the info on what
 ml>> message areas a user has selected to join... never
 ml>> mind, as you can't tell me that... truth be known,

 MvanL> Heh. The keyword is "can" - and surprise door.sys can.

yeah? for 65535 files areas and 65535 message areas? what format does this
data take? it isn't detailed in any of the specs i have...

 ml>> exitinfo.bbs carries all bbs config information as it
 ml>> relates to the currently logged on user...

 MvanL> So why should dorinfo1.def carry any more details. It
 MvanL> satisfied the requirement of whomever invented it.

i never said that dorinfox.def should carry more details... i said that it
doesn't carry the node number internally... you extrapolated that on to
something else...

 MvanL> If people deviate from the specification and adopt different
 MvanL> methods for using dorinfo1.def that's their perogative, which
 MvanL> doesn't change the fact that the number in the dorinfo1.def
 MvanL> dropfile was never meant to designate a node number.

you've still not provided the proof of this... i'm more than willing to
look at it once it is made available... i would hope that it is written by
the original author of the dorinfox.def specification ;)

 H>> What's wrong with passing the node number as an option to
 H>> the door ? hence rendering node number dropfile naming
 H>> conventions irrelevant. Believe it or not it works for
 H>> many doors out there.

 ml>> duh? i think i've been doing this a few more years than
 ml>> you have, Mvan... at least as long as you are years
 ml>> old, thankyouverymuch...

 MvanL> Oooo wow I'm scared.

ROTFL! no doubt...

 >>>  MvanL> A "/node=65535" sounds pretty limitless to me.

 >>> furrfu, damn good thing you're not a real programmer ;) it
 >>> is arbitrary limit like that that have caused all kinds of
 >>> problems over the years...

 H>> It's not an arbitrary limit. It's an example command line
 H>> option.

 ml>> it doesn't read that way... apologies if i misread your
 ml>> mind as you didn't say that in that manner...

 MvanL> Does "65535" LOOK like an arbitrary number to you ?

no... it is the largest value that a 16bit WORD can hold... that makes it
the upper limit...

)\/(ark