Previous | Contents | Index |
The following sections discuss some of the errors that can occur while
running the TP Desktop Connector client services sample applications.
B.1 Errors Related to the Desktop System
Errors can arise when any of the following conditions exits:
Problems might be caused by a faulty startup or configuration file. Example B-1 shows a sample startup.bat file.
Example B-1 Sample startup.bat File |
---|
path=c:\;c:\PWV51;c:\dos;c:\MSVC\bin;c:\windows;c:\windev;c:\acmsdi mouse set lib=c:\MSVC\lib;c:\windev\lib;c:\acmsdi;c:\decnet\src set include=c:\MSVC\include;c:\windev\include;o:\acmsdi;c:\decnet\src set helpfiles=c:\MSVC\help\*.hlp set init=c:\MSVC\init |
Example B-2 shows a sample config.sys file.
Example B-2 Sample config.sys File |
---|
files= 30 buffers=10 device=C:\himem.sys shell=\command.com /P /e:1024 device=C:\WINDOWS\smartdrv.sys 2048 1024 lastdrive=z |
Use the samples as guidelines to finding and fixing the problem.
B.1.2 Errors on OpenVMS Desktops
If errors occur in running the Motif Avertz program, verify the following:
If you encounter font-support problems running the program, you can
modify the fonts used by editing the m_avertz resources file
(m_avertz.dat in the user's home directory).
B.1.3 Errors on Tru64 UNIX Desktops
If errors occur in running the Motif Avertz program, verify the following:
If you are installing this application once for use by many users, make sure that the users copy m_avertz to their home directories.
If you encounter font-support problems running the program, modify the
fonts used by editing the m_avertz resources file (m_avertz in the
user's home directory).
B.2 Errors Related to the ACMS System
If you have used the client services sample to communicate with the ACMS system, errors will occur if any of the following conditions exists:
Index | Contents |