From: "Hans" <hans64@ht-lab.com>
To: silvercreekvalley@yahoo.com, linux-8086@vger.kernel.org
Subject: Re: Starting with bcc and ELKS
Date: Wed, 11 Mar 2009 22:09:40 -0000 [thread overview]
Message-ID: <4E76B356822240E085501BEFB93552A9@linux104> (raw)
In-Reply-To: 110653.35201.qm@web56204.mail.re3.yahoo.com
----- Original Message -----
From: "silvercreekvalley" <silvercreekvalley@yahoo.com>
To: <linux-8086@vger.kernel.org>
Sent: Wednesday, March 11, 2009 9:18 PM
Subject: Re: Starting with bcc and ELKS
>
>
>> > ELKS binaries built with bcc. But this stuff is all
>> pretty
>> > archaic so I don't know if it still works.
>
> I couldnt get the various flags to work, and objcopy
> didnt seem to do the trick. It just makes emulation
> a bit easier.
>
>
>>
>> I've never tried this, but don't you have to have
>> BINFMT_AOUT or BIMFMT_MISC enabled in your kernel?
>>
>>
>
> The documentation mentions Linux 2.0 / 2.1 so I'm
> thinking of installing an older Linux to see if I
> can patch the kernel as discussed in the docs.
>
> Tracking down an actual 8086 XT is quite tricky
> these days to run the code, so its useful to
> be able to emulate. I think there are some actual
> IBM XT emulators out there which I might try.
A few to check out (there are more):
http://dioscuri.sourceforge.net/ (comes with ELKS diskimage)
http://www.hampa.ch/pce/index.html
http://www.xs4all.nl/~rjoris/retro/
http://www.shinelife.co.uk/legacy-ibm-pc-emulator/
However, IA-32 emulators like Bochs/Qemu etc also work fine.
Hans
www.ht-lab.com
>
> Thanks
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2009-03-11 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 22:26 Starting with bcc and ELKS silvercreekvalley
2009-03-10 23:21 ` David Given
2009-03-11 1:42 ` Ben Weiss
2009-03-11 21:18 ` silvercreekvalley
2009-03-11 22:09 ` Hans [this message]
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=4E76B356822240E085501BEFB93552A9@linux104 \
--to=hans64@ht-lab.com \
--cc=linux-8086@vger.kernel.org \
--cc=silvercreekvalley@yahoo.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