From: b4@gewt.net (Cory Smelosky)
Subject: [TUHS] SCO OpenDesktop 386 2.0.0
Date: Mon, 27 Feb 2017 19:54:34 -0800 [thread overview]
Message-ID: <1488254074.690176.895047888.7A0983F2@webmail.messagingengine.com> (raw)
In-Reply-To: <D024D577-B0BE-4D53-AB92-64A0E26AFA12@gewt.net>
I have had great success with PCem (http://pcem-emulator.co.uk/)
Config:
gameblaster = 0
gus = 0
ssi2001 = 0
voodoo = 0
model = 39
cpu_manufacturer = 0
cpu = 27
cpu_use_dynarec = 1
cpu_waitstates = 0
gfxcard = 15
video_speed = 5
sndcard = 0
cpu_speed = 21
has_fpu = 1
disc_a = Z:\Users\<redacted>\id.ima
disc_b =
mem_size = 262144
cdrom_drive = 200
cdrom_enabled = 1
cdrom_channel = 1
cdrom_path = Z:\Users\<redacted>\SCO-2.1-CD.iso
vid_resize = 0
vid_api = 1
video_fullscreen_scale = 0
video_fullscreen_first = 1
hdc_sectors = 63
hdc_heads = 16
hdc_cylinders = 511
hdc_fn = sco-testing.img
hdd_sectors = 0
hdd_heads = 0
hdd_cylinders = 0
hdd_fn =
hde_sectors = 0
hde_heads = 0
hde_cylinders = 0
hde_fn =
hdf_sectors = 0
hdf_heads = 0
hdf_cylinders = 0
hdf_fn =
drive_a_type = 5
drive_b_type = 7
window_w = 0
window_h = 0
window_x = 0
window_y = 0
window_remember = 0
joystick_type = 0
mouse_type = 0
enable_sync = 1
[Joysticks]
joystick_0_nr = 0
joystick_1_nr = 0
cdrom_channel MUST be 1, and the floppy MUST end with an
extension of .ima
It runs on windows and linux, and happily in wine in macos. Once the
install completes I am confident it will work on bochs et al:
file sco-testing.img
sco-testing.img: DOS/MBR boot sector; partition 4 : ID=0x63, active, start-
CHS (0x0,1,1), end-CHS (0xfe,31,63), startsector 63, 514017 sectors
It's not a special image format, but a raw image.
--
Cory Smelosky
b4 at gewt.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170227/6a68bdab/attachment.html>
next prev parent reply other threads:[~2017-02-28 3:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 5:31 Rudi Blom
2017-02-26 15:07 ` Corey Lindsly
2017-02-26 18:50 ` Cory Smelosky
2017-02-27 7:53 ` Rico Pajarola
2017-02-27 9:51 ` Wesley Parish
2017-02-27 13:57 ` Arthur Krewat
2017-02-27 16:49 ` Corey Lindsly
2017-02-27 17:12 ` Cory Smelosky
2017-02-27 19:59 ` Arthur Krewat
2017-02-27 20:06 ` Cory Smelosky
2017-02-27 20:08 ` Cory Smelosky
2017-02-27 20:18 ` Arthur Krewat
2017-02-28 0:19 ` Arthur Krewat
2017-02-28 1:15 ` Michael Kerpan
2017-02-28 1:31 ` Cory Smelosky
2017-02-28 3:54 ` Cory Smelosky [this message]
2017-02-28 6:50 ` Cory Smelosky
2017-03-01 22:45 ` Josh Good
2017-03-01 22:52 ` Cory Smelosky
2017-03-01 23:06 ` Arthur Krewat
2017-03-01 23:07 ` Cory Smelosky
2017-03-01 23:13 ` Arthur Krewat
2017-03-01 23:24 ` Arthur Krewat
2017-03-02 19:56 ` Corey Lindsly
2017-03-02 23:24 ` Josh Good
2017-03-03 16:22 ` Arthur Krewat
2017-03-03 16:54 ` Henry Bent
2017-03-04 4:18 ` Cory Smelosky
2017-03-04 4:56 ` Cory Smelosky
2017-02-28 2:52 ` Cory Smelosky
2017-02-28 2:55 ` Cory Smelosky
2017-02-28 21:00 ` Josh Good
-- strict thread matches above, loose matches on Subject: below --
2017-02-27 0:44 Rudi Blom
2017-02-26 0:55 Cory Smelosky
2017-02-26 3:35 ` Jason Stevens
2017-02-26 3:46 ` Cory Smelosky
2017-02-26 16:13 ` Arthur Krewat
2017-02-26 18:50 ` Cory Smelosky
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=1488254074.690176.895047888.7A0983F2@webmail.messagingengine.com \
--to=b4@gewt.net \
/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).