Kbase 20779: How to Configure a GUI Session with a Mapped Network Drive?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/25/2011 |
|
Status: Verified
GOAL:
How to Configure a GUI Session with a Mapped Network Drive?
GOAL:
How to setup a GUI Session with Mapped Network Drive?
FACT(s) (Environment):
Progress 8.X
Progress 9.X
OpenEdge 10
All Supported Operating Systems
FIX:
- Have mapped the network drive in each remote client use the same specification (for example, the letter U:\.)
- If you are going to map the .ini file, modify the file to contain the entries for the mapped network drive (explanation below).
- If the remote clients are to use a local working directory, add the directory to the PROPATH variable in the shared mapped .ini file.
The name and location of the directory should be the same for all the clients.
- If the application also resides on the file server machine, it also is mapped.
The following is an example of a configuration in a mapped network drive shared by several clients. It has:
- A file server machine with a client networking installation.
- The remote clients map the Progress installation directory in their machines (for example, as drive U:\).
- The application resides in the u:\workdir directory, and this entry must be in the PROPATH.
- All remote clients must have a local working directory for their temporary files called c:\temp.
- The .ini file is also mapped also (for example, u:\dlc\bin\progress2.ini), and it should have the following entry modifications:
DLC=u:\DLC
PROBUILD=u:\DLC\PROBUILD
PROPATH=.,u:\DLC\PROBUILD\EUCAPP\EUC.PL,u:\DLC\PROBUIL
D\EUCAPP,u:\work dir,C:\temp
- The client icon should have the following information:
Target
U:\DLC\bin\prowin32.exe -basekey "INI" -ininame U:\dlc\bin\progress2.ini -db dbname -H HOST1 -S serv1 -N tcp -p u:\workdir\menu.r
Start in
C:\temp
NOTE: Be careful when you make reference to the application in the -p parameter. It should have the full path reference. If not, use -p menu.r. The execution of this icon looks first for the application in the "start in" location and you could get a (293) error.
You can add all the parameters into a parameter file.
If your installation is made using NETSETUP, the PROPATH information in the Registry of the client machine points to the mapped network drive. You should add the remote application directory and the local directory for the temporary files to it. You do not need to use -basekey and -ininame parameters.