Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!ted@cgl.ucsf.edu@blia.UUCP
From: ted@cgl.ucsf.edu@blia.UUCP
Newsgroups: mod.computers.vax
Subject: Re: Ethernet promiscuious problem, was: (none)
Message-ID: <8702251738.AA09603@blia.BLI>
Date: Wed, 25-Feb-87 12:38:22 EST
Article-I.D.: blia.8702251738.AA09603
Posted: Wed Feb 25 12:38:22 1987
Date-Received: Fri, 27-Feb-87 21:39:16 EST
References: <8702250023.AA17038@ucbvax.Berkeley.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 24
Approved: info-vax@sri-kl.arpa
Summary: DEQNA driver doesn't like _PRM and _BFN together.


I have found that the DEQNA driver (which I see you are using) does not like
to have a buffer count (_BFN) specified for promiscuious mode (or maybe the
number of buffers must be small, I haven't checked). I had a program that
specified both which ran fine on a big VAX with a DEUNA but wouldn't run
on a MICRO-VAX until I removed the _BFN. This is not documented.

The reason the error pointed at the _PRM specification is that the conflicting
specification came first. To find out for sure what is conflicting, move the
_PRM specification to the front of the parameter list. The error will then point
to the other.

===============================================================================
            Ted Marshall
            Britton Lee, Inc.
p-mail:     14600 Winchester Blvd, Los Gatos, Ca 95030
voice:      (408)378-7000
uucp:       ...!ucbvax!mtxinu!blia!ted
ARPA:       mtxinu!blia!ted@Berkeley.EDU
disclaimer: These opinions are my own and may not reflect those of my employer;
            I leave them alone and they leave me alone.
fortune for today:
Put your Nose to the Grindstone!
		-- Amalgamated Plastic Surgeons and Toolmakers, Ltd.