* MS DOS 6.22
@ 2004-02-19 10:23 House, John D. CIV
2004-02-19 11:24 ` Ged Haywood
2004-02-19 13:25 ` Lars Bjørndal
0 siblings, 2 replies; 3+ messages in thread
From: House, John D. CIV @ 2004-02-19 10:23 UTC (permalink / raw)
To: linux-msdos
All,
I have a problem with the current operating system (DOS 6.22) I'm using
for military applications. It seems that it can't be loaded on systems
with higher speeds. In other words, when we try to upgrade to Pent III
or equivalent system the DOS program spits out fragmented characters. An
emulator would solve many problem as we're trying to prepare for future
modernization. Any assistance you could provide would be appreciated.
vr,
John D. House
Technical Coordinator, CUTS
USEUCOM J63- SATCOM MGT
DSN: 314-430-4011 FAX# 5614
Comm: +49-0711680-4011
NIPR: housejd@eucom.mil
SIPR: housejd@eucom.smil.mil
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: MS DOS 6.22
2004-02-19 10:23 MS DOS 6.22 House, John D. CIV
@ 2004-02-19 11:24 ` Ged Haywood
2004-02-19 13:25 ` Lars Bjørndal
1 sibling, 0 replies; 3+ messages in thread
From: Ged Haywood @ 2004-02-19 11:24 UTC (permalink / raw)
To: House, John D. CIV; +Cc: linux-msdos
Hello there,
On Thu, 19 Feb 2004, House, John D. CIV wrote:
> I have a problem with the current operating system (DOS 6.22) I'm using
> for military applications. It seems that it can't be loaded on systems
> with higher speeds. In other words, when we try to upgrade to Pent III
> or equivalent system the DOS program spits out fragmented characters. An
> emulator would solve many problem as we're trying to prepare for future
> modernization. Any assistance you could provide would be appreciated.
If I understand you correctly, the DOS program which is causing the
problem is a program which has been written to run under DOS, and it
is not MS-DOS itself which is spitting out fragmented characters. I
am sure that DOS itself will work fine on PentiumIII and even better.
Many programs have problems related to timing, some simply because of
poor design and some because of known constraints which were accepted
at the time the specifications were drawn up. I wonder which we are
looking at here. Since you mention military applications you might be
forgiven for letting us know very little about the programs, but I'm
sure it would help if you could tell us exactly what is this problem
program, where this fragmented output appears, what it looks like and
under what circumstances it is fragmented. Precise details of the
hardware configuration would also help.
MS-DOS 6.22 itself works fine under the DOSEMU emulator, but there are
all sorts of caveats about other software which you might want to run
under a DOSEMU-controlled MS-DOS. Things like memory management and
direct access to the I/O ports can be particularly knotty problems,
and you can't run the processor in real mode at all - not that you'd
probably want to.
So what I'm saying is that although an emulator might solve many of
your problems, it might introduce some too. If you can be a bit more
forthcoming about your application's technical details, people here
will be able to help you better.
73,
Ged.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: MS DOS 6.22
2004-02-19 10:23 MS DOS 6.22 House, John D. CIV
2004-02-19 11:24 ` Ged Haywood
@ 2004-02-19 13:25 ` Lars Bjørndal
1 sibling, 0 replies; 3+ messages in thread
From: Lars Bjørndal @ 2004-02-19 13:25 UTC (permalink / raw)
To: linux-msdos
Have you tried the program "slowdown"? (It's free.)
Lars
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-02-19 13:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-19 10:23 MS DOS 6.22 House, John D. CIV
2004-02-19 11:24 ` Ged Haywood
2004-02-19 13:25 ` Lars Bjørndal
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox