Skip to content

TDT Drivers Tech Notes

Windows 10 and Windows 8 issues

TN0970

Product: TDT Drivers, PO5, PO5e, PO5c
Version: All
Date Added: 2016-02-08

Issue

Windows 8 and above known issues:

  1. Windows 10 has no option to delay or disable updates for non-enterprise users. Users running long/overnight experiments will have to disable the service to ensure recordings aren't interrupted. See Tech Note #0964.

  2. The 'Fast Startup' function in Windows 8 and above causes problems with the PCI Interface on bootup. Disabling this setting resolves the bootup issue.

  3. Data Saving and Cache errors can be caused by the Windows 8 and 10 Superfetch/Prefetch (a feature that caches data to improve the performance off some applications) and Indexing (used to speed-up searches) services are turned off.

zError: ZGB8 after upgrading drivers.

TN0897

Product: TDT Drivers
Version: All
Date Added: 2012-04-24

Issue

When upgrading from an older version of TDT drivers, some PCs may reuse old hardware drivers during the automatic PCIe card driver update. This causes a communication error in zBUSmon that returns zError: ZGB8.

Workaround

To resolve this issue, update the device driver manually.

To manually update drivers using Windows 7:

  1. Press the Start button.

  2. Right-click My Computer.

  3. Select Manage.

  4. Select Device Manager.

  5. Select TDT.

  6. Right-click Tucker-Davis Technologies PO5/PO5e Card.

  7. Click Update Driver Software on the shortcut menu.

  8. From the driver update wizard, select Search Automatically.

  9. If windows is unable to locate the drivers automatically, choose to Browse then search your computer's C:\ drive for the driver files and click Next.

  10. If your PC recognizes multiple drivers, specify the version with the newest date. It should be dated 1/14/11 or newer and click Next.

  11. Reboot your PC and run zBUSmon to verify your device is working properly.

Note

If you receive a warning that the driver is "unsigned" or "not digitally signed" then continue with the update. This is just a warning related to Windows 7.

To manually update drivers using Windows XP:

  1. Right-click My Computer.

  2. Select Manage.

  3. Select Device Manager.

  4. Select TDT.

  5. Right-click Tucker-Davis Technologies PO5/PO5e Card.

  6. Click Update Driver Software on the shortcut menu.

  7. In the hardware update wizard, select Install the software automatically.

  8. Choose to search your computer's C:\ drive for the driver files.

  9. If your PC recognizes multiple drivers, specify the version with the newest date. It should be dated 1/14/11 or newer.

  10. Reboot your PC and run zBUSmon to verify your device is working properly.

Using TDT equipment through a USB interface with 64-bit Windows 7

TN0875

Product: UZ2, TDT Drivers
Version: < 76
Date Added: 2010-09-17

Issue

With the introduction of the 64-bit operating system, Windows required all drivers to be signed. The USB drivers version 74 and below are not signed drivers.

Solution

Upgrade to the latest version of TDT Drivers. This issue was resolved in v76.

v71 Drivers don't uninstall properly

TN0874

Product: TDT Drivers
Version: 71
Date Added: 2010-02-22

Issue

If you have upgraded your TDT drivers to v71 from an older version, and then want to go back to an older version, the uninstall tool will not remove v71 properly.

This is not an issue if you installed v71 on a machine that did not have an older version of TDT drivers.

Workaround

To revert to a version of TDT drivers prior to v71(after you have upgraded to v71 from an earlier version):

  1. Uninstall v71 drivers.

  2. Install v70 drivers. The install will fail.

  3. Uninstall v70 drivers.

  4. Reinstall the desired version.

RPvdsEx update macro

TN0860

Product: TDT Drivers, SpikePac, Synapse
Version: All
Date Added: 2009-07-09

Issue

When an existing circuit is opened, RPvdsEx checks to see if any of the macros contained within the circuit are out-of-date by comparing the build date with the circuits last modified date. RPvdsEx will prompt a dialog that asks the user if they wish to update any out-of-date macros.

Using the Gigabit interface with 32-Bit versions of Windows Vista or Windows 7

TN0837

Product: TDT Drivers, OpenEx, OpenDeveloper, OpenExplorer, OpenSorter
Version: 70
Date Added: 2008-08-15

Issue

After performing a typical installation of the TDT Drivers, running RPvdsEx results in an error message which states "Error loading component specification file: CmpSpec.txt". Or, if you launch zBUSmon, you will see "NO TDT card Detected."

Workaround

32-bit versions of Windows Vista or Windows 7 can be used with some adjustments to security settings and program compatibility settings. This procedure has proved successful for running OpenEx with a Gigabit interface.

Configuring 32-bit versions of Windows Vista or Windows 7 for TDT software installation

  1. First, you must be using an Administrator account.

    Turn off the User Account Control (UAC) for the account that will be used to install the applications.

    The option to turn this on or off is seen when viewing the details of your user account.

  2. Download the software installation packages from the web from here: V70 software installation packages Contact TDT to request passwords for applications you have purchased.

  3. Edit the properties of the *.EXE installation files. Under the Compatibility tab, click the Run this program in compatibility mode for: checkbox and choose Windows XP (Service Pack 2) in the dropdown.

  4. Run the install packages as normal. Start with the TDT Drivers and reboot when asked. Install OpenEx before installing OpenDeveloper, OpenExplorer or OpenSorter.

Hardware Installation

Windows will recognize your hardware when it is first installed. When prompted, let windows search for drivers automatically. If you have any further difficulty, contact TDT Support.

Solution

Upgrade to Optibit Interface (FO5 with PO5/PO5e/PO5c/UZ3) and the latest version of TDT software. Current drivers are also compatible with the 64-bit USB Interface.

Not enough space on drive C: to extract package

TN0831

Product: TDT Drivers
Version: < 71
Date Added: 2008-06-27

Issue

When installing TDT software, the following error prompts:

"Error: There is not enough space on drive C: to extract this package. Please free up [space] and click Retry."

The issue occurs due to a miscalculation in the amount of free space computed to extract the installation files to your computer. The error may occur even if there is enough free space on the target drive.

Workaround

Run the windows disk clean-up utility to remove unnecessary temporary files and free up additional space. Double-click the package and attempt to extract again.

Solution

Upgrade to latest packages.

Unable to install software from disk

TN0251

Product: TDT Drivers
Version: < 71
Date Added: 2007-04-23

Issue

If the TDT Install Disk is not run from the primary CD or CD/DVD drive, the TDT Drivers, SykoFizX, OpenEx, and OpenExplorer cannot be installed from the disk. When the installation menu is displayed, clicking the button for any of these applications fails to launch the installation.

Workaround

Move the CD to the primary CD or CD/DVD drive

'Bad XM-Data read' error message displayed when performing a Transfer Test in zBUSmon with an RX7 with version 59 microcode

TN0201

Product: TDT Drivers, RX7
Version: 59
Date Added: 2005-11-07

Issue

When performing a Transfer Test in zBUSmon with an RX7 with version 59 microcode, a 'Bad XM-data read' error message is displayed.

Workaround

Use version 58 microcode with the RX7. If you have already loaded version 59 drivers and programmed your RX7, contact TDT for a version 58 microcode replacement file.

RP2.1 DACs and ADCs will not function with v59b microcode

TN0189

Product: TDT Drivers, RP2.1
Version: 59b release 44 (before 08/02/2005)
Date Added: 2005-06-22

Issue

Installing TDT Drivers v59b release 4 (downloaded before 08/02/2005) and updating the microcode on an RP2.1 causes the DACs and ADCs to lose functionality. The RP2.1 will display properly in zBUSmon and it will load and run circuits, however no analog signal will appear on the outputs and no analog signal will be converted on the inputs.

Solution

As of 8/02/2005, the downloadable file TDT Drivers/RPvds v59b - release 4, available on the Downloads page, contains version 58 microcode for the RP2.1 module, which resolves the problem. If you are experiencing the problem, download the latest version of TDT Drivers/RPvds v59b - release 4, install the drivers, and reprogram the microcode on your RP2.1.

zBUSmon returns invalid version numbers when using USB 2.0

TN0167

Product: TDT Drivers, UZ2, UB2
Version: All
Date Added: 2005-01-24

Issue

When using the UB2/UZ2 USB 2.0 interfaces, clicking the Hardware Reset button in zBUSmon will change the version numbers to 65535 and a transfer test will fail.

Workaround

After using the Hardware Rest button wait 20 seconds, then close and reopen zBUSmon. The correct version numbers should be displayed.

'Bad XM' error message

TN0131

Product: TDT Drivers
Version: 57
Date Added: 2003-12-11

Issue

When running a Transfer Test in zBUSmon, a "Bad XM" error message is displayed.

Workaround

Please contact TDT at +1.386.462.9622.

Solution

Update to latest version of TDT Drivers.

Running multiple TDT applications causes crash

TN0118

Product: TDT Drivers
Version: All
Date Added: 2004-04-02

Issue

TDT System 3 hardware can only communicate with one application at a time. Addressing the hardware from multiple applications can generate data errors as well as potential hardware crashes. Programs such as BioSigRP and SigGenRP, which could be run at the same time with System II hardware, can cause communication problems when run at the same time with System 3 hardware. OpenEx applications avoid this issue by having a single application acting as server to client applications that control the hardware. However, when using OpenEx or Synapse applications it is important to NOT use the TDT ActiveX controls. Use the TDevAccX control for OpenEx and SynapseAPI for Synapse.

Logical device number changes after cycling power on system

TN0019

Product: TDT Drivers
Version: <= 46
Date Added: 2002-07-22

Issue

Each time you cycle the power on the system it changes the position of the zBUS racks with logical devices. Closing RPvdsEx and other programs before cycling power may help to avoid this problem.

Workaround

Reboot the system.

Messages when installation is attempting to delete files

TN0017

Product: TDT Drivers
Version: <= 46
Date Added: 2002-08-20

Issue

During installation, sometimes messages come up stating one of several things:

  • locked file cannot be deleted, do you want to try again?

  • shared file, do you want to delete?

  • read-only file, do you want to delete?

Solution

The proper response is to choose Ignore for the locked files, Yes for the shared files and Yes for the read-only files.