Contents of the DVNOVL.DOC file
This document is an anecdotal of my experiences bringing up
DV on a Novell Network.
The network in question has a wordprocessor (Office Writer),
and a database (dbase 3+) and Lotus 2.0 in shared areas, and
Kedit in a private directory.
On the development workstation (an XT) exist Framework II, Access
(which is used to run dbase on a net) and ATO (at the present
time, all ATO files are local).
Further, the workstation has its memory amount dip switches set
to 64K (switches 3&4 are OFF - this is undocumented, but works -
thanks to Gary Saxer for pointing it out) and a 2MB Rampage
board. Maximum window size is about 500K.
Changed Autoexec.bat to:
subst e: c:\frame20\newmods * A: to E: are for local use
* here, E: is for FW II ease
anet30p * loads Novell network shell
f: * change to login drive
c: * change to local drive
* load any global TSR's here
dv * DV start, from dist disk,
* except that I use XDV
Added a program called NOVELL (NO) to the DV menu.
(Note: I always open this window first because it logs me
onto the NET).
The Setup is as follows:
Start Command = NETSTART(.bat)
CED * or any other TSR's you like
Path = F:\LOGIN * use whatever you want as your
* "home" directory
Size = 460
OPTIONS (x = highlighted, o = not highlighted)
x Writes o Disp
x Runs o Uses
o Can be x Allows type ahead
x Allows TV x Allows script
o Close o Runs
1) The path in the netstart simulates what novell
normally does to the path command when you login. (i.e.,
if you login without using DV and say ask what your current
path is (just issue a PATH with no parameters, like in DOS)
your response will be similar to the above. Novell starts with
Z: for drives that you map as search drives and "counts"
backwards. The login that I use has five search drives mapped,
hence the letters V thru Z. Obviously, you will have to make
appropriate adjustments for yourself.) The reason for the addition
of the db3plus subdir to the path is that I use this window much as
I used the DOS window before installing the net.
2) Setting the F:\LOGIN dir as the path parameter causes DV
to issue a switch for me to that drive\dir. And the Login command
functions normally. Note that opening another Network window
would issue another login command, which would effectively logout
your previous session. If you have a need for multiple Network
windows (which works fine), take the login command out of the
3) Options: the only options I'm sure of now are the four
corner ones and the swapping one. Writes directly to screen is on
so that I get a full sized window on startup. It also allows me
to start any program on the server without concern. Close on Exit
to DOS *MUST* be off. When I had this one on, lots of network
commands (e.g., SPOOL, MAP, etc.) caused the window to close.
Displays graphics is off (as it is for all of my applications
except spreadsheets) because its use only wastes 12K if you don't
need to use graphics screens. If I ever need it on, I create a
separate window for it. Runs from Floppy is off (self-evident).
Swapping must not be allowed. If you inadvertently swap out the
network, you'll lose addressability to all of your mapped drives.
The others are in experimantal stages, and as I find reasons for
changes I'll modify this document.
Adding other applications to DV
The obvious preliminary to this is to load the programs onto the
net and test them without regard to DV. Also, since I had the
programs running under DV before the net was installed (cf.
DVCFG2.DOC) I did not have to worry about the DV install program
finding them. If I were to install DV after getting the net, I'd
have to use the Add Program feature extensively.
Running Lotus 2.0
I have this in a shared subdir on the net. It was installed as
per the instructions in the Lotus manual for installing on a hard
disk, but running from floppy. The purpose of this is to have the
a standard lotus installation (except for driver sets) in the
shop and to avoid wasted space on each workstation's hard disk.
Since the use of the program requires a key disk in drive A on
each workstation, I cannot see where Lotus Devel. Corp would have
any complaints. The default lotus files subdir, by the way, is
c:\spread which causes all worksheets to be kept on the local
disk. There is a shared (read-only) subdir of company developed
model worksheets that can be accessed by the users.
Running dbase 3 plus
This one gets a bit of special handling. Ashton Tate has
developed a scheme whereby one can load about 90% of the program
onto the server (goes under the name of Data Base Administrator
DBA) and the other 10% on the local hard disk (includes the copy
protect scheme). Once having done this, you merely have to start
the workstation part (goes under the name of Access) and tell
access where the DBA is located. Since not all workstations have
Access installed and since you have to map the DBA before you
start, I have a small batch program that first does the
appropriate checking. Text of the batch program follows:
if EXIST c:\db3plus\access.com GOTO found
if EXIST g:dba.ld1 goto process
echo You must include the following statements in your SETLOGIN
echo map g:=sys:db3plus
echo map s*:=g: (where * is your next available search number)
echo also, map to any subdir that has files for dbase's use, if
echo you are unsure which to include, type out your config.db and
echo use the ones listed in the path command found there
echo Sorry, Access is not installed on this workstation
Note: This batch file should go into your sys:public subdir with
flags set for SRO. Also note that the path statement that
reads PATH C:\DB3PLUS;Y:.; assumes that Y: is mapped as a
search path for SYS:PUBLIC Also, go into the Change Program
screen on DV and set Y:\PUBLIC as the Path to Data Files parameter.
Installation of db3+ for Novell and DV requires that you make
very careful use of the Writes Directly... and the Runs in
Foreground .... options. In short, leave them both on or both
off, and if both off, don't run anything that does screen
Running Framework II
Note: In order to run FW II under DV you must have over 400K
available. I run it in a 460K window. Note that FWII will take
over all of the remaining memory on the Rampage(s) you have
installed so if you want to have multiple windows with FW as one
of them you will have to load it last. If not, then opening
another window will cause a swap to disk, which tends to lead to
the BOS (my guess is that FW space management and DV space
Also, FW II requires a fair amount of horsepower. Either go into
DV SETUP to allocate a larger time slice to the foreground or
else CRTL-NUM LOCK the inactive partitions.
DV is smart and so is Novell, but there is still an open question
as to printing from multiple partitions. Will test further.
Preliminary results are:
Run the SPOOL command from your SETLOGIN (Use #SPOOL). This will
cause the Novell software to open a spooler for all of your
output. Then write to the printer as you would normally do. I've
successfully written from FW II, Officewriter(*), and the command
line ( COPY FOO.BAR LPT1 By the way, do not use the DOS print
command under DV, it fouls up memory management. I have a CED SYN
that changes PRINT into COPY; if you don't have/use CED then
rename PRINT to avoid using it accidentally). So long as you
don't have multiple partitions writing at the same time, all is
OK. Then when you are done, switch to the Novell window, issue an
ENDSPOOL followed by another SPOOL to close the original spool
file (and start it printing) and to open another spooler so as to
be ready for future output.
(*) You MUST use the network version of OfficeWriter if you are
going to use it under DV on the net. The non-net version works OK
under DV on a stand-alone machine, and it works OK on the net
with all flags set to NRW (non-shareable, read-write), but all
three together lead, inevitably (at the point where you save or
print the document) to the BOS.