Category : Paradox DBMS
Archive   : TECH91.ZIP
Filename : TI618.ASC

PRODUCT : Paradox NUMBER : 618
VERSION : 3.x
OS : PC DOS
DATE : September 11, 1991 PAGE : 1/3

TITLE : Paradox Network Installation Overview




Network Installation Overview
(Quick summary of the Network Administrator's Guide)

These notes are applicable to any Network using Paradox.
-----------------------------------------------------------------

You must create and map/link 3 special directories:

1) Paradox system file directory
2) Data file directory
3) User Private directory
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³1) \Paradox ± After installed give ³
³ minimum read, open, ³
³ search rights ³
³ ³
³øProgram Files ³
³øCustom.sc and Custom.lib ³
³ ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³2) \Pdoxdata (Name is optional, could be any directory. Do not³
³ make \Pdoxdata a subdirectory of \Paradox.) ³
³ ± Give all rights - ³
³ read, write, create, ³
³øShared User Data delete. Parental not³
³øParadox.Net necessary (for the ³
³ || creation of dirs).³
³(Will be created as ³
³ first user loads Paradox) ³
³ (Controls sharing of data ³
³ and serial numbers) ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³3) \Private ± Give all rights ³
³ Can be local hard ³
³ disk directory ³
³øEach user needs unique Private dir ³
³øTemp files - Answer ... ³
³øScratch/Sort files ³
³øParadox.CFG (Default printer, ³
³ User Name, ³
³ Private Dir Location) ³
³ (First .CFG file found on path will be used!) ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ













PRODUCT : Paradox NUMBER : 618
VERSION : 3.x
OS : PC DOS
DATE : September 11, 1991 PAGE : 2/3

TITLE : Paradox Network Installation Overview




Tips:

o Read the first two chapters of the Paradox Network Administrator's
Guide and the chapter on "Other" Networks.

o Start Paradox from the Private Directory.

o Have Paradox and the Private directories on the DOS PATH with the
Private directory appearing before Paradox.

o Do NOT make the \PDOXDATA directory a child directory of \PARADOX.
On some networks the child directory cannot have greater rights than
the parent.

o Have every user reference shared directories by the same logical
drive name (NOT C:\something).

o If on a non-dedicated network such as LANtastic, do not let users
work from the server via a physical drive name such as C:, but
rather make sure to work from logical drives like E:.

o Create a PARADOX.CFG for each user as per the Network
Administrator's Guide chapter "Configuration".

o Once installed eliminate PARADOX.CFG from the Paradox system file
directory since each user will have their own copy.

o On most Networks of type OTHER use -SHARE option to start Paradox
(Paradox -share). This will usually mean that you have to invoke
the DOS SHARE command as well.

o If you are using Paradox version 3, substitute "Paradox3" where you
read "Paradox" above.























PRODUCT : Paradox NUMBER : 618
VERSION : 3.x
OS : PC DOS
DATE : September 11, 1991 PAGE : 3/3

TITLE : Paradox Network Installation Overview




Common Questions: (See also Network Administrators Guide)


What are the causes for the message "Unable to record lock unlock
Paradox.Net"?

o Insufficient rights in PDOXDATA directory.

o Linking or mapping statements do not match the location specified at
install time for the Paradox.Net (Run Nupdate.exe from the \Paradox
directory or the install disk to reset location, or redo network map
or link statements).

o Finding someone else's PARADOX.CFG file along PATH at startup.

o Presence of a leftover *.lck file due to someone abnormally exiting
Paradox. (With no one in Paradox the presence of a *.lck file
indicates an earlier problem. When no one is in Paradox you can
delete any *.lck files or even the Paradox.net file to start
afresh).

Why the message "Not enough disk space to complete operation"?

o On networks, Paradox disk space requirements refer to the User's
PRIVATE directory. You need between 2 and 3 times the size of free
disk space available in the User's PRIVATE directory for the tables
in question. Use Tools/Net/SetPrivate to test Private Directory
location.

Is there a way around the message "Sharing Violation"?

o This message may occur with multiple users (or sessions such as in
Microsoft Windows) sharing the Paradox system files. This message
has been reported on Networks such as Banyan's Vines and Lantastic
from Artisoft. Another symptom of the same problem is when a second
session cannot start Paradox.

o One method of getting beyond this message is to use the DOS ATTRIB
Command to set *.EXE Files within the Paradox directory to READ ONLY
(eg. ATTRIB +R *.EXE from the Paradox directory prompt).