| Date |
Problem
|
Solution
|
|
5-Mar-2008 |
Timer (all versions) has problems with the display on some International versions of Microsoft VISTA
|
Some International installations of VISTA have problems with the timer when the Timer finishes and tries to display a flashing screen.
This is being looked at.
return to Top of Page
|
|
27-Nov2005 |
Version 6.0 of the Network Diary loses events in the calendar.
|
Version 6.0 of the Network Diary had a problem where events were not visible in the calendar if entered at the end of the month when the user is in weekly view.
This has been fixed with release 6.1 of the Network Diary.
return to Top of Page
|
|
23-Jan-2005 |
ASCON 3.1 returns nothing when clicking History
|
This problem was due to the new Diary format.
You can download a patch which fixes the problem. Simply extract the ASCON exe file
ontop of your existing installation.
return to Top of Page
|
|
06-Nov-2004 |
Network Diary Server sometimes brings up a message saying 'problem writing file'
|
In some cases a message appears on the diary server which halts the operation of the server. This has been fixed in the latest 4.2 release
return to Top of Page
|
|
1-Aug-2004 |
on startup, Network Diary 4.2 shows wrong start day in week mode.
If the diary is started in week mode - before you select a date, the screen shows
the first day of the week as a Tuesday (should be a monday).
|
The screen displays normally
once you click a date in the calendar.
This bug has been fixed in version 4.3
return to Top of Page
|
|
24-Sep-2002 |
Timer 3.0 times out immediately after installation
|
This is a bug in the shareware version which occurs on Non-English versions of Windows. It can be fixed by downloading the latest version 3.1 of the Timer.
return to Top of Page
|
|
26-Aug-2002 |
FileList 2.1 shows duplicate files in the list
|
This is caused by adding wildcard paths to the 'directories to search in' list which are duplicated.
For example - adding C:\data\* and C:\data\November will result in all files in the November subdirectory
being listed twice (because C:\data\* will search all of its subdirectories). This is by design.
return to Top of Page
|
|
26-Apr-2003 |
Network Diary 3.0 does not auto configure to the server..
Click here to download the 3.0 update
|
The autoconfigure routines in the Network diary client, depend on the fact that the client PC has access to the shared
folder on the server PC ( e.g. \\server_name\netserver\users\your_user_name\ ).
Version 3.0 of the Network diary has been repackaged (27/4/2003) to fix the client autoconfigure, so that if it cannot
connect to the server, it will show the network path in Windows Explorer to assist the administrator with the problem.
Generally, the user does not have access to the folder on the Win2000 server, or they have not cached their password.
Temporary Workaround
If you do not want to cache passwords, you need to make a text file in Notepad containing the line
start "\\[servername]\netserver\users\[username]"
where servername = name of the PC running the diaryServer, and username = the name of your PC
Save this text file and place it into your startup folder so that when the PC boots it will load this folder, and
windows will ask the user for the password - once connected, InfoLink will be able to talk to the server.
return to Top of Page
|
|
16-Aug-2002 |
Network Diary 2.4 doesnt find other users appointments.
|
You need to add at least one appointment (not a meeting - just an appointment) to each of
the clients diarys before they are seen by the server.
return to Top of Page
|
|
8-Feb-2000 |
If the installation program fails and you get and error message saying 'Cant start SETUP.EXE '
|
This is caused by either :
1. A previous installation of a program has left tempory files. Try reinstalling the software.
2. The ZIP file has been corrupted during the download. You should re-download the ZIP file.
return to Top of Page
|
|
19-Jan-2000 |
If you get an error message 'System Files are out of date' |
This is a normal occurance for early versions of Windows 95 - simply click OK and reboot when prompted.
return to Top of Page
|
|
15-Oct-1999 |
If the application installs OK and fails to start with a 'cant find DLL' error
|
You will need to download and
install the
VB6 Runtime Files
return to Top of Page
|
