Download Cressi Port Devices Driver
- Download Cressi Port Devices Driver Manual
- Download Cressi Port Devices Driver Combo
- Download Cressi Port Devices Driver Ed
Virtual COM Port Driver is available in the Standard and PRO editions, so you can choose the optimal set of features that is perfectly suited to your needs. Standard version Virtual Serial Port Driver is designed to provide your system with an unlimited number of virtual serial port pairs that work like real hardware COM interfaces and fully. In the Device Manager right pane, locate and expand Portable Devices or Other Devices, depending on which one you see. Right-click the name of the device you connected, and then select Update Driver Software. In the Hardware Update wizard, select Browse my computer for driver software and click Next. PC Pitstop - PC Performance Roots. PC Pitstop began in 1999 with an emphasis on computer diagnostics and maintenance. During the early days of the dot com boom, our online PC maintenance tools were skyrocketing.
In our share libs contains the list of USB DISK 2.0 USB Device drivers all versions and available for download. To download the proper driver by the version or Device ID. If not found in our garage driver you need, please contact us, we will help you in time, and updates to our website.
Legacy download files
Legacy PROWIN32 and PROWIN64 download packages provide PROSet, driver, ANS, FCoE, and DCB support for Windows 7* and Windows Server 2008 R2*.
Regular webpacks provide Intel® PROSet support for operating systems Windows 8.1*, Windows Server 2012*, Windows Server 2012 R2*, Windows® 10, Windows Server 2016*, or newer supported operating systems.
Note: New hardware support or new features will not be added to legacy download packages.
Overview
This download contains the Intel® Ethernet network drivers and software for Windows 7*.
Which file should you download?
Note: 10GbE adapters are only supported by 64-bit drivers:
- PROWin32.exe for 32-bit (x86) editions of Windows*
- PROWinx64.exe for 64-bit (x64) editions of Windows
How to use this download
Download the self-extracting archive and run it. It will extract the files to a temporary directory, run the installation wizard, and remove the temporary files when the installation is complete. All language files are embedded in this archive. You do not need to download an extra language pack.
See readme notes if you want to extract the files without installing.
This software may also apply to Intel® Ethernet Controllers. Support for built-in network connections is provided by the system or board manufacturer.
About Intel® drivers
The driver or software for your Intel® component might have been changed or replaced by the computer manufacturer. We recommend you work with your computer manufacturer before installing our driver so you don’t lose features or customizations.
See list of manufacturers’ Support websites.
In the past, manufacturers provided a serial (RS-232) interface to download data from their dive computers. Nowadays, recent systems do not have serial ports anymore, and almost all manufacturers have switched to USB interfaces. In contrast to the legacy serial interfaces, these cables require a driver to operate.
On Windows systems, you can simply install the drivers that are provided with the Windows application.
On Linux and Mac OS X, the situation is more complicated because most manufacturers do not provide a driver for non-Windows systems. However, most USB interfaces contain a serial-to-usb chip from one of the companies listed below, and you can obtain a driver from their website. Note that some Linux distributions or Mac OS X systems, already have these drivers included by default.
- FTDI (driver)
- Silicon Labs CP210x (driver)
- Prolific PL-2303 (driver)
In some cases, the generic driver from the chip manufacturer does not recognize the USB interface automatically and you need to perform some additional steps.
Manufacturer | VID | PID |
---|---|---|
FTDI | 0x0403 | 0x6001 |
Heinrichs-Weikamp | 0x0403 | 0x6001 |
Ratio | 0x0403 | 0x6015 |
Oceanic | 0x0403 | 0xF460 |
Suunto | 0x0403 | 0xF680 |
Suunto (Smartinterface) | 0x0403 | 0x6001 ? 0x6010 ? 0x6011 ? |
Cressi (leonardo) | 0x0403 | 0x87D0 |
Silicon Labs | 0x10C4 | 0xEA60 |
Suunto (CustomIdea) | 0x10C4 | 0xEA60 |
Mares | 0x10C4 | 0xEA60 |
Prolific | 0x067B | 0x2303 |
Reefnet | 0x067B | 0x2303 |
Mares (Nemo Sport) | 0x04B8 | 0x0521 |
Cressi | 0x04B8 | 0x0521 |
Zeagle | 0x04B8 | 0x0522 |
Freescale Semiconductor | ? | ? |
Mares (Icon HD) | 0xFFFF | 0x0005 |
Suunto
The FTDI driver is included in the Linux kernel. The device node (usually /dev/ttyUSBx) will appear automatically once you plug in the USB cable.
Pelagic (Oceanic, ...)
The standard FDTI driver works just fine, but the custom Oceanic VID/PID (Vendor ID/Product ID) is not recognized automatically.
Linux
You need to load the driver manually, by executing the following command (as root):
Download Cressi Port Devices Driver Manual
To make the change permanent, you can add the parameters to the file /etc/modprobe.d/options (or modify the source code and recompile the driver, but that is beyond the scope of this document):
An alternative approach for binding the Oceanic VID/PID to the FTDI driver is executing the following command (as root):
Mac OS X
Note: The latest FTDI driver (version 2.2.14 or higher) recognizes the Oceanic cable automatically and the procedure below is not necessary anymore.
Follow these steps to make the FTDI driver recognize the Oceanic cable:
- Locate the file /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist
- Alter the permissions to make it writeable, but BE SURE TO SET THEM BACK EXACTLY THE SAME AFTER YOU'RE DONE
- Open it, and search for 'Oceanic'. You'll find a Pelagic Oceanic entry (which is apparently something else). Change the idProduct from 62566 to 62560.
- Save, quit and restore the permissions.
- Reload the driver by running the following commands (as root):
Seiko (Cressi, Zeagle, ...)
The standard Prolific driver works just fine, but the custom Cressi VID/PID (Vendor ID/Product ID) is not recognized automatically.
Windows
Update: More detailed instructions are available here.
The Cressi software installs a USB only driver that does not provide a serial interface. Follow this procedure to modify the generic prolific driver to work with the Cressi interface.
- Download and install the generic pl2303 driver from the Prolific website.
- After installing the driver, a new oemXX.inf file (with XX being the last number available) will appear under c:windowsinf.
- Open this file and substitute the original vid/pid (067b 2303) with the 'new' ones (04b8 0521).
- After saving the file, the interface gets recognized as a standard pl2303 usb-to-serial interface.
Note that it's not possible to have two drivers installed for the same device. You'll have to uninstall the usb only driver first. You can always re-install it again.
Download Cressi Port Devices Driver Combo
Linux
Use the Oceanic procedure, with this command (as root):
Replace PID with 0521 (cressi) or 0522 (zeagle).
Mac OS X
Update: I made a bash script to automate the driverpatching. Download the script, start a terminal and runthe command: sudo bash seiko.sh The sudo command is to runthe script with root priviliges. You'll have to enter your password whenasked.
Use the Pelagic procedure.
Download Cressi Port Devices Driver Ed
The Prolific driver you need to modify is named 'ProlificUsbSerial.kext'. Search for the keys idVendor and idProduct, and change the idVendor value from 1659 to 1208, and the idProduct value from 8963 to 1313 (cressi and mares) or 1314 (zeagle).