Super WinLog V 2.0

Known Problems - installing and running

Installing.

A halted installation with a VER.DLL message may be due to no file 
VER.DLL exsisting in the Windows directory.  

Problems can occur with the VBRUN300.DLL file.  
Check that this file is already on your system either in Windows or Windows\system directory,  if it is not then.....
Use 'EXPAND' (MS DOS Command) like

EXPAND A:\VBRUN300.DL_ C:\Windows\system

to uncompress and copy the file from the WinLog floppy Disk1 to your Windows\system directory, now try to install again.

If it IS there then try loading 'Setup.lst' from disk1 into a text editor and deleting the line 'VBRUN300.DL_' from the list and saving the file.  Try installing again. 

Graphics problems.
An old version of 'THREED.VBX' is known to give graphics problems 
(usualy Grey areas remaining White) in some areas of Winlog. 
An old version of 'THREED.VBX' may have been installed by another 
application.  
The version supplied with Super WinLog is installed in the 
'Windows\System' directory (file date 16/07/93), other versions can hide under 'Windows'. 
Any 'THREED.VBX' file other than in 'Windows\system' can be moved to a temporary directory to see if that corrects the problem.

ERROR MESSAGES
Error trapping was used during the development of Winlog, 
unexpected Error messages such as 'ERROR1 IN MAIN' should be reported to me.  
A known cause is if certain files are missing, e.g. database files.  DO NOT delete databases or any other files from the Super WinLog directorys to save disk space!

INSTALLING
In some instances there has been a problem with the file 'SETUPKIT.DLL' causing a halted install.  Try manually expanding this file into the Windows/System folder (from Super WinLog Disk 1), and try installing again.

In Windows 3.1x a problem may arise if using 'File Manager' to run Setup.exe with a "Commdlg.dll in use" error. Solution is NOT to use File Manager but use the command 'RUN' Setup.EXE.

In Windows 3.1 it may be necessary to add 'SHARE' to your config.sys

If you intend installing from the hard drive it will be neccessary to unzip both Disk1.zip & Disk2.zip into a single folder/directory, when prompted to 'insert Disk2' hit return and the install will continue. 

RUNNING
There have been problems with certain files corrupting during the install process, causing errors when first running 'Super WinLog'.  The problem file seems to be VBDB300.DLL (installed in the Windows/System folder).  Try manually expanding this file off Super WinLog Disk 2.
MS EXPAND, - to expand any problem files from the floppies, use this MS system file - at the MSDOS prompt:
EXPAND A:\VBDB300.DL_ C:\Windows\system\VBDB300.DLL
Note the spaces and the underscore in the first (compressed) file name and not in the second.  Use a similar procedure to expand other files this way substituting the file names of course. 
I hope to have these problems fixed in the future, it seems to happen sporadically on some systems so its a tricky one!

When updating to a new version, sometimes error messages may appear on first starting the new version - this may be caused by the new configuration or preference settings, and these errors should disappear after the new version of WinLog has been run and shutdown for the first time.


Any further problems that you encounter can be reported to me for further investigation to any of the following addresses:-

C.D.Morris G0CUZ
12 Turners Hill Road
Lower Gornal
DUDLEY
West Midlands
DY3 2JU
ENGLAND

PACKET MAIL	G0CUZ@GB7PZT

EMAIL		cuz@allcomm.co.uk

Colin D Morris G0CUZ. 

15 May 1998  
