public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaw Tong Tan <shawtan@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Status Update : Deployment of DOSEMU Application Server
Date: Tue, 28 Oct 2008 22:43:43 -0700 (PDT)	[thread overview]
Message-ID: <881628.35417.qm@web52508.mail.re2.yahoo.com> (raw)

A while back I sent a request to the list for advice on running such a setup.  I received several kind suggestions from the list members.  I am now in 1st week of deployment and decide to submit a status update.

My thanks to all the people who pass me info and solutions.

Basic:
1.  Multi-user DOS clipper-based software.
2.  User access from LAN and WAN.
3.  DOS-based dot matrix printing for LAN and WAN clients.

There are currently 2 major ways to do this.
A.  Microsoft Terminal Server/Citrix Products.
B.  Open Source Software.

Option A is known to work.  It does incur higher cost, hardware and software and license management overhead.  I was asked to explore Option B as priority choice.  In case it doesn't work then fall back to Option A.

Observation
1.  Server hardware Quad-Core
2.  Server software CentOS 5.x (32-bit)
3.  DOSEMU with FreeDOS (32-bit) standard RPM download from website
4.  To address the 100% CPU utilization issue, I have used a combination of specialized dos program, Linux NICE value tuning and CPU affinity control to achieve acceptable response to enduser
5.  Initially I use PUTTY and REMOTE ANSi Printing with lpansi for printing
6.  I ran into problem where small size print jobs are ok, but big size print job always hang.
7.  After fruitless workaround attempts and decided against running custom kernels, I made the decision not to use REMOTE ANSI Printing, thus creating a new problem on how to pass print job from server to remote WAN client over the Internet.
8.  Implement OPENVPN for remote WAN clients with DSL connection.
9.  With VPN tunnel open, setup std CUPS printer with SMB config for remote client printer.
10.  Tune the setup to minimize packet fragment, timeout and firewall rules issues.

             reply	other threads:[~2008-10-29  5:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29  5:43 Shaw Tong Tan [this message]
2008-10-29 14:33 ` Status Update : Deployment of DOSEMU Application Server Alain M.
2008-10-29 18:36   ` Andrew Joakimsen
2008-10-29 21:15     ` Alain M.
2008-10-29 21:47       ` Andrew Joakimsen
2008-10-30  1:57   ` Shaw Tong Tan
2008-10-31  0:10     ` Andrew Joakimsen
2008-10-31  2:59       ` Shaw Tong Tan
  -- strict thread matches above, loose matches on Subject: below --
2008-10-30  9:02 Shaw Tong Tan
2008-10-30 13:42 ` Ivan Baldo
2008-10-30 13:43 ` Alain M.
2008-10-30 13:45 ` Alain M.
2008-10-30 17:14 Manfred Scherer
2008-11-02 22:40 ` Claudia Neumann
2008-11-08 16:49 Manfred Scherer
2008-11-09  8:24 ` Claudia Neumann

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=881628.35417.qm@web52508.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