X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: 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> <16897467 DOT post AT talk DOT nabble DOT com> Subject: RE: Looking for basic documentation on Cygwin and Serial Ports Date: Fri, 25 Apr 2008 17:31:52 +0100 Message-ID: <022601c8a6f1$de46f320$2708a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <16897467.post@talk.nabble.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Nefastor wrote on 25 April 2008 17:26: > Thanks Dave, I kinda suspected the FTDI drivers for the COM3 issue One tip I've learned is never, ever, ever, unplug them while you're still running your terminal software (or whatever) and it's got the port open. Disconnect, or exit the application, or you're screwed until you reboot. However, discussion of their many and varied flaws is getting fairly far off-topic because it's not cygwin-specific; if you'd like to pursue that angle, we should TITTTL. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/