Subject: RE: Network Interface Cards
To: 'Steven M. Bellovin' <smb@research.att.com>
From: David Woyciesjes <DAW@yalepress3.unipress.yale.edu>
List: port-i386
Date: 09/29/2000 14:28:57
	That's news to me. I personally have never ran into that, but
wierder things do happen... Did that problem happen to you? Did you try
booting to only DOS and using the 3Com 3c5x9.exe config program?

---   David A Woyciesjes
---   C & IS Support Specialist
---   Yale University Press
---   mailto:david.woyciesjes@yale.edu
---   (203) 432-0953
---   ICQ # - 905818

> -----Original Message-----
> From:	Steven M. Bellovin [SMTP:smb@research.att.com]
> Sent:	Friday, September 29, 2000 2:13 PM
> To:	David Woyciesjes
> Cc:	'dribbling@thekeyboard.com'; port-i386@netbsd.org
> Subject:	Re: Network Interface Cards 
> 
> In message
> <9011A52E011ED311B4280004AC1BA6156D519E@yalepress3.unipress.yale.edu
> >, David Woyciesjes writes:
> >Here's my $0.02 ---
> >ISA - If you can find it, get your hands on a 3Com 3C509B, download the
> >config disks, and set all the parameters by hand. Do not use Plug And
> Pray
> >on those cards...
> >PCI - Any other 3Com card, and again, get the config disks.
> >PCMCIA - 3Com 3C589
> >
> >Never had a problem with any 3Com card. Unless, of course, I left it in
> >PnPray mode...
> 
> One word of warning...  There is (or at least was; I haven't checked 
> lately) a problem with the 3c905B (maybe all models) and some BIOSes if 
> you boot without power-cycling after you've been running Mr. Bill's 
> operating system.  It leaves the card in a funky state so that NetBSD 
> can't deal with it.
> 
> 		--Steve Bellovin
>