Vista Users:
Install:
During the install process, please do not worry that we are an “unknown publisher” to Microsoft!, and allow the install to proceed.
Vista Stand-Alone Machines with more than one user account
Installation must be carried out by a Vista Administrator, NOT restricted user (if unsure, go to control panel / user accounts to check).
You will require your Vista Administrator’s user password to install as a restricted user, OR [as in XP] will need to be signed on as the computer administrator. One customer with “Vista Home Basic” encountered an “Error 5002” whilst installing as a restricted user, but was able to install successfully when logged on as administrator: After this, the customer was then able to use the program as a restricted user
A small number of customers with Vista computers with multiple users have reported an error “Java Virtual Machine Launcher: Fatal Exception Occurred: Program will exit”. See here for a fix.
Vista Graphics: Several customers have rung to say that when loading the program they are given a warning that “The color scheme has been changed to Vista Basic: A running program isn’t compatible with certain visual elements of Windows”. This has no effect on our programs. It may, however, slow other programs running in the background. The colour scheme reverts automatically to your normal colour scheme when you close Wordshark or Numbershark, and with this, the other programs restore to normal performance. To fix this: In the root of the CD (both single user and network) is a program “fixgraphics.exe”. Double-click this, tick the box “Run with graphics fix” and click “Exit”. If you have multiple user accounts on the Vista machine, you may need to do this for each user OR do this as Vista Admin, and move nshark_graphicsfix from c:\users\[name of user\/AppData\Local\VirtualStore\ProgramFiles to c:\ProgramFiles
A very small number of customers have reported some odd graphics problems on some games, and particularly down the right hand side of the screen. We are investigating. Please contact us if you note any such problems.
COM surrogate has stopped working
We have one report of this error, coupled with serious problems with text entry and mouse/cursor movement both in Wordshark and in other programs working in the background. In this Vista-specific case, a graphics driver appears to have conflicted with our program. Applying fixgraphics.exe proved to be a quick and effective solution.
Vista Service Pack 1 Since this was launched in Feb 08, we have had a very small number of customers with Nvidia cards and Creative soundcards experiencing problems. This would appear to be an issue that these companies are aware of. Creative NVidia A review of SP1, along with a very short list of known problems is here: Vista SP1
Peer to Peer Vista Networks (more than 2 machines) Wordshark and Numbershark will not work. Later versions will typically freeze, whilst earlier versions will typically end up with corrupted data. Networks with Vista client machines do work as intended if you locate the [word][number]shark-shared directory on a server, or a XP client or a Linux file-serving machine. Vista file-locking effectively prevents a single Vista machine from allowing more than one other Vista machine to access or lock a given file.
Java Virtual Machine: Could not find the main class: Program will exit This has occurred in a small number of Vista machines where “User Account Control” is switched on, resulting in Vista creating individual virtual stores. Switching off user account control resolves the issue. If you need to have user account control on, please contact Support, requesting instructions on how to remove virtual stores for our programs.
Printing Problems We have compatibility problems with old versions of Wordshark (pre 3s.07) and Vista on a few printers: Check the printer is set as the default before opening Wordshark. Ensure the paper is set to A4. Go to file / print word list (or Numbershark sums): Click on the printer in the list (even though it is the default), and select OK. This has almost always worked.
To date, there are no other Vista-specific known issues