If what you want to tell us is really more of a suggestion or a request for enhancement, please use our suggestion form instead.
When you submit your bug report, it will be entered into our database for tracking purposes. We will attempt to re-create the problem, but if we cannot re-create it we will need to contact you for additional information so be sure to leave a phone number where we can reach you. Periodically we will post notices regarding bugs reported by our customers in the Known Problems section of this page, and tips or workarounds on the FAQ page.
Please be as specific as possible when describing the problem.
Back to Top
The following is a list of some known problems with our software; we are working to correct them for the next release.
Insight, Audio Playback, incompatible hardware, SoundBlaster ISA SB16, AWE32/64:
Insight's audio playback uses a standard high-level Windows API. This API is not fully supported by SB16 based ISA cards (SB16,AWE32/64). All PCI sound cards tested thus far work properly (Including SoundBlaster Ensonic PCI). Since this appears to be a SoundBlaster 16 driver/HW issue (and not the Windows API) we cannot provide SB16 support. If you experience problems with any PCI-based sound card (and you are able to hear your default sound when the "test" button is clicked in the Insight Audio Playback dialogue) contact us. If you do not hear your default sound when clicking the "test" button in the Insight Audio Playback dialogue your sound card may not be properly configured.
Version 2003.11.24 and Persyst 05-01 NK on Nihon Kohden 2100/1100/9100 or later:
NEW
By default, AutoStart
for Reveal and MagicMarker are off
for compatibility with Persyst LightHouse.
Selecting on
from the Command drop-down will not save this setting in the Windows Registry.
The result is that Reveal will not launch when the next recording stage
is started.
To fix this,
download and launch the following registry keys that will save the AutoStart
setting for Reveal and MagicMarker.
IMPORTANT: These
are for use with Nihon Kohen instruments running integrated Reveal and
MagicMarker. Do not use this when launching these programs with Persyst
LightHouse (otherwise the programs
will crash).
AutoStart Registry
Entries:
Reveal
AutoStart On
Reveal
AutoStart Off
MagicMarker
AutoStart On
MagicMarker
AutoStart Off
Version 1999.06.23 and later on Nihon Kohden 2100:
The directory \NFX includes old versions of system files named mfc42.dll and msvcrt.dll. The Persyst programs require new versions of these files, which are installed by the 1999.06.23 update to the \Windows\System folder. Since NKReview is invoked from the NFX directory, the older versions of these files are loaded and the EEG Suite PlugIns (SpikeDetector, Prism, and MagicMarker will not run. This problem will affect any software, e.g., Microsoft Word, if NKReview is launched first. The fix is to simply delete these files from the \NFX directory as newer versions are stored in the Windows\System directory.
International customers:
If you are using a version of Windows 95/98/NT other than the English Language version please check with your Nihon Kohden representative before performing this upgrade or deleting these files from your \NFX directory (as these files are language-dependant).
Version 2000.01.27 on Nihon Kohden 2100:
After opening a Nihon Kohden 2100 format file, and saving the montage within Insight using the original name, some traces may be displayed as flat lines. Specifically EKG-EKG and HAN-HAN traces may be displayed as flat-lines.
The solution is to not record data files with duplicated channel names, or do not save Nihon Kohden montages within Insight. The above problem is the result of two input channels having the same assigned label name (e.g., just as Fp1-Fp1 will display a flat trace, so will EKG-EKG). When creating Patterns on the Nihon Kohden 2100 system, use unique names to label all channels, especially EKG, EMG, and HAN (e.g., EKGA-EKGB, EMG1-EMG2, etc.).
