The bugs described below refer to particular versions of our software. To find out which version you have, choose the About command from the product's Help menu.

Choose a product:

• VisiMap
• VisiMap Lite
• VisiMap Viewer

VisiMap

Version: 2.5c and earlier

 

a. Using the colour palette when the QuickEditor is active may lose recent changes made to the notes. The workaround is to click on the map pane (which will cause the notes changes to be saved) before using the colour palette whenever you have unsaved changes in the notes pane. This will be fixed in a future maintenence release.
b. When pressing a style hot key, VisiMap erroneously applies the Default Branch Style rather than the correctly associated style. This will be fixed in a future maintenence release.
c. Under Win NT 4.0, the Universal Scrolling feature of IntelliPoint 2.2 does not function correctly with VisiMap. There is no such problem on Win 95/98.

Version: 2.5b and earlier

 

a. A few users are experiencing a fault in the Windows help system on Windows 95 when launching VisiMap on-line help. The problem is caused by a known bug in Microsoft's IntelliPoint 2.0 software, as described at http://support.microsoft.com/support/kb/articles/Q148/1/17.asp.

b. If you have a display driver configured for 32-bit color VisiMap will fail to print icons correctly (but they will display correctly on-screen).
c. Under some circumstances, a GPF can occur when, or subsequent to, cutting and pasting into the QuickEditor.

 

Version: 2.5 and 2.5a

 

a. Resource degradation can occur when running under Windows 3.x of Windows for Workgroups 3.x.

b. A small number of users suffer from an occasional GP fault when exiting VisiMap.

c. The File Locations dialog fails to change default directories for some users.

d. Under Win95 and WinNT 4.0 where more than one program has registered itself as the program to open HTML files, VisiMap may incorrectly identify the default web browser.

 

Version: 2.5

 

a. A very small number of users have found VisiMap freezes during startup. This is due to a web browser configuration error in the system registry coupled with VisiMap's failure to react to it properly.

b. A cosmetic error exists whereby the document window captions do not show the correct instance numbers when more than one window is open on the same map.

 

Version: 2.5 or earlier

 

a. When exporting a file in RTF format to AMI Pro 3.1, the targets' auto-numbering option is ignored when imported into AMI Pro. You should therefore use the RTF filter's VisiMap numbering option instead when exporting to AMI Pro 3.1.

VisiMap Lite

Version: 2.5d and earlier

 

a. Using the colour palette when the QuickEditor is active may lose recent changes made to the notes. The workaround is to click on the map pane (which will cause the notes changes to be saved) before using the colour palette whenever you have unsaved changes in the notes pane. This will be fixed in a future maintenence release.
b. When pressing a style hot key, VisiMap Lite erroneously applies the Default Branch Style rather than the correctly associated style. This will be fixed in a future maintenence release.
c. Under Win NT 4.0, the Universal Scrolling feature of IntelliPoint 2.2 does not function correctly with VisiMap Lite. There is no such problem on Win 95/98. We are researching this issue.

 

Version: 2.5c and earlier

 

a. A few users are experiencing a fault in the Windows help system on Windows 95 when launching VisiMap Lite on-line help. The problem is caused by a known bug in Microsoft's IntelliPoint 2.0 software, as described at http://support.microsoft.com/support/kb/articles/Q148/1/17.asp.

b. If you have a display driver configured for 32-bit color, VisiMap Lite will fail to print icons correctly (but they will display correctly on-screen).
c. Under some circumstances, a GPF can occur when, or subsequent to, cutting and pasting into the QuickEditor.

 

Version: 2.5, 2.5a and 2.5b

 

a. Resource degradation can occur when running under Windows 3.x of Windows for Workgroups 3.x.

b. A small number of users suffer from an occasional GP fault when exiting VisiMap Lite.

c. The File Locations dialog fails to change default directories for some users.
d. Changes to the 'maximum branch length' preference are not saved for later sessions.

 

Version: 2.5

 

a. A very small number of users have found VisiMap Lite freezes during startup. This is due to a web browser configuration error in the system registry coupled with VisiMap Lite's failure to react to it properly.

b. A cosmetic error exists whereby the document window captions do not show the correct instance numbers when more than one window is open on the same map.

VisiMap Viewer

There are currently no known problems in VisiMap Viewer version 2.5c. If you have an earlier version, and you are experiencing one of the problems listed here, download version 2.5c.

Version: 2.5c and earlier

 

a. A few users are experiencing a fault in the Windows help system on Windows 95 when launching VisiMap Viewer on-line help. The problem is caused by a known bug in Microsoft's IntelliPoint 2.0 software, as described at http://support.microsoft.com/support/kb/articles/Q148/1/17.asp.

b. If you have a display driver configured for 32-bit color, VisiMap Viewer will fail to print icons correctly (but they will display correctly on-screen).
c. Under Win NT 4.0, the Universal Scrolling feature of IntelliPoint 2.2 does not function correctly with VisiMap Viewer. There is no such problem on Win 95/98. We are researching this issue.

 

Version: 2.5 and 2.5a

 

a. Resource degradation can occur when running under Windows 3.x of Windows for Workgroups 3.x.

b. A small number of users suffer from an occasional GP fault when exiting VisiMap Viewer.

c. The File Locations dialog fails to change default directories for some users.

 

Version: 2.5

 

a. A very small number of users have found VisiMap Viewer freezes during startup. This is due to a web browser configuration error in the system registry coupled with VisiMap Viewer's failure to react to it properly.

b. A cosmetic error exists whereby the document window captions do not show the correct instance numbers when more than one window is open on the same map.