ml> now the question is "which packet driver(s) are compatible
with IREX?"

 MvdV> I was hoping to get an answer to thet.

that is, really, the only answer that is needed... IIRC, there were several
packet drivers for DOS but they didn't all use the same "device
name" or routine calls... it made for quite a heady situation, back in
the day, when one attempted to be compatible with more than one packet
driver...

sadly, i've never run IREX (in any flavor) and have no clue as to which
packet driver it was written for...

the second question in the equation is: will that DOS setup and packet
driver work with today's connection methods... for most, it should be no
real problem as long as the connection is maintained by something else
other than the DOS machine... POTS dialup internet /may/ still be supported
by /some/ ISPs but most are only supporting PPP, DHCP or STATIC
connections... generally speaking, this means that, as mentioned above,
something else (ie: another machine) needs to be maintaining the connection
AND there must also be a TCP/IP network that the DOS machine can be a
member of... this should not be a real problem as long as TCP/IP
connectivity of the DOS machine is the main configuration... i have a
couple of DOS boxes around here somewhere that i only /pull/ data to
because they simply cannot run any kind of server stuff... i do, however,
also have one old XT or AT, that i shoehorned the necessary items into that
does have netbios peer2peer capabilities but those packet driver modules
eat all available DOS 640K memory so the only thing i can run on it outside
of DOS is something teensy like {COMMO}... forget anything like IREX or FD
or even a full blown BBS...

)\/(ark