On Fri, Jul 28, 2006 at 11:07:06AM +0200, [EMAIL PROTECTED] wrote:
> Hello
>
> Every USB to serial adapter I've seen so far is using these Prolific
> drivers.
> Seems it's same thing as for the USB to Bluetooth, a great majority is
> using the very same hardware.
How many have you tried? I have tested two so far, and have seen two
different drivers.
The 'Prolific' as previously described for the Newlink device, and the
device whose manufacturer I do not know, whose driver offers these
different characteristics:
Driver Provider: FTDI
Date: 19May2006
Version 2.0.0.0
Baud Rates: 300-921600
Data Bits: 7,[8]
Stop bits: [1],2
Flow control: Xon/Xoff,Hardwarre,[None]
USB Transfer rates Rv: 64-[4096]
USB Transfer rates Tx: 64-[4096]
Latency timer(ms): 1-255 [16]
Read Timeout (ms): [0]-10000
Write Timeout (ms): [0]-10000
Miscellaneous: Serial Enumerator (on), Serial Printer (off),
Cancel if Power off (off), Event on surprise removal (off),
Set RTS on close (off), Disable Modem Ctrl at Startup (off)
The driver for the borrowed device was found by letting Windows search
on the Internet - and connecting a Windows machine to the network
is something I don't normally like doing.. It also results in the
system being permanently lumbered with this driver - as doing an
'uninstall' of the driver doesn't result in a need for the network
to be connected next time I plug it in :-/
My guess is that the USB devices can not provide details of their capabilities,
but can provide a unique device identifier which can be matched with
information provided by the manufactuerer (via a Windows driver).
Can anyone familiar with the USB hardware interface or USB serial spec
confirm or correct this?
Regards,
DigbyT
--
Digby R. S. Tarvin digbyt(at)digbyt.com
http://www.digbyt.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
