Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Jonadab the Unsightly One" Organization: There is no organisation. To: cygwin AT cygwin DOT com Date: Wed, 27 Jun 2001 10:50:53 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Windows processes (was Re: two problems with cygwin's zip) Reply-to: jonadab AT bright DOT net Message-ID: <3B39BA8D.12229.76377D@localhost> In-reply-to: <20010627015444.M19058@redhat.com> X-Eric-Conspiracy: My name is not Eric. X-Platform: Windows '95 OSR2 (heavily adjusted and customised) X-mailer: Pegasus Mail for Win32 (v3.12) # One reason for that is that iterating over all of the processes in the # system is not a trivial task. You use different mechanisms in Windows # NT and Windows 9x. Furthermore, the way Windows (not sure about NT) handles processes is pretty darn bizarre. I've got some half dozen different ways to look at the process list (taskbar/systemtray, Close Program dialog, native port of kill someone did using NT, EndItAll, HandleEx, killdll, ...) and at any given time no two of them report exactly the same list of processes. I'm not the least bit sure Windows even maintains a single exhaustive list. # In VMS, paths look like this: sys$diskc:[windows.system]kernel32.dll . Heh. You have unwittingly armed me with knowledge I can use at work (where we have an actual VMS system but no VMS manuals). Previously I never understood the VMS path syntax, but seeing a familiar recognisable path in that syntax has clued me in. -- jonadab -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/