Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-Id: <4.3.2.7.0.20001018214927.00c8bb50@pop.bresnanlink.net>
Date: Wed, 18 Oct 2000 21:52:54 -0500
To: cygwin@sources.redhat.com
From: Chris Abbey <cabbey@chartermi.net>
Subject: Re: cygwin on a 386?
In-Reply-To: <20001018224518.B10333@cygnus.com>
References: <035d01c03976$730e6020$3c5350d8@guinness>
 <20001018212921.A9690@cygnus.com>
 <4.3.2.7.0.20001018211721.00b78990@pop.bresnanlink.net>
 <20001018223351.A10333@cygnus.com>
 <035d01c03976$730e6020$3c5350d8@guinness>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

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@sourceware.cygnus.com