Visimage 2.6 FAQ
Contents
Common TCP Errors
Once you have correctly installed and configured Visimage to use a TCP connection you should not have any problems starting server. If you are having trouble starting server, you should check the following:
The host listener job/service is running. You are specifying the correct IP address. You are using a valid user name. The user name must have been added to VSRVINI.
If you continue to have problems after verifying that all of these are correct, check the $STDLIST of the VSRVJOB listener. This may give you some additional clues. If you continue to have problems, contact technical support.
How to install Visimage to a network server
Start the installation in the normal way. Use the directory browse button to locate and specify a network drive. You must have write access to this drive. The installation will then provide you with three options.
How to install Visimage from a network directory
Visimage can be installed from a network server by running the setup program from the network drive. For example, if Visimage has been installed in F:\APPS\VISWIN2, an individual workstation can be installed by running:
F:\APPS\VISWIN2\DISK1\SETUP.EXE
Error installing Visimage, DLL too old
The main Visimage installation was written using the latest version of Microsofts Visual Basic. Consequently, it requires recent versions of Microsofts own Windows DLL files. If you get an error message for a specific DLL file when you insert the CD, take one of the following steps to resolve the error.
COPY the DLL from the CD. The Visimage Installation CD contains newer versions of the Microsoft DLLs. Copying the DLL from the CD will allow you to run the installation program successfully. It is possible that a DLL in the WINDOWS\SYSTEM directory cannot be updated, because it is already in use. If this is the case, copy the DLL from the CD into some other location on your C drive. Then reboot in DOS mode and copy the DLL from your C drive into the WINDOWS\SYSTEM directory.
Install Visimage without using the main Installation program. To install Visimage without running the main installation program, run X:\DISK1\SETUP.EXE Where X: is the appropriate drive letter for your CD drive.
I click the Visimage icon but nothing happens!
If Windows is unable to load the Visimage program, and no error message is displayed, it means that there is a problem with one of your DLLs. It could be a Reflection DLL or the WINSOCK DLL. The most common problems are with PPL.DLL, RCOM.DLL and WINSOCK.DLL.
PPL.DDL and RCOM.DLL
Visimage uses the files PPL.DLL, RFILES.DLL and RUSER.DLL. These DLLs should be located in the Visimage installation directory (VISWIN2). During installation, Visimage will verify the version of Reflection you are using and install the correct versions of these DLLs.
| Reflection Version (*) | DLL Creation Date |
|---|---|
| 4.01 | 7/21/93 |
| 4.1x - 4.2x | 4/21/94 |
| 5.x (16 bit) | 12/12/95 |
| 5.x (32 bit) | Not supported |
| Dummy (1) | 9/4/95 |
Use File Manager or Windows Explorer to search for all occurrences of PPL.DLL. Make sure that there is one located in the Visimage installation directory (VISWIN2) and that it has the correct date. If the dates are wrong, update the appropriate files from installation disc 2 (4.01 & 4.1-4.2) or disc3 (5.x). See Extracting a file from the installation disc for more information. You will need to update PPL.DLL, RFILES.DLL, RUSER.DLL, PPLSERVE.EXE and PPLDDE.EXE (5.x only).
(1) For users that do not want to use a Reflection connection and specify TCP only during installation, Visimage will install a dummy PPL.DLL file. This is because Windows requires that all DLLs be present, even if they are never called. This DLL must be deleted if you later wish to use a Reflection (PPL) connection.
In addition to the DLLs mentioned above, Visimage must also have access to DLLs in the Reflection directory. Make sure that Reflection directory (R1WIN) is included in your DOS path. To check, shell to DOS and type PATH. Do not move any Reflection DLLs from R1WIN into the Visimage directory, instead modify your path to include R1WIN and reboot.
WINSOCK.DLL
For TCP connections you must have a TCP/IP stack installed and a WINSOCK.DLL. The directory that includes the WINSOCK.DLL must be included on your DOS path.
If you specified Reflection only during the installation, Visimage will install a dummy WINSOCK.DLL in the Visimage installation directory. This is required if you do not have a valid WINSOCK.DLL but must be deleted if you later install a TCP/IP stack that contains a valid WINSOCK.DLL
