jbvb@FTP.COM (James B. Van Bokkelen) (06/12/91)
    BUT... I have a client that is demanding a dual stack (IP and IPX) PC
    solution that is fully vendor provided/vendor supported....
    
At least Interlan, Hughes LAN Systems, Schneider & Koch, Gateway, Acer and
IMC Networks all have supported Packet Drivers and Netware which runs with
them (there are half a dozen more board vendors with supported packet drivers,
but I don't know if they have their own Netware drivers or rely on the BYU
stuff - ask them).  I wouldn't expect any of the vendors to support the use
of their own Netware with someone else's board, though.
    
3Com and Spry both have supported modules which allow Netware to run on NDIS
drivers (and NDIS is presumably as likely to be 'well supported' by the
average board vendor as ODI is).  We support the version of the DIS_PKT
adapter module that we ship with our commercial PC/TCP product (but we
don't support the version we released as freeware, or Joe Doupnik's improved
version).  TWG, Sun and B&W will presumably support their own products
running on an NDIS driver as well.  We're working on an ODI-to-Packet-Driver
converter module which we intend to support when sold with PC/TCP.  You
know about Novell's product on ODI.
James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901skl@wimsey.bc.ca (Samuel Lam) (06/15/91)
In article <9106121357.AA28590@ftp.com>, jbvb@ftp.com wrote: >> ... I have a client that is demanding a dual stack (IP and IPX) PC >> solution that is fully vendor provided/vendor supported.... >At least Interlan, Hughes LAN Systems, Schneider & Koch, Gateway, Acer and >IMC Networks all have supported Packet Drivers and Netware which runs with >them ... Western Digital also provides a pair of Netware/Packet drivers which can co-exist with each other and share the same Ethernet card concurrently. You just need to SHGEN your IPX with their Netware driver. When their Packet driver starts it will check to see if their Netware driver is already active, and if so it will use the Ethernet through it. Thus for the WD cards there should be no need for the BYU stuff. ...Sam -- <skl@wimsey.bc.ca>
DMM@UGA.CC.UGA.EDU (David Matthews-Morgan) (06/16/91)
Jim has tested the packet driver that comes with the newer WD cards (as
has Joe Doupnik of Kermit fame); both indicate that the Clarkson packet
drivers and BYU IPX work better.  I will review the issue with Jim.
         Davidmcdonald@aries.scs.uiuc.edu (Doug McDonald) (06/16/91)
In article <9106152148.AA07661@ucbvax.Berkeley.EDU> DMM@UGA.CC.UGA.EDU (David Matthews-Morgan) writes: >Jim has tested the packet driver that comes with the newer WD cards (as >has Joe Doupnik of Kermit fame); both indicate that the Clarkson packet >drivers and BYU IPX work better. I will review the issue with Jim. > > David I got a Western Digital EtherCard Plus Elite last week. The packet driver that comes with it crashes in Windows. The readme file for the driver that came with it says that sine this card uses a new chip, you HAVE to use the new driver. Yet the old driver seems to work fine and their own driver most certainly does invariably crash big time. You figure this out! And if you do, PLEASE POST. Doug McDonald