ml>> some bbs systems got around the 9 node limitation by
 ml>> creating dorinfo1.def for all nodes, though... and
 ml>> that's no real problem if the door can look in a
 ml>> directory other than its own for the drop file...

 ml>>   ie: somedoor c:\bbs\n1

 ml>> where c:\bbs\n1 is where the dropfile, whatever is
 ml>> being used, is located... c:\bbs\n42 for node 42... no
 ml>> copying or overwritting and no possibility of things
 ml>> going wonky if two users enter the door at the same time...

 MvanL> My argument would be people started writing and using TCP/IP
 MvanL> and multithreaded daemons and computer clusters and invented
 MvanL> the I-n-t-e-r-n-e-t.

haha... that's not an argument... that's a diversion so that one can exit
the building and not have to face the discussion at hand ;)

 MvanL> And that's why those large multinode BBS's are extinct and any
 MvanL> node/dropfile conflict issues are nowadays virtually
 MvanL> impossible.

i disagree... most of them have simply changed faces... many BBS systems
are now ISPs... a lot of BBS systems have also moved to forum style
interfaces... i don't see any of the goo old BBS doors available in any new
formats, though...

)\/(ark