HDTenEightyP/NetNews huggingface dataset:
From: shwhang@rose.handy.co.kr (Whang)
Subject: Help wanted!!! OS/2 and ABEND on NW
Organization: HandySoft Institute of Technology, HandySoft Corp.
X-Newsreader: Tin 1.1 PL3
Date: Thu, 5 Nov 92 11:50:30 GMT

I installed OS/2 2.0 and NetWare Requester(NSD201).
But NetWare 3.11 refuses to co-work with my OS/2 machine.
I set Name space to my SYS volume for HPFS.
NetWare ABENDs especially when i trying to login(not allways) and
when I try to print to "capture /q=q0 /l=1"'ed printer.

Is there anyone who experienced simillar thing?.

I want to here from someone who have an idea about it.
	thanks for your kindness in advance.
	jhlee@rose.handy.co.kr

PS. Is OS2UTIL disks which comes with NetWare 3.11 usefull?
From: keith@novell.com (Keith Brown)
Newsgroups: comp.sys.novell
Subject: Re: TxLateCollisions - what's a late colloREFRESH
Date: 12 Nov 92 08:15:07 GMT
Organization: Novell, Inc. San Jose, California

In article <1992Nov11.185632.49888@ccvax.ucd.ie> ctoomey@ccvax.ucd.ie writes:
>Hmmm, taking a look under the `Custom Statistics' for the NE2100 Ethernet card
>in our NetWare 3.11 server, using `MONITOR' I see the following:
>
>TxLateCollisions:	67
>
>Now, can anyone tell me what a late collision is

To cut a long story short, there is a chance that your ethernet cables
are longer than the spec allows. Either that or you have some repeaters
that are not propogating the signals between segments as fast as they ought
to be.

Keith
-
Keith Brown                                       Phone: (408) 473 8308
Novell San Jose Development Center                Fax:   (408) 473 8990
2180 Fortune Dr, San Jose, California 95131       Net:   keith@sjf.novell.COM
Newsgroups: comp.sys.novell
From: thcheng@csie.nctu.edu.tw (a)
Subject: Why Appleshare PC 2.0 won't work w/ novell MLID?
Keywords: ASPC, MLID
Organization: National Chiao Tung University
X-Newsreader: TIN [version 1.1 PL6]
Date: Tue, 10 Nov 1992 10:42:25 GMT

Since Apple's Appleshare PC 2.0 software driver supports 3Com ethernet card
only, I have tried to use novell's NE2000 MLID to substitute 3c503's MLID, but
I failed miserably.

The Appleshare PC loads drivers in the following order:
LSL            <--- link support layer
3c503          <--- 3com's MLID
atalk          <--- Appletalk protocol stack
ashare         <--- Appleshare file service

According to Apple, the Appleshare PC comforms novell's Open Datalink Interface
(ODI). What do I do wrong with the installation?

Please E-mail your instruction to :
thcheng@csie.nctu.edu.tw

Any suggestion is highly welcomed.
From: dseeman@novell.com (Daniel Seeman)
Newsgroups: comp.sys.novell
Subject: Re: Novell vs. Lan Manager, which one do I choose?
Date: 11 Nov 92 16:13:14 GMT
Article-I.D.: novell.1992Nov11.161314.3615
Organization: Novell Inc., San Jose, Califonia

In article <74315@hydra.gatech.EDU> gt2768b@prism.gatech.EDU (JENGLUNG LIN) writes:
>Our department has a need to purchase a seperate network in addition to
>existing Novell IPX/NETX.
>
>Can anyone tell me about the pro and cons of purchasing another Novell or
>switching to Microsoft Lang Manager?
>
>Thanks in advance.

Remember, your current forum is comp.sys.NOVELL.  I say, stay with NetWare.  Our
efforts are not concentrated on workstation software packages like Windoze.  We
are a NETWORKING company which caters to your networking needs...

If there is a comp.sys.microsoft forum, you might recieve similar drum beating
responses in favor of LanManager.

Remember your audience...
Lines: 42
Date: Thu, 29 Oct 92 11:38:34 MST
From: sson@bones.caedm.byu.edu (Stacey Son)
Organization: Brigham Young University, Provo UT USA
Newsgroups: comp.sys.novell
Subject: LPR_GWY is *very* buggy (Was: LPR_GWY gen. prot. error)
Reply-To: sson@ee.byu.edu

>>>>> On Thu, 22 Oct 1992 14:31:12, eprie@news.msen.com  (Eric W. Priebe) said:

Eric> Hello fellow netters.  I've a 486, ISA based AGI computer running 3.11 with
Eric> NFS 1.2.  I've got 9 print queues redirected to 9 SUN printers via the LPR
Eric> gateway.  They work great except for one problem.

Eric> About every 10-14 days, I get a general protection failure and the running
Eric> process is always LPR_GWY.  The error code varies.  I've looked at patches
Eric> nfs012, nfs113 and nfs114 but they dont seem to relate to the problem.
Eric> Any ideas?

Eric> If it helps any, Ive got 16M ram and two 1.2G scsi drives.

We are having the same problem, however, it is starting to occur more
and more often.  It happened last night and this morning. We get
something like the following on the screen:

	System halted 	October 29, 1992 9:04:24am
	Abend: General Protection Processor Exception (Error Code 01D10000) 

		OS Version: Novell Netware v3.11 (250 user) 2/20/91
		Running Process: lpr_gwy	0 Process
		Stack: 58 A1 D0 ....

Of course, we already are waiting for a patch for this same NLM for
different non-related bug in which Novell has verified.  This is the
second bug in the two weeks that we have started using LPR_GWY.  Has
Novell heard of *software testing*?

If others are having this some problem, let me know.  I trying to
convince Novell it is a bug with LPR_GWY.NLM. If you have every called
in a "General Protection Processor Exception" to Novell you will know
they will say "it is your hardware."

BTW, we have a true blue IBM PS/2 Mod 95 w/ 32MB RAM, three 1.2GB SCSI
drives, and Novell's ethernet cards.

--
Stacey D. Son                           459 Clyde Building      
Operations Manager                      Provo, UT 84602
Brigham Young University                Voice:(801)378-5950 FAX:(801)378-6586
College of Engineering & Technology     Email: sson@ee.byu.edu
From: ctoomey@ccvax.ucd.ie
Newsgroups: comp.sys.novell
Subject: NE2000->NE2100 & PBURST.NLM ABENDs my server!!
Date: 10 Nov 92 13:18:35 GMT
Organization: University College Dublin

About a week back I was looking for some help with my ABENDing NetWare 3.11
server.. I'm still looking for help, but I definitley (!) know where the
problem lies :-D

Basically it boils down to the fact that using a NE2100 card in the 3.11 server
with the PBURST.NLM (Packet Burst Support NLM) instead of our original NE2000
card causes the server to ABEND.

The server has been up and running with no problems for nearly a year now, and
running using PBURST.NLM and BNETX at the workstations for about 3 months again
with no problems.

The server is a Dell 333P (33Mhz i386 with 32K external cache), 12Mb RAM, 535
Maxtor IDE driver, 1.44Mb floppy.  It's a bog-standard ISA machine, with one
NIC in a slot; used to be a NE2000.

Anyhow, I decided to try replace the NE2000 with a NE2100, as it claims to give
30% increase in performance, being a BusMastering card - we use a large MRP
Database system, which can suck a lot of bytes over the wire.

So, I swap NE2000 for NE2100 [look, no tricks..], bring up the server, place it
under some moderate load, and KABOOOOOOOM..

The server ABENDs with a GPPE running ISR (nested count 2), with the running
process being the Polling Process.

After a lot of testing, and stripping the server down to the bare NLMs
(IDE.DSK, NE2100.LAN), I managed to find a consistent pattern:

**Using the NE2100 (NE2100.LAN v3.11) with PBURST.NLM works fine if a client
  Does NOT try to use a Packet Burst 'session', e.g. by loading NETX at the
  Client workstation.  However, load BNETX at the client, and start doing some
  Read/writes from the server [say, by using NWTEST's Intensive Disk Tests],
  And the server goes belly up.  Using the NE2000, there is no problem, and
  Using the NE2100 without Packet Burst support again works, but using the
  NE2100 & Packet Burst kills my server.

I have a full transcript of the ABEND, plus version details of the NLMs, and
also the info. gleaned from the NetWare Debugger, if it helps at all.

Does anyone, especially anyone from Big Red Central (Novell..), know if there
any known problems with the NE2100 and PBURST, or is anyone ACTUALLY using this
combination with success - I've checked my NSESTD and have found no mention of
problems with the NE2100, but my version dates back to before Packet Burst
became widely available [the company I work for are getting their act together
to get a CD ROM driver & drivers, so we can mount NSEPRO as a volume on the
server (foot tap, impatient waiting...)]

Thanks,

	- Colm Toomey -
From: bob@comlab.gatech.edu (Bob Baggerman)
Newsgroups: comp.sys.novell
Subject: Re: Novell vs. Lan Manager, which one do I choose?
Date: 13 Nov 92 16:59:05 GMT
Organization: Georgia Institute of Technology

First, let me state that I think Novell, Microsoft, and Banyan all make
very fine products.  Each has it's relative strengths and weakness.
Which one is best?  It's like asking what is the best computer to buy.
It all depends on what you are trying to accomplish.

Paul Moore writes:
>My answer is dont touch LAN manager. It big slow complex hard to install on
>a PC , big on the PC, not so well supported by 3rd parties ....
>WHereas Novell is big fast complex to install easy to install on a PC, small
>on the PC and well supported ..

I suspect there will be a number of folks who can address the virtues of
NetWare (this being a NetWare news group 8-).  Just to add a little balance
I'd like to mention a couple of things that I like about LanMan.  Hopefully
this is of general interest.  If not please flame me via private email.

First and foremost, LanMan is protocol independent.  LanMan comes with
a small, fast non-routable protocol (NetBEUI) and a larger, routable 
protocol (TCP/IP) as standard equipment.  If those protocols don't suite
you other vendors protocol stacks can be used instead.  XNS, NBP, OSI,
DECnet, and other flavors of TCP/IP come to mind.

The specifications for LanMan, the protocol on the wire and the server
message block (SMB), are published and available for little or no charge.
Third parties can and do sell LanMan clients and servers for DOS, OS/2,
and most flavors of Unix.  This is handy when you need to decode packets
on the wire to debug a problem.

The third party support for LanMan isn't as big but we've found it to be
sufficient.  One major difference is that because Novell holds their 
NetWare Core Protocol (NCP) so near and dear there doesn't seem to be
much of an after-market of non-Novell licensed clients and servers.
Novell seems to want to keep that segment of the market to themselves.

The LanMan server is based on a good, well documented general purpose
multitasking operating system, OS/2 1.3.  It runs in protected mode
(something I think Novell is adding to their 4.0 server).  Writing and
running server based applications is straightforward and safe.  And it
doesn't take a special version of a C compiler.

Installation has always gone smoothly for me provided I wasn't trying to
do something nonstandard (which I usually am).  LanMan 2.1 comes with
an over-the-net installation program that worked well for us.

Let me sum up by saying LanMan certainly has its warts, too.  And again, I
don't think you can say one is *better* than the other.  Most of the
network vendors these days seem to be delivering real fine products.
I think it would be hard to go seriously wrong with any of the big network
vendors.

Bob
--
Bob Baggerman                         !  bob.baggerman@gtri.gatech.edu
Communications Laboratory             !  bob@comlab.gatech.edu
Georgia Tech Research Institute       !  qseclrb@prism.gatech.edu
Atlanta, GA  30332  USA               !  404-894-3525
From: villalj@xanth.CS.ORST.EDU (John Villalovos)
Newsgroups: comp.sys.novell
Subject: Re: NE2000->NE2100 & PBURST.NLM ABENDs my server!!
Date: 11 Nov 92 05:13:26 GMT
Organization: Oregon State University
NNTP-Posting-Host: xanth.cs.orst.edu

In article <1992Nov10.131836.49869@ccvax.ucd.ie> ctoomey@ccvax.ucd.ie writes:
>Basically it boils down to the fact that using a NE2100 card in the 3.11 server
>with the PBURST.NLM (Packet Burst Support NLM) instead of our original NE2000
>card causes the server to ABEND.
>

>So, I swap NE2000 for NE2100 [look, no tricks..], bring up the server, place it
>under some moderate load, and KABOOOOOOOM..
>
>**Using the NE2100 (NE2100.LAN v3.11) with PBURST.NLM works fine if a client
>  Does NOT try to use a Packet Burst 'session', e.g. by loading NETX at the
>  Client workstation.  However, load BNETX at the client, and start doing some
>  Read/writes from the server [say, by using NWTEST's Intensive Disk Tests],
>  And the server goes belly up.  Using the NE2000, there is no problem, and
>  Using the NE2100 without Packet Burst support again works, but using the
>  NE2100 & Packet Burst kills my server.
>

I have had problems with PBURST.NLM and the driver for my Micronics
Ethernet card.  When I load PBURST everything is fine but as soon as one of
my stations run BNETX the station locks up and then all the other stations lock
up with Network errors and then the file server can't be downed.  You have to
reset it.  So I don't use PBURST until and update comes out either for my card
or PBURST.  And the NLM for the ethernet card is Novell Tested and Approved.

Later,
-- 
John Villalovos
Certified Netware Engineer
villalj@xanth.cs.orst.edu
(503) 753-7883
Newsgroups: comp.sys.novell
From: abooth@ERA.COM (Alan Booth)
Subject: Access of Novell 2.15 and NetWare 3.11 File servers.
Organization: Engineering Research Associates, Vienna, VA
Distribution: usa
Date: Fri, 6 Nov 1992 14:43:41 GMT


I recently set up a NetWare 3.11 File server.  I placed it on a token ring
network with a Novell 2.15 File server. If I use the old 2.15 IPX.COM it
can only see the 2.15 File server and if I use the new IPX.COM it only sees
the NetWare 3.11 File server.  I would like to be able to attach to both File
servers so I can transfer files.

I'm not sure if I have to upgrade the version of the network driver on the
2.15 File server or exactly what to do.  Any help would be greatly appreciated.


  ----------------------------------------------------------------------------
  | Alan Booth                          Software Development Manager         |
  | email    abooth@era.com             Engineering Research Assoc., Inc.    |
  | phone    (703)734-8800 ext. 8523    1595 Springhill Rd, Vienna, VA 22182 |
  ----------------------------------------------------------------------------
From: bgruttad@slick.webo.dg.com (Brian Gruttadauria)
Newsgroups: comp.sys.novell
Subject: LAN WorkPlace NFS Client (Permissions)
Date: 5 Nov 92 20:15:50 GMT
Organization: Data General Corporation, Westboro, MA

Novell NFS LAN WorkPlace is succsessfully installed on my PC
I have also built and executed the lwpnfsd daemon to run
in my Unix server.

The problem which I am having has to do with the user/ownership
permissions given to a file when it is created by ROOT on a NFS 
mounted filesystem.

Scenario:
------------------ From the PC -------------------------------

1. net register as root
2. net link k: <exportable file system>
3. Do a net group k: to see which groups are available to root
   Everything looks OK; group on k: is set to other 
4. create a file on the k: drive
5. The file is created as follows: 
   ls -gal
   -rwx------  1 nobody   65534        36       foo 

------------------ On Unix side --------------------------------
ls -al
-rwx------   1 nobody   65534         36 Nov  5 15:03 foo 


Does Anyone have any suggestions!!!


				- Thankyou in Advance
 
------------------------------------------------------------------
|Brian R. Gruttadauria         Phone : (508) 870-8239            |
|NSDD / OpenLAN Development    FAX   : (508) 898-4212            |
|Data General Corporation      INet  : Brian_Gruttadauria@dg.com |
|Westboro, MA USA                      bgruttad@slick.webo.dg.com|
------------------------------------------------------------------
Newsgroups: comp.sys.novell
From: dseeman@novell.com (Daniel Seeman)
Subject: Re: Q. (Deals with Atalk packets..more in article)
Organization: Novell Inc., San Jose, Califonia
Date: Mon, 9 Nov 1992 17:38:11 GMT

In article <BxB5Ko.HzG@news.orst.edu> gonzalem@ucs.orst.edu (M-FORCE) writes:
>OK here is the deal.. we have a campus wide network and we have server
>servers (100+) setup all over the place.  What I need to find out is if
>it is possible to get all the macs to see the other novell servers
>running mac.nlm's or similar.  I think I have traced the problem down
>to the central router not passing appletalk packets.  Now if this is
>the case, how would I trick/shim/force novell to send those packets
>like it use to when ww had 2.15c running mac vaps?  I have tried binding
>the atalk to pc (ether_ii to enter_snap) with no luck.
>
Hi,

NW 2.15c wasn't providing you with AppleTalk routing services.  It provided you
with an AFP GATEWAY (AFPSPG.VAP).  If you are having trouble seeing all of your
file servers, it most certainly will have to do with routing and cabling.  I
will assume you have the cabling part taken care of and will focus on routing.

If you have traced the problem to a particular 3.x NW4MAC server, AND you
absolutely KNOW the protocols have been appropriately bound, you may have a 
driver problem.  It is not uncommon to have a LAN driver that supports a frame
type but does not support a particular protocol that uses that frame type.

The other thing that you must consider is that Novell releases two routers.  One
is called ROUTER and is made with ROUTEGEN (this product is bundled with the OS)
while the other is called the Multi-Protocol Router (MPR).  ROUTER is an IPX
router ONLY.  The MPR will support AppleTalk (as well as other notable protocols
hence the name---Multi-Protocol Router)...

If you are using ROUTER, you will NEVER get AppleTalk routed from one interface
to the other.  The best you can get is to use the GATEWAY services offered by
the VAPs.  The MPR should be able to handle this, and you would use INETCFG
to appropriately configure your routing interfaces for  AppleTalk.

There should be enough information here for you to make the needed configuration
decisions.  The bottom line is to use AppleTalk routers when needed, and to
realize when you are using an IPX router (like the ROUTER/ROUTGEN router).  If 
you are using ROUTER, replace it with the MPR, or some other true AppleTalk
router (like a FastPath or even another NW4MAC file server).

Hope this helps...

Think Peace... (PLEASE!!! THERE IS TOO MUCH VIOLENCE ALREADY!!!)

Dan Seeman
Novell
Walnut Creek, Ca.
Newsgroups: comp.sys.novell,comp.protocols.tcp-ip
From: mr@ogre.cica.indiana.edu (Michael Regoli)
Subject: ODIPKT Freezes with my Accton EtherCombo-32
Organization: Indiana University
Date: Thu, 5 Nov 1992 21:51:43 GMT


I'm having difficulty with ODIPKT on a 486/50 EISA machine, and was
wondering if anyone else is in this boat with me as well.  ;)

I've got a nice little net.bat file that loads lsl, ec32mlid,
ipxodi, and bnetx (burst).  That all works fine.  And I can connect to
LAN servers like crazy.  However, the TCP/IP side is a bit more
sticky.   

Has anyone a packet driver for this card???  

Thanks for the help!

--
michael regoli
mr@cica.indiana.edu
regoli@indiana.BITNET
..{ames, rutgers}!iuvax!cica!mr
Newsgroups: comp.sys.novell
From: walter@lkn.e-technik.tu-muenchen.de (Walter Loepsinger)
Subject: Re: Interrupt problem
Organization: Lehrstuhl fuer Kommunikationsnetze, TU Muenchen (Germany)
Date: Thu, 5 Nov 1992 12:45:02 GMT

j.laidman@cowan.edu.au (Jeremy Laidman) writes:

>You've probably got your network card IRQ setting to 3 or 4, and your mouse
>will be a serial mouse.  Serial ports use IRQ 3 (COM2) and IRQ4 (COM1).
>Or your mouse could be a bus-mouse, which I think work on IRQ5, but I'm not
>sure.  If this is the case, you'll have to alter the IRQ setting on your
>network card (easiest) or your comms/mouse port.

The mouse uses IRQ 3 and the ethernet uses 5. 
I already tried a change: no effect :-(

What now?
 
Walter.

Newsgroups: comp.sys.novell
From: newson@eecs.nwu.edu (Bryan M. Newson)
Subject: One quick printing question...
Organization: EECS Department, Northwestern University, Evanston, Il., USA
Date: Fri, 6 Nov 1992 00:04:19 GMT

I am running PS-Print ver. 3.1 on Novell 2.15.  However, I need a package
that will allow me to print to printers attached to logged off workstations
. Any (inexpensive) suggestions?

Thanks,
Bryan
Newsgroups: comp.sys.novell
Subject: Upgrade
From: pzocco@falcon.wcc.wesleyan.edu (Paul Zocco)
Date: 13 Nov 92 09:46:07 EDT
Keywords: Upgrade

To all networkers,

I need some help in doing NetWare 2.15 to 3.11 upgrades.  I've done a  
couple and have a couple more to go.  Things haven't gone as smooth as  
I've wished.  I've run UPGRADE using the backup method and transfer  
method.  In both cases, I've had to recreate all Users' Trustee Directory  
Rights (the same goes for the Groups.)

In most of the upgrades I've done so far,  I've gone from a NetWare 2.15  
server with just a SYS: volume to a NetWare 3.11 server with at least two  
volumes, say a SYS: and a USER:, that is:

	NW 2.15 with SYS:   ------->>>>   NW 3.11 with	SYS:
							USER:
							

I usually can't (or don't want to) make the SYS: on the new server as  
large as the SYS: on the old server.  Usually the UPGRADE dies when I'm  
restoring files to the new server (because SYS: runs out of room.)  By  
this time I've already done the BINDERY transfer so by then I figure I've  
got all of my directory rights anyway and I usually restore the rest of  
the info. from tape.

If my logic is wrong, please tell me.  I've go to know the correct way to  
upgrade my next server (less than 2 weeks away!)  How do I go about  
upgrading the server to save all the users' (and groups') rights and  
establish a new volume structure?

Thanks in advance!  Please send all replies to:

PZOCCO@falcon.wcc.wesleyan.edu

Paul Zocco
Computing Center
Wesleyan University
Middletown, CT
From: ctoomey@ccvax.ucd.ie
Newsgroups: comp.sys.novell
Subject: Annointing & Laying-on-of-hands on server..
Date: 5 Nov 92 14:37:07 GMT
Organization: University College Dublin

Ahh come on folks, don't be shy; I only received one reply to my plea for
suggestions on my ABENDing 3.11 fileserver, when I try using a NE2100 instead
of the NE2000 we've been using for a year now..

Thank you, Marty Collins, from 'Big Red' central - you're the only one who
cares :-D

Marty suggested that it could be caused by using a BustMastering card in an ISA
machine with more than 16Mb of RAM.  I know about that, but it's not the
problem here - the server has only 12Mb of RAM.

The ABEND is consistenly the same, halting on an ISR (Nested Count 2), while
running the Polling Process.

I'm wondering if this above ABEND could be caused by PSERVER v1.26 which is
running on the server; does anyone out there have details of what v1.26 did
that caused Novell to withdraw it; did it <fingers-crossed> cause an ABEND such
as the one above??

I'm due to retry the NE2100 this weekend, and I'll try it with PSERVER v1.22,
and see what happens, but I'd love to get some suggestions before I waste my
time chasing dead-ends.

A prize for the 1st correct answer sent to me on a postcard... :-D


Cheers,

	- Colm Toomey -
	B.Sc.(Hons.), Graduate Student in Comp. Sci.
	[Saving to pay for CNE testing in January;
	 credit card donations on 1-800-DEAD-SERVER]