HDTenEightyP/NetNews huggingface dataset:
From: hchin@fraser.sfu.ca (Hong Chin)
Newsgroups: comp.sys.novell
Subject: Looking for PCNT12.ZIP from NovLib #15
Date: 28 Jul 92 22:49:05 GMT
Organization: Simon Fraser University, Burnaby, B.C., Canada


Hello netter,
    I am looking for a file in Novell Library (Nov Lib) called PCNT12.ZIP. 
I have try a few FTP sites and all I get is novlib #1-#11. Where can I ftp 
this file? 
    This file/program is a print job page counter for postscript and HPGL
printer. Thanks in advance.

Fred Chin    				chin@cs.sfu.ca
					hchin@SFUVAX.BITNET
Newsgroups: comp.sys.novell
From: rogers@eagle (Bill Rogers)
Subject: Help? Fatal dir error on vol:xxx
X-Newsreader: Tin 1.1 PL4
Organization: Sangamon State University
Date: Wed, 29 Jul 1992 21:17:26 GMT

What has been a reliable 2.15c SFT in the past is now spuriously getting this
"fatal dir error" on several diferent volumes. TFM indicates it could be 
anything on God's green earth causing it. Does anyone have any experience
in this problem. Here is the general description:

 generic 386-25 w/ 9mb
 2 micropolis ESDI 330mb ( seem to run awful hot for a long time )
 UltraStor controller several years old
 3Com 505 NIC

the workstations are on 10Base-T hubs.
the server is on coax segments connecting the hubs

Does not seem to be load related, have transaction tracking off.

Directories could be somewhat large.

Thanks,
Bill

--
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<> Bill Rogers, Assistant Director for Academic Computing Services          <>
<>              Sangamon State University, HSB-115                          <>
<>              Springfield, Il 62794-9243     fax:217-786-7188             <>
<> Internet:rogers@eagle.sangamon.edu        voice:217-786-7352(Mon.->Thur.)<>
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
From: tom@incom.de (Thomas Staudte)
Newsgroups: comp.sys.novell
Subject: Re: Adaptec drivers (Was: Scsi Tape Backup Software for Novell v3.11)
Date: 21 Jul 92 21:15:02 GMT
Reply-To: tom@in.sub.org
Organization: Thomas Staudte EDV-Beratung, Germany

In article <1992Jul17.151650.19962@sjsumcs.sjsu.edu> rick@sjsumcs.sjsu.edu  
(Richard Warner) writes:
[previous post deleted]
> Adaptec sells the driver disks for ~$70.  Or you can futz with the
> BBS and get them for whatever time it takes and phone charges.  
> 
> +-----------------------+-------------------------------------+
> |   Richard M. Warner   |   Internet:  rick@sjsumcs.sjsu.edu  |
> |                       | CompuServe:  71121,2257             |
> +-----------------------+-------------------------------------+
> |  ** DISCLAIMER:  All opinions are strictly my own.  I work  |
> |                  hard enough at forming them!               |
> +-------------------------------------------------------------+

If I understand you correctly, you can download the drivers from their BBS  
? If that's correct, then they would be somewhat freeware and I could just  
copy them from a friend ?

I mean this questions seriously, as this would make it easier to install  
the drivers on existing customer's controllers.

Does anybody know anything about the availability of adaptec drivers on  
the public adaptec BBS ?

Tom
---------------------------------------------------------------
            Thomas Staudte                Voice  +49 6074 43230
DP Consultant - Development - Training    Fax    +49 6074 43298
Roemerstrasse 2,  FRG-6075 Dietzenbach    NeXTMail tom@incom.de
---------------------------------------------------------------
I am an independent DP Consultant and in no way associated with
any company possibly mentioned above,  unless stated otherwise.
From: jrd@cc.usu.edu
Newsgroups: comp.sys.novell
Subject: Re: BOOTP
Date: 28 Jul 92 18:09:01 MDT
Organization: Utah State University

In article <n0613t@ofa123.fidonet.org>, Rick.Ellis@ofa123.fidonet.org writes:
> On <Jul 27 15:47> Edward Quillen writes:
> 
>  EQ> I have come across BOOTPFWD.NLM but I don't have any documentation on it.
>  EQ> Could anyone point me to where I can get documentation for bootp.
> 
> We tried loading it here...it wouldn't.  It couldn't find the symbol
> 'ARPMakeTempEntry'.
> 
---------
	Bootpfwd requires an enhanced TCPIP.NLM. Both should still be available
from sjf-lwp.novell.com, but if not then get archive file BOOTP311.ZIP from
netlab2.usu.edu, cd misc. I've renamed the file to be TCPIP1.NLM, to avoid
local confusion, and one should ignore the minor complaint from NW when it
loads the file (says the external and internal names are not the same).
	Documentation consists of:
	LOAD BOOTPFWD <ip numerical address of the Bootp server>
and a postscript that if you are running Multinet on your VAX then expect
plenty of console msgs about a bootp request arriving. Note that this NLM also
tends to repeat what it hears so a slew ("slew", a plethora) of bootp request
pkts arrive. Other than that we love it and make very heavy use of it at 
Utah State Univ. The person to thank is Don Provan of Novell.
	Final note: this is a forwarding device and not a bootp server.
	Joe D.
Newsgroups: comp.sys.novell
From: donp@novell.com (don provan)
Subject: Re: Novell IPX / NET Layers (ODI or not to ODI)
Organization: Novell, Inc., San Jose, California
Date: Wed, 29 Jul 1992 21:33:49 GMT

In article <1992Jul27.143003.19159@murdoch.acc.Virginia.EDU> skc@Turing.ORG (Shriram K. Chaubal) writes:
>PDETHER does not work well with IPXODI! The only combination I have working,
>is PDETHER with IPXODI 1.0. This may suit your needs .. but IPXODI 1.0 is
>old and none of the newer IPX's seem to work over PDETHER.

A new version of PDEther, version 1.02, is now available through
anonymous FTP from sjf-lwp.novell.com.  It can be found in the file
odi/pdether/pde102.zip.  This should solve your problem as well as
just about everyone else's that's wanted my butt in a sling since the
newer ipxodi's started coming out last year.

Let me repeat that: anyone that's been in contact with me to get PDEther
fixed should now try the 1.02 release.  So many people have been
complaining for so long, i've lost track of you all.

>They had never heard of a "packet driver" and refused to 
>give any intelligent help unless I switched to the the ODI drivers.

What a great idea!  Maybe i should do that with PDEther support. :-)

>Oh well ... Could someone at Novell PLEASE take a look at the PDETHER problem
>and give us a FIX :-) ... this would really convince us that Novell is indeed
>politically correct! Either that or turn over the source code and a developers
>kit to someone who is willing to look into it!

OK, let me make this perfectly clear: PDEther is *not* -- i repeat, NOT --
supported by Novell in any way, manner, or fashion.  It is supported by me
personally, as an individual, with no authorization or consent from
Novell.  I'm saying this not so much because support for PDEther is a
burden (well, it *is* a burden, but it's my own damn fault so i have to
live with that), but just to make sure that everyone understands that
Novell is in no way responsible for PDEther and cannot be held accountable
for the level of support PDEther receives.
						don provan
						donp@novell.com
From: SDENARO@vm.poly.edu
Newsgroups: comp.sys.novell
Subject: Looking for TSR to count Packets
Date: 30 Jul 92 20:16:29 GMT
Organization: Polytechnic University

I am looking for a utility to monitor NetWare Packets, I would like
it to work like the "Drive" tsr that flashes a dot on the screen when
you use the disk.
 
Any help on finding one would be great.
 
thanks
--
SAL DENARO      "Live Fast, Die Young, Hack 'C'"
sdenaro@polyvm.poly.edu  sdenaro@polyvm.bitnet
>>> This line is to confuse CIA, FBI, NSA, KGB, IBM DESTROY HACKER
BUSH QUAYLE DRUGS MONEY CREDIT CARDS POWER NUKE IRAQ KILL PENTAGON
Newsgroups: comp.sys.novell
From: alan@mailhub.scf.lmsc.lockheed.com (Alan Strassberg)
Subject: Re: BYU packet driver IPX doesn't do SPX
Organization: Lockheed Santa Cruz, CA.
Date: Tue, 21 Jul 92 19:00:21 GMT

In article <1992Jul21.085515.128@indyvax.iupui.edu> imhw400@indyvax.iupui.edu writes:

>>>   The BYU packet driver shell doesn't do SPX.  I don't know why, I
...
>>>Are there important programs which use SPX and don't run?

>>     Well, important is a relative term. I have a package called LAN Command
>> which requires full SPX functionality in order to work. There are also a
>> couple of utilities from Fresh Technology (the Map Assist people) which
>> seem to want full SPX as well.

	Hmmm. Specifically what ? I think I have everything from
	Fresh Technology and it all works fine with BYU shell.

>Not to mention RCONSOLE, found in the red box.

	This works too.

	What *doesn't* work is ARCserve's workstation backup.
	And as yet unknown is NetWare Management Services,
	they use SPX too.

					alan
----
Alan Strassberg		oetl1.scf.lmsc.lockheed.com	(408) 425-6139
Newsgroups: comp.sys.novell
From: harvey@indyvax.iupui.edu
Subject: Re: QUESTIONS : bootp & novell
Organization: Indiana University
Date: 22 Jul 92 14:30:51 -0500

In article <1992Jul22.044303.23814@slate.mines.colorado.edu>, cjmarsha@slate.mines.colorado.edu (Charles Marshall) writes:
> x98943@phillip.edu.au writes:
> : >
> :   You cant run a BOOTP SERVER ( or not that I know of ) on novell, but if
> : your running a V3.11 Novell server you can run a bootp forwarder on the
> : server. Its an NLM utility, I think its called BOOTPFWD.NLM ( correct me if
> : i'm wrong ), and it should be available from Simtel, among other places.
> : ( Check your archie server !! )
> :
> : Essentialy, it forwards a bootp request ( and replies ) for IP addresses,
> : among other things, from the PC to a Bootp Server running somewhere else,
> : like a Sun Workstation for example as is in my case!
> :
> : I use BOOTP mainly for NCSA Telnet and Popmail/PC and it all works extreamly
> : well for me !
> :
> : Also, if you intend to try this you have to have TCP/IP routing implemented
>  on your Novell Server if you haven't already !
>
> What about the RARP server?  Or the ARP server?  Both should do what you
> need.

IMHO, RARP is of extremely limited usefulness.  All it can tell a workstation
is the IP address it should use.  BOOTP is a lot more useful in that it can
also return the netmask, default router's IP address, the addresses of one or
more nameservers, etc.  And it's user-extensible.

At some point in the future more of the workstations here will probably get
configuration info from one or more servers, but it won't be using RARP...
--
James Harvey    IUPUI OIT Technical Support/Networks
harvey@iupui.edu  uucp: iugate!harvey  bitnet: harvey@indyvax
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.sys.novell
Subject: LWP 4.01 over Packet or NDIS? 
Distribution: world
Date: Wed, 22 Jul 92 13:50:14 GMT
Organization: Crynwr Software

In article <1992Jul21.215426.25917@worldbank.org> rpcfod@nimbus.worldbank.org writes:

   We're trying to get LWP to work with our SMC ethernet card in
   order to explore DesqView-X. Unfortunately the ODI driver for our
   SMC-Ethernet board (3016) doesn't seem to work, and the vendor is
   temporarily or permanently at a loss.  The board is fine, working
   just dandy with NDIS and Packet drivers.

   Is there a way to run the LWP IP stack over Packet or NDIS rather than
   ODI?  If so, how?

Sure.  You can use pdether to provide packet driver services over ODI.
It's available from sjf-lwp.novell.com via FTP.

-russ <nelson@crynwr.com>  I'm proud to be a humble Quaker!
Crynwr Software            Crynwr Software sells packet driver support.
11 Grant St.               315-268-1925 Voice   [ if mail bounces, forward it ]
Potsdam, NY 13676          315-268-9201 FAX     [ to uuadmin@uu.psi.com.      ]
From: dseeman@novell.com (Daniel Seeman)
Newsgroups: comp.sys.novell
Subject: Re: Netware for Macintosh 3.011 upgrade details?
Date: 24 Jul 92 22:26:03 GMT
Organization: Novell Inc., San Jose, Califonia

In article <67670007@acf3.NYU.EDU> chapman@acf3.NYU.EDU (Gary W. Chapman, , , ) writes:
>>We just got our upgrade postcard in the mail for Netware for Macintosh
>>3.011.  Unfortunately, the card provides no details regarding
>>changes from 3.01.
>
>And I'd like to know if there are changes in 3.01 to 3.011 which go
>beyond what apple distributed in ATSUP.ZIP on NetWire (consisting of
>enhancements to the Appletalk stack for reporting via SNMP).  In other
>words, doesn't buying buy anything?
>
Hi,

The version of AppleTlk.nlm that is sent with ATSUP.ZIP is 3.04.  That is the
same version as that which is sent with 3.011 NetWare for Macintosh.  So no,
there is no difference between the APPLETLK.NLMs shipped with 3.011 NW4MAC and
ATSUP.ZIP.  However, you will notice that ATSUP.ZIP doesn't come with AFP.NLM 
nor ATPS.NLM.  Many of the new features and changes were incorporated into these
modules.  So, if you want to take advantage of the new print service accounting
features (for example) you must upgrade to 3.011 NW4MAC.

In regards to a full description of the 3.011 product, you can take a look into
our NSE (Network Service Encyclopedia) for the press release concerning this
released update.  Other news services may also have records of this announce-
ment, so you may want to check with them.  Finally, if you are wondering about
fixes, most of the patches that were available for NetWare for Macintosh (like
ATPSFIX2.NLM and other similar patches) have been incorporated into the 3.011
product.  So if you would like to know what problems were fixed, just take a 
look at the README files for all of the NW4MAC patches.  This will give you a
pretty good idea of these fixes. But you are correct, the easiest way to get a 
look at the README file for 3.011 is to get the product.

Hope this helps...

Think Peace...

Dan Seeman
Novell
Walnut Creek, Ca.
Newsgroups: comp.sys.novell,comp.sys.att,comp.os.os2.networking
From: msn@cbnewsh.cb.att.com (matthew.s.nelson)
Subject: Re: Moving away from StarLan
Organization: AT&T
Distribution: usa
Date: Wed, 29 Jul 1992 17:47:23 GMT

In article <1992Jul29.140340.17455@cbfsb.cb.att.com> ncherry@cbnewsg.cb.att.com (neil j.cherry) writes:
>
>When I used to work at the hotline many people would call in with Novell and
>ask us for the drivers for the AT&T StaLAN 1 and 10 Meg boards. Eventually
>someone setup a BBS and AT&T mail access to the drivers. One problem we did
>have is that When Novell releases a new version of the OS, please give at
>least 3.5 seconds for the developers to get a fully tested and debug version
>of the driver writen and posted ;-}. I also do not know what AT&T/NCR is
>currently thinking in this area, but I would venture a guess that they are
>making drivers available when finished.
>
>(Anyone from AT&T/NCR care to comment on the above?)
>
>NJC

Sure. Drivers are available for the major NOS (NDIS, Novell, Packet)
for the NCR/AT&T StarLAN 1/10 boards. For more information, contact
the NCR/AT&T Hotline at 1-800-543-9935.
-- 
Matthew Nelson
NCR - Network Products Group
msn@cbnewsh.att.com
From: gchamber@nfsun.UUCP (Glenn Chambers)
Newsgroups: comp.sys.novell
Subject: Re: Telnet and stuff on ipx/spx?
Date: 22 Jul 92 17:03:31 GMT
Reply-To: gchamber@nfsun.UUCP (Glenn Chambers)
Organization: Intelligent Technology Group, Pittsburgh, PA

In article <331@asylum.UUCP> roger@asylum.UUCP (Roger Greene) writes:
(in reply to an unknown third party)

UTP>>What I mean is, is the a client/server combination that runs
UTP>>entirely on ipx. So is there?

RG>If it ran entirely on IPX, what would clients talk to?  (i.e. on what
RG>machine would the server run?)

The various 'netware for unix' products include a program called NVT
(for Netware Virtual Terminal), which is functionally equivalent to
Telnet, but running over SPX/IPX instead of TCP/IP.  This is also
included, I think, in the new SCO IPX/SPX product.

I have not yet seen an actual copy of this software, so I can only
guess, but I presume there is an IPX protocol stack, and something
similar to inetd and telnetd running on the host machine.
Newsgroups: comp.sys.novell
From: newlin@hardy.u.washington.edu (Jay Newlin)
Subject: Re: Netware NFS 1.2 and Windows 3.1 printing
Keywords: Windows, NFS
Organization: University of Washington
Date: Tue, 28 Jul 1992 14:37:32 GMT

edmund@qualcom.qualcomm.com (The Silver Surfer) writes:

>Hello out there. I recently purchased Netware NFS 1.2 and enabled
>the feature which allows Netware clients to print to printers
>on UNIX. I was able to nprint any file  (text or postscript), but
>when I try printing from Windows, it doesn't seem to want to work.
>I have as my destination printer an Apple II NTX Laser Writer. The
>file being printed actually gets placed in the UNIX print queue but
>doesn't get printed. Here's what it looks like when I run lpq:

Try changing the print job configuration to "Text" instead of
"Byte Stream".  I had the same problem, and discovered that Netware
seems to create a different type of cf* file for print jobs of type
"Text".  This seemed to fix the problem for me.

>-- 
>--------------------------------------------------------------------------
>edmund@qualcomm.com  (Ed Villavert)   "There's a place I like to hide,
>Qualcomm Incorporated		       A doorway that I run through in the
>San Diego, Ca  phone: (619) 597-5192   night." -- Silent Lucidity
Newsgroups: comp.sys.novell
From: harvey@indyvax.iupui.edu
Subject: Re: BYU packet driver IPX doesn't do SPX
Organization: Indiana University
Date: 28 Jul 92 13:05:38 -0500

In article <1992Jul28.064029.28301@novell.com>, donp@novell.com (don provan) writes:
> In article <1992Jul27.205641.1@indyvax.iupui.edu> harvey@indyvax.iupui.edu writes:
>>I just hate to interrupt this thread, but I had some thoughts on the original
>>question which started it all, which was (see subject line :-)...
>
> You have some interesting theories, but they are, unfortunately, wrong.

(faint choking sounds heard while Jim extricates foot from mouth)
Thanks.  I needed that.

>>Now, SPX just uses IPX (right?), so it would seem odd that a working IPX
>>driver would not work with a particular application that uses SPX...
>
> "IPX driver" is not a correct description, and it's misleading you.
> It would make more sense to say "NetWare protocol stack".  That might
> make it clearer why an SPX application would have trouble: the SPX
> protocol stack is, from what others are saying, simply missing from
> the picture.  SPX is not implemented in SPX applications, it's
> implemented in the executable supporting the NetWare protocol stack.
> Apparently in the case of the BYU stuff, no one implemented it.

But I thought the original poster claimed that SPX wasn't implemented because
some database application didn't work, and then others replied claiming that
SPX _was_ implemented because other SPX applications worked (RCONSOLE?).
--
James Harvey    IUPUI OIT Technical Support/Networks
harvey@iupui.edu  uucp: iugate!harvey  bitnet: harvey@indyvax
Newsgroups: comp.sys.novell
From: jbvb@vax.ftp.com  (James B. VanBokkelen)
Subject: Re: BYU packet driver IPX doesn't do SPX
Nntp-Software: PC/TCP NNTP
Reply-To: jbvb@ftp.com
Organization: FTP Software, Inc., Wakefield, MA
Distribution:  world
Date: Mon, 27 Jul 1992 17:23:15

In article <brian.19.0@Novell.COM> brian@Novell.COM (Brian Meek) writes:

    So one might ask: "why not support Packet Drivers".  Well, the fact that
    Packet Drivers are shipped in PC/TCP on a disk labeled "Unsupported 
    Software" by the originators of the Packet Driver(s) Specification speaks
    volumes to that...

Really, Brian, you should think what this will look like if you ever
change jobs.

Let's say that a buggy ODI driver got released by Generic NetCards Inc.
Novell isn't any more likely to get a Novell engineer to work fixing the
problem than Microsoft, IBM or FTP Software would for their favorite
driver spec.  The warranty and support comes from the driver
author/owner.

To date, all ODI drivers apparently have been written by board vendors
(not a surprise, given the history of the availability of the spec).  So
have all ASI (LAN Support Program) drivers and NDIS drivers.  The Packet
Driver spec has an even mixture of vendor-supplied and user-written
drivers, which indicates that there's a trade-off between 'clout' and
ease of development.  Because of Russ's involvement, Crynwr is actually a
much better "single point of support" than anyone's had since each vendor
had to write its own hardware drivers (we reached 27, I hope that's all).
    
    Secondly, can anyone point to a protocol stack other than IP that uses
    Packet Drivers?  Probably, but I can't think of any offhand...

You can get IPX, DECNet and LAT products which use the PDS.

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901

Newsgroups: comp.sys.novell
From: fengstad@alpha.uleth.ca (Grant Fengstad)
Subject: Re: Charon 3.4 (Questions)
Organization: University of Lethbridge
Distribution: usa
Date: Fri, 24 Jul 1992 04:26:22 GMT

In article <Brv3Cq.BDy@news.udel.edu> william@ravel.udel.edu (Wild William) writes:
>I got the 3.4 version of charon, I thought it was s'posed to allow
>printing from unix to novell and vice versa?
>
>anyone know about this?
>

Charon 3.4 serves as a Novell <-> SMTP Mail transfer gateway.  It works
very will with Pegasus Mail.

Charon 2.0 is a BSD Compatible LPD service.  

If you want to have lpd print functions, you have to get Charon Version
2.0 today.

Brad Clements (author of Charon), plans to release Charon 3.5 in a few
weeks.  This version, as I understand it, will perform both the
Novell/SMTP and LPD functions.


--
#====================================================================#
# Grant M. Fengstad		     E Mail: fengstad@alpha.Uleth.CA #
# Manager, Network Operations	     Voice:     (403) 382-6724       #
# Canadian Regional Airlines Ltd.    FAX:	(403) 327-1229       #
# "OS/2 opens up Windows.... Shuts up Gates"			     #
#====================================================================#
Newsgroups: comp.sys.novell
Subject: N.A.S. Parity Problem.
From: Bob.Clegg@bbs.actrix.gen.nz
Date: Fri, 24 Jul 1992 04:46:19 GMT
Organization: Actrix Networks

We are intending to use Novell Network Access Server to provide a connection
point for remote async terminals and PCs. The problem is that this equipment
and the intermediate Stat muxes are set for 7 bit even parity and the NAS
software is 8 bit no parity only. We can't change easily from 7 bit because
there is a software component to the parity checking in the terminals. (Yes it is
primitive).
Has anybody out there been in a similar situation?
Any advice on ways around this problem would be appreciated.