4.8 Cascade query code
The AdderView GEMs use a special ‘query code’ to detect whether or not they are connected to another AdderView GEM. By default your AdderView GEM uses query code AD. SmartView (another range of keyboard / mouse / video switches from Adder Technology) units with firmware versions less than 1.09 used query code EF. This was found to conflict with a small number of other (rare) devices that used the same query code so an alternative query code was provided to ensure compatibility. Either query code may be used but you should make sure that all cascaded AdderView GEM and SmartView units are set to use the same query code. If any of the cascaded SmartViews have firmware versions less than 1.09 then the cascade query code for all the AdderView GEMs and SmartViews should be set to EF.
L7 – Cascade query code = AD (default)
L8 – Cascade query code = EF
4.9 Resolving slow mouse problems
Due to certain technical reasons some systems running particular combinations of operating system and mouse drivers are sensitive to small timing changes relating to mouse communications. The introduction of a switch like the AdderView inevitably causes some timing changes and in rare cases interactions have been observed that causes the mouse to run very slowly. Certain HP Vectra computers running later versions of Windows NT with Logitech mouse drivers and Logitech mice have been observed to exhibit such interactions with older switches. One solution to this problem is to change the mouse driver.
The AdderView GEM is a high performance device that is carefully engineered to minimise such interactions and should not exhibit this characteristic. Nevertheless such interactions are unpredictable and so the AdderView is fitted with a feature that ensures that the mouse can never operate at a very slow rate regardless of such interactions. This feature is activated using the following options:
L5 – Allow the mouse to run at any speed (default)
L6 – Don't allow the mouse to run at very slow speeds
AdderView GEM | Installation and Use | Page 32 |
