delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT sources DOT redhat DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT sources DOT redhat DOT com> |
List-Help: | <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT sources DOT redhat DOT com |
Delivered-To: | mailing list cygwin AT sources DOT redhat DOT com |
Date: | Wed, 18 Oct 2000 21:29:21 -0400 |
From: | cgf AT redhat DOT com |
To: | cygwin AT sources DOT redhat DOT com |
Subject: | cygwin on a 386? |
Message-ID: | <20001018212921.A9690@cygnus.com> |
Reply-To: | cygwin AT sources DOT redhat DOT com |
Mail-Followup-To: | cygwin AT sources DOT redhat DOT com |
Mime-Version: | 1.0 |
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 AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |