If you are affected by this problem, it is not necessary to repeat already properly conducted test runs, since it is purely an analysis problem. The standard values - as well as the other statistical values - are calculated by the program only when calling up a test result.
After certain Windows 10 updates, the programmes (TAP, KiTAP and TAP-M) no longer work properly. We have adapted our software accordingly.
Please contact support@psytest.net for this.
Please let us know the serial number of the affected program (TAP, KiTAP or TAP-M) when making your request. You can find this on the key usb or in the program under the menu item "Help / About".
For this there is a series of possible reasons:
- First of all it should be made sure that the subtest is normed, that the subjects' age is within the normed range and that the subtest has been passed completely.
On the following sites you'll find an overview of the standardisation for the different TAP programs:
TAP standardisation
TAP-M standardisation
KiTAP standardisation
- Not all test parameters are normalized. Which parameters are normalized can be looked up in the manual in the section "results" of the subtest in question.
- Maybe the norm files are not selected correctly. To check this, choose "Options>Norms" from within the corresponding TAP program, mark the entry ("All", "Children", etc.) with a left click, confirm with "OK" and and call up the result once again.
If an error message occurs calling the results this could explain missing norm data. (q.v. corresponding error message in the FAQ).
Empirically also virus scanners - especially the scanners running in background - constrict a correct norm data output. In this case it has been proven as helpful to exclude the corresponding process ("tap.exe","kitap.exe" or "tapm.exe") from this so called "On-Access-Scan"; most of the antivirus programs provide enhanced settings for it.
As it is necessary for the norm data output to access the Dongle a newer version of the HASP driver may help. It's available in the download section.
Basically, the TAP program calculates the mean value and the standard deviation for any number of measured values. Then all trials are excluded that are 2.35 x standard deviation above or below the mean. The statistics (median, mean, standard deviation, etc.) are then calculated for the remaining trials.
The outliers are determined separately for each subset of trials. Since, for example, when looking at all trials without a warning tone, a different mean value and a different standard deviation are determined than when looking at the individual series 1 and 4, slightly different outlier limits result. This can lead to the sum of the outliers in series 1 and 4 being not equal to the number of outliers in the set of all trials without a warning tone.
After starting a subtest the screen switches black shortly, after that the Interface of the TAP program reappears (in some cases the subtest freezes and has to be stopped using the task manager). This incorrect behaviour can have several reasons:
Missing graphic functions
The subtests of TAP need so called DirectDraw functionality which are part of the DirectX functions of the Windows operating system. The functionality can be checked with the help of the so-called "DirectX diagnostic program", to be started via "Start>Run>dxdiag". Beneath the tab "display" the DirectDraw functions can be checked and tested. If DirectDraw is marked as "deactivated" or "not available" the cause for the non starting subtests is found at least.
Missing DirectDraw functions in turn can have multiple reasons:
- Graphic drivers are too old or not installed at all
- No up-to-date DirectX version (for Windows 2000 an XP the current version ist 9.0c)
- Remote administration tools which interfere with or deactivate DirectX functions
To search for newer drivers/new DirextX the Windows update function can help. Whether a remote administration tool is the cause can be checked by a deinstallation of the program and maybe an additional research on the manufacturer's website.
Missing sound output
Maybe the sound output isn't working properly because of missing drivers.
The sound can be checked from within the program by choosing "Options>Adjust volume". There you can playback the single sounds for testing (green arrows/triangles).
If the tests fail, upgrading or installing proper drivers will put things right in most cases.
In such cases please contact the PSYTEST support.
This problem usually is due to the encryption of our software which is often classified as potentially malicious by the heuristics of some antivirus programs. This results in the programs (located as individual exe files in the TAP program directory) being quarantined. That also leads also to the according test results not being shown (this is just a display error, they are still there).
To solve this problem you have to define the test procedures within the antivirus program as an exception.
To do this, please proceed as follows:
- Temporarily deactivate the real-time protection.
- Reinstall the TAP (here you can deselect the installation of the drivers for the usb key and the reaction key adapter since they are still installed)
- Define all EXE files (e.g. tap.exe, alert.exe, flexi.exe etc.) or the whole folder 'C:\Program Files (x86)\TAP' (or \KiTAP or \TAP-M, depending on your installation) as exceptions within the antivirus software.
- Then the real-time protection can be reactivated
If possible, you may also restore the blocked files inside the virus scanner and then continue with step 3 without reinstalling the TAP.
If the problem still persists, please contact our PSYTEST support.
These differences are due to the automatic age correction (usually trend and variance correction). In some cases, gender and educational effects are also taken into account.
Before the measured test value can be looked up in the norm tables, a so-called corrected score is calculated from the raw value, taking into account the regression parameters of the respective parameter. (The formulas and the regression parameters of the individual test parameters can be found in the section on normalization in the manual). Only this corrected score can be looked up in the tables of norm values in the manual.
The pictured scenario is similar to the previous FAQ item, the fact that the test is obviously running in the background limits the possible cause of the failure to the following points:
Wrong or only standard monitor driver installed
Please check the monitor settings and the installed driver: Right click on a free area of you desktop>Properties>Tab "Settings">Advanced>Tab "Monitor". Here "Plug and Play-Monitor" or the model of your monitor device should be noted. Otherwise you may install a specific monitor driver via "Properties>Tab "Driver".
Older DirectX version
With older Windows versions an out-dated DirectX version could be the cause. It can be checked by means of the so called "DirectX diagnostic program, which has to be started via "Start>Run>dxdiag". Under the tab "System" the DirectX version is noted.
For updating the Windows update function can be helpful. However on the start page one has to choose "Custom Search", because Microsoft doesn't consider DirectX as a "Critical Update"; because of this fact it is not updated automatically by the Windows update function.
Power-saving settings on notebooks
In the advanced and partly very detailed power-saving settings on notebooks with the operating systems Windows 7/8/10 some special settings concerning the graphics card may lead to an erratic output or no output at all during a subtest.
In this case it normally helps to switch the power plan to "High performance" and/or make appropriate settings within the graphics driver (if available).
2nd Generation Intel Core Processors with Intel HD Graphics 3000/2000
This graphics solution (built into many newer laptops, even in conjunction with a so called "dedicated" graphics chip from Nvidia or AMD) leads to the mentioned problem; since the end of September 2012 new graphics drivers are available which obviously solve the problem and are also available via the Windows Update function in many cases as a so called "Optional Update".
Using subtests with sound output (Alertness, Divided Attention, etc.) the tones may be distorted and delayed.
In that case you should check if your operating system is up-to-date, especially regarding graphic and sound drivers.
Also check for sound-enhancement tools that are possibly installed to modify the sound output. These should be deactivated.