home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Hall of Fame
/
HallofFameCDROM.cdr
/
lan2
/
blts.lzh
/
BLT10
< prev
next >
Wrap
Text File
|
1989-09-14
|
5KB
|
95 lines
The following information was compiled by Borland technical support and is
posted unmodified (except for this message and our address) as taken from
CompuServe's BORAPP forum.
============== INSTALLING PARADOX 3.0 ON THE LANtastic NETWORK ===============
3/16/89
The LANtastic Network, by Artisoft (575 E. River Rd., Tucson, AZ 85704 (602-
293-6363)) is a low-cost non-dedicated network that is fully NETBIOS
compatible. Paradox 3.0 was installed and tested on LANtastic (version
current as of 3/16/89). Trasfer rate on the network boards is 2mbs, not
bad considering the cost of the entire net. The following paragraphs walk you
through the installation.
Installation of the LANtastic network itself is very straightforward and
easy. The purpose of this technote is NOT to explain the installation of
LANtastic, but rather the installation of Paradox 3.0 on LANtastic. It is
assumed that you have installed LANtastic and have it running. Your file
server, which is also a workstation, has a C: drive and you are logged in
as the supervisor (ie. in LANtastic lingo, the "manager", if you followed
the LANtastic installation accordingly).
In terms of LANtastic, there's really only 1 thing you must do in order to
prepare it for use with Paradox: you must set up a directory to be used as
the location of the PARADOX.NET file - this will also be the shared data
directory. As per the Paradox manuals, this directory should be called
\PDOXDATA
All users should have all rights to this directory since it will be a
shared directory. The PARADOX.NET control file will be stored in this
directory. From the root directory on your C: drive, type in
MD PDOXDATA
You now have a \PDOXDATA directory.
Assuming you're logged in as the "manager" and sitting at the DOS prompt,
load the NET_MGR.EXE program supplied by LANtastic. This program will
allow you to map a share-name to the C:\PDOXDATA directory. When the
NET_MGR program loads, choose the "Network access information" choice
from the menu. You will then get a list of your current share-names and
directories that they're linked to. Press the [Ins] key on your keyboard
to add a new share-name. You'll be prompted for the "..name of the link
directory or @Device". Type in "PDOXDATA" and press [Enter]. You'll then
be returned to the list of current share-names. Select the PDOXDATA choice
and press [Enter]. You'll then get a menu of choices, one of which will be
"Link path". Choose this option and type in "C:\PDOXDATA" and press [Enter].
Now press [Esc] a couple of times to return to the DOS prompt.
You'll now have to edit you AUTOEXEC.BAT file and add the following line:
NET USE E: \\SERVER1\PDOXDATA
where SERVER1 is the name you gave to your file server when you installed
LANtastic. That's it for the LANtastic end of it!
Now install Paradox according to the directions in the Paradox manuals.
Log onto the C: drive of the file server as "manager" and make sure you're
in the root directory and the Paradox installation is in your A: drive,
type in:
A:INSTALL
Answer "Yes" when asked if you'll be installing Paradox on a network, choose
"Other" for network type (number 7) and for the location of the network
control file, type in "E:". Continue the installation as instructed by the
Paradox manuals.
Once Paradox has been installed, go to the \PARADOX3 directory and use the
DOS ATTRIB command to make all the files except PARADOX3.SOM read-only:
ATTRIB +R *.*
ATTRIB -R PARADOX3.SOM
When you load Paradox, load it with the -SHARE option:
PARADOX3 -SHARE
This lets Paradox know that you want it to treat the local drive (the
server's C: drive) as a network drive. This is necessary since this is
a non-dedicated network. Be sure to play the CUSTOM script for each user
to specify their username and the location of their private directory.
That's it!
I tested this on 2 Compaq portables, 2 net boards supplied by ArtiSoft,
each station had 640K RAM and a monochrome monitor. Performance was good
and all file/record locking worked correctly.
Peter M. Jagielski
Borland International
Technical Support Engineer