home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.os2.advocacy:12123 comp.os.os2.apps:10080 comp.os.os2.misc:42096 comp.os.os2.networking:2689
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!usc!howland.reston.ans.net!spool.mu.edu!olivea!inews.Intel.COM!imutm1.de.intel.com!gold.sub.org!jonas.gold.sub.org!rommel
- From: rommel@jonas.gold.sub.org (Kai Uwe Rommel)
- Newsgroups: comp.os.os2.advocacy,comp.os.os2.apps,comp.os.os2.misc,comp.os.os2.networking
- Subject: Re: ibm tcp/ip a ripoff?
- Message-ID: <726847072rommel.root@jonas.gold.sub.org>
- Date: 12 Jan 93 13:57:52 GMT
- References: <1iratf$aqq@agate.berkeley.edu> <C0pB29.6Lx@ccu.umanitoba.ca>
- Sender: root@jonas.gold.sub.org
- Organization: Private
- Lines: 44
-
- In article <C0pB29.6Lx@ccu.umanitoba.ca> umcarls9@ccu.umanitoba.ca (Charles Carlson) writes:
- >In <1iratf$aqq@agate.berkeley.edu> ucbked@athena (Earl H. Kinmonth) writes:
- >>c) few ethernet cards supported (compared to wattcp with clarkson
- >>packet drivers);
- >
- >That's why I stick with WD/SMC stuff, its ALWAYS supported. Perhaps you
- >should contact the manufacturer of the card for MAC and NDIS drivers for OS/2?
-
- That's plain wrong. There are *plenty* of NDIS drivers for all kind of
- cards for OS/2 LAN manager/server. All of them should work with
- TCP/IP. Now, only a few NDIS drivers come with TCP/IP. Check the disk
- you got with your network card and you will probably find NDIS drivers
- for OS/2 LAN manager/server. Plug that in (and fix protocol.ini
- accordingly) and it will most certainly work. I have used quite a
- number of cards now (to try them out) this way and all of them worked
- although not initially supported by TCP/IP from IBM.
-
- In my archives I have almost 2MB worth of NDIS drivers for network
- cards for OS/2. Take a look at ftp-os2.nmsu.edu or uunet (where MS has
- drivers for LAN manager for ftp) if your card did not come with one.
-
- >>i) hard to setup (xenix tcp/ip took me about three hours from
- >>openning the box to a reliable anonymous ftp service; wattcp took
- >>about an hour from loading to basic operation; with os2, i'm
- >>still at it weeks later).
- >
- >It took me about as long to get going as it did to install it and read the
- >online docs. I wasn't setting up for nameservers however. Which caused
- >another problem in that even if the /etc/resolv.conf file exists, it still
- >"hangs" looking for a nameserver.
-
- Same here, installation was rather easy, I did never install a TCP/IP
- product on a PC before, so I was a beginner here. The nameserver
- problem has disappeared, I do *not* have a /tcpip/etc/resolv file.
-
- Kai Uwe Rommel
-
- --
- /* Kai Uwe Rommel Muenchen, Germany *
- * rommel@jonas.gold.sub.org Phone +49 89 723 4101 *
- * rommel@informatik.tu-muenchen.de Fax +49 89 723 7889 */
-
- DOS ... is still a real mode only non-reentrant interrupt
- handler, and always will be. -Russell Williams
-