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
Message-Id:	<4.3.2.7.0.20001018214927.00c8bb50@pop.bresnanlink.net>
X-Sender:	cabbey AT pop DOT bresnanlink DOT net
X-Mailer:	QUALCOMM Windows Eudora Version 4.3.2
Date:	Wed, 18 Oct 2000 21:52:54 -0500
To:	cygwin AT sources DOT redhat DOT com
From:	Chris Abbey <cabbey AT chartermi DOT net>
Subject:	Re: cygwin on a 386?
In-Reply-To:	<20001018224518.B10333@cygnus.com>
References:	<035d01c03976$730e6020$3c5350d8 AT guinness>
	<20001018212921 DOT A9690 AT cygnus DOT com>
	<4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001018211721 DOT 00b78990 AT pop DOT bresnanlink DOT net>
	<20001018223351 DOT A10333 AT cygnus DOT com>
	<035d01c03976$730e6020$3c5350d8 AT guinness>
Mime-Version:	1.0

At 22:45 10/18/00 -0400, Christopher Faylor wrote:
>So, somebody would have to install Windows 95 onto the emulator, then.
>Wow.

yup, all I remember is what he told me, that it presented an 80386 chip
and all the accompanying controllers, and a bios. I know he had MS DOS
working on it, because we exchanged word perfect files all the time. Beyond
that I've no idea about the rest of his setup.

Now that I've had a minute to think about this though, let me ask you
a better question.... WHY? What could you possibly want to put into
cygwin that you feel it HAS to be done in asm? And that you can write
better asm for this than gcc?


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -