public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eddy Setyawan" <eddymilis@teguhabadi.com>
To: Frantisek Hanzlik <franta@hanzlici.cz>
Cc: linux-msdos@vger.kernel.org
Subject: Re: Dosemu Slower than CMD
Date: Fri, 30 May 2008 15:40:31 +0700	[thread overview]
Message-ID: <34cfb2e90805300140w5951e192k4880d0ea06e06acf@mail.gmail.com> (raw)
In-Reply-To: <483FBA89.5070207@hanzlici.cz>

hello Frantistek,
Which segment you try ? I mean slow is at menu Master -> Persediaan ->
Ubah Harga Jual, while entering this section application cpu usage
jump to 100% and waiting to load all data is takes time than CMD
does... even at windows i try it with shared drive

some alert dialog also eat CPU but after search around i found that
clipper function for alert dialog has some bug

On Fri, May 30, 2008 at 3:27 PM, Frantisek Hanzlik <franta@hanzlici.cz> wrote:
> As I wrote in my previous mail, in tested program segment is about
> 200000 times called INT0x16 Fn 0x11 : Check_Enhanced_Keystroke.
> In corresponding dosemu routines in "base/bios/int16.c" are called
> some delay functions - maybe these may add some delay to program
> execution.
> On my system CLK_TCK=100 (ticks/sec), thus JIFFIE_TIME=10000 and
> INT2F_IDLE_USECS=80000 (=> 80msec delay).
> But as I wrote, on my faster PC exec time was 3 sec, thus delay
> added in INT16 can't be longer.
>
> Bart Oldeman probably can say more about this.
>



-- 
regards,
Eddy Setyawan
http://eddysetyawan.blogspot.com
+6208123049592

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GB/IT d--()>+ s++:+ a- C+++@ !ULC++>++++ P L+++(++++)@>++++ !E-- W++@?
N !o K--? w-- !O !M !V PS PE+@ !Y PGP@>++ t+ 5 X !R tv-(--) b DI D+
G++ e++ h--->---- r+++ z+++
------END GEEK CODE BLOCK------

  reply	other threads:[~2008-05-30  8:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-15 16:47 Dosemu Slower than CMD Eddy Setyawan
2008-03-15 19:54 ` Reinhard Karcher
2008-03-16  2:22   ` Eddy Setyawan
2008-03-16  7:23     ` Rafał Cygnarowski
2008-03-16 10:41 ` Frantisek Hanzlik
2008-03-16 13:35   ` Eddy Setyawan
2008-03-16 13:43     ` Eddy Setyawan
2008-04-01 18:33     ` Mike McCarty
2008-05-29 17:19   ` Eddy Setyawan
2008-05-30  3:53     ` Frantisek Hanzlik
2008-05-30  8:27     ` Frantisek Hanzlik
2008-05-30  8:40       ` Eddy Setyawan [this message]
2008-05-30  8:56         ` Frantisek Hanzlik
     [not found]           ` <34cfb2e90805300203t1f904938q60405bbbe3e035a2@mail.gmail.com>
2008-05-31  8:15             ` Frantisek Hanzlik

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=34cfb2e90805300140w5951e192k4880d0ea06e06acf@mail.gmail.com \
    --to=eddymilis@teguhabadi.com \
    --cc=franta@hanzlici.cz \
    --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