From: Ivan Baldo <ibaldo@adinet.com.uy>
To: shawtan@yahoo.com
Cc: linux-msdos@vger.kernel.org
Subject: Re: Experienced Advice needed urgently: DOSEMU
Date: Wed, 10 Sep 2008 12:55:20 -0300 [thread overview]
Message-ID: <48C7EDE8.5080405@adinet.com.uy> (raw)
In-Reply-To: <334764.29480.qm@web52510.mail.re2.yahoo.com>
Hello.
Maybe try changing the value of the HogThreshold configuration option,
or use the speed command under the DOS session.
First try the value 1, then the value 2, then the value 7, then the value 0.
If it doesn't work with that, then try a 32 bits Kernel instead of a 64
bits one, since the 64 bits one requires the use of CPU emulation and
may be slower.
Otherwise you may try to use QEmu, KVM, VirtualBox OSE, etc. (machine
virtualization solutions), if you go the virtualization route, you may
need a "DOS Idle" program to release the CPU when not needed while
waiting for a keystroke.
Hope this helps, best wishes!
P.s.: didn't answer earlier because I wanted to see if someone else with
better experience would answer first, and then forgot about this email
entirely, sorry.
El 28/08/08 13:47, Shaw Tong Tan escribió:
> Background info
>
> 0. CentOS 5.2 i386
> 1. Clipper-based program. No source.
> 2. DOS program 100% CPU hog. Tested various software tools, only official citrix dpakbd seems to work slightly, but user request improvement.
>
> Question :
> Is DOSEMU capable of practical usage in such manner as below.
>
> (I have a working setup with 2 sessions, but unsure when it scale up)
>
> 1. User login through ssh client on Windows XP
> 2. Total 16 active DOSEMU/Clipper sessions on 1 server.
>
> my previous results, I use processor affinity control to force DOSEMU to run on 1-core. I found 4-instances dosemu/clipper on 1-core, program erratic behavior and frequent hangup. less than 4 instances per core seems OK.
>
> Thank you for your kind suggestion
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
Ivan Baldo - ibaldo@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: ibaldo@codigolibre.net - http://go.to/ibaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-09-10 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 16:47 Experienced Advice needed urgently: DOSEMU Shaw Tong Tan
2008-09-10 15:55 ` Ivan Baldo [this message]
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=48C7EDE8.5080405@adinet.com.uy \
--to=ibaldo@adinet.com.uy \
--cc=linux-msdos@vger.kernel.org \
--cc=shawtan@yahoo.com \
/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