Re: Uc232a Usb To Serial Driver Xp
Anfos Sin
If the driver listed is not the right version or operating system, search our driver archive for the correct version. Enter ATEN UC232A into the search box above and then submit. In the results, choose the best match for your PC and operating system.
Once you have downloaded your new driver, you'll need to install it. In Windows, use a built-in utility called Device Manager, which allows you to see all of the devices recognized by your system, and the drivers associated with them.
However you need to change the copied section just above the copied section to create a different key for the driver. Change the key by entering the hex value for the Vendor Id in hex, an underscore, and then the Product Id in hex reported by the System Report tool. For example the duplicate 067B_2303 would be changed to 0557_2008 for the Aten Cable.
To get the USB adapter to work with Linux I initially used my Slackware 8.0 box with kernel 2.4.8. Today I am using 2.4.13 and it's still working fine. You need at least a 2.4.6 kernel. The driver for this RS232 serial line to USB converter is fairly new and was introduced with the 2.4.6 kernel.
This article describes the procedure for downloading and installing version 2.0.2.1 of the Bridgemate Pro server USB-to-serial converter (dongle) for 32-bit versions of Microsoft Windows. In case you experience connection problems with the Bridgemate Pro server, it is recommended the driver be updated.
Version 2.0.2.1 of the Aten USB-serial converter driver has been tested successfully on 32-bit version of Microsoft Windows XP, Windows Vista and Windows 7. Version 3.7 and 3.8 of the Aten driver cd-rom contain this version of the driver (the version number of the cd-rom is written on the cd-rom itself). Previous driver cd-roms and driver files downloaded from the internet possibly contain older versions of the driver and applying these drivers may result in problems during use. Possible symptoms are:
This driver should only be used on 32-bit versions of Microsoft Windows XP, Windows Vista or Windows 7; this driver has not been tested on W8, 8.1 or 10 32-bit systems. On 64-bit operating systems Windows Vista, 7, 8, 8.1 or 10, use the 64-bit driver instead.
If Windows keeps using the older driver after uninstalling the driver, you should permanently delete the driver files. Note: incorrect deletion of files may damage your Windows system. Bridge Systems is not responsible for any action you take when uninstalling these driver files.
USB devices have high throughput, but they use a shared data bus. Data is wrapped up and transferred in packets. To handle the packets and move data in and out of the program accessing the USB device, a software driver is needed. The software driver sits between the hardware and the computer program you are using, and it must be installed and working correctly.
For USB to RS-232 chips, there are two primary manufacturers: Prolific and FTDI. Because off-brand chips with poor drivers are unreliable, Campbell Scientific recommends and currently sells a cable using an FTDI chip (part number 17394). We chose this cable because it uses a chip that has a certified driver available on Windows Update. (The older cables were silver in color and did not have a driver available for Windows beyond version 7.)
I have an issue where my prolific USB to Serial adapter stopped being detected as 'n "Ports (Com & LPT)" device. It keeps on detecting it is a " USB Composite" device, even after installing the correct Windows drivers downloaded directly from the manufacturer's website. Uninstalling it and reinstalling it doesn't help.
I get the same result on another computer also running Windows 10. It simply refuses to recognize the adapter as a USB to Serial device anymore and keeps on detecting it as a "USB Composite" device as soon as you plug it in after uninstalling it and restarting Windows. Windows also claims that it finds no better driver than the one currently installed when doing a driver search, even after installing the manufacturer drivers.
Hi,
I'm facing a weird problem with my USB to serial-adapter. The adapter has a Prolific-2303 chipset. The COM port is not getting detected by the Windows 7 laptop.
I've installed the drivers and restarted the computer after installing the drivers.
I've run the driver update from the device manager and updated the drivers.
I also tried to install the COM port manually from the device manager.
I checked the adapter by connecting it to another desktop computer and the COM port is getting detected.
Where possible, the drivers applicable to each device or classof devices is listed. If the driver in question has a manual pagein the FreeBSD base distribution (most should), it is referencedhere. Information on specific models of supported devices,controllers, etc. can be found in the manual pages.
Note: The device lists in this document are beinggenerated automatically from FreeBSD manual pages. This means thatsome devices, which are supported by multiple drivers, may appearmultiple times.
With all supported SCSI controllers, full support is providedfor SCSI-I, SCSI-II, and SCSI-III peripherals, including harddisks, optical disks, tape drives (including DAT, 8mm Exabyte,Mammoth, and DLT), medium changers, processor target devices andCD-ROM drives. WORM devices that support CD-ROM commands aresupported for read-only access by the CD-ROM drivers (such ascd(4)). WORM/CD-R/CD-RW writingsupport is provided by cdrecord(1), which is a part ofthe sysutils/cdrtools port in the PortsCollection.
The sis(4) driver supports SiliconIntegrated Systems SiS 900 and SiS 7016 based Fast Ethernetadapters and embedded controllers, as well as Fast Ethernetadapters based on the National Semiconductor DP83815 (MacPhyter)chip. Supported adapters include:
Lucent Technologies WaveLAN/IEEE 802.11b wireless networkadapters and workalikes using the Lucent Hermes, Intersil PRISM-II,Intersil PRISM-2.5, Intersil Prism-3, and Symbol Spectrum24chipsets (wi(4)driver)
About PCI: you don't use the bus number at all. The sequence of PCI device:function id-s starting from the root bridge through all downstream bridges and ending at the device gives you a guaranteed unique mapping for that hardware regardless of BIOS, kernel, etc. You only need to define a mapping once for a motherboard/CompactPCI chassis and you get a reliable physical slot identification. That is how it is supposed to work and incidentally that is how Windows identifies its PCI devices.
udev and sysfs provide the same information, so it is technically possible to get the same functionality in Linux.
In a previous life I had to do stuff like hack an embedded PC BIOS and Windows bus driver to support huge numbers of PCI devices. The BIOS code was so bad it was scary (to this day I am impressed that PCs can boot at all), but the PCI bus itself at the logical level was a joy.
So purely as a user of USB, I naively believed that it was similar to PCI.
And I am surprised you commented on i2c. It is fundamentally different from USB - the device ids are fixed, or you can choose a bit at most (in hardware). There is no plug and play. Often you can't even have two devices of the same kind on the same bus. It takes half an hour to implement I2C from scratch via bit banging :-)
And ISA. Oh, ISA... It didn't have slot id-s, but it did have jumpers :-) Not to mention you could actually build an ISA board from scratch and do the decoding manually with wires... Good times.
User-friendly disk names Posted Jun 27, 2011 3:33 UTC (Mon) by dlang (guest, #313) [Link]
Do they _really_ work perfectly in Windows? In my experience, cheap serial converters are prone to dropping a byte now and then, and when I searched online it turned out that it was hardware not drivers -- Windows users would experience the same problem given the same level of usage and attention to detail (it just happens a lot less often, because there are more of us Linux developers making heavy use of serial ports).
Sorry I can't find an actual reference explaining the hardware issue on a common PLX usb-serial chip; there is no sufficient replacement yet for the recently-discontinued Google Linux search :`-(
I agree that keyspan did not have these problems, but they were significantly more expensive and seem to have lost out to the even cheaper but somewhat flaky adapters...
If there are current multi-port adapters that really do have higher quality chips in them (i.e. like keyspan rather than PLX) but lack Linux drivers, then somebody should get in touch with the Linux Driver Project and donate such an adapter!
USB Serial port woes Posted Jun 27, 2011 3:34 UTC (Mon) by mikov (guest, #33179) [Link]