Deutsch English Francais

FAQ - Problems during use

  • Why is there no or only erratic output of norm data in the result report?
  • For this there is a series of possible reasons:

    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.

    • 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 separate sides you'll find an overview for the individual TAP programs:
    • Not all test parameters are normalized. Which parameters are normalized can be looked up in the manaul 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 via the download section.
  • The norm data given in the output of the TAP programs differ from those in the manual. Which ones are correct then?
  • The norms of the TAP output have been corrected to age and sometimes gender or education. The norms given in the operating manual tables are uncorrected. Before the norm tables you will find the correction values with which you should be able to manually calculate the corrected values. Should you, after these steps, still find any differences between printout and manual, please contact us directly.
  • I often find that, when adding the outliers for separate trials (e.g. Alertness: series 1-4), they differ from the total sum of outliers. How can this be?
  • Outliers are always calculated related to the current condition. First, TAP calculates the mean and standard deviation, then trials above or below 2,5*SD are excluded. After that, statistics (Mean, Mdn, SD) are calculated in relation to the resulting trials. This is done separately for each testing condition, so that the values underlying outlier calculation may differ in respect to condition. This may result in differences of total outliers compared to adding up single trials.
  • I upgraded my laptop with an extension card and configured it correctly following the instructions from the download area. But the reaction keys don't work reliably.
  • This problem may occur (particularly since Windows Vista/7, in rare cases on Windows XP) with Laptops if you're using an older version (before build 02/2011) of your TAP program without automatic parallel port detection. Windows often assigns different addresses, which seems to depend on at which time during system start the extension card is plugged in.
    If you are affected by this problem please contact us directly, so that we can provide you with a version of your program that includes an automatic configuration.
  • Why do the reaction keys not work?
  • First of all the reaction keys can be tested from within the TAP program choosing "Options>reaction keys". By keeping one of the reaction keys pressed the shown text "no key pressed" should change to "key 1" or "key 2" respectively.
    Since build 02/2011 all available parallel ports are configured automatically (therefore only available ports are listed) - if there is more than one available the used one has to be chosen manually.
    With older versions 4 LPTs are listed overall.
    If a parallel port has been upgraded (q.v. Technical Details) please note that it has to be set up manually using these older versions. You'll find a corresponding document in the download section.
    In some rare cases a default parallel port hasn't been setup automatically. But in this case the already mentioned document will also help.
  • Why can't the subtests be started (possibly no error message)?
  • 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 killed 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 which are in turn part 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.
    • No parallel port available
    • Perhaps the parallel port hasn't been setup correctly for use by the TAP programs. This can be checked from within the program by choosing "Options>reaction keys" - if every address (in brackets) is listed with the value "0x0000", you will have to setup the parallel port according to the manual in the download section.
    • 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.
  • After starting a test the screen gets blank (maybe with a window border), but no output is visible. The test itself seems to be running, because after a while the interface of the TAP program reappears.
  • This fault scenario is similar to the previous FAQ point, but the fact that the test is obviously running in the background the cause of the failure is limited 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 (especially Windows 2000) and such without a recent service pack (Windows XP) 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 (a link should be in the start menu). 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 Vista/7 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". You'll find further information about how to install these updates on http://windows.microsoft.com/is-IS/windows7/Install-Windows-updates.
  • Distorted and/or delayed sound output
  • Using subtests with sound output (Alertness, Divided Attention, etc.) the tones may be distorted and delayed (nearly solely with Windows 2000).
    In that case you should check if your operating system is up-to-date, especially regarding graphic and sound drivers (mainly take care of a ongoing DirectX version (9.0c for Windows 2000)). For updating the Windows update function can be helpful.
  • While performing a subtest the message "Keep your fingers off the key, please!" appears constantly.
  • Most probably the lpt port isn't set correctly under "Options>reaction keys", in particular when using an upgraded parallel port. To check the address and the setup you'll find a document in the download section.

Top