Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 18 Oct 2000 21:29:21 -0400 From: cgf@redhat.com To: cygwin@sources.redhat.com Subject: cygwin on a 386? Message-ID: <20001018212921.A9690@cygnus.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: cygwin@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i I am contemplating adding some more assembly language stuff to Cygwin but on reading the Microsoft docs, it became apparent that some of the cruft in Windows 95 is due to its ability to run on a 80386 platform. So, things like InterlockedIncrement and InterlockedExchange, which are relatively simple on NT are amazingly complicated on Windows 95. So, my question is, has anyone ever used cygwin on a 80386 system? I'm wondering if it works at all right now. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com