From: "Neil Holmes" <neil.holmes@zoom.co.uk>
To: Michael McConnell <soruk@eridani.co.uk>
Cc: Linux 8086 <linux-8086@vger.kernel.org>
Subject: RE: Elks Distribution on Bochs 1.4
Date: Tue, 28 May 2002 18:39:08 +0100 [thread overview]
Message-ID: <DDENIOHFNLNMCGGDFDPCIEACCEAA.neil.holmes@zoom.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0205281812060.8460-100000@Zeskia.int.eridani.co.uk>
Thats great news Michael. I am pleased that to hear that you are up and
running. Let me know if you find any problems with your installation.
Keep your eyes open for upgrades. My current development version (which will
become 0.0.4 in due course) is now installing from a single floppy disk. Its
also not asking for a login at the start. It goes straight into the
installation.
Thanks
Neil
-----Original Message-----
From: Michael McConnell [mailto:soruk@eridani.co.uk]
Sent: 28 May 2002 18:13
To: Neil Holmes
Subject: RE: Elks Distribution on Bochs 1.4
On Tue, 28 May 2002, Neil Holmes wrote:
> Please keep me posted.
I had an invalid floppy delay count - yours was 500, mine was 100 times
that!
Setting it to 500 made it work.
Whee. I now have an ELKS bochs ;-)
> Thanks
>
> Neil
>
> -----Original Message-----
> From: Michael McConnell [mailto:soruk@eridani.co.uk]
> Sent: 28 May 2002 14:14
> To: Neil Holmes
> Subject: Re: Elks Distribution on Bochs 1.4
>
>
> [Not sent to the list]
>
> Thanks for that, I'll give it a try.
>
> The HD image my bochs setup is currently using is a 504Mb file
(1024/16/63)
> which works fine with a normal Linux installation (albeit very slowly).
>
> I'll try with a smaller one such as described in the config file you
emailed
> me, and see if that works.
>
> (I note that ELKS picked it up as 1022/16/63 not 1024.. wonder if that has
> anything to do with it?)
>
>
> On Tue, 28 May 2002, Neil Holmes wrote:
>
> > Hi Michael,
> >
> > I have installed the Elks Distribution on Bochs ok now. I have attached
my
> > confirguration file for your consideration. I wasn't sure how to create
a
> > disk file in Bochs so I borrowed the hdimage.test file from dosemu.
> >
> > As per my initial instructions I have found that its best to use dos
fdisk
> > to create a partition to start with. I tried without and the install
> failed.
> >
> > A reminder that 0.0.3 is available for download and thats the version
that
> I
> > tested with.
> >
> > Thanks
> >
> > Neil
> >
>
> -- Michael "Soruk" McConnell [Eridani Linux 6.3 Now!]
> Eridani Linux -- The Most Up-to-Date Red Hat-based Linux CDROMs
Available
> Email: linux@eridani.co.uk http://www.eridani.co.uk Fax:
+44-8701-600807
> "No. 'Eureka' is Greek for 'This bath is too hot.'" - Dr Who.
>
>
>
>
-- Michael "Soruk" McConnell [Eridani Linux 6.3 Now!]
Eridani Linux -- The Most Up-to-Date Red Hat-based Linux CDROMs Available
Email: linux@eridani.co.uk http://www.eridani.co.uk Fax: +44-8701-600807
"No. 'Eureka' is Greek for 'This bath is too hot.'" - Dr Who.
next parent reply other threads:[~2002-05-28 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0205281812060.8460-100000@Zeskia.int.eridani.co.uk>
2002-05-28 17:39 ` Neil Holmes [this message]
2002-05-28 17:44 ` Elks Distribution on Bochs 1.4 Michael McConnell
2002-05-28 17:46 ` Neil Holmes
2002-05-28 12:01 Neil Holmes
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=DDENIOHFNLNMCGGDFDPCIEACCEAA.neil.holmes@zoom.co.uk \
--to=neil.holmes@zoom.co.uk \
--cc=linux-8086@vger.kernel.org \
--cc=soruk@eridani.co.uk \
/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