TCP/IP stack for MS-DOS
Hermann Hemmersbach
Hello,
I think I need a little help!
To exchange data between 2 computers via UDP or TCP i have some questions:
Where can i find a TCP/IP stack for MS-DOS ?
Where can i find information (Books or Links) ?
Is somewhere an development kit or tool availible ?
I hope, anyone can give me some tips where I can find information or data.
H.Hemmersbach
Germany
10045...@compuserve.com
Greg Chapman
>Hello,
>I think I need a little help!
> To exchange data between 2 computers via UDP or TCP i have some questions:
>
>Where can i find a TCP/IP stack for MS-DOS ?
>Where can i find information (Books or Links) ?
>Is somewhere an development kit or tool availible ?
>
>I hope, anyone can give me some tips where I can find information or data.
The DOS network client, available free from ftp.microsoft.com in the
/bussys/clients/msclient directory, supports TCP. It does not include
an FTP client or any other basic TCP utilities. You'll have to come up
with another source for those tools.
Greg Chapman
MVP DTS
ClubWin
Mark Farnsworth
>>Where can i find a TCP/IP stack for MS-DOS ?
>>Where can i find information (Books or Links) ?
>>Is somewhere an development kit or tool availible ?
>>I hope, anyone can give me some tips where I can find information or
data.
Hermann, Attachmate still puts out a DOS product called PathWay which
comes in two versions: the full product with all sorts of utilites,
called Access, and just the stack, by the name of Runtime. I cannot
make any recommendations either for or against the product having had
but little experience with it. You can visit Attachmate's (formerly
Wollongong's) web site at http://www.attachmate.com.
My only experience with TCP/IP is with Windows sockets, so I can't
really point you toward a DOS-based SDK.
Mail me if you would like more information.
Mark Farnsworth
gcu...@fanniemae.com
J.C. Archambeau
Mark Farnsworth <gcu...@fanniemae.com> wrote:
>>>Where can i find a TCP/IP stack for MS-DOS ?
>>>Where can i find information (Books or Links) ?
>>>Is somewhere an development kit or tool availible ?
>
>>>I hope, anyone can give me some tips where I can find information or
> data.
>
> Hermann, Attachmate still puts out a DOS product called PathWay which
> comes in two versions: the full product with all sorts of utilites,
> called Access, and just the stack, by the name of Runtime. I cannot
> make any recommendations either for or against the product having had
> but little experience with it. You can visit Attachmate's (formerly
> Wollongong's) web site at http://www.attachmate.com.
We use Attachmate's Pathway for our Win 3.x workstations in our
WAN. Because our primary client application is still MS-DOS based
with the WinNT version coming anytime after late October, we have
to use a TCP/IP stack for MS-DOS. It works very well and if you have
Win 3.1, it will add winsock support to Win 3.1 if you're not using
WFW 3.11.
We are expecting our upgrade to the latest version which supports
DHCP anytime now. However, because of the UPS strike, it has
been slow getting here.
I have gotten the impression from the sales rep that there probably
won't be any Pathway DOS/Win 3.x versions past 3.21. If you want
a commercial product, I would entertain that before it gets
discontinued. Unlikely, but the possibility is still there.
--
/*
** n-...@worldnet.att.net
*/
Werner Ernst
As to article <5to15l$f...@mtinsc03.worldnet.att.net>,
n-...@worldnet.att.net by J.C. Archambeau:
>>>>Where can i find a TCP/IP stack for MS-DOS ?
Besides PathWay there are
BWNFS by Beame & Whiteside
PC/TCP FTP Corporation.
Few years ago prices for this stacks were about $400 ...
A less expensive way is Novell's Netware Client Kit for DOS and
MS-Windows. Look for the file VLMKT6.EXE (it is part 6 of the
complete kit). Some missing files will be found in the Klos archive
PPPShare or Caldera OpenDOS.
Not really a stack but a possibility are versions of NOS family
(JNOS, TNOS...).
>>>>Is somewhere an development kit or tool availible ?
PC/TCP Software Development Kit by FTP Software, Inc. Perhaps there
are others. You could also try EMX.
>>>>Where can i find information (Books or Links) ?
There are different docs and faqs on the net but I dont remember
the exact file names (pcnfs.faq?).
Greetings from Munich,
Werner Ernst
Mike Durkin
In article <01bcb2e2$aa2d9bc0$4d01015d@mhenrique> "Henrique Ribeiro Filho" <Hen...@SoftwareExpress.com> writes:
>I need to program in TCP/IP for DOS too. The library DOS_SOCK.LIB is at
>"Microsoft TCP/IP Sockets Development Kit Version 1.0" but I don't know
>where can we buy this product (it isn't in MSDN).
>
>If someone know the answer, please mail me at Hen...@SoftwareExpress.com
It may a brief appearance one time on MSDN Level II in, I believe, July 1994,
but was considered unsupported-and-never-should-have-been-put-on-MSDN at
the time by the tcp/ip / os group people, so removed from the next release.
It was also available as a separate product for $195 at least a few months
before that, but I'd assume they've throughly wiped it out of the system by
now in their YouWillUseWinsock(tm) mode. Your best bet is probably to find
those old MSDN CDs.
Or you could use WatTCP.
Mike
--
mdu...@wiretap.spies.com Is this a crappy time or what? :-(
Jeff Patterson
On Fri, 29 Aug 1997, Mike wrote:
> Path: news.unb.ca!coranto.ucs.mun.ca!news1.bellglobal.com!bellglobal.com!not-for-mail
> From: Mike <NoS...@Today.Thanks>
> Newsgroups: microsoft.public.technet,comp.os.msdos.programmer,comp.protocols.tcp-ip,comp.protocols.tcp-ip.ibmpc,de.comm.protocols.tcp-ip,microsoft.public.win3x_wfw_dos
> Subject: Re: TCP/IP stack for MS-DOS
> Date: Fri, 29 Aug 1997 05:59:24 -0700
> Organization: UTS
> Lines: 23
> Message-ID: <3406C7...@Today.Thanks>
> References: <01bca0ff$6aec31a0$LocalHost@default> <33FDEE27...@fanniemae.com> <01bcb2e2$aa2d9bc0$4d01015d@mhenrique>
> NNTP-Posting-Host: 204.101.212.112
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> X-Mailer: Mozilla 2.02 (Win16; I)
> Xref: news.unb.ca microsoft.public.technet:2042 comp.os.msdos.programmer:59228 comp.protocols.tcp-ip:31173 comp.protocols.tcp-ip.ibmpc:20288 de.comm.protocols.tcp-ip:559 microsoft.public.win3x_wfw_dos:4271
> X-Cache: nntpcache 1.0.6.5 (see ftp://suburbia.net/pub/nntpcache)
>
> Henrique Ribeiro Filho wrote:
> >
> > I need to program in TCP/IP for DOS too. The library DOS_SOCK.LIB is at
> > "Microsoft TCP/IP Sockets Development Kit Version 1.0" but I don't know
> > where can we buy this product (it isn't in MSDN).
> >
> > If someone know the answer, please mail me at Hen...@SoftwareExpress.com
> >
> > Henrique Ribeiro Filho
> > (Brazil)
>
> If you can program in Pascal, you might look at Jonathan Ramsey's
> TCP/IP for DOS.
>
> http://www.csolve.net/~add/zips/internet.zip (471K)
>
> It is a full PPP, TCP, IP, UDP, ICMP, DNS Lookup, sockets, POP3,
> SMTP and FTP software package, written to the latest RFC's and
> with ongoing support.
Doesn't work without DPMI memory, nor with Turbo Pascal, nor with a
Packet Driver. Also, doesn't work on my ISP (doesn't seem to support
all the PPP specs). I don't recall seeing ICMP nor FTP implemented in it
either.
Do you know when he might have an update at the site?
--
Jeff Patterson Internet: aa...@fan.nb.ca
Author of jpIRC DOS IRC Client PGPKey: pgp-pub...@keys.pgp.net
| HomePage: http://www.geocities.com/SiliconValley/Vista/7104/ |
| PGP Info: 2048/A8A1DCD5 : E0 9E 9B EF C8 E4 68 3D B5 9C 72 4C EC 61 DD 7A |
Claudio Potenza
Vladimir Alexiev <vlad...@cs.ualberta.ca> wrote:
> Get WatTCP which is available with source and free.
... but the documentation is $40
however i will be more then happy to pay for it if it saves me time, if
the software works and more important, if it suits my need
i have a small DOS machine (just a couple of megs of ramdisk) where I
need to run a simple application that will use UDP (kind of TFTP).
My main concern (beside reliabilty) is small disk footprint.
what is the size of WatTCP?
Also I will need to use BOOTP for assigning the address to the computer.
Can it be done with WatTCP (I understand that the protocol stack is
linked with the application)?
thanks
Anthony Stanford
On Sat, 30 Aug 1997, Claudio Potenza wrote:
> Vladimir Alexiev <vlad...@cs.ualberta.ca> wrote:
> > Get WatTCP which is available with source and free.
> need to run a simple application that will use UDP (kind of TFTP).
> My main concern (beside reliabilty) is small disk footprint.
> what is the size of WatTCP?
>
> Also I will need to use BOOTP for assigning the address to the computer.
> Can it be done with WatTCP (I understand that the protocol stack is
> linked with the application)?
Before you try punching code under WatTCP, you should try running some WatTCP
applications written by other people. I downloaded the entire thing,
successfully compiled some samples, and found I couldn't run them. Then I
downloaded some precompiled clients, and found the same problem.
WatTCP does not handle dynamic IPs well. There's various solutions for this,
but it's rather pointless to write a program you can't run. Even if others can
run it, how will you debug it?
First get some precompiled clients based on WatTCP running on your system.
THEN think about using it to write your own clients.
ing. Gert-Jan de Jonge
mc4...@mclink.it (Claudio Potenza) wrote:
>Vladimir Alexiev <vlad...@cs.ualberta.ca> wrote:
>
>> Get WatTCP which is available with source and free.
>
>... but the documentation is $40
>
>however i will be more then happy to pay for it if it saves me time, if
>the software works and more important, if it suits my need
>
>i have a small DOS machine (just a couple of megs of ramdisk) where I
>need to run a simple application that will use UDP (kind of TFTP).
>My main concern (beside reliabilty) is small disk footprint.
>what is the size of WatTCP?
>
>Also I will need to use BOOTP for assigning the address to the computer.
>Can it be done with WatTCP (I understand that the protocol stack is
>linked with the application)?
>
>thanks
Yes, Wattcp supports bootp.
Claudio Potenza
I have seen that Trumpet Software makes TCP-IP software for DOS
(see at <http://www.trumpet.com/text/dossoft.htm>).
It is a (freeware?) TSR that gives the programmer an ABI through INT
calls.
Has anybody used this? as in the docs it is said that it is experimental
I would be interested in knowing its reliability.
dly...@cruzio.com
In <33FDEE27...@fanniemae.com>, Mark Farnsworth <gcu...@fanniemae.com> writes:
>>>Where can i find a TCP/IP stack for MS-DOS ?
>
>data.
Caldera is giving out something that they call webspydr, which seems to
be a version of the arachne dos tcp/browser thingie from Czechland.
I was looking for a caldera, or opendos newsgroup but there do not seem
to be any such. After my install of opendos and webspydr I ended up
without a startnet.bat in the net client directory, so I am looking for
someone who knows what is supposed to be in such a startnet file.
Anyone here know about that?
Jeff Patterson
Yeah, I use it, I think its kinda nice however I can't solve a problem
of my programs sort of "freezing" on occassion. All the samples (when
using NTCPDRV.EXE, not the TCPDRV.EXE) in TCP201.ZIP seem to work just
fine.
It doesn't do DNS lookups on its own (but I got my own Turbo Pascal 7
unit to do it), and it is difficult to intercept incoming ICMP messages.
Werner Ernst
In article <5udctd$8...@redtail.cruzio.com>, dly...@cruzio.com wrote:
> I was looking for a caldera, or opendos newsgroup but there do not seem
> to be any such.
There is a mailing list, write to majo...@caldera.com and enter in
the body
subscribe caldera-opendos <your@address>
Werner Ernst from Munich/Germany
Kevin Connolly
Jeff Patterson wrote:
>
> On Sun, 31 Aug 1997, Claudio Potenza wrote:
>
> > I have seen that Trumpet Software makes TCP-IP software for DOS
> > (see at <http://www.trumpet.com/text/dossoft.htm>).
> > It is a (freeware?) TSR that gives the programmer an ABI through INT
> > calls.
> > Has anybody used this? as in the docs it is said that it is experimental
> > I would be interested in knowing its reliability.
>
> Yeah, I use it, I think its kinda nice however I can't solve a problem
> of my programs sort of "freezing" on occassion. All the samples (when
> using NTCPDRV.EXE, not the TCPDRV.EXE) in TCP201.ZIP seem to work just
> fine.
>
> It doesn't do DNS lookups on its own (but I got my own Turbo Pascal 7
> unit to do it), and it is difficult to intercept incoming ICMP messages.
>
When I used NTCPDRV.EXE it froze when the first incoming ping request
arrived. Every time.
I then tried TCPDRV.EXE and that worked fine.
Does anyone know why that might be so? What new in NTCPDRV (besides
using less RAM)?
BTW it did DNS lookups just fine.
Kevin
--
<<<<<< remove the NO-SPAM from reply address >>>>>>
Jeff Patterson
On Tue, 2 Sep 1997, Kevin Connolly wrote:
> Jeff Patterson wrote:
> >
> > On Sun, 31 Aug 1997, Claudio Potenza wrote:
> >
> > > I have seen that Trumpet Software makes TCP-IP software for DOS
> > > (see at <http://www.trumpet.com/text/dossoft.htm>).
> > > It is a (freeware?) TSR that gives the programmer an ABI through INT
> > > calls.
> > > Has anybody used this? as in the docs it is said that it is experimental
> > > I would be interested in knowing its reliability.
> >
> > Yeah, I use it, I think its kinda nice however I can't solve a problem
> > of my programs sort of "freezing" on occassion. All the samples (when
> > using NTCPDRV.EXE, not the TCPDRV.EXE) in TCP201.ZIP seem to work just
> > fine.
> >
> > It doesn't do DNS lookups on its own (but I got my own Turbo Pascal 7
> > unit to do it), and it is difficult to intercept incoming ICMP messages.
>
>
> When I used NTCPDRV.EXE it froze when the first incoming ping request
> arrived. Every time.
Hmm, never had that happen to me. I have had people try and ICMP ping me
while I was running jpIRC, and they said that they got back an ICMP
packet correctly. I never knew it would reply to ICMP until that test.
> I then tried TCPDRV.EXE and that worked fine.
> Does anyone know why that might be so? What new in NTCPDRV (besides
> using less RAM)?
> BTW it did DNS lookups just fine.
NTCPDRV uses different structures as well as other undocumented stuff. I
think its quicker plus much much more reliable. Are you using an Class 1
or Class 6 packet driver?
I have tried using both and have had it work with both. I just can't
get my programs to work good like Trumpet's example programs. My
programs don't seem to like other programs running at the same time (that
could be a flaw with how I have it written), but it still locks up on
occassion (NTCPDRV doesn't remove the CriticalFlag setting).
Vladimir Alexiev
> i have a small DOS machine (just a couple of megs of ramdisk) where I
> need to run a simple application that will use UDP (kind of TFTP).
I ran successfully a wattcp-based talk client on a XT (with 1M ramdisk, but
talk doesn't use it).
> My main concern (beside reliabilty) is small disk footprint.
> what is the size of WatTCP?
The talk client (including the tcp stack) is 40-50k.
> Also I will need to use BOOTP for assigning the address to the computer.
> Can it be done with WatTCP
Yep.
Anthony Stanford <leg...@netins.net> wrote:
> Before you try punching code under WatTCP, you should try running some WatTCP
> applications written by other people.
A good idea, preferably something similar to your app.
> I downloaded the entire thing, successfully compiled some samples, and found
> I couldn't run them. Then I downloaded some precompiled clients, and found
> the same problem.
Did you try to diagnose the problem? There ARE well-runnning wattcp apps
out there (kermit's telnet, talk, etc).
> WatTCP does not handle dynamic IPs well.
What exactly do you mean? I ran the talk client quite nicely over a ppp link
using epppd (from dosppp05.zip), with dynamic IP and hostname and using bootp.
One well-known problem with wattcp is that if you tell it your doman list is
"foo.com", then it'll ask DNS to complete even full names (eg for "bar.com" it
will try "bar.com.foo.com"), and it takes time until these attempts fail...
> First get some precompiled clients based on WatTCP running on your system.
> THEN think about using it to write your own clients.
Right. I could try to help. I had some routing problems with ppp (had to
request proxy_arp on the remote host), but they were resolved successfully.
Geoffrey Levand
"Henrique Ribeiro Filho" <Hen...@SoftwareExpress.com>:
>I need to program in TCP/IP for DOS too. The library DOS_SOCK.LIB is at
>"Microsoft TCP/IP Sockets Development Kit Version 1.0" but I don't know
>where can we buy this product (it isn't in MSDN).
>
>If someone know the answer, please mail me at Hen...@SoftwareExpress.com
>
I think it might be available from HP.
Jeff Patterson
On Wed, 3 Sep 1997, Kevin Connolly wrote:
> Jeff Patterson wrote:
> >
> Are you using an Class 1
> > or Class 6 packet driver?
>
> (re: On my PC NTCPDRV hangs on receiving a ping...)
>
> Class 1 over an Ethernet LAN. The problem is that our network monitoring
> sw does regular pings to see if everyone is still alive.
> It's not a big issue for me as I mostly use WATTCP for DOS work but
> I do intend to experiment some more as I like the idea of a TSR using
> INTs as an ABI for a TCP/IP stack.
> thanks for your reply.
I don't see how a ping could cause NTCPDRV to hang, Do you know how
large the ping packet is? Just a simple 4 byte one or is it larger/smaller?
I know several people using NTCPDRV and have no problems with it. I do
know however that if ICMP packets are intercepted by openning IP with
NTCPDRV that the buffer can fillup completely and that communcation would
cease until the packets are removed. I haven't had any other ping problems.
Kurt Wall
Werner Ernst <bm17...@muenchen.org> wrote in article
<wjxC0cvW...@muenchen.org>...
and in the body
write
subscribe opendos <name@address>.
Kurt
ashod
I have a slip/ppp/ip stack for dos, which is interface
independant. i.e
int EncodeIp
(_iphdr*IPHDR,unsigned char far*buffer);
int DecodeIp
(unsigned char far*buffer,_iphdr*IPHDR);
int EncodeSlip
(unsigned char far*buffer,int len,unsigned char far*slipbuf,int
*outlen);
etc///
Mike
Hi Ashod!
DOS TCP/IP is hard to find, and people are always looking for it.
Would you be interested in making it available to others - I seem to be
collecting DOS TCP/IP software, and I wouldn't mind adding yours to my
site also.
Best Regards,
Mike
Hosting Jonathan Ramsey's TCP/IP with Pascal source:
http://www.csolve.net/~add/zips/tcp.htm
Rob Kramer
Hi Mike,
: DOS TCP/IP is hard to find, and people are always looking for it.
: Would you be interested in making it available to others - I seem to be
: collecting DOS TCP/IP software, and I wouldn't mind adding yours to my
: site also.
I've been looking for a non-commercial TCP lib for ages now, and have quite
a collection of links now, but none really what I'm looking for. Is this of
interest to you, for your site? What is your site anyway?
Eize Slange
For the C-programmers here:
Waterloo TCP/IP C-library is a fully functional implementation.
All sourcecode is also included and it is mostly bugfree.
I've made a lot of server and client applications with it.
It has high-level functions to the user alike the UNIX
TCP/IP socket implementation.
Probably the latest version: WAT9609.ZIP
Where? Don't know at the moment, but most ftp-sites have it.
Search-engine search key: WATTCP
CU
Mike
For the Pascal programmers here:
Jonathan Ramsey's Pascal TCP/IP for DOS is written to the latest RFC's,
and a small discussion thread on minor bugs can be found on
comp.lang.pascal.borland.
Best Regards,
Mike
CEO, Analog & Digital Design
Automated Production Test
http://www.csolve.net/~add/home.htm
Hosting Jonathan Ramsey's Pascal TCP/IP for DOS:
http://www.csolve.net/~add/zips/tcp.htm
Ashod
Eize Slange <e.sl...@pbc.be.philips.com> wrote in article
<01bcc1de$4be17ae0$fd29...@116151p.bcs.cs.philips.com>...
>
> For the C-programmers here:
>
> Waterloo TCP/IP C-library is a fully functional implementation.
> All sourcecode is also included and it is mostly bugfree.
> I've made a lot of server and client applications with it.
> It has high-level functions to the user alike the UNIX
> TCP/IP socket implementation.
>
> Probably the latest version: WAT9609.ZIP
> Where? Don't know at the moment, but most ftp-sites have it.
> Search-engine search key: WATTCP
>
> CU
>
>
Agreed WATTCP is great, but it has a somewhat steep learning
curve ( even for a good coder ) , plus its buffering architecture
combined with its deep memory referencing, buffer shuffling
etc etc ( plus that its coded in portable C), dont make
it ideal for high speed games.
My stack consists of 4 internet command send,get,status,purge
which can be used on its own for low-level protocols,or
implementing your own TCP layer ( there is no restrictions ),
the learning curve is about 30 minutes, and your ready to
make software. Im going to release it soon...
Ashod
Len
In article <34197C...@ozemail.com.au> ashod <as...@ozemail.com.au> writes:
>From: ashod <as...@ozemail.com.au>
>Subject: Re: TCP/IP stack for MS-DOS
So where do we find it?
Michael Bernardi
Has anyone created a FAQ or Web page listing all these MSDOS stacks
recently mentioned?
Mike
--
A Webified version of the MS-DOS Applications for Internet Use FAQ can be
found at <URL:http://www.dendarii.demon.co.uk/FAQs/dos-apps.html>