>> CONNECT local_port, server_port, server_name, mode TM> local_port is an integer value between 0 and 9, similiar to the TM> file number used in the file functions TM> server_port is a real port number , e.g 80 for http or 23 for TM> telnet server_name is a string with either the name of the TM> server or its IP-adress. mode is a string. Possible modes are TM> "a" for ascii mode or "b" for binary mode.
TM> I don't want to quote 100 lines, but how is the local_port number TM> determined, especially if DOS and the BIOS don't recognize the port by TM> an integer between 0 and 9? Like maybe a modem at base 0xd400 IRQ 11, TM> or even base 0x2e8 IRQ 5? Is there a form of the OPEN command that TM> dials the modem and installs a packet driver? Ricsi: > You don't understand ... > You need to have a running connection ... so you have already dialed in, (chat/epppd or whatever dialer or packet driver) > The port which is mentioned above is either TCP or UDP port. eg host:port Host port makes sense to me, usually 21 for ftp, 80 for http, 25 for smtp, 110 for pop3, etc. But I don't see how local_port would be mapped to an integer between 0 and 9. I browsed the Netbasic web site but declined to download. Maybe I should have downloaded Getnews and Postnews just to see if they were updated. I don't see anything useful with Netbasic, considering chat or miniterm dials but epppd fails to make the IP connection, while LSPPP connects OK but can't negotiate Bluegrass Net's name servers properly, consistent 30-second delay accessing hosts by name for 16-bit DOS programs, no go for 32-bit DPMI, no problem accessing hosts by IP address where I know it. So I was looking for a way around. programs, no go for 32-
