X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 23 Oct 2007 12:32:08 -0500 From: Brian Ford Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: RE: milliseconds on Windows In-Reply-To: <000201c81593$045ae260$02fea8c0@DDZG9K91> Message-ID: References: <38624 DOT 131 DOT 220 DOT 7 DOT 1 DOT 1193151578 DOT squirrel AT webmail DOT iai DOT uni-bonn DOT de> <000201c81593$045ae260$02fea8c0 AT DDZG9K91> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes 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 On Tue, 23 Oct 2007, Robert D. Holtz - Lists wrote: > If you're feeling frisky it's also possible to write a low level routine > that hooks the hardware clock and uses it for retrieving the time. Or simply use QueryPerformanceCounter. > This clock does go down to microsecond granularity. Sure, there are lots of solutions to measuring time more accurately. The solution I provided is better suited for scheduling processes as accurately as Windows allows. -- Brian Ford Lead Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained crew... -- 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/