home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Current Shareware 1994 January
/
SHAR194.ISO
/
networks
/
pcg3r112.zip
/
RELEASE.111
< prev
next >
Wrap
Text File
|
1993-08-02
|
5KB
|
161 lines
This is the release note file for PC Gopher III, version 1.1.1, released
3 August 1993.
---------------------------------
Fixed Bugs
---------------------------------
* the active query counter wasn't being properly decremented in all
cases, leading to bogus "no more than two active queries allowed"
messages
* the option to disable DOS shells was being ignored
---------------------------------
Added Features
---------------------------------
* gopher can now read the values of environment variables placed in
GOPHER.INI (see below)
* added five parameters to GOPHER.INI:
- in the [paths] section:
bookmark_file = .\GOPHER.BMK ; filename for bookmarks
binary_save_dir = . ; default directory for binary file saves
text_save_dir = . ; default directory for text file saves
- in the [prefs] section:
allow_shells = YES ; YES to allow DOS shells, else NO
allow_swap = YES ; YES to allow swap to disk
; during shells, else NO
---------------------------------
Changes
---------------------------------
Commandline Switches
--------------------
There's only one switch accepted now: the path to GOPHER.INI. If you
want to, you can put environment variables in GOPHER.INI, but be aware
that the environment space is LIMITED, and that filling it up may have
UNPREDICTABLE CONSEQUENCES. You can always expand the enviroment
space (see your DOS manual), but that takes memory that could
otherwise be used for large file or directory viewing...
There's been some concern about removing the @configfile option; I got
rid of it because I think it's confusing to have two config files, one
overriding the other but only in some cases, etc., etc.
I can't imagine a scenario that would require the @configfile option,
especially with the addition of environment variables to the
GOPHER.INI file. If your needs still aren't met by this new
arrangement, send me mail.
Here are the possiblities as I see them, and the suggested options:
1. Gopher lives on user's local drive
--------------------------------------
Just use GOPHER.INI. If you MUST, define environment variables
for things, and put them in the file. For example,
bookmark_file = %ugly_var
would look in the environment for the value of ugly_var, and
use that for the name of the bookmark file.
2. Gopher lives on a shared network drive
------------------------------------------
There are two options:
1. Use a separate copy of GOPHER.INI for each user. To run
gopher, type
GOPHER D:\MOO\GOPHER.INI
D:\MOO can be a local or network drive.
Advantages:
- No use of environment space.
- User can change preferences and settings without
interfering with other user's preferences and settings,
by editing GOPHER.INI.
Disadvantages:
- If you have 8 million users sharing the same copy of
gopher, you'll need 8 million copies of GOPHER.INI, one
for each user.
This is exactly the same as the old @configfile option.
Actually, since GOPHER.INI is just a plain ASCII text file,
some clever person could write a utility for server
administrators to use to generate 8 million copies of
GOPHER.INI.
2. Use a shared copy of GOPHER.INI. Use environment variables
from the user's machine to handle addressing. For example, if
the user's IP address is 9.9.9.9, you could set an
environment variable called "fooIP" to "9.9.9.9", like this:
SET FOOIP=9.9.9.9
and in the shared copy of GOPHER.INI, set the "pc_ip" line to
look like this:
pc_ip = %FOOIP
Advantages:
- Less work for server administrator, only need one copy of
GOPHER.INI
- User can change preferences and settings without
interfering with other user's preferences and settings,
by setting environment variables.
Disadvantages:
- Environment variables are a waste of memory, and filling
the environment space can have unpredictable
consequences.
---------------------------------
Unfixed Bugs
---------------------------------
* if there's a non-single-window mode browser on the screen, and you
switch to single-window mode, you have to open a new browser to get
the "Go Back" button to appear
* in single-window mode, a failed query shouldn't close the window
* in single-window mode, the list of items is sometimes incomplete
until the scrollbar has been moved.
* still no help system
* empty directories shouldn't be displayed
* MS-DOS and 64k segments. This bug is unlikely to be remedied in the
near future.
Have fun, and keep reporting bugs!
Daniel A. Torrey
Chief Cook and Bottle-washer, PC Gopher
daniel@boombox.micro.umn.edu