X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<16897467.post@talk.nabble.com>
Date:	Fri, 25 Apr 2008 09:26:02 -0700 (PDT)
From:	Nefastor <nefastor AT hotmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	RE: Looking for basic documentation on Cygwin and Serial Ports
In-Reply-To:	<28D25EB5A34E89408B73B6793C742171CAB6B4@nutmeg.CAM.ARTIMI.COM>
MIME-Version:	1.0
X-Nabble-From:	nefastor AT hotmail DOT com
References:	<16827997 DOT post AT talk DOT nabble DOT com> <480F02EA DOT AF265921 AT dessent DOT net> <16853883 DOT post AT talk DOT nabble DOT com> <28D25EB5A34E89408B73B6793C742171CAB6B4 AT nutmeg DOT CAM DOT ARTIMI DOT COM>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Thanks Dave, I kinda suspected the FTDI drivers for the COM3 issue (I've seen
worse : once, the COM port number would be incremented every time the cable
was unplugged and replugged). Unfortunately I'm stuck with FTDI chips as
they are, AFAIK, the only USB-to-serial adapters I can buy as chips and
solder myself.

The device and/or driver info I was asking about is just that : whatever
system variable(s) hold the information about the hardware present on the
PC. I'm no Windows programmer (though not for lack of training), I suppose I
can find my way from the win32 pnp API. Thank you for the pointer.

The program I'm trying to write is for an autonomous machine. Normally I'd
design my own single-board computer for maximum reliability but this time I
need the functionality of an OS like Windows or Linux. I'm trying to make
the behavior of that OS as predictable as possible, because the end-product
will have to operate away from someone who could "CTRL-ALT-DEL" it (and it
would really be overkill to install VNC on my application :-U)

Thanks for all the info, everyone :-D. I'm gonna try a few things and get
back to you.

Nefastor
-- 
View this message in context: http://www.nabble.com/Looking-for-basic-documentation-on-Cygwin-and-Serial-Ports-tp16827997p16897467.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -