home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.misc
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!lanl!godzilla.jdola.lanl.gov!gavin.adams
- From: Gavin Adams <gavin.adams@lso.mts.dec.com>
- Subject: Re: Generic NDIS driver installations for Windows for Workgroups
- Message-ID: <1993Jan12.184441.16151@newshost.lanl.gov>
- X-Xxmessage-Id: <A7785E4EA301BA16@godzilla.jdola.lanl.gov>
- X-Xxdate: Tue, 12 Jan 93 11:38:54 GMT
- Sender: news@newshost.lanl.gov
- Organization: Digital Equipment Corporation
- X-Useragent: Nuntius v1.1.1d13
- References: <1993Jan11.231520.18707@newssrv.edvz.univie.ac.at>
- Date: Tue, 12 Jan 1993 18:44:41 GMT
- Lines: 19
-
- In article <1993Jan11.231520.18707@newssrv.edvz.univie.ac.at> Erich
- Neuwirth, A4422DAB@vm.univie.ac.at writes:
- >i habve a relatively exotic Ethernet card, a Mylex LNE390.
- >I also have an NDIS driver. is there anywhere documented
- >how to indtrall a card with an NDIS driver in Windows for Workgroups
- >when one does not have the OEMSETUP.INF one needs for the
- >standard procedure?
-
- Look for a default PROTOCOL.INI file that came with the Mylex (if one did).
- What you need to do is add the section that describes the etherete card into
- WfWG PROTOCOL.INI file, and change the transport bindings to the one listed
- in the bracketed section of your cards description (see how WfWG does the
- Etherlink II setup).
-
- If it was anything like my installation (WfWG and 3COM's TCP/IP), you're in
- for a lot of fun. :(
-
- --- Gavin
- Visualize Whirled Peas!
-