Serial WinCE 4.2-6.0. Driver Version 184.108.40.206 © Future Technology Devices Intl. Ltd. 2008 ftdi_ser.dll - the serial driver - type this in when prompted after device plug in. FTDIPORT.INF - inf file Copy both files (if required - see INF files for additional information) to the \Windows directory then plug in device. Dialog will prompt for a driver name - use "ftdi_ser.dll" in full. Release 220.127.116.11: Resolved interface selection issue for FT2232H and FT4232H. Release 18.104.22.168: Included support for FT2232H and FT4232H. Release 22.214.171.124: Changes for CE 6.0 compatibility. Included file version info viewable from Windows Explorer. Release 126.96.36.199: Fixed an issue with .NET serial port component compatibility. Release 188.8.131.52: Fixed an issue with multiple ports above COM10 on Widows CE 5.0 and later. Works with Windows Mobile 6 (Windows CE 5.2). Release 184.108.40.206: Added support for 255 COM ports on CE 5.0 and later (COM0 - COM 254). Release 220.127.116.11: Modified location of registry keys under ClientDrivers and LoadClients. Release 18.104.22.168: Added registry setting to use CeSetThreadPriority API to set bulk thread priority (BulkPriorityEx) (CE 5.0 and above only). Release 22.214.171.124: Bug fix for notify on device removal Release 126.96.36.199: Potential lockup on Write to device fix. Release 188.8.131.52: Event Char 0x0D included in DCB setup. Release 184.108.40.206: 232R extended command support added (Latency Timer etc). Release 220.127.116.11: Flow control on infinite timeout fix. Release 18.104.22.168: Added EV_ERR support. Release 22.214.171.124: Updated persistant unplug/replug. Release 126.96.36.199: Internal release fixing persistant unplug/replug issues. On persistant unplug WriteFile, ReadFile, and IOCTL will return ERROR_GEN_FAILURE instead of ERROR_INVALID_HANDLE Release 188.8.131.52: Persistant unplug/replug with ConfigData entry (see README.txt). Release 184.108.40.206: Fix Access on unplug. Release 220.127.116.11: Memory leak bug fix in unplug/replug. Release 18.104.22.168: Internal release. Release 22.214.171.124: Modem Emulation support added (requires EmulationMode registry setting as per Application Note AN232B-09 and INF Files Readme). ActiveSync monitoring support added (requires registry setting - see INF Files Readme). Release 126.96.36.199: Removed persistent registry FIX in 188.8.131.52 to allow for unique COM port settings. Release 184.108.40.206: Added support for notify on device removal (using the FTVCP2G.dll) Release 220.127.116.11: Bug fix with persistent registry not allowing unique driver settings on install Minor internal changes. Release 18.104.22.168: Calculates baud if no ConfigData setting in registry Removed ConfigData as a default INF file setting Release 22.214.171.124: Added support for Ratoc USB host Release 126.96.36.199: Fixed RLSD event reporting Release 188.8.131.52: Alias baud rate functionality Unique device settings in registry (Requires devices with serial number) Driver version number in registry Fixed disconnect on open port bug Release 184.108.40.206: Initial release after Beta testing Tested with: AMD Personal Internet Communicator RATOC Host CF card (REX-CFU1) - with Toshiba e800 Toshiba e800 with Presentation pack (PA3326U-1PRP) Toshiba e400 with USB host cable CEPC - running Windows CE 4.2 Further information about FTDI's products as well as updates of drivers can be obtained from FTDI's web site at URL http://www.ftdichip.com We recommend that customers join the FTDI Newsletter. The FTDI NewsLetter is a e-mail based service which allows you to receive the latest FTDI related news, product releases, current driver version information. To join the FTDI NewsLetter, go to our web site http://www.ftdichip.com and click on the "FTDI NewsLetter" button on the LHS navigation panel. For technical support on our products and drivers, please e-mail email@example.com For sales enquiries please e-mail firstname.lastname@example.org For general enquiries please e-mail email@example.com Disclaimer This software is supplied on an as-is basis and no warranty as to their suitability for any particular purpose is either made or implied. Future Technology Devices International Ltd. will not accept any claim for damages howsoever arising as a result of use or failure of this software. Your statutory rights are not affected. This software or any variant of it is not intended for use in any medical appliance, device or system in which the failure of the product might reasonably be expected to result in personal injury. This document provides preliminary information that may be subject to change without notice.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.