From: usagi.tsukino@pinku.zzn.com (Steve Nickolas)
Subject: [TUHS] v6on286
Date: Wed, 9 Jul 2003 11:25:12 -0500 [thread overview]
Message-ID: <B7188237D5E93714FBC9EBACA1463010@usagi.tsukino.pinku.zzn.com> (raw)
>From: Kenneth Stailey <kstailey at yahoo.com>
>Sent: Wed, 9 Jul 2003 05:37:09 -0700 (PDT)
>To: Steve Nickolas <usagi.tsukino at pinku.zzn.com>
>Subject: Re: RE: [TUHS] v6on286
>The README says:
><< The kernel makes heavy use of the special 286 protected mode
>features >>
>Try bochs set to be a 286.
I figure that a Celeron is a superset of the 386 - ergo, of the 286
also - so there shouldn't be a problem. Maybe I'll do that though,
it's safer in a sandbox.
>I am wondering if Cygwin could be used to build the code. I see that
>ancient C stuff like "=+" was eliminated already.
!!
I think if you converted the ASM to some other format, you could use
Turbo C++ to build it, though...haven't tried that, I don't grok ASM.
>Plus check this site out:
>
>http://www.thefreecountry.com/compilers/cpp.shtml
LOL, I have 6 working C compilers on the Windows/DOS side of my box
already :) (Turbo C++ 1, Borland C++ 3, Watcom C 11, djgpp, MinGW32,
Cygwin)
-uso.
kirei-na pinku-na E-MAIL-saito
___________________________________________________________
Get your own Web-based E-mail Service at http://www.zzn.com
next reply other threads:[~2003-07-09 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 16:25 Steve Nickolas [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-11 18:38 JStevens
2003-08-08 22:14 JStevens
[not found] <20030709002523.GA7146@minnie.tuhs.org>
2003-07-09 2:34 ` Maciek Bieszczad
2003-07-08 16:08 Steve Nickolas
2003-07-08 5:21 Steve Nickolas
2003-07-08 15:07 ` Maciek Bieszczad
2003-07-09 7:00 ` SZIGETI Szabolcs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B7188237D5E93714FBC9EBACA1463010@usagi.tsukino.pinku.zzn.com \
--to=usagi.tsukino@pinku.zzn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).