home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1993 #2
/
Image.iso
/
database
/
p4w_all.zip
/
TI1251.ASC
< prev
next >
Wrap
Text File
|
1993-02-02
|
25KB
|
793 lines
PRODUCT : Paradox for Windows NUMBER : 1251
VERSION : 1.0
OS : WIN
DATE : February 2, 1993 PAGE : 1/12
TITLE : Installing Paradox for Windows on a Network
Intended Audience:
This Technical information bulletin is intended for network
administrators.
Prerequisites:
This document assumes that Microsoft Windows was installed
correctly. This means that the steps in the Windows Getting
Started guide, Chapter 1, and Windows User's Guide, Chapters 14,
15, and Appendix A were followed. If your Windows installation
does not conform to those standards, Paradox for Windows may not
be able to run successfully. This document also assumes you have
read the Paradox for Windows Getting Started guide, Chapters 1,
2, and 15.
Purpose:
This Technical Information Sheet will help you install Paradox
for Windows on a network file server.
There are two possible configuration combinations when installing
Paradox for Windows on a network file server:
1. Windows on local hard disk, Paradox for Windows on file
server.
2. Windows on file server, Paradox for Windows on file
server.
There are a number of steps required to install Paradox for
Windows. Use the worksheet at the end of this document to
prepare your Paradox for Windows installation.
IMPORTANT: Quattro Pro for Windows must be installed before
Paradox for Windows. The Quattro Pro for Windows installation
does not check for the existence of Paradox for Windows, while
the Paradox for Windows installation does check for the existence
of Quattro Pro for Windows. If Quattro Pro for Windows is
installed after Paradox for Windows, all of the ODAPI
configuration information will be lost.
PRODUCT : Paradox for Windows NUMBER : 1251
VERSION : 1.0
OS : WIN
DATE : February 2, 1993 PAGE : 2/12
TITLE : Installing Paradox for Windows on a Network
As an example, this document will assume that you are using a
single volume Novell Netware v3.11 server and Windows Program
Manager as the Windows shell program.
I. Preparation steps
There are a few preparation steps before beginning the actual
installation of Paradox for Windows. These involve checking the
existing application software on your network. You will need to
check for the existence of ObjectVision 2.1, Quattro Pro 4.0 for
DOS, Quattro Pro for Windows, Paradox 4.0 for DOS, and any other
Paradox Engine 3.0 applications. Each of these applications are
Paradox aware, and you will need to know the location of the
Paradox Network control file that each program uses. If there
are no Paradox aware applications on your network, you can skip
ahead to the section titled "Windows on the Local Hard Disk" or
"Windows on the file server".
Quattro Pro 4.0 for DOS is capable of using Paradox tables and
network locking protocols. You can determine the location of the
Paradox Network Control File Quattro Pro 4.0 for DOS is using by
selecting Options | Other | Paradox | Directory from the Quattro
Pro 4.0 menu. This information should be placed in step 5 of the
worksheet.
ObjectVision 2.1 uses the Paradox Engine 3.0 to connect to
Paradox tables. You can determine the location of the Paradox
Network Control File ObjectVision 2.1 uses by running the program
PXENGCFG.EXE, which should have been installed in the
ObjectVision directory. Once PXENGCFG.EXE is running, choose
File | Network Configuration. This window will specify the
Paradox Network Control File Path and the Locking Protocol. If
the Locking Protocol is set to Paradox 4.0, then write the
Paradox Network Control File Path in step 7 of the worksheet.
Quattro Pro for Windows also uses the Paradox Engine 3.0 to
connect to Paradox tables. Since Quattro Pro for Windows uses
the Paradox Engine, you can determine the location of the Paradox
Network Control File by running the program PXENGCFG.EXE, which
should have been installed in the Quattro Pro for Windows
directory. Once PXENGCFG.EXE is running, choose File | Network
Configuration. This window will specify the Paradox Network
Control File Path and the Locking Protocol. If the Locking
PRODUCT : Paradox for Windows NUMBER : 1251
VERSION : 1.0
OS : WIN
DATE : February 2, 1993 PAGE : 3/12
TITLE : Installing Paradox for Windows on a Network
Protocol is set to Paradox 4.0, then write the Paradox Network
Control File Path in step 12 of the worksheet.
The Quattro Pro for Windows DataBase Desktop uses an earlier
version of the same ODAPI engine that Paradox for Windows uses.
You can determine the location of the Paradox network control
file that the DataBase Desktop uses by running the Configuration
Utility, ODAPICFG.EXE. This program should be installed in the
Quattro Pro for Windows directory. Run ODAPICFG.EXE, and copy
the Network Control file directory to step 13 of the worksheet.
For other Paradox Engine 3.0 applications contact the programmers
for the Paradox locking protocols being used and the Paradox
Network Control File locations.
Paradox 4.0 for DOS uses the Paradox 4.0 locking protocol. You
can determine the location of the network control file by running
NUPDATE.EXE. NUPDATE.EXE is located in the same directory as
Paradox 4.0 for DOS. Run the program, press <Enter>, <F2>, and
<F2> to get to the fourth screen in this program which lists the
location of the Paradox network control file. Write this
information into step 16 of the worksheet.
If there are other Paradox aware applications on the network,
there is probably a shared working or data directory for Paradox
tables. If so, write the main shared data directory into step 17
of the worksheet.
II. Windows on Local Hard Disk
At this point you should have answered all the applicable
questions on the worksheet through number 17. If the answer to
Question 2 of the worksheet is "Yes", please go to the section
titled "Windows on the File Server", otherwise continue with this
section.
The next step in the process is to decide where to install
Paradox for Windows. For our example we are using
F:\WINAPP\PDOXWIN as the destination directory for Paradox for
Windows. You may use some other directory. Each user needs to
have read/open/scan/executable rights (or the equivalent) to this
directory. Write the name of this new directory into step 18 of
the worksheet.
PRODUCT : Paradox for Windows NUMBER : 1251
VERSION : 1.0
OS : WIN
DATE : February 2, 1993 PAGE : 4/12
TITLE : Installing Paradox for Windows on a Network
The next directory to decide upon is for the ODAPI files. Since
Windows is not installed on the file server, there are two
possible locations for the ODAPI files: the Paradox for Windows
directory, or a special ODAPI directory. If Quattro Pro for
Windows is installed on the file server, there should already be
a special directory for the ODAPI files (worksheet, step 10),
write this directory into step 19 of the worksheet. If Quattro
Pro for Windows is installed, but there is no special directory
for the ODAPI files, or if there are other Paradox aware
applications on your network, you should designate a new
directory for the ODAPI files. We suggest F:\WINAPP\ODAPI. This
new directory must be on the path of each user working with
Quattro Pro for Windows or Paradox for Windows. Each user should
have read, open, scan, execute rights to that directory.
However, if Paradox for Windows is the only Paradox aware
application on your network, it is permissible, although not
advised, to install the ODAPI files in the Paradox for Windows
directory (worksheet, step 18). After deciding where the ODAPI
directory will be, write its location into step 19 of the
worksheet.
Please continue with the section titled "Combined Steps"
III. Windows on the File Server
If Windows is installed on the file server, see the answer to
question 2 of the worksheet, continue with this section.
The next step in the process is to decide where to install
Paradox for Windows. For our example we are using
F:\WINAPP\PDOXWIN as the destination directory for Paradox for
Windows. You may use some other directory. Each user needs to
have read/open/scan/executable rights (or the equivalent) to this
directory. Write the name of this new directory into step 18 of
the worksheet.
Since Windows is installed on the file server, use that directory
as the location of the ODAPI files. Fill in question 19 of the
worksheet with the answer to question 3 of the worksheet.
PRODUCT : Paradox for Windows NUMBER : 1251
VERSION : 1.0
OS : WIN
DATE : February 2, 1993 PAGE : 5/12
TITLE : Installing Paradox for Windows on a Network
IV. Combined steps
The location of the Paradox Network Control file should be the
same for all Paradox aware applications on the network. This is
to allow the highest level of data concurrency among Paradox
users. The worksheet hints at this in steps 7, 12, 14, 16, and
20. If there are no other Paradox aware applications on the
network, you need to create a new directory for the Paradox
Network Control file. Since all Paradox users must have read,
write, create, and delete rights (or the equivalent), we suggest
using a sub directory of the main shared data directory, such as
F:\DATA\PDOXDATA. Write this information into step 20 of the
worksheet.
The last step before running the installation program, requires
you to determine the location of the Paradox for Windows sample
files. There are three different sets of sample files: Sample
Tables, Sample Application, ObjectPAL Examples. Each set of
files needs its own directory. Since all users will need read,
write, create, and delete rights (or the equivalent) for these
files, it would make most sense to install them with the main
shared data directories. If there are no other Paradox aware
applications, place the sample files in sub directories under the
Network Control File directory (worksheet, step 20). If there
are other Paradox aware programs, place the sample files in sub-
directories under the existing shared Paradox table directories
(worksheet, step 17). Write this information into step 21 of the
worksheet.
Now you are ready to actually run the installation program for
Paradox for Windows. (Note: The installation program requires
about 1MB in your personal Windows directory and after the
installation program has completed, you may delete the file
PDOXINST.EXE). Use the answers to the questions on the worksheet
to fill in the information on the installation options screen.
Fill in your name, the name of your company, and the serial
number found on disk one of the Paradox for Windows distribution
diskettes. The installation program will fill in the Install
From information. Use the answer from question 18 of the
worksheet for the Install To directory. Use the answer from
question 19 of the worksheet for the location of the ODAPI
Directory. Press the <Subdirectories> button and fill in the
information for each of the sample directories from question 21
PRODUCT : Paradox for Windows NUMBER : 1251
VERSION : 1.0
OS : WIN
DATE : February 2, 1993 PAGE : 6/12
TITLE : Installing Paradox for Windows on a Network
of the worksheet. Press <OK> to return to the main installation
screen. Press <OK> to continue the installation.
Now that Paradox for Windows has been successfully installed onto
the file server, you will need to prepare it for other users on
the system.
Additional user counts
When you purchased Paradox for Windows, that copy of Paradox for
Windows also had a single user count. If more than one user will
be working with Paradox for Windows at the same time, you must
purchase additional user counts. The serial numbers for those
additional user counts are installed using the Serial Number
Utility installed with Paradox for Windows. Run the Serial
Number Utility icon in Program Manager.
NOTE: You may receive an error message dialog box that states
"BWCC.DLL is out of date or could not be found. Press OK to
update the file, or press CANCEL to quit." This error message
means that one of the Borland shareable library files is either
an older version or does not exist. Press <OK> to correct this
situation.
Now follow the instructions in the Paradox for Windows Getting
Started guide pgs. 183 and 184 to add additional user counts to
Paradox for Windows.
ODAPI Configuration
The ODAPI engine (Object Database Application Programming
Interface) configuration file holds some network specific
configuration information. Specifically the location of the
network control file. It also holds the list of database
aliases. (For more information about aliases, see the Paradox
for Windows User's Guide, chapter 3). It will be located in the
same directory as the ODAPI files (worksheet, step 19).
Run the Configuration Utility program in the Paradox for Windows
group. Type in the location of the Paradox Network Control file
(worksheet, step 20). Press <OK>. Paradox is now ready to
access data on the file server. Those users who want or need
their own ODAPI.CFG file can copy it from this location.
PRODUCT : Paradox for Windows NUMBER : 1251
VERSION : 1.0
OS : WIN
DATE : February 2, 1993 PAGE : 7/12
TITLE : Installing Paradox for Windows on a Network
Tutility Configuration
It is a fact of DOS database life, that from time to time, data
files will be damaged. This is a limitation of the MS-DOS
operating system error checking routines. We provide a utility
program that will help you rebuild damaged files: TUTILITY.EXE.
Will each user be allowed to use the table rebuilding utility
TUTILITY.EXE? If so, copy the TUTILITY.* files from the Paradox
for Windows directory to the network control file directory
specified above (worksheet, step 20). Also change the properties
for the Table Repair icon to reflect the new location of
TUTILITY.EXE. Otherwise, leave the files in the Paradox for
Windows directory.
Program Manager Group Configuration
In order to make the installation on each workstation as quick
and trouble free as possible, we suggest creating a Program
Manager group file for all users. This group file will be
located in the same directory as Paradox for Windows. It will
have only those icons that users will need to work with Paradox
for Windows.
Choose File | New from the Program Manager menu. In the New
Program Object dialog box select Program Group and press <OK>.
In the Description edit box, type in: Paradox for Windows. Tab
to the Group File edit box and type in the full path and file
name of this new Program Manager group. It will be the directory
for Paradox for Windows (worksheet, step 18) and the file name
PDOXWIN.GRP. Write this information into step 22 of the
worksheet. Press <OK>. Windows has now created a new Program
Manager group. Move the Paradox for Windows icon and the Local
Settings Utility icon into this new Program Manager group. If
users will be allowed to use Tutility, move the Table Rebuilding
Utility icon into this new Program Manager group. After
arranging this new Program Manager group, select File | Exit from
the Program Manager menu to save it.
Workstation Configuration
With this installation, there are two steps required to configure
the local workstation. After the user has started Windows, they
PRODUCT : Paradox for Windows NUMBER : 1251
VERSION : 1.0
OS : WIN
DATE : February 2, 1993 PAGE : 8/12
TITLE : Installing Paradox for Windows on a Network
will need to go to the File menu and select New. In the New
Program Object dialog box, each user will select Program Group
and press <OK>. Have them <Tab> to the Group File edit box, type
in the full path and file name of the Program Manager group
created above (worksheet, step 22), and press <OK>. The group
file is now installed in Program Manager for that user. NOTE: if
the user makes any changes to this group file, a Windows error
message will display when exiting Windows. Users can safely
press <OK> to close that error message box.
Each user must now run the Local Settings utility program in the
new Paradox for Windows group. The user may receive the
"BWCC.DLL is out of date or could not be found. Press OK to
update the file, or press CANCEL to quit." error message. This
error message means that one of the Borland shareable library
files is either an older version or does not exist. Press <OK>
to correct this situation. The Working Directory should be set
to the same directory as the sample files (worksheet, step 21,
sample files), the Private directory should be set to that user's
personal Windows directory, and the ODAPI configuration file
should be set to the location of the ODAPI.CFG file (worksheet,
step 23).
Some users may want or need their own ODAPI.CFG file. If so,
they can copy the existing ODAPI.CFG file into their own personal
Windows directory, and use the Local Settings Utility to change
the location of their ODAPI.CFG file.
V.Conclusion
This completes the Paradox for Windows network installation.
After installation, the directory structure of a single volume
server should look like the example on the next page (remember,
we are using a single volume file server for our example).
PRODUCT : Paradox for Windows NUMBER : 1251
VERSION : 1.0
OS : WIN
DATE : February 2, 1993 PAGE : 9/12
TITLE : Installing Paradox for Windows on a Network
F:\
F:\WINDOWS (Optional, Windows installed on file server)
F:\WINAPP
F:\WINAPP\PDOXWIN
F:\WINAPP\ODAPI (Optional, Windows installed on local hard
disk)
F:\DATA
F:\DATA\PDOXDATA
F:\DATA\PDOXDATA\SAMPLE
F:\DATA\PDOXDATA\DIVEPLAN
F:\DATA\PDOXDATA\EXAMPLES
With careful planning of a network installation of Paradox for
Windows, a network administrator can reduce or eliminate the need
to personally configure each and every workstation using Paradox
for Windows.
PRODUCT : Paradox for Windows NUMBER : 1251
VERSION : 1.0
OS : WIN
DATE : February 2, 1993 PAGE : 10/12
TITLE : Installing Paradox for Windows on a Network
VI. Worksheet
Fill in each of the following questions that pertain to your
network.
1. Do you have network administrator, supervisor, or super-User
rights? ___________(Yes/No)
2. Is Windows installed on the network file server?
__________(Yes/No)
3. If Windows is installed on the network file server, where is
it located: _________________________________________________
4. Is Quattro Pro 4.0 for DOS installed on the network file
server, or any local hard disk: ______(Yes/No)
5. If Quattro Pro 4.0 for DOS is installed on the network file
server, or any local hard disk, what is the location of its
Paradox network control file: _______________________________
6. Is ObjectVision 2.1 installed on the network file server, or
any local hard disk: ______(Yes/No)
7. If ObjectVision 2.1 is installed at all and it is using 4.0
locking protocol, what is the location of its Paradox Network
Control File (NOTE: Should be the same as step 5):
_____________________________________________________________
8. Is Quattro Pro for Windows installed on the network file
server, or any local hard disk: ______(Yes/No)
9. If Quattro Pro for Windows is installed on the network file
server, where is it located: ________________________________
10. If Quattro Pro for Windows is installed on the network file
server, where are its ODAPI files located (NOTE: This should
be the same directory as step 3, if Windows is installed on
the file server): ___________________________________________
PRODUCT : Paradox for Windows NUMBER : 1251
VERSION : 1.0
OS : WIN
DATE : February 2, 1993 PAGE : 11/12
TITLE : Installing Paradox for Windows on a Network
11. If Quattro Pro for Windows is installed at all and it is
using 4.0 locking protocol, what is the location of its
Paradox Network Control File (NOTE: It should be the same as
step 5 and step 7): _________________________________________
12. If Quattro Pro for Windows DataBase Desktop is installed at
all, what is the location of its Paradox Network Control File
(NOTE: This should be the same directory as steps 5 and 7):
_____________________________________________________________
13. Are there any other Paradox Engine 3.0 applications running
on this network: ___________(Yes/No)
14. If there are any other Paradox Engine 3.0 applications
running on this network, and their network locking protocol
is Paradox 4.0, where are their Network Control Files (NOTE:
this should be the same directory as steps 5, 7, and 12):
_____________________________________________________________
15. Is Paradox for DOS 4.0 installed on the network file server,
or any local hard disk: ______(Yes/No)
16. If Paradox for DOS 4.0 is installed at all, what is the
location of its Paradox Network Control file (NOTE: This
should be the same directory as steps 5, 7, 12, and 14.):
_____________________________________________________________
17. If you have any shareable Paradox tables on the network file
server, what is the location of those tables:
_____________________________________________________________
18. Where do you want to install Paradox for Windows on the
network file server: ________________________________________
19. Where should you install the ODAPI files for Paradox for
Windows (Note: This will be the same directory as step 3 or
6): _________________________________________________________
20. Where should you place the Paradox Network Control File for
Paradox for Windows (NOTE: This will be the same directory as
steps 5, 7, 12, 14, and 16): ________________________________
PRODUCT : Paradox for Windows NUMBER : 1251
VERSION : 1.0
OS : WIN
DATE : February 2, 1993 PAGE : 12/12
TITLE : Installing Paradox for Windows on a Network
21. Where should you install the Paradox for Windows samples
(Note: These will be sub directories of steps 17 or 20.):
Sample Files: _____________________________________ + SAMPLE
Sample Application: _____________________________ + DIVEPLAN
ObjectPAL Examples: _____________________________ + EXAMPLES
22. What is the name of the new Program Manager group file for
Paradox for Windows (Note: It will be the directory that
Paradox for Windows was installed in, step 18, and the file
name PDOXWIN.GRP.): ________________________________________
DISCLAIMER: You have the right to use this technical information
subject to the terms of the No-Nonsense License Statement that
you received with the Borland product to which this information
pertains.