From: Paul Crawford <psc@sat.dundee.ac.uk>
To: Steve Cohen <stevecoh1@comcast.net>
Cc: Frank Cox <theatre@sasktel.net>, linux-msdos@vger.kernel.org
Subject: Re: Hoo boy! This is going to be interesting.
Date: Mon, 18 Oct 2010 19:21:16 +0100 [thread overview]
Message-ID: <4CBC901C.1010003@sat.dundee.ac.uk> (raw)
In-Reply-To: <4CBC876A.90204@comcast.net>
Dear Steve,
> It's 1.4, the version you get with apt-get from Ubuntu 10.04 and the
> latest stable version, I believe.
Are you using 32-bit or 64-bit? I found 32-bit plays better generally.
> Although we have source code and suitable compilers, tweaking it much is
> probably not an option for business reasons. We are on a 2-week
> fish-or-cut-bait time frame for evaluating DOSEMU for this purpose. If
> we can't get this to work, we will look at rewriting instead, which is
> our preferred long-term solution. DOSEMU, if it proves out in the two
> weeks allotted, would be the short term solution. The reason for this
> whole effort is hardware exhaustion - we haven't figured out a workable
> way to replace the old hardware, and are running out of suitable
> replacements, which are no longer available.
If all you talk to are serial ports, then you can use a VM under Linux
and have that run your software & MS-DOS in it, and pass through the
serial stuff to the machine's hardware.
Only 'gotcha' I have found is VM's generally can't successfully set
non-standard baud rates, where as dosemu can (particularly if its going
via direct hardware I/O to the serial ports rather than emulation).
Re-writing, while a good long terms solution, should *not* be under
estimated in terms of the effort needed!
Having the source code is a *major* bonus, and you might be able to
re-compile for Linux by only replacing some of the I/O and user
interface side of it. We still have a 19-year old DOS control program
that we use 24/7 on several systems because:
1) It works reliably (a lot of debugging over the years).
2) There is little "value" in a new program. Given we have it happy
under dosemu, there is no functional advantage to changing.
3) It is around 6 months effort to re-write, then at least another 6
months to debug to an acceptably good degree of reliability. Given (2)
there is a lot better use of our time on other projects (i.e. little
"business case" for it).
Regards,
Paul
next prev parent reply other threads:[~2010-10-18 18:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 19:25 Hoo boy! This is going to be interesting Steve Cohen
2010-10-08 20:22 ` Frank Cox
2010-10-09 9:47 ` Paul Crawford
2010-10-18 17:44 ` Steve Cohen
2010-10-18 18:21 ` Paul Crawford [this message]
2010-10-18 21:18 ` solarflow99
2010-10-18 22:00 ` Steve Cohen
-- strict thread matches above, loose matches on Subject: below --
2010-10-08 19:19 Steve Cohen
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=4CBC901C.1010003@sat.dundee.ac.uk \
--to=psc@sat.dundee.ac.uk \
--cc=linux-msdos@vger.kernel.org \
--cc=stevecoh1@comcast.net \
--cc=theatre@sasktel.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