Linux MS DOS discussions
 help / color / mirror / Atom feed
From: John Coppens <john@jcoppens.com>
To: Clarence Dang <clarencedang@yahoo.com>
Cc: linux-msdos@vger.kernel.org
Subject: Re: Timing problems
Date: Mon, 25 Jun 2007 22:33:20 -0300	[thread overview]
Message-ID: <20070625223320.a4417f9d.john@jcoppens.com> (raw)
In-Reply-To: <200706221740.44421.clarencedang@yahoo.com>

On Fri, 22 Jun 2007 17:40:42 +1000
Clarence Dang <clarencedang@yahoo.com> wrote:

> On Wednesday 20 June 2007 15:08, John Coppens wrote:

> > I suspect this program uses the DOS 18.xxx Hz timer for its loops. Is
> > the emulation of the timer under DOSEMU the same frequency? Does it
> > depend on setting up the 250/1000 tick/s of the kernel?
> 
> DOSEMU can handle about 100 Hz for the PIT.
> 
> I have a patch I can dig up that can go up to 250 (or even 1000
> depending on the kernel version).  It's just a quick hack and not the
> proper solution though.

Hi Clarence,

Thanks for the reply, and my apologies for the delay in confirming...

In reality, the problem is the other way around - I have the impression
that DOSEMU is using anything but 18.29 Hz. At least the program is not
responding the same way under DOSEMU as in real DOS, which causes the
login sequence to fail.

It's rather strange really - using the normal serial port, I get one kind
of behaviour, and using an USB to serial converter, DOSEMU responds
completely differently (none of them correct). I'm somewhat at a loss
where to look for solutions here...

John

  reply	other threads:[~2007-06-26  1:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20  5:08 Timing problems John Coppens
2007-06-22  7:40 ` Clarence Dang
2007-06-26  1:33   ` John Coppens [this message]
2007-07-09  8:30     ` Clarence Dang

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=20070625223320.a4417f9d.john@jcoppens.com \
    --to=john@jcoppens.com \
    --cc=clarencedang@yahoo.com \
    --cc=linux-msdos@vger.kernel.org \
    /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