From: Shaw Tong Tan <shawtan@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Experienced Advice needed urgently: DOSEMU
Date: Thu, 28 Aug 2008 09:47:56 -0700 (PDT) [thread overview]
Message-ID: <334764.29480.qm@web52510.mail.re2.yahoo.com> (raw)
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
next reply other threads:[~2008-08-28 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 16:47 Shaw Tong Tan [this message]
2008-09-10 15:55 ` Experienced Advice needed urgently: DOSEMU Ivan Baldo
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=334764.29480.qm@web52510.mail.re2.yahoo.com \
--to=shawtan@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