From: "Neil Holmes" <neil.holmes@zoom.co.uk>
To: Michael McConnell <soruk@eridani.co.uk>
Cc: Linux 8086 <linux-8086@vger.kernel.org>
Subject: Elks Distribution on Bochs 1.4
Date: Tue, 28 May 2002 13:01:05 +0100 [thread overview]
Message-ID: <DDENIOHFNLNMCGGDFDPCAEPFCDAA.neil.holmes@zoom.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
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
[-- Attachment #2: elksdistro.txt --]
[-- Type: text/plain, Size: 765 bytes --]
# configuration file generated by Bochs
floppya: 1_44="/dev/fd0", status=inserted
#floppyb: 1_44="b.img", status=inserted
diskc: file="elksdisk", cyl=615, heads=6, spt=17
# no diskd
# no cdromd
romimage: file=bios/BIOS-bochs-latest, address=0xf0000
vgaromimage: bios/VGABIOS-elpin-2.40
megs:4
# no parport #1
# no sb16
boot: c
vga_update_interval: 300000
keyboard_serial_delay: 250
keyboard_paste_delay: 100000
floppy_command_delay: 500
ips: 1000000
mouse: enabled=0
private_colormap: enabled=0
i440fxsupport: enabled=0
time0: 0
# no ne2k
newharddrivesupport: enabled=1
# no loader
log: elkserror.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
keyboard_mapping: enabled=0, map=
keyboard_type: mf
next reply other threads:[~2002-05-28 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 12:01 Neil Holmes [this message]
[not found] <Pine.LNX.4.44.0205281812060.8460-100000@Zeskia.int.eridani.co.uk>
2002-05-28 17:39 ` Elks Distribution on Bochs 1.4 Neil Holmes
2002-05-28 17:44 ` Michael McConnell
2002-05-28 17:46 ` 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=DDENIOHFNLNMCGGDFDPCAEPFCDAA.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