From: kwang@zeus.calpoly.edu (Kevin Wang)
Newsgroups: comp.sys.novell
Subject: comp.sys.novell: Frequently asked questions (FAQ)
Summary: FAQ
Date: 1 Sep 92 00:01:00 GMT
Expires: 16 Sep 1992 00:01:00 GMT
Organization: Networks 'R' Us


 Frequently Asked Questions for comp.sys.novell
================================================

I appreciate any and all input for improving this FAQ.  Please email
suggestions and other such nonsense to kwang@hermes.calpoly.edu.

In need of (perhaps desperately)
================================

A generic list of pointers to ftp sites where to look for drivers for
specific hardware types, i.e. 3-com NICs.

A Q/A portion on known printer, rprinter, and pserver 
problems/bugs/fixes

General information about putting a CDROM drive on the network (server
or workstation based)

Solutions for running packet drivers under Windows 3.x & where/why/how
WINQVT and WINPKT fit into the picture.

Contents
========

New questions are marked by (+),
Modified/revised questions are marked by (*), and
Deleted questions are marked by (-).

  01. What is this "FAQ" List?
  02. What is the origin of this FAQ and how do I add to it?
* 03. Is this FAQ available by anonymous FTP?
  04. What rules of etiquette apply on this newsgroup?
* 05. Where can I anonymous FTP Netware utilities, programs, etc?
  06. Is there an official Novell FTP site for patches and updates?
  07. How do I become a CNE (Certified NetWare Engineer)?
  08. How can I send email from Novell to the Internet?
  09. What is Pegasus/Charon?
* 10. Why can't I get my 3.x server to forward TCP/IP packets?
  11. What is Trumpet?  
  12. Is there a TELNET compatible program for remotely controlling a PC?
  13. How can I boot my server without running STARTUP.NCF/AUTOEXEC.NCF?
  14. How can I reach Novell by phone?
  15. What is BOOTP and where can I find it?
  16. How can I login *without* running login scripts?
  17. How can I get user-ids (and other information) into programs?
  18. What are Packet, ODI and NDIS drivers?
* 19. How can I connect up with the Internet?
  20. Where can I get FSUUCP?
  21. What is RARP and where can I find it?
  22. Why won't RPL (remote boot) work?
* 23. How can I get started programming with Novell?
  24. What is Burst Mode and where can I get it?
  25. Are there any related mailing lists?
  26. Where can I get Packet drivers?
  27. What software metering packages are available?
  28. What remote-dialup options do I have for Novell?
* 29. How can I connect my Novell Network with TCP/IP?
  30. Can I print from *nix -> Novell?
+ 31. How can I access other TCP/IP resources on my Novell network?
 
  01. What is this "FAQ" List?
--- 07/12/92 ---
This FAQ contains information about common questions, problems, and
bugs in Novell's and other third-party, shareware, and freeware
products.  You will also find hints and generally good ideas for
improving and/or expanding an existing system.

  02. What is the origin of this FAQ and how do I add to it?
--- 08/05/92 ---
All typos, spelling errors, slang, and errors are mine.  Should you
find a Q/A in error or an addition, please email me with a COMPLETE
answer/update/fix/change/addition.  A 3-line "That's wrong, fix it"
will be completely ignored.  I don't have the time to research every
single problem.  I will, however, try and briefly double-check it (if
it is within my power) and then add it to the next edition of the FAQ.

* 03. Is this FAQ available by anonymous FTP?
--- 09/01/92 ---
John Wobus of Syracuse University has generously provided a ftp site for
this FAQ.  It can be found at syr.edu under novell/papers/ as 
FAQ-comp.sys.novell.  Thanks again!

  04. What rules of etiquette apply on this newsgroup?
--- 08/12/92 ---
I willnot/cannot summarize net etiquette here.  Instead, try reading
the newsgroups news.announce.newusers and news.newusers.questions.

* 05. Where can I anonymous FTP Netware utilities, programs, etc?
--- 09/01/92 ---
Official and Unofficial Novell patches, updates, and information are
available from Novell on their anonymous ftp server.  (See ftp list) On
other anonymous ftp servers (below) you can find the latest versions of
Telnet, Charon, Trumpet, and other utilities.  Archie and Gopher can be
helpful in finding anonymous ftp sites that carry the programs you seek.

If you are not familiar with anonymous ftp, you can RTFM, ask your
local administrators, or better yet, a friendly *nix guru.  8>

A partial list of ftp sites with Novell stuff is:

Changes:
rodan.acs.syr.edu              (deleted)
syr.edu                        128.230.1.49

Major Novell ftp sites:
ftp.is.sandy.novell.com	       137.65.12.2, Alias: ftp.novell.com
newsun.novell.com              130.57.4.1
sjf-lwp.novell.com             130.57.11.140
barnacle.erc.clarkson.edu      128.153.28.12, Alias: grape.ecs.clarkson.edu
omnigate.clarkson.edu          128.153.4.2
splicer.cba.hawaii.edu	       128.171.17.7
sun.soe.clarkson.edu           128.153.12.3

novell.com mirrors:
netlab2.usu.edu                129.123.1.44

monk.proteon.com               128.185.123.16
spdcc.com                      140.186.80.3
cbaux.cba.hawaii.edu
cc.usu.edu                     129.123.1.1
chaos.cc.ncsu.edu              152.1.10.23
cs.ep.utexas.edu               129.108.1.41
das.harvard.edu                128.103.50.55
dcsprod.byu.edu	               128.187.7.3
harvard.harvard.edu            128.103.1.1
info.umd.edu                   128.8.10.29
netlab.usu.edu	               129.123.1.11
netlab1.usu.edu                129.123.1.43
noc.byu.edu                    128.187.7.2, Alias: dcsprod.byu.edu
remus.rutgers.edu              128.6.13.3, Alias: topaz.rutgers.edu
risc.ua.edu                    130.160.4.7
shasta.scl.cwru.edu            129.22.32.7
ucs_wcc.ucs.indiana.edu        129.79.16.96, Alias: lan_stuff.ucs.indiana.edu
watsun.cc.columbia.edu         128.59.39.2
zaphod.ncsa.uiuc.edu           141.142.20.50, Alias: ftp.ncsa.uiuc.edu
wsmr-simtel20.army.mil         192.88.110.20

nestroy.wu-wien.ac.at          137.208.3.4
kirk.bu.oz.au                  131.244.1.1
sunee.uwaterloo.ca             129.97.50.50
hamster.business.uwo.ca        129.100.22.100
ftp.uni-koeln.de               134.95.80.1
iraun1.ira.uka.de              192.13.10.90, Alias: ftp.ira.uka.de
ftp.uni-kl.de                  131.246.9.95
garbo.uwasa.fi                 128.214.87.1

simtel20 mirrors:
rigel.acs.oakland.edu          141.210.10.117, Alias: oak.oakland.edu
wuarchive.wustl.edu            128.252.135.4
ftp.uu.net                     137.39.1.9
nic.funet.fi                   128.214.6.100
src.doc.ic.ac.uk               146.169.3.7
archie.au                      139.130.4.6
nic.switch.ch                  130.59.1.40

  06. Is there an official Novell FTP site for patches and updates?
--- 08/05/92 ---
Unofficial patches, programs, nlm's, drivers, etc, can be found on
sjf-lwp.novell.com.  The official anonymous ftp server is at
ftp.is.sandy.novell.com.  In /novlib you will find a structure similar
to that on CompuServe.  However, Novell cannot offer anything other
than its own uploads to the internet, due to legalities.

Janet Perry has pointed out that "while CompuServe libraries allow
the posting of third party information, Novell does not hold the
copyright to that information and it will not be found on Novell's FTP
server."

      1.   Novell new uploads
      2.   General Information (General Information, Press Releases,
           Education)
      3.   NetWare 2.x specific files
      4.   NetWare 3.x specific files
      5.   Client/shell drivers (workstation shells, drivers, Windows
           files, etc)
      6.   NetWare utilities
      7.   Btrieve/XQL Novell
      8.   Mac/UNIX/LANalyzer
      9.   Communications Products
      10.  NetWare Lite
      11.  Tech Info/IMSP (Tech Bulletins, IMSP, APNotes)

  07. How do I become a CNE (Certified NetWare Engineer)?
--- 07/27/92 ---
For detailed information and flyers, call 1-800-NETWARE.  Here is an exerpt
from the CNE info blurb:

(From pages 3, 4, 6, 8 & 10 of the Novell CNE PROGRAM Flyer)

EARNING YOUR CNE CERTIFICATION

To earn your CNE certification, you must demonstrate your mastery of
networking concepts by passing a series of proficiency test. You have
one year to complete all proficiency tests. The one year begins the day
you take your first test whether you pass or fail.

PROFICIENCY TESTS

The CNE proficiency tests are divided into three categories: core
requirements, operating systems requirements and electives.  Each
proficiency test has a number of Novell credits associated with it.  To
become a CNE, you must:

	Pass all three tests in the core requirements category (a total
	of 10 credits).

	Pass two tests in the operating systems requirements category
	(a total of 5 credits). You can specialize in either in the
	NetWare v2.2 operating system or the NetWare v3.11 operating
	system.

	Earn at least four credits in the electives category.

All current CNE proficiency tests, test numbers and credits are listed below.

Test Title

Core requirements (10 credits required)
    DOS/Microcomputer Concepts...         50-15 Adaptive  2  30 min.
    NetWare Service and Support           50-46 Adaptive  5  30 min.
    Networking Technologies               50-80 Adaptive  3  30 min.

Operating systems requirements category (5 credits required)
NetWare v2.2 track
    NetWare v2.2: System Manger           50-20   Adaptive  3   30 min.
    NetWare v2.2: Advanced System Manger  50-44   Adaptive  2   30 min.

NetWare v3.11 track
    NetWare v3.11: System Manger          50-91   Adaptive  3   30 min.
    NetWare v3.11: Advanced System Manger 50-82   Form*     2   60 min.

Electives (4 credits required)

NetWare v2.2 electives**
   |NetWare v2.2: System Manger           50-20   Adaptive  3   30 min.
   |  and
   |NetWare v2.2: Advanced System Manger  50-44   Adaptive  2   30 min.
      or
    NetWare v2.15 to v2.2: Update         50-37   Adaptive  2   30 min.

    Note: The NetWare v2.2 elective credits will not count if the NetWare
    v2.2 track was used to meet the operating systems requirements. If you
    pass 50-20 or 50-44 exams, the 50-37 exam will not count as elective
    credit.

NetWare v3.11 electives**
   |NetWare v3.11: System Manger          50-91   Adaptive  3   30 min.
   |  and
   |NetWare v3.11: Advanced System Manger 50-82   Form*     2   60 min.
      or
    NetWare v3.11: OS Features Review     50-45   Adaptive  2   60 min.

    Note: The NetWare v3.11 elective credits will not count if the NetWare
    v3.11 track was used to meet the operating systems requirements. If you
    pass 50-91 or 50-82 exams, the 50-45 exam will not count as elective
    credit.

Additional electives**

    Product Information Course
    	for Authorized Resellers          50-18   Adaptive  2   30 min.
    	for Gold Authorized Resellers     50-19   Adaptive  2   30 min.
    LAN WorkPlace for DOS Administration  50-95   Form*     2   60 min.
    NetWare TCP/IP Transport              50-86   Form*     2   60 min.
    NetWare NFS                           50-87   Form*     2   45 min.
    NetWare for Macintosh Connectivity    50-93   Form*     2   60 min.
    LANalyzer for Ethernet                50-90   Form*     2   60 min.
    LANtern Service Manager               50-89   Form*     2   45 min.
    NetWare Asynchronous Connectivity     50-88   Form*     2   60 min.
    NetWare for SAA Installation 
        and Troubleshooting               50-85   Form*     2   60 min.
    NetWare v2.15: System Update          50-35   Adaptive  2   30 min.

 * This test is currently a form test, but it will be changed to a 
   30-minute Adaptive test in the future.

** More electives will be made available as products are released.

CONTINUING CERTIFICATION REQUIREMENTS. To ensure that CNEs keep up with
the latest advancements in network computing technology, all CNEs are
required to meet Continuing Certification requirements. When Novell
introduces a major new product, for example, or if there is has been a
major technological advance, CNEs will be required to pass a
proficiency test on the subject, This ensures that CNEs can continue to
provide the best support in the industry.

Novell will mail notification of CONTINUING CERTIFICATION requirements
to all CNEs. You will then have six months to complete the new
requirements.

  {delete material}

CERTIFICATION EXPIRATION

CNEs who do not complete Continuing Certification requirements in the
six-month time limit will lose their CNE Certification. All
Certification requirements completed up to that point become point
void, and the individual must complete all certification requirements
again, within a one-year period, to regain CNE status.

  {delete material}

PREPARING FOR THE CNE PROFICIENCY TESTS

To prepare for the CNE PROFICIENCY tests, you have several options,
including instructor-led courses and a variety of self-tests.

INSTRUCTOR-LED COURSES

Instructor-led courses designed by Novell are offered through NOVELL
Authorized Education Centers (NAECs). All NAECs have been certified by
Novell and use Certified NetWare Instructors (CNIs).  For more
information in your area or for general course information, contact
Novell Education at (800) 233-3382 in the United States and Canada.  In
all other locations, contact one of the Novell offices listed on the
back cover of the (this) brochure.

  {deleted list of instructor-led courses}

SELF_STUDY OPTIONS

You have three self-study options, student kits, self-study workbooks
and computer-based training courses.

STUDENT KITS

If you elect not to take instructor-led courses but would like to study
the course materials on your own, you can order a student kit.  Student
kits were developed for instructor led environments; however , if you
have a background in DOS, microcomputer hardware and NetWare, these
materials may be adequate for test preparation. This option may not be
offered by all regions outside the United States and Canada. All
student kits may not be available at all NAECs.

  {deleted list of student kits}

WORKBOOKS

Two workbooks are available that cover most of the information in the
DOS/Microcomputer Concepts for NetWare CNE proficiency test. You can
order these workbooks by contacting your local NAEC.

  {deleted list of workbooks}

COMPUTER-BASED TRAINING COURSE

One computer-based training (CBT) course is currently available. This
course covers material taught in the instructor-led course. You can
order a CBT course by contacting your local NAEC.

  {deleted list CBT course}

  08. How can I send email from Novell to the Internet?
--- 09/01/92 ---
Pegasus Mail is a free email package written by David Harris.  It has
many features such as file transfer, send-to-group, and message
passwording.  It can also interface with MHS and send (with the support
of Charon) Internet mail.  Pegasus mail can be found at
splicer.cba.hawaii.edu and risc.ua.edu

There are two main versions of Charon.

	Version 2.x is a bi-directional Unix <--> Novell lpd gateway

	Version 3.x of Charon is a bi-directional Novell to
	Internet email gateway.  It will transfer mail from Pegasus to
	the world-at-large.  This version requires that you have a SMTP
	mail server in your area.

	Both versions of Charon require a dedicated PC.  Charon can be
	found at splicer.cba.hawaii.edu and omnigate.clarkson.edu.

	Version 4.x has just been released, and combines the above two
	functionalities.  It will serve as both an lpd gateway and a
	SMTP gateway.

Commercial packages that you might also want to look at are:
cc:Mail
Da Vinci Mail

In any case, you will probably need a SMTP gateway to translate the
email messages into something the Internet can understand.

  09. What is Pegasus/Charon?
--- 08/05/92 ---
See previous question

* 10. Why can't I get my 3.x server to forward TCP/IP packets?
--- 08/19/92 ---
With 2 or more network cards in the server, you can forward TCP/IP
packets relatively simply.

The first common problem is that when you load TCPIP.NLM the
forward=yes options is forgotten.  Thus, the AUTOEXEC.NCF file should
have the line:
	load tcpip forward=yes

Another possibility is that the transmitting station is not sending the
packets to the right place.  If packets must go through the server, you
must set up a "gateway=aa.bb.cc.dd" option on the workstation.  The
server will then decide which network card the packet must be
retransmitted on, thus leaving all routing to the server, instead of
trying to have the programmers put it into the program itself.  Also,
if you have some older routers on, say, a campus backbone, they might
have to be reprogrammed as well, so that they can send packets back to
your workstation, should they need to make several hops to get to their
destination.  Older routers require this, while the newer ones will
automatically "find" your server as a router through RIP.

Another common problem that people have is that Novell will only
forward between two different subnets, i.e.  
	129.65.1  & 
	129.65.2  with a mask of
	mask=ff.ff.ff.00

According to mcollins@novell:

	There is a flaw in this design because Netware 3.11 IP routers
	require unique IP network numbers for different physical
	networks.

	In certain IP arenas you can do this through the use of PROXY
	ARP which NOVELL does not support yet in this release of TCPIP
	routing.

	This is being worked on however.

  11. What is Trumpet?  
--- 07/22/92 ---
Trumpet is a NNTP newsreader.  Version 1.04 is FreeWare and Version
1.05 is ShareWare (modest donation).  The only requirement is that
there be a NNTP server accessable from your network.  

  12. Is there a TELNET compatible program for remotely controlling a PC?
--- 07/27/92 ---
Yes.  Get pub/wattcp/telnetd.zip via anonymous FTP from
sunee.uwaterloo.ca.  It works really well with CUTCP TELNET, and also
works fine with MacTCP TELNET and most other TELNETs as well.

  13. How can I boot my server without running STARTUP.NCF/AUTOEXEC.NCF?
--- 08/05/92 ---
For Netware ver 3.xx, use these command-line options:

	SERVER -NS   To skip STARTUP.NCF, and
	SERVER -NA   To skip AUTOEXEC.NCF

NetWare 2.x does not HAVE the files STARTUP.NCF and AUTOEXEC.NCF.
Instead they hard-code all the information into NET$OS.EXE, so you will
have to rebuild it to change anything.

  14. How can I reach Novell by phone?
--- 07/12/92 ---
This list comes from a mailing from Sarah Peterson (Novell) to Larry
Bradly, which he posted to the novell listserv.  These numbers are
valid as of 10/18/91.

Department/Group                       Toll-Free          Regular

After Market Products (AMP)            800-346-7177       801-568-8856
Anthem/Eagle (Ethernet)                800-733-2453       408-453-1200
API Development/Austin                 800-RED-WORD       512-794-1795
Authorized Reseller Information        800-828-3362
Contract Inquires/AMP                  800-346-7177       801-568-8856
Contract (for those who have them)     800-51-3184
Corporate Headquarters                 800-453-1267       801-429-7000
Customer Success Portfolios            800-UPDATE1        801-429-5155
Developer Assistance                   800-729-4357
Reseller Authorization                 800-828-3362
LANalyzer Products                     800-243-8526       408-473-8324
Literature Orders                      800-UPDATE1        801-429-5155
NetWare Users International            800-228-4NUI
OURS Program                           800-237-OURS
Professional Developers Program(PDP)   800-RED-WORD       512-794-1795
Piracy                                 800-PIRATES        801-429-7600
Product Information                    800-NETWARE        801-429-5155
Promotional Products                   800-526-4483
RMA                                    800-NETWARE
Technical Marketing Support            800-733-9673
Technical Support                      800-NETWARE        801-429-5588
Technical Support/PDP                  800-SAY-HELP       512-794-1795
Upgrades/Updates                       800-UPDATE1        801-429-5155
Warranty Registration                  800-458-7773

  15. What is BOOTP and where can I find it?
--- 08/05/92 ---
BOOTP is a method for a workstation to query a central server and
inquire what its IP setup should be: address, mask, gateway,
nameserver, etc.  This differs from RARP in that RARP *ONLY* returns
the IP address of the machine.

BOOTP is available on lancaster.andrew.cmu.edu.  This, however, appears
to be C source code for a *nix box.  Many other sources are available
for BSD BOOTP.  Archie can readily find 20 or 30 sources.  If anyone
can point me in the direction of a BOOTP.NLM, I'd be happy to add such
information here.

If BOOTP is available to you, consider looking into BOOTPFWD.NLM, the
bootp packet forwarder for Novell 3.11 servers.  It can be found on
sjf-lwp.novell.com, under nw311/bootpfwd/.

  16. How can I login *without* running login scripts?
--- 07/12/92 ---
To avoid running the user login scripts:

	Have "EXIT" as the last line in your system login script.  This
	prevents the system from running a user's login script or the
	default if a user does not have one.

To avoid running any login scripts at all:

	1. Use ATTACH instead of LOGIN to connect to a server.  ATTACH
	will not run the login script, whereas LOGIN will.  ATTACH.EXE
	will either have to copied to a local HD or put in sys:login.

    2. Use the /s <fname> option for LOGIN.  Using "LOGIN /S NUL
    <login>" will cause LOGIN to load the DOS device NUL which will
    always seem like an empty file.

  17. How can I get user-ids (and other information) into programs?
--- 08/05/92 ---
There are many ways to import Novell information into programs you have
written, each of which is appropriate for some solutions:

A. Environment variables

Use the login script command:
	dos set VARIABLE="Value"
to put the user-id (%LOGIN_NAME), station number, etc. (the
documentation for the list of available values), into an environment
variable.  Now, you will be able to retrieve the environment variable,
both in batch files, and in programs.  In Turbo Pascal, C, and C++ use
the expression GetEnv("VARIABLE") to retrieve an environment variable.
This technique is good for simply programs which only need a few Novell
values, and for batch files.

B. Piping in information from WHOAMI

Write your program to read its input in the form that WHOAMI types, and
then pipe in the output from WHOAMI:
	WHOAMI [/a] | YOURPROGRAM
You will have to program to ignore lines that contain only / -
\ because these still appear at the head of the file while the program
is scanning the bindery information.  This is inefficient, but it is
the only way to get group arbitrary group memberships if you cannot use
any of the below options.

C. Novell API's

Purchase the Novell API's, available in both C, C++, (including all
Borland products) and assembly language.  With these you can retrieve
directly almost any information that the account running the program
has access to.  The API's provide not only basic services like
user-names and connection number, but advanced ones like print queues
and IPX/SPX communications, among others.  This is the best and most
efficient solution, but requires investment in the API's as well as
programming knowledge.

D. Third Party API's

Libraries are available that are virtual duplicates of Novell's API's.
Some are commercial, some are shareware, and some are even freeware.
Try looking around at some of the ftp sites, and see what you can dig
up.

E. Using Novell's API's through interrupt calls

You can also pick up any number of books that will show you how to
access all of the API functions through system interrupt calls, thus
requiring only investment in a compiler and a book, with the
appropriate programming knowledge.

F. Third Party Utilities

Obtain a commercial or shareware utility to enhance batch files with
Novell information.  You could also write your own (see solutions C, D,
E).

  18. What are Packet, ODI and NDIS drivers?
--- 07/07/92 ---
Packet Drivers, ODI drivers, and NDIS drivers share a common
purpose of recognizing packets coming in and distributing them to the
appropriate piece of networking software as well as sending pre-built
packets.  Packet Driver was first on the block once FTP Software
realized the difficulty of writing complete drivers for every Ethernet
board on the market.  It's a short specification that does little more
than hand out packets; consequently a Packet Driver is very small (about
2.5K in memory) but highly effective.

3Com/Microsoft came out with the NDIS specification to accomplish
the same goal, but with many enhancements.  The specification itself is
very large and difficult to understand, and the code was the same way. 
NDIS is most commonly seen on Lan Manager systems (3Com, Microsoft, DEC,
AT&T, and so on).

Then, most recently, Novell decided to tackle the board variety
problem, but by starting from the top and looking down toward the
hardware. Their ODI specification is the largest and most elaborate, and
yet in many ways is the "best" of the bunch.

Both NDIS and ODI drivers are commercial endeavors, but their
specifications are public.  However, neither NDIS or ODI makes any
effort to accommodate alternate ("competing") protocol stacks.  This is
changing with the appearance of small software converter "shims" which
have a Packet Driver interface as the common denominator.  Novell's Lan
WorkPlace for DOS is a shining example of providing an ODI driver
supporting both NetWare and TCP/IP.  You can see the pressures here: 
software vendors want a cheap way of using many boards because drivers
are expensive to write, and users want everything, including the ability
to run things requiring dual protocol stacks on a single board.

The commercial NDIS and ODI drivers should be more solid than the
volunteer effort Packet Drivers, and correspondingly harder to get
changed when bugs are found.  NDIS and ODI drivers need to come from
board vendors; Packet Drivers come, normally, from individuals and are
distributed via Clarkson University (you may get them by anonymous ftp
from omnigate.clarkson.edu).

Currently, Packet Drivers have the widest acceptance and support
base.  NDIS is probably next and ODI is too new to be counted. It takes
considerable time to fully understand a specification and produce an
acceptable quality driver.

      [Thanks to Joe Doupnik for the substance of this answer.]

* 19. How can I connect up with the Internet?
--- 09/01/92 ---
If you have a network connection with the Internet, either through a
router or a gateway, you can immediately use PMail with Charon and
Trumpet newsreader.  If you do not have a network connection, you can
try alt.internet.services and alt.internet.wanted for ideas and places
where you can purchase an internet address.  UUCP is a dial-up option
that can be found relatively cheaply (maybe even free if you look hard
enough!).

telnet:
	NCSA telnet, CUTCP telnet, are fairly common telnet packages
	for the PC.  Both use packet drivers as to maintain
	compatibility across hardware platforms.  Bother support a wide
	variety of configuration items such as RARP and BOOTP.

EMail:

	Pegasus Mail in conjunction with Charon will transport mail in
	and out from a Novell network to a SMTP server.  Charon also
	requires a dedicated machine for the email gateway.

News:

	The Trumpet news reader will connect with a NNTP server and
	provide you with news capability.  

UUCP:

	UUCP is a dial-up standard that can handle both news and
	mail.  Many shareware packages exist, and one such is called
	FSUUCP (see question 20).  Most of these alternatives will
	require that you save all mail and news messages locally, so
	this will require varied amounts of disk space depending on how
	much news and mail traffic you handle.  UUCP requires one
	machine, a modem, and a phone line at least once per night, if
	not more frequently.  Many places also allow UUCP over a
	network connection (versus dial-up).

  20. Where can I get FSUUCP?
--- 07/27/92 ---
FSUUCP is a shareware package that will handle both news and mail
through a UUCP feed, whether it be a dial-up or a network connection.
Send email to fsuucp-request@zeus.calpoly.edu for more information
about FSUUCP.

  21. What is RARP and where can I find it?
--- 07/27/92 ---
RARP: Reverse Address Resolution Protocol

This will allow a Novell 3.11 server to tell any workstation what its
IP address is.  This is very handy for student or public-access labs,
where some malicious persion might want to change ip addresses for
network hacking.  RARPSERV.NLM can be found on Novell's anonymous ftp
server, sjf-lwp.novell.com, as well as other ftp sites across the
globe.  (see also: BOOTP)

  22. Why won't RPL (remote boot) work?
--- 09/01/92 ---
There is a known problem with DOS 5 and remote boot.  You will need to
get rplfix.exe.  It will patch the disk images so that it will boot
properly.  You can find this program in dosup5.zip on Novell's ftp
site, among others.

There have been some people that have reported that an incompatible
system BIOS does not allow RPL to work.  Try a different DOS version
(non DOS 5) and see if that works.

* 23. How can I get started programming with Novell?
--- 08/19/92 ---
You can purchase Novell's API for C, or you can pick up a book
describing how to access the same functions through DOS interrupt
calls.  There are also many libraries that you can find at various
anonymous FTP sites that have essentially the same functionality as
Novell's API.

However, Novell's API is strictly for DOS, so if you are writing for
Windows, you will need to find Novell's Netware Windows SDK, which
documents their DLL's.

To program NLMs, though, I believe you still need to purchase the NLM
development kit from Novell.

There are several books you can pick up that describe how to use the
interrupt calls

	"Programmer's Guide to NetWare" by Charles Rose from McGraw
	Hill, Lan Times Book Series.  ISBN 0-007-607029-8  Extensive
	documentaion on how everything works.  Includes VAP information
	(but not NLM) Covers up through ver 3.x

	"Netware System Calls - DOS" from Novell, documents the API
	call (it is reported to be incomplete for some new Netware 3.x
	API)

	"PC Interrupts" by Ralf Brown & Jim Kyle from Addison-Wesley
	Publishing Company, Inc.  It documents basic API calls and many 
	other interrupt calls besides Novell alone. ISBN 0-201-57797-6

Some ftp'able listings of the Novell Interrupts are:

	HOST wuarchive.wustl.edu  (128.252.135.4) Location:
	/mirrors3/archive.umich.edu/msdos/info
	  FILE          245887  Nov 18 1991    inter28a.zip
	  FILE          196927  Nov 18 1991    inter28b.zip
	  FILE          135096  Nov 18 1991    inter28c.zip

	HOST ccadfa.cc.adfa.oz.au Location:  /pub/pc/progdev/docs
	  FILE                                 ?inter.txt

Here's a post from krussel about programming NLMs:
---------------8<---------- cut here ----------8<---------------
NLM DEVELOPMENT EXPERIENCES ETC.

Over the past two years I have written about five different NLMs.  Usually
it goes pretty well but I have run into quite a few little things.  First
you should join Novell's Professional Developers Program.  This enables you
to buy their 'Software Developers Kits.'  These are the latest and greatest
development tools that they have available and are much further along than
their standard 'Red Box' products.  You can call Novell and just ask for
the Professional Developers Group.  You fill out some papers and then your
in.  The greatest advantage is unlimited free technical support for all of 
the Novell development products that you own.

The next big issue is the fact that NLMs run with absolutely no protection
from each other.  If you write an NLM that messes with memory it can 
crash itself, affect other NLMs, or abend the server.  You can also abend
the server by not closing semaphores on unload, and various other little
things.  You must be 'resource responsible' when writing NLMs.  The server
will complain about anything that you use and then don't return to it
when your NLM is unloaded.  In some cases this can be just a message that
you didn't free some memory.  In other cases it can cause an abend.  In
the code that I have written I would say that at least 25% of the actual
code is required to be 'resource responsible.'

Just as your NLM can affect others you are not alone in the server.  At one
installation where several of my NLMs are in use they use TCP/IP, PSERVER,
UPS monitoring, BTRIEVE, and several other NLMS.  I have had a few instances
where I have had problems and they turned out to be some little quirk in
NW3.XX itself.  These can be very hard to track down and Novell support 
can help but often don't have the ability to duplicate your code for 
testing etc.  As a general rule I would say that it takes someone who
has been writing NLMs for a while at least twice as long to write an
NLM version of an application as it would to write a similiar application
under more mature development environments.

The good news is that NLMs are very fast and have much greater resources
available than DOS.  The libraries that come with the Novell SDK 2.0 
include built in support for the following in addition to the usual
'C' libary stuff:

	Remote File Server Support - access resources on remote servers
	Accounting Services
	Advanced Services - very low level interface to server processes
	AppleTalk Filing Protocol Services
	Bindery Services
	Bit Array Services
	Communications Services - IPX/SPX transports
	Connection Number and Task Management Services
	Device I/O Services
	Directory Services
	DOS Partition Services
	Execution Thread Services
	File Engine Services
	File Server Environment Services
	File Services
	Library API - for creating CLIB like NLMs
	Message Services - console broadcasts etc.
	Queue Management Services
	Screen Handling Services - primitive at best
	Service Advertising Protocol Services
	Stream I/O Services
	Synchronization Services - Semaphores & record locking
	Transaction Tracking System Services
	Transport Interfaces - TCP/IP using sockets or TLI
	UNIX STREAMS services

It is probably a good idea to allow for a lot more test time for NLMs than
you do for DOS products.  You need to run all kinds of tests with various
other NLMs running and throw as many variables at your code as you can.
It is not a good idea to debug NLMs on servers that are in use by people
in an existing network.  When you join the developers group mentioned above
you can buy a 250 user NW3.11 license for development use for only $500.  
I would highly recommend getting the additional Netware licenses and 
setting up a test server.  I use the same system for development and 
test.  I have a 486 with 8MB and a 200MB drive.  I partition the drive
for 150MB dos and 50MB NW386.  Then I do the development on the dos
partition and when I am ready to test I just load NW386 from the
dos partition and load my app and go.  This works best for what I
have developed.  You can also get Netware NFS for $500 for development
use only.  

Here are examples of some of the NLMs I have written and their actual 
development times.  You can use this to get an idea of what your looking
at.


Broadcast Operations Supervisor                                 4 months

This is used on air at CBS's broadcast origination center in NYC.  It 
is a replacement for BSERVER that provides btrieve services to 
DOS based clients running a client module instead of BREQUEST.  In
addition to the normal btrieve services it notifies all stations
that have a btrieve file open of any changes that are made to that
file at the time they occur.  It communicates with the client stations
using SPX.  They have two servers and this application runs in 'active
mode' in one and 'standby mode' on the other.  As changes are made
to databases on the active server they are automatically copied to 
the stand-by server.  A keep alive ethernet broadcast is sent by 
the active server once a second.  When the standby server does not
see the keep alive for 15 seconds it goes active and reboots all 
stations on the network.  They then connect to what was the standby
server and resume operation using the automatically backed up databases.
A central logging service is provided that allows all the client applications
to log status information and messages to a single database that is used
to track system activity when problems arise.

Facilities Assignment                                          2 months

This is also used at CBS in NYC.  A schedule is created on DOS based
platforms using btrieve files that hold events to be executed at 
certain times throught the day.  The NLM periodically checks the
schedule and executes any events that are pending.  For each event
the NLM initiates 1-3 TCP/IP connections to various control systems
(about 40) on the ether.  Commands are sent and then the connection
is closed.  In addition when a control system first is restarted for
whatever reason it must find out its current assignment.  This NLM 
listens on a well known port for requests of this nature and accepts
connections from these clients.  Assignments are given and then 
the client goes away.  All activities are logged in the schedule file
as being completed, having errors etc.  This application actually 
consists of three seperate NLMs.
---------------8<---------- cut here ----------8<--------------

  24. What is Burst Mode and where can I get it?
--- 08/12/92 ---
Burst mode is a protocol that will allow your server to send
larger-than-normal packets in essentially a continuous stream.  This
will increase throughput when accesing large files.  Applications
include databases, backups, and similar.

You can get Burst mode protocol (PBURST.NLM and BNETX.COM) by
purchasing a disk called Windows Workstation Diskette from 800-Netware
and asking for Updates and Upgrades.  Cost is about $30.

  25. Are there any related mailing lists?
--- 08/19/92 ---
Yes, there are a few mailing lists that deal with Novell, Pmail, Charon, and
related issues.

Subject: Novell Netware and related products and problems.
Subscription requests to: listserv@suvm.syr.edu
Average traffic: 100+ messages per day (BUSY!)

Subject: Pegasus Mail and the Charon e-mail gateway
Subscription requests to: pmail-updates@splicer.cba.hawaii.edu
Average traffic: 10-20 messages per day

Subject: AVGate asynchronous email transfer gateway
Subscription requests to: avgate-l@musicnet.ua.edu

  26. Where can I get Packet drivers?
--- 09/01/92 ---
Crynwr Packet drivers (previously known as Clarkson packet drivers) can
be found on omnigate.clarkson.edu.  

If you are running Windows, you cannot run standard packet drivers.
WINQVT and/or WINPKT are required, but I do not know any of the
solution specifics at this time, but I'm sure someone knows...

  27. What software metering packages are available?
--- 08/19/92 ---
For IBM platforms, try these:

	Sitelock from Brightworks - Requires a TSR on client.
	Difficult to bypass.  Includes virus protection.

   Meter from Saber Software - No memory overhead.  Platform
   independent.

	Direct Access Network
		Fifth Generation Systems
		10049 N. Reiger Rd.
		Baton Rouge, LA  70809

	APPMETER - This is a new product from Funk Software, reviewed
	by Glenn Fund a few months ago (pre-release).

	NetLock - This is a shareware package available from the
	anonymous ftp site simtel, in the LAN directory.  It is written
	by julian byrne from Monash University, Australia  Requested
	cost is $75.

For the Macintosh, I know only of the following: 

	LabLauncher - available from nervm.nerdc.ufl.edu, written by Leo W.

  28. What remote-dialup options do I have for Novell?
--- 09/01/92 ---
Remote LANnode is written by DCA/Crosstalk Communications.  Call Ed
Walton at (800) 274-6633 for an evaluation copy.

Other packages I have heard of are:
LANfast 
LANmodem
PCAnywhere

* 29. How can I connect my Novell Network with TCP/IP?
--- 08/19/92 ---
NOTE: These instructions are for Novell 3.x.  If anyone can write me
something up for Ver 2.x, I'd be more than happy to add it in here.

There are two halves of this problem.  One, you need to get your Server
to talk (and perhaps route) TCP/IP and then two, your workstations need
to talk TCP/IP.

First, though, a few (re)definitions.  These are what I consider
"classic" definitions, although with the growing industry of LANs,
WANs, and even GANs, the definitions keep on changing.
	gateway: passes and re-frames data between different hardware topologies
	repeater: passes data between similar hardware topologies
	router: passes data between similar/different topologies, but also
	        provides addressing and subnet control.  Because of
	        this, it must "talk" the protocol on the wire.
	packet driver: a generic interface for talking to the network board

For the server, you only need to follow the TCP/IP Installation guide.
The instructions are relatively simple.  To use the server as a gateway
or a repeater, you need the line:
	load tcpip forward=yes
in your AUTOEXEC.NCF.  Please see Question 10 for more information relating
to TCP/IP routing quirks.

For your workstations, there are multiple platforms to consider:
	On a DOS workstation, you can use five main options:
		ODI with packet drivers
		ODI with Lan Workplace
		ODI with NDIS with packet drivers
		ODI with 3rd party software
		Crynwr Packet drivers

	To use ODI with packet drivers, you will need to load up ODI
	using a net.cfg with at least these lines:
		Link Driver 3c523
			Frame Ethernet_II     # for packet driver, MUST be first!
			Frame Ethernet_802.3  # for IPX
			Protocol IPX 0 ethernet_802.3  # bind protocols to frame type
			Protocol IP 800 Ethernet_II
			Protocol ARP 806 Ethernet_II
			Protocol RARP 8035 Ethernet_II
	The packet driver is also loaded with the command line:
		ODIPKT 0 96  
	Note that 96 Decimal translates to 0x60 hex, where all of the
	"standard" packet driver programs look for the packet driver
	stub.

	To gain TCP/IP through Lan Workplace, follow the instructions.  I cannot
	offer any help here, since I don't have any experience with Lan Workplace.

	NDIS on top of ODI: (anyone care to fill in the blank?)

	Since Novell is slowly going to be moving to ODI as their
	workstation network shells, an option growing in popularity is
	ODI with 3rd party software.  In these cases, the program will
	talk directly with LSL, bypassing the need for a second level
	of "genericism" (read: packet drivers).  However, at this time,
	the only package that I know of that uses the ODI interface
	directly are Beta versions of Kermit.

	Formerly known as Clarkson Packet Drivers, the Crynwr drivers
	provide a free/shareware (Support is extra) option for TCP/IP.
	Configuration of the Crynwr packet drivers is relatively
	simple, but you will also have to regenerate your NETX with the
	BYU packet driver.  This second step will allow NETX to talk
	IPX to the server through the packet driver.

  30. Can I print from *nix -> Novell?
--- 09/01/92 ---
Yes.  Options include:
Shareware:
	Charon 2.0a    strictly a lpd gateway.
	Charon 4.0     lpd gateway and SMTP gateway.

Commercial:
	Flex/IP from Novell (as of 07/92, apx $1995 list) which
	includes lpr, lpd, and ftpd, nlms

+ 31. How can I access other TCP/IP resources on my Novell network?
--- 08/20/92 ---
If you are looking for telnet, ftp, and a few other basic utilities,
look at the NCSA telnet, CUTCP telnet, and a few other similar
utilities (anyone care to add to this list?).  

nntp news reading capability can be gained through the Trumpet newsreader.

A bi-directional lpd gateway is Charon V2.0a

E-mail access can be gained with Pmail and Charon 3.x

All of these utilities use the Packet Driver interface.
From: Garry.Lawson@f369.n633.z3.fidonet.org (Garry Lawson)
Sender: acsnet@csource.oz.au