In Windows XP the numbers for USB serial port dongles keep moving around, which makes it hard to use in scripts or makefiles (for example for flash programming NXP controllers via their built-in bootloader, or for controlling a target and two lab devices at the same time).
Prolific Usb To Serial Comm Port Driver Windows Xp
Download File: https://shoxet.com/2vAOC6
Is there a way to fix the COM-port for such a dongle? In Linux I can do this via udev by matching against the serial number of FTDI dongles (see this answer I just gave while searching for an answer to this question).
The FTDI driver will assign serial ports to the same COM ports by the serial number of the device connected. So, the ports should remain the same regardless of USB port. However, if you plug in a new USB device, it will not reuse the previously assigned COM ports.
the real 9/25 pins serial port will not show in the mode status, only those USB2serial will be, if got the right setting. if it didn't show up or not show the right speed as for printer will print funny letters, etc.
using mode to test the usb2serial device:using mode set the com? to hardware or XonXoff, if it show none or it cann't be set, then this device's driver BUGs or device is part faulty.It still work on NONE detection condition,.. that fine if you do not need any detection of the hardware.example: check is the printer online for print, NONE will not provide the offline status,..
not to mention of Pl2303 usb,.. ca-42 & dku-5, have them all for last 3 monthseach of it can only use on different version of driver,..most new PC only has USB ports,.. so I found 1 ca-42(com1) for cell phone & 1 usb2serial(com2) for printer. I havefacing so much problems. tried use 1 pl2303 & 1 CH340 (different drive) problem too because of the ser2pl.syslook as it not share by 2.
Use "FT_INF 2.0.61.242 - Custom INF File Generator"and set "Initial Index" to the first COM port number to be assigned (e.g. 32).Then install the FTDI driver using the newly generated .inf (might require .cat file self-signing)
I have a few handheld radios that I need to update the frequencies and when I connect to the USB, it fails to connect. In device manager and Ports it says - "Please install corresponding PL2303 driver to support Windows 11 and further OS"
Windows 11 update loaded Prolific PL2303 driver 3.8.40.0 and when I go to device manager it says "Please install corresponding PL2303 driver to support Windows 11 and further OS" This driver does not even attempt to communicate with my X10 CM11 hooked to my serial port. I had to go to Prolific website and load their current driver 3.6.81.357. (uninstall driver first) Serial to X10 device now working fine. Don't install Windows update for Prolific or it will change it back.
Check in device manager for the presence of serial pointing devices, andcheck which comm port they are using. If you find one, click properties andchoose disable. If you delete it Windows will re-install it.
Also, I just wanted to verify that the software you are using, SMC60WIN supports using running multiple instances and comm ports at the same time. I installed it on our XP computer, and a single instance seems to allow only one comm port to be set. I wonder that when you try to open a second instance and set a new comm port, it causes a conflict on the comm port that is set for the first instance that is running.
The other software I am using is called Wedgelink Lite. It allows me to download data from a data collection box to MS Excel. I had to go in using device manager and manually pick the COM port that I wanted this equipment to communicate on. Since I knew that SMC60WIN was operating on COM2 I select COM7 which seemed to be the next available port.
You would be correct. I am running an instance of each of those softwares. Within the SMC60WIN I had to tell the software which COM port to use and I used the port that was shown in the device manager which was COM2. After getting that to work I plugged in the second usb to serial adapter for the data collection box. I have to do the same thing for this device as well. I went in and had to tell the software which COM port to use which was COM7. If I go into the device manager and look under ports as you have shown. In the description, the parentheses it lists COM7 for both devices. I do not recall having to change this in device manager, only in the software.
windows update is updating ser2pl64.sys from 2.0.13.130 to 3.4.36.247 (especially after the prolific installer has been installed; or when you hit the driver update button from the driver properties).
int main(int argc,char** argv) HANDLE hfile = CreateFile(serial_port ,GENERIC_READ
The prolific driver version 3.3.2.102 works in Windows 10 with older Prolific cables (with real or fake chips). The latest version from the Microsoft driver repository does not because Prolific has deprecated the older chips because the Chinese were creating fake copies. It has nothing to do with Windows. The trouble is the web driver update from Microsoft's repository will update the driver by default unless you turn off the driver updating which of course then affects all other drivers that you do want to keep up-to-date.
So although group policy editor only exists in Pro editions of Windows, it is just a front-end to the registry. So, to prevent the prolific driver from being updated in Windows 10/8/7 use the registry:
Basically, you can do this via gpedit.msc if you have Windows Pro, if not, do it via a reg file and import into the registry. Then all other drivers can still be updated via the default web search. I would also recommend hiding the prolific driver update in Windows update. In Windows 10, you must use the windows update troubleshooter to hide it...
Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC. Application software can access the USB device in the This page contains the VCP drivers currently available for FTDI devices.
Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC. Application software can access the USB device in the same way as it would access a standard COM port.
Download free driver for Prolific USB-to-Serial Comm Port Windows 2000, Windows XP, Windows 2003, Windows XP x64, Windows 2003 x64If You cannot find the appropriate driver for your operating system you can ask your question to the users of the service in our section of questions and answers or contact our support team at
Adapter FAQ Bluetooth to serial adapterEthernet to Serial Adapters: Digi One SP Moxa Nport 5110DocuClock Time Stamper Star Sync GPS time receiverCell Sync CDMA receiverRadio Sync WWVB time receiver
If the O/S in your laptop is Windows Vista, you may not needto install the driver by yourself, just plugthe USB adapter into a USBport and let the Vista search the driver for you. Most likely the Vista willdownload and install it automatically.
NMEA has traditionally been implemented as a serial protocol and therefore, even if a USB connection is used, there needs to be a USB to Serial Port conversion. The specific driver for the each GPS receiver will handle this conversion.
If you change the USB port for the GPS receiver Prolific will reassign the COM port number. This will require repeating steps 4-12 above. If you are having trouble with Prolific drivers and an Error Code, try reading this page
Windows with GNSS Sensor outputs Location/Sensor API data, but OpenCPN needs an NMEA data stream over a virtual serial port. In most cases the integrated GPS receivers just support the Windows Sensor API, the program below uses the API and produces NMEA sentences that OpenCPN can use.
Attaching a GPS device to a Mac is done via one of the USB ports. Whether using a device with its own USB lead or via a serial-USB adapter lead or an NMEA multiplexer with USB port, the appropriate OS X driver needs to be installed. Nearly all hardware uses one of just two chip makes: those from FTDI or Prolific. Both those companies make OS X drivers available on their web sites, but manufacturers of GPS devices usually package the driver with device.
Use of Virtualized Environments such as Parallels, VM, VirtualBox, etc to run an alternative version of Opencpn on your Mac or PC are beyond the scope of this section. However experienced users are invited to report the specifics about using USB ports with Virtual Configurations. Please be specific about the setup and software and explain how virtual USB ports work in that environment. These commenta will eventually make their way into this section. 2ff7e9595c
Comments