GOPHERD installation
- copy GOPHERD.NLM and customized version of GOPHERD config file to SYSTEM 
  directory
- install HellSoft's name resolver RESOLV.NLM 
  (available at novell.felk.cvut.cz)

GOPHERD loading
at console prompt type 'load gopherd sys:system\gopherd.ini <Enter>', where 
gopherd.ini stands for GOPHERD config file (note that CWD for NLM is SYS:)

GOPHERD config file
items :
	- log_to_screen = 0 or 1	(default 0)
		logging of incoming client requests to GOPHERD screen

	- log_to_file = 0 or 1		(default 0)
		logging of incoming client requests to GOPHERD log file
	- log_answers = 0 or 1		(default 0)
		logging of outgoing items info
	- log_file = name_of_log_file	(default 'gopherd.log')
		when log_to_file equals 1, logs of client requests will 
		be written to this file

	- sys_admin_person = name_of_novell_server_administrator
	- sys_admin_email  = supervisor@kmat.fjfi.cvut.cz
		name and email address of system administrator for error
		reporting to client; also used when ADMIN block not specified
		for requested Gopher+ item

	- sys_error_text_file = name_oc misc_error_text_file
		text used for reporting not recognized errors

	- root_dir_file = name_of_root_gopher_dir_file
		name of file describing root directory-menu
		(format of this file is described in 'GOPHERD dir file' section)

	- default_gopher_addr = xy.cnbcm.cxksk.shdj
	- default_gopher_port = 70
		gopher server name and port used for items that has no info in 
		dir file about their location

	- default_text_view = Text/plain Text
	- default_binary_view = Application/octet-stream
		for Gopher+ items (gplus=yes) with no view explicitly 
		defined, default view is constructed for compatibility
		with Unix/VMS Gopher client 2.016 (thanks to J.Lance Wilkinson)

	- gplus_client_must_notify = 0 or 1 (default 0)
		When 1, GopherD NLM will use Gopher+ extensions in answers 
		only when client requests this info. Switch is intended only 
		for compatibility with old (pre Gopher+) clients.

GOPHERD dir file
format is the same as used by Windows *.ini files

[Selector] : for local items selector is constructed as a path from the top
	      to this item
	     for remote items only this section heading is used as selector

type = one of {directory,text_file,binary_file,userlist,finger}

string = string displayed on client screen, when selecting items

file= name of file
	- if type == directory, this is name of dir file with same format
	  as root_dir_file
	- if type == text_file, this is name of text file, which will be sent 
	  to client
	- if type == binary_file, this is name of binary file, which will be 
          sent to client

addr= address of gopher server, where item is placed (entry not present means
      default_gopher_addr from GOPHERD config file will be used)

port= port of gopher server, where item is placed (entry not present means
      default_gopher_port from GOPHERD config file will be used)

gplus= one of {yes,no}, default is no, specifies whether item has 
       Gopher+ attributes

admin= name and e-mail of administrator of this item (entry not present means
       sys_admin_person and sys_admin_email form GOPHERD config file will 
       be used)

userlist_server= if(type==userlist) 
                   name of Novell server to ask about connected users
                 if(type==finger) 
                   name of host to ask via FINGER protocol

userlist_user   = name of user used to establish connection to Novell server 
userlist_pass   = password of user used to establish connection to Novell
                  server 

viewX=string;filename;filter
     'X' is number of view (between 1 and 4). 'string' is name of the view, 
     'filename' is name of file, where the view is stored, 'filter' is not 
     used yet (will be used for Czech character coding).