From: Samuel Falvo <falvosa@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: DOSEMU mouse-related problem that is not in the FAQ
Date: Sun, 10 Aug 2003 23:53:57 -0700 (PDT) [thread overview]
Message-ID: <20030811065357.24182.qmail@web10708.mail.yahoo.com> (raw)
Greetings.
I am trying to install dosemu as a solution to one of my customer's needs. He
needs to run PC/GEOS (actually NewDeal Office) alongside his normal Linux
desktop to gain access to some very old business files.
I've gotten dosemu (I forget what version now, but it is 1.0.1 at the very
least) installed, and it seems to run GEOS perfectly, except for
the mouse. Here is how to reproduce the problem on my machine:
0. I launch the DOS environment using xdosemu. I'm using FreeDOS beta 9
installed on /dev/hda1. $_mouse_dev = "/dev/mouse", and $_mouse_type =
"imps2". I've tried just regular "ps2" with similar results. No com-port
interfaces are defined. The X version is XFree86 4.3.0 running the Trident
video driver.
1. From a freshly booted instance of FreeDOS beta 9, and without any sort of
MOUSE.COM/.SYS loaded, I can type EDIT FOO.TXT, and the mouse responds as
expected, though it is missing the usual mouse cursor. Fortunately, X's
mouse pointer is present.
2. After exiting from the editor, I then type NDO to launch NewDeal Office.
This places the screen into graphics mode. If configured for a real mouse,
NDO complains about not being able to load the mouse driver unless you load
it's
keyboard-based mouse emulator. At this point, the mouse functionality utterly
disappears, including the normal X11 mouse pointer when the pointer is over
the xdosemu window.
2a. Trying to re-establish communications with the mouse via the Preferences
tool fails every time, again excepting the simulated mouse driver.
3. I then EXIT NDO completely, bringing me back to the DOS prompt. The
mouse pointer does NOT return.
4. I type EDIT FOO.TXT again, and the mouse is dead. EDIT does not respond
to any mouse input of any kind.
Why does the mouse disappear when the DOS emulator is shoved into a graphics
mode? How do I prevent this from occuring? How can I "fake" a serial or PS/2
mouse based on the X11 event stream? Do I need to hack the sources to
prevent this behavior? If so, where do I look? If not, who should I contact
regarding this behavior? Can you offer advice on how to start debugging
this?
Thank you for your time in this matter. I look forward to hearing from you
soon.
--
Samuel A. Falvo II
Falvo Technical Solutions
http://www.falvotech.com
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
reply other threads:[~2003-08-11 6:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030811065357.24182.qmail@web10708.mail.yahoo.com \
--to=falvosa@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