home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Datafile PD-CD 3
/
PDCD_3.iso
/
internet
/
www
/
ArcWEB
/
Instruct
< prev
next >
Wrap
Text File
|
1995-06-15
|
6KB
|
158 lines
ArcWeb Instructions
===================
Instructions
============
This file gives some instruction on how to get ArcWeb up and running at
least on a local basis. Once this has been achieved, there are help files
supplied in HTML format. Run !ArcWeb and click SELECT over the icon bar
icon to open the index page, and then you can follow links to information
about the helper applications and their configuration. I suggest you read
the instructions for ArcWebTCP very carefully. There are instructions
further down for upgrading your current ArcWeb to this version.
If you get stuck, try the Problems file.
Before running for the first time
=================================
Copy any auxiliary applications you have into !WebHelper application. To do
this, double-click on !WebHelper and the subdirectory will be displayed.
ArcWebImg and ArcWebLcl are already installed in this directory. Before
running ArcWebTCP, you must configure your e-mail address and on-line news
server name (if you have one). See 'Configuration' below.
ArcWebTCP is ONLY for use with Acorn TCP/IP release 2 (or other network
packages which support the same BSD socket interface as Acorn TCP/IP 2 and
provide that interface in SWI chunk &41200). FreeNet does.
InetDB
======
If you want to use ArcWebTCP you need InetDB - read InetDB.ReadMe1st
for more information
Upgrading from an older version (older than 0.22)
=================================================
You must delete your current !WebCache as the new version is incompatiable
(the file structure and the index structure has changed)
To run it
=========
Launch !ArcWeb by double-click on !ArcWeb in directory viewer, or
double-clicking on HTML files. Click icon bar icon to bring up 'home' page.
All applications inside !WebHelper will be loaded automatically.
Rather than babble on at great length on what each menu entry does, I
recommend loading the Acorn !Help application and then an exploring of the
menus. !ArcWeb, !ArcwebLcl and !ArcwebImg support full interactive help on
all windows, dialogue boxes and menus.
Basically: To follow a link, click SELECT over it; to open a new page choose
Open URL from the Navigate menu over a document (or from the icon bar menu).
If you get 'Too Long' errors
============================
Move !WebCache and !WebHelper closer to the root directory of the device
on which they are stored.
Configuration
=============
If you are going to be using ArcWebTCP, you MUST reconfigure the e-mail
address and the news server address. Click SELECT over the ArcWebTCP icon
bar icon to open the configuration window. You may wish to set up proxy
servers for HTTP, FTP, gopher and WAIS. ArcWebTCP will handle FTP and HTTP
itself if you want it to.
The 'home page' is controlled by an environment variable ArcWeb$Home. If
this variable is not set when ArcWeb is run, it will set it to a default
document within an ArcWeb subdirectory.
The 'cache directory' is controlled by an environment variable
Arcweb$CacheDir. If this variable is not set when ArcWeb is run, it will
set it to a default directory within an ArcWeb subdirectory. The !WebCache
application supplied contains a !Boot file which initialises this variable
to a subdirectory of itself. This allows !ArcWeb to be stored in a R/O FS.
The 'authentication database' holds a cache of servers and their realms which
have required authentication in the current session. By default, it is
wiped when ArcWebTCP exits (but can be reconfigured in the config window) as
a security precaution. Its location is controlled by ArcWeb$AuthFile which
is set by !WebCache or !ArcWebTCP when it is run and !WebCache hasn't set
it yet.
To flush the cache, use the menu entry in ArcWeb version 0.20. (Earlier
versions required you to open the !WebCache directory). You can wipe it
all or just the images.
Don't put extra files in the cache directories. The cache manager will find
these and remove them. By default it allows 75 files to be cached (no size
limit) so it doesn't want other things clogging up the directory. The cache
manager will remove anything not in the index, and remove anything from the
index which doesn't exist in the sources directory. IF the Cache Manager
cannot remove a file (because it is open for example), it will leave it
there.
Every 60 seconds, the cache is checked for documents which have passed their
expiry date. These old documents are removed (unless they are currently
being fetched, or are currently being viewed, or if it is inlined image
which is part of a currently being fetched/viewed document.) This facility
can be disabled on the ArcWeb options menu.
Choices file.
Configuration of ArcWeb
=======================
I am currently working on a configuration utility for ArcWeb which will
provide a more sensible approach to change fonts and default option
settings.
Full Icon Bar Problem
=====================
From version 0.13 this is not a problem as ArcWebLcl and ArcWebImg are
supplied configured not to install icon bar icons. ArcWebTCP is
configured to install an icon so that you can change the proxying
information. For an explanation of proxying and ArcWebTCP use, load
!ArcWeb and open the default page (click on icon bar icon) and follow
the link to the ArcWebTCP information page. Each program decides whether to
install an icon by checking its command line. If it contains -iconbar then
it will install one. If it contains -noiconbar and doesn't contain -iconbar
then it won't. If it contains neither then it will. When ArcWeb autostarts
applications, it uses -noiconbar. This means that any applications
autostarted by ArcWeb (except ArcWebTCP which needs its icon for email
sending) won't have icon bar icons (unless you edit the !Run file), and if
you run them manually then they will.
See the Problems file for more on how to reconfigure these programs.
Comments and bug reports via e-mail as below, please.
Thanks for your help,
Stewart
--
Contact Addresses
=================
Mountbatten Building, Level 3
Department of Electronics & Computer Science
Southampton University
Highfield
Southampton
SO17 1BJ
E-mail: S.N.Brodie@ecs.southampton.ac.uk
WWW : http://louis.ecs.soton.ac.uk/~snb94r/