 |
|||
 |
 |
||
      |
 |
 |
|
To install the new drivers, please unplug the 3540, go into Control Panel-> Add/Remove programs, and uninstall the program "FTDI FTD2XX USB Drivers". Restart the computer to complete the un-installation. Then unzip the USB drivers to a folder on your Desktop, and turn back on the 3540. When the Add New Hardware wizard comes up, choose "Specify a Location", choose the USB drivers folder you created on the desktop and it will install using the new drivers. The Add New Hardware wizard will run twice, for the 3540 CPU and the DSP. When it completes the second time, start win3540, and please verify the win3540 version is correct (right-click in titlebar - About). |
 
To download the latest 3540 software, click the top link:Update 10/10/06 (win3540 ver. 2.9.3.0, System ver. 2.9.0.5) Changelog: New USB drivers supported, Japanese Caller ID Changed to accept ring-trip as valid CAR acknowledgement. Update 7/31/06 (win3540 version 2.9.2.0, System version 2.9.0.1) Changelog: New USB drivers supported, better DTMF detection in Network Emulation and Caller ID screens, Australian Type II Caller ID dialtone modulation fixed, and "3540 received an unknown transmission error" clarified to "3540 received FSK it didn't understand" or "3540 received a Caller ID Event out of sequence". (Patches below this line are no longer supported, kept for archival purposes only): Update 3/28/06 (win3540 version 2.8.7.2, System version 2.8) Changelog: Fix script parser to be compatible with dos tab character (0x09). Update 3/15/06 (win3540 version 2.8.7.1, System version 2.8) Changelog: Fix of sendCas/sendAlert level bugs. Update 3/14/06 (win3540 version 2.8.7, System version 2.8) Changelog: Reenabled Calling B to A on Network Emulation Screen. Update 2/8/06 (win3540 version 2.8.6, System version 2.6) Changelog: Corrected OSI bug, DTMF Decoding bug, and "Modem" Script command bug. They all work properly now. Update 12/12/05 (win3540 version 2.8.5, System version 2.6) Changelog: Corrected Ring detection bug. If 3540 was acting as FXO, it would detect Polarity Reversal as a ring. This update addresses that, and adds more robust country-specific caller id detection. Update 7/7/05 (win3540 version 2.6, System version 2.6) Changelog: Fixed RSL 3.0 compatibility bug. DUALTONE command generated Parameter Clipped error when it shouldn't have. This update addresses that problem. Update 4/26/05 (win3540 version 2.6, System version 2.5.1) Changelog: Fixed Japanese Caller ID bug. When the length of the phone number is 14, a duplicate DLE character must be added. This update addresses that problem. Update 4/15/05 (win3540 version 2.5.3, System version 2.5.1) Changelog: Fixed 3500 to 3540 script bug. When 3500 scripts were run, some fields were incorrect. This update addresses that problem. Update 3/17/05 (win3540 version 2.5.2, System version 2.5.1) Changelog: Fixed Caller ID Checksum bug. When a non alphanumeric character (such as . , &) was put in the Calling Name field, the checksum was calculated incorrectly. This update addresses that problem. Update 9/23/04 (win3540 version 2.2.5, System version 2.3.1) Changelog: Fixed System Info bug. Some users reported disconnect errors when going to the System screen and leaving suddenly. This update addresses that problem. Update 9/13/04 (win3540 version 2.2.5, System version 2.3.0) Changelog: Fixed long command bug. Commands longer than 128 bytes were ignored by the 3540. This update addresses that problem. Update 8/27/04 Changelog: Fixed large font bug. Using large fonts caused buttons to not be shown. This update addresses that problem, and includes other enhancements. Update 8/25/04 Changelog: Fixed USB disconnect bug. USB would disconnect if left on overnight. This update addresses that problem, and includes other enhancements. |
|
|