HDTenEightyP/NetNews huggingface dataset:
X-Pmrqc:      1
Priority: normal
X-Mailer:     Pegasus Mail v2.3 (R5).
Newsgroups: bit.listserv.novell
Date:         Mon, 25 Jan 1993 08:36:49 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Dan Hale <DAN@SAFETY.NWSCC.SEA06.NAVY.MIL>
Organization: Resource Protection Department
Subject:      CD ROM Listserv

Does anybody know if there is a CD-ROM mailing list? I have an
address but do not know if it is a mailing list or a newsfeed also I
need a internet address.  The address I have is cdromlan@idsu.bitnet.

Any information would be helpful.

Thanks




        Imagination is the one weapon in the war against reality.



                 +--------------------------------+
                 | Dan Hale                       |
                 | Senior Systems Eng.            |
                 | Computer Data Systems Inc.     |
                 | Resource Protection Department |
                 | Naval Surface Warfare Center   |
                 | Crane IN 47522                 |
                 | (812) 854-3207 or 3776         |
                 | Dan@safety.nwscc.sea06.navy.mil|
                 +--------------------------------+
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Encoding: 240 Text
Newsgroups: bit.listserv.novell
Date:         Thu, 21 Jan 1993 18:16:41 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Don Kazem <dkazem@NAS.EDU>
Subject:      Re: A problem with an IBM Token-Ring ISA board

We had some problems with those cards in Valuepoints as well. The problem
was with the ODI driver (TOKENBM.COM). Make sure that you have the latest
version. The one we use here is 48871 bytes and is dated 12-9-92.

Don
dkazem@nas.edu
Newsgroups: bit.listserv.novell
From: donp@novell.com (don provan)
Subject: Re: IP Tunnel loses connection
Organization: Novell, Inc., San Jose, California
Date: Fri, 22 Jan 1993 01:52:14 GMT

In article <106068@netnews.upenn.edu> tony@scotty.dccs.upenn.edu (Anthony Olejnik) writes:
>Q: What is this watchdog packet?

If a NetWare server hasn't heard from a particular client for a while,
it sends a watchdog packet to see if the client is still maintaining
the connection.  This allows the server to cleanup if a client goes
away without telling the server.

>Q: Is it encapsulated in IP (when using IP tunnel)?

All IPX traffic, including watchdog packets, are encapsulated in IP
when using the IP tunnel.

>Q: Does this packet have any effect on perfomance (of an IP tunnel)?

Not generally.  Watchdog packets are sent infrequently, so they would not
use a significant fraction of a tunnel's bandwidth or the tunnel end
point's CPU.  They are also only sent when the connection is idle, so
there typically wouldn't be anything else happening on the tunnel anyway.

>On the same IP subnet (using IP Tunneling anyway between a WS and Server),
>I see about a 40% loss in performane.

From what i'm told, most of this is caused by the WS architecture.  If
you can set up the tunnel between two servers without adding any extra
hops, you should see a smaller loss.

>However, on different IP subnets (using IP Tunneling between a WS and Server),
>I see > 40% (about 60%)/
>Q: Is this normal?
>Q: Why would the performance be less going thru a (Cisco) IP router?

I suspect you're comparing the performance in this case with the
performance of a direct connection.  Adding a hop through a router,
regardless of whether or not you're tunnelling, is going to increase
the round trip time, and NetWare performance is very sensitive to the
round trip time.  I think if you were to compare this configuration
with a pure IPX connection that went through that same router, you'd
see about the same 40% degradation.  (Actually, there's reason to
believe it would be a bit less than 40% since the tunnel overhead
would be a smaller percentage of the overall round trip time.)

						don provan
						donp@novell.com
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Fri, 22 Jan 1993 08:20:37 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         dersch@SHRSYS.HSLC.ORG
Subject:      SIDEWIND.NLM and 100% Utilization of processor

I have loaded SIDEWIND.NLM on about 20 file servers. On one and one only, the CP
 U
utilization went to nearly 100% as soon as sidewind was loaded. This didn't
happen on any other servers.  Most of the servers are the same as this one
except that this one has more than 32 MB of memory.

Does anyone know of existing problems with sidewind.nlm? Are there patches?

As soon as I unload SIDEWIND.NLM the utilization drops back to the normal
7-20%.

THanks in advance,

Douglas Dersch
DERSCH@SHRSYS.HSLC.ORG
(302) 324-3517

Medical Center of Delaware
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=us-ascii
Newsgroups: bit.listserv.novell
Date:         Thu, 21 Jan 1993 15:18:32 -0800
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
Comments:     Warning -- original Sender: tag was tmoss@CARSON.U.WASHINGTON.EDU
From:         Christine Moss <tmoss@U.WASHINGTON.EDU>
Subject:      Re: A: Command.com not found ** HELP

Make sure command.com is in a directory in the user's search path for
those applications that do not use comspec
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Tue, 26 Jan 1993 14:29:36 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         JAY SISSOM <JSISSOM@INDYCMS.BITNET>
Subject:      Re: Version 3.26 Shells
              26 Jan 1993 14:29:30 GMT from <Rod.Wilson@BARCLAYS .CO.UK>

I have had lots of problems with SEND locking up workstations.  I haven't
found any connection, so I haven't mentioned it.  The workstations that
lock up are running MS-DOS 5.0, have an ODI stack with ODIPKT and are
running NETX 3.26.

These problems didn't happen with NET5 or NET3.

Sometimes, you will receive one send message, then a second one will
appear without clearing the first one.  After that, the workstation is
locked up.

Jay Sissom
Indiana University Department of Medicine
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Fri, 22 Jan 1993 07:53:47 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Peter Ballantyne <peterb@SVENGALI.US.DG.COM>
Subject: Re: Adding memory to server

stephen@bokonon.UUCP writes:
>
>    Actually, this is backwards.  On an EISA machine, unless told otherwise
> with an
>
> SET AUTO REGISTER MEMORY ABOVE 16 MEGABYTES = OFF
>
> statement in STARTUP.NCF, NetWare _will_ use all available memory.  This
> parameter defaults to ON on EISA machines, so unless you indicate
> otherwise, all memory will be used, with potentially disastrous
                                           ^^^^^^^^^^^^^^^^^^^^^^
> consequences depending on what cards you have plugged into your
  ^^^^^^^^^^^^

> server.
>


Steve - could you explain what "disastrous consequences" you're
referring to?  I'm just about to transfer our server to an EISA 486
w/64MB RAM and would prefer to make the experience as pleasant as
possible!

TIA

Peter
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: NOVELL@SUVM.BITNET
X-VMS-To: IN%"NOVELL@SUVM.BITNET"
X-VMS-Cc: JRD
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.novell
Date:         Tue, 26 Jan 1993 21:24:28 -0600
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Joe Doupnik <JRD@USU.BITNET>
Subject: Re: ODI ?

>
>In article <930126132107.3da0185d@STORK.IUPUI.EDU> you write:
>>        Is ODI some kind of cruel joke perpatrated by Novell on unspecting
>>LAN administrators? We recentlly obtained PathWorks which requires the frame
>>type of "Ethernet_II". In addition we are running all our Novell server using
>>frame type "Ethernet_802.3". The VAST majority (nearly 100%) of our network
>>cards are NE1000 and NE2000 cards.
>
>I believe (and I could be did wrong since I haven't worked with it much) that
>ODI only supports one frame type on a workstation.  But the file server can
>support multiple workstations.  So set your workstation to the Ethernet_II
>frame type and add that frame type on your file servers.  I hope that helps.
>
>Later,
>--
>John Villalovos
>Certified Netware Engineer
>villalj@xanth.cs.orst.edu
>(503) 753-7883
------------
        Actually John, both client (workstation) and server can use multiple
frame kinds with ODI, by inherent design of the basics of ODI. A workstation
cannot bridge traffic whereas a NW server can. What the trouble was above was
loading multiple frames (ok) but not pointing IPX at the desired virtual board
(one per frame kind) so IPX grabbed the first available. That is the whole
purpose of the BIND minor clause in NET.CFG: to target a specific virtual
board either by name (if one frame on it) or by v. board number (if many to
choose from). BIND is needed only in cases of choices.
        Joe D.
Newsgroups: bit.listserv.novell
From: jones@plains.NoDak.edu (Scott Jones (Dr. Jones))
Subject: A: Command.com not found ** HELP
Date: Wed, 20 Jan 1993 21:28:00 GMT
Distribution: na
Organization: North Dakota Higher Education Computing Network

Hello Folks,

We have a Novell 3.11 Network running DOS 5.  The nodes boot from the
file server and have no drives in them at all.  

The problem is that the nodes will radomly get a request for command.com
to be inserted into drive a:  which doesnt exist.  :-(

We have COMSPEC installed to redirect the command.com search to the Y:
directory of the Network, the same place the nodes find DOS 5..
But the problem still exists. 

Any help would be greatly appreciated, but please respond via E-Mail..

Thanks..

Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Via:        UK.AC.SOTON.ECS; 27 JAN 93 16:23:18 GMT
Via:        diana.ecs.soton.ac.uk; Wed, 27 Jan 93 16:17:16 GMT
Newsgroups: bit.listserv.novell
Date:         Wed, 27 Jan 1993 16:22:44 GMT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Harald Geiger <H.G.Geiger@ECS.SOTON.AC.UK>
Subject:      Re: Print Screen

In bit.listserv.novell you write:

>How do I configure my workstations to print screen dumps to network
>printers properly? At the moment it seems to work sometimes, then wont
>print for a while, then maybe lump screen dumps into one job etc. I simply
>want a shift-printscreen to send that ONE page to the printer as a network
>job. TIA

Try capture lpt1 q=printer_queue nb ti=2.

As long as you ensure that you don't have a second PrtSc within 2
seconds from termination of the first job, you should get one printout per
PrtSc.
You might want to change the timout (ti) a bit.


Harald
hgg@ecs.soton.ac.uk
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Priority: normal
X-Mailer:     Pegasus Mail v2.3 (R5).
Newsgroups: bit.listserv.novell
Date:         Mon, 25 Jan 1993 12:04:01 +1200
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Kevin Sartorelli <KEVIN@CSC.CIT.AC.NZ>
Organization: C.I.T.,  New Zealand
Subject:      Re: CAPTURE TI= option

> >file, many programs don't close the printer.  With the printer still open,
> >novell cannot know a printout is complete.  The timeout switch gives novell
> >an alternate method of determining the completeness of a printout.  Most
> >programs will send a stream of info to the printer in a fairly constant rate,
> >with few interruptions.  With a timeout set to a value greater than the
> >maximum interruption, novell will collect all the parts of a printout.  When
> >the time passes the timeout point, novell assumes that a printout is done.
> >In this manner, It can send a printout to the printer without waiting for the
> >program to exit.

> thanks for the above explanation.
> That still leaves the question: How does one "close the printer"? Is
> there a special command you have to send or a control character you
> have to include at the end of your file?

The printer (job) is closed when the timeout is reached.  If your timeout
is set for, say, 10 seconds after the queue gets no input from your
machine it assumes you have finished and closes the job.

Kevin

----------------------------------------------------------------------
Kevin Sartorelli      Central Institute of Technology, Computer Centre
kevin@cit.ac.nz       New Zealand     Ph: 4 527 6398   Fax: 4 527 6376
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Via:      UK.AC.YORK.VAXA; 22 JAN 93 17:06:54 GMT
Newsgroups: bit.listserv.novell
Date:         Fri, 22 Jan 1993 15:31:00 GMT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Chris Elliott <CJE2@VAXA.YORK.AC.UK>
Subject:      remote boot frames

I can remote boot using this autoexec.bat file

echo. set up network

ywd8003e -d -n  0x61 10 0x300 0xcc00
byu_ipx
y_netx
f:login

but if I take out the -n parameter the remote boot fails after byu_ipx
whereas the disk version runs OK as the file server has both 802.3 and
ethernet_ii frames

Any suggestions gratefully received
Chris
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
From: imhw400@indyvax.iupui.edu
Newsgroups: bit.listserv.novell
Subject: Re: No Math - 486SX or 486DX
Date: 25 Jan 93 15:13:35 -0500

In article <107978@bu.edu>, anneklin@acs.bu.edu (Patricia Anne) writes:
> In article <1993Jan22.095501.261@indyvax.iupui.edu> imhw400@indyvax.iupui.edu writes:
>>In article <00966EF8.BDAA5580.29636@lewis.umt.edu>, lw_flw@LEWIS.UMT.EDU writes:
>>In a protected-mode application with little or no floating-point (such as a
>>NetWare server) I'd take a 386DX over a 486SX of equal clock speed.  The 486
>>does require fewer clocks to execute some instructions, but the DX requires
>>half as many bus cycles to get data on/off the chip.
> 
> BOGUS!
> 
> This isn't oversimplification, it's just plain wrong--the SX in 486SX
> indicates nothing about the address bus width, as it does in the case
> of the 386SX--it just tells you that the chip doesn't have a FP unit.

Thank you.  I rechecked, and my 1990 _i486 Microprocessor Programmer's
Reference Manual_ makes no mention of the 486SX, so I really didn't have any
idea how it differs from the DX.  I stand corrected.  (Now I know why Intel
bothered to make a 486SX chip:  it's not at all what I thought it was.)

Do you happen to know the name of the twit who decided to reuse the SX/DX
nomenclature for something so radically different from what it appears to mean
for 386 chips?

> In lab tests, a 486SX/25 has beaten every 386 out, including the 40Mhz
> AMD 386 clone.  And in my expoerience, it's true in real-world
> situations as well.

Thank you.
-- 
Mark H. Wood, Lead Analyst/Programmer    +1 317 274 0749   [@disclaimer@]
Internet:  IMHW400@INDYVAX.IUPUI.EDU     BITNET:  IMHW400@INDYVAX
Celebrate freedom:  read a banned newsgroup.
From: MAILBOX@ZEUS.ICE.NL (Zeus Mailbox)
Newsgroups: bit.listserv.novell
Subject: report about charon 4.0 on ODI
Date: 27 Jan 93 12:41:36 GMT
Reply-To: mailbox@zeus.ice.nl
Organization: ETB-Lubbers Nederland B.V.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer:     Pegasus Mail v2.3 (R3).

Dear fellow pmail/charon users...

Iam just starting a test on charon 4.0 running on ODI.
I have the following config:

xt with 640Kb/30Mb hdd
dos 3.30
WD8003EP 8bit nic
lsl 1.2
smcplus 2.00
ipxodi 1.2
netx 32.6

I have hardware=odi in my config.tel and everything seems to work fine.
However brad (clements) stated in the config.tel file that odi doesn't seem
to be stable with VROOM, borlands memory swapper.
Is there anyone out there who has charon 4.0 running on ODI instead of
running it on a packet-driver (sorry russ) ??
My previous setup was ODI with ODIPKT, which runs fine.
I will try the setup for a few days and report back to you.

Greetings...

Henno.


mailbox@zeus.ice.nl                                 Zeus mailbox
----------------------------------------------------------------
ETB Lubbers Nederland B.V.                          Henno Keers
Korenpad 1                                          CNE
6534 AS Nijmegen                                    Henno@zeus.ice.nl
Tel. +31 80 540111                                  The Netherlands
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Via: uk.ac.manchester.computer-science; Thu, 21 Jan 1993 18:32:39 +0000
X-Disclaimer: Any opinions expressed herein do not necessarily reflect
X-Disclaimer: those of Barclays Bank Plc.
Priority: normal
X-Mailer: Pegasus Mail v2.3 (R4).
Newsgroups: bit.listserv.novell
Date:         Thu, 21 Jan 1993 18:28:09 GMT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Rod Wilson <Rod.Wilson@BARCLAYS.CO.UK>
Subject:      IP Tunnelling

Hi there,

Whenever this subject seems to appear on the list, a lot of people
mention that they had problems running rconsole over an IP Tunnel.

Is this the case for everyone using it? i.e. Is there anyone who has
rconsole working over an IP Tunnel or is it a known problem?

The reason I ask this, is that I am looking at implementing IP
Tunnelling, and if rconsole will not work it is a showstopper,
and means that we needn't waste any time looking at it.

Many thanks.


Rod.Wilson@barclays.co.uk      "My opinions are my own
Barclays Bank Plc               and do not reflect those
England, U.K.                   of my company".
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Priority: normal
X-Mailer:     Pegasus Mail v2.3 (R5).
Newsgroups: bit.listserv.novell
Date:         Wed, 27 Jan 1993 13:46:58 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Jeff Macdonald <JEFF@SAND.LIUNET.EDU>
Organization: Long Island University
Subject:      Netware for MAC 2.2 and Pegasus with Netware 3.11

Hi,
I can't seem to see the address books from the pmail for mac side,
but I can see them from the PC version of pmail. I got it to work on
a 2.15c server some many moon ago but forgot how I did it. Any
suggestions?

I'm using Netware for Mac 2.2 on a 3.11 server. The program runs
fine.. I just can't see the address books...

Jeff Macdonald
Assistant Network Engineer
Southampton Campus
Long Island University
Southampton, NY 11968
(516)283-4000 ext 352

======================================================================
jeff@sand.liunet.edu                Novell File Server (perferred)
======================================================================
jdonald@liuvax.bitnet               Bitnet Site
jdonald@vax86.liunet.edu            Internet Site
jdonald@ibm520.liunet.edu           Internet Site #2
======================================================================

    Dictatorship (n): a form of government under which everything
    which is not prohibited is compulsory.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Mailer: Elm [revision: 66.36.1.1]
Newsgroups: bit.listserv.novell
Date:         Wed, 27 Jan 1993 19:15:43 MET
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Partner Support Group <psg@HPUAMSC.NETH.HP.COM>
Subject:      Re: Network Printers
              25, 93 3:14 pm

>
>    We are interested in purchasing a fast laser printer
>    for our Department.  I was wondering if people had comments
>    (performance, price, support) on the HP LaserJet IV, and
>    the new Compaq Pagemarq 15 and 20 printers.
>
>    Also, does HP plan a high speed version of the LJ IV?
>
>    Please reply to Stephen_Hahn@brown.edu.  If asked, I'll summarize
>    the received responses and post to the list.
>
>    Thanks,
>    Stephen Hahn
>    Dept. of Physics, Brown University
>

Stephen,

Yes, HP will come with a high speed version of the LJ IV.
I'm not in the position to tell you when the release date will be, but I can
assure you that this will be very soon. It will be of the same class as the
HP LaserJet IIIsi.

Jaap van der Hak
Hewlett-Packard Nederland B.V.
Customer Response Center.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Original_To:  JNET%"novell@suvm"
Original_cc:  BSMITH
Newsgroups: bit.listserv.novell
Date:         Wed, 27 Jan 1993 14:25:00 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "Bob Smith,
              Kent State - East Liverpool Campus" <BSMITH@KENTELIV.BITNET>
Subject:      RX BUFFER OVERFLOW ???

Hello all,

I've been poking around the ol' LAN with LANSight's Network Diagnostics.
While monitoring connections, I've noticed that we are getting a LOT of
RX buffer overflows, defined in the LANSight manual as "The number of times
the driver received a packet larger than the buffer allocated for it."  This
number seems to increase at a rate of about 1 every one or two seconds.

While I'm not all that familiar with what is actually happening, it seems
that this must cause a ton of resends, threrby degrading performance.
Can anyone tell me if that's right?

Also, is it possible to increase the size of the receive buffers to eliminate
or reduce the problem?

Any help appreciated.

Thanks,

Bob Snith
KSU-EL
jnet%"bsmith@kenteliv"
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: NOVELL@SUVM.BITNET
X-VMS-To: IN%"NOVELL@SUVM.BITNET"
X-VMS-Cc: JRD
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.novell
Date:         Wed, 27 Jan 1993 16:25:43 -0600
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Joe Doupnik <JRD@USU.BITNET>
Subject:      Re: More on ODI

        <leadin omitted>
>        I would like to configure my WORKSTATION card to communicate with my
>reqular servers running IPX/Ethernet_802.3 frame type AND communicate with the
>VAX-Novell server utilizeing IPX/Ethernet_II frame type - with out a going thru
>a router. Using a protocol stacker I beleived would also allow me to "stack" th
   e
>frame types. I beleive now that ODI may not allow this.
>        Should I be tossing ODI out the window and looking at NDIS?; perhaps
>resigning my self to set up a router?; or is it I just dont know enough
>about Novell and Pathworks yet?
>        One last item - What prompted Digital to use Ethernet_II when it is
>fairly obvious that everyone else is using Ethenet_802.3?
>
>        Paul Anderson                           paul@vax1.iupui.edu
>        Wishard Memorial Hospital
>        Indiana University Medical Center
---------------
        "Everyone else" is NOT using Ethernet_802.3. The name is deceiving,
and it really means Pre-IEEE 802.3 committee framing, known as Old Novell
or "Raw Ethernet" (polite) frames. The world works on Ethernet_II, aka
Digital Intel Xerox DIX. The 802.3 committee did not do an acceptable job
and the standard gathers dust (is dead, forget it). Novell's style arose
before then and does not agree with it. Novell provides it's non-standard
ancient frame only for backward compatibility purposes, and we all strongly
recommend moving away from that. Ethernet_II and Ethernet 802.2 plus variations
such as SNAP are the modern Ethernet frames, with Ethernet_II vastly
dominating the scenery.
        I suggest biting the bullet, finding a magic day, and convert all to
Ethernet_II. It can be done, as we have done it here, and down time was 1 hr.
        Please forget about kludges attempting to run two protocols of the
same kind at the same time over the same board. You will get what you've paid
for, and less.
        Joe D.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU