From: "Klemens Lichter \(via GMX\)" <living-water@gmx.net>
To: linux-msdos@vger.kernel.org
Subject: strange beep at every keystroke
Date: Thu, 31 May 2007 07:33:10 +0200 [thread overview]
Message-ID: <002201c7a345$2d161000$ca1ca8c0@klemens> (raw)
Hi,
I´m new here, so first let me say hello.
I just installed the 1.4.0. version on a Suse 10.2 server and want top run
some dos programs there. My first trial was with 1.2.2 but there the dos
programs (written with clipper compiler) crashed. So I decided to install
1.4.0. Now the programs run, if I open the dosbox at the servers screen,
lredir to the apropriate direcory and from there start the program.
Now my problem. I don´t want to work at the servers screen but on remote
screens: So I use NX server and NX client software on a windows PC that is
connected either within our internal network to the server or via a
VPN-connection from outside. When I there start dosemu than I get a double
beep at every keystroke and also at every mouse click within the dos window.
This was not while running the 1.2.2 version of dosemu, so I think it is not
a problem of NX. Unfortunately I can not check if it is a general problem
from the 1.4.0 version, because the server it runs on does not have any
speaker or sound card.
Maybee someone can give me some advice where to look to solve this problem.
Please ask if you need more information.
Thanks in advance
Klemens
-
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
next reply other threads:[~2007-05-31 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 5:33 Klemens Lichter (via GMX) [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-23 8:45 strange beep at every keystroke Tarquin Adams
2007-10-23 13:13 ` Rafał Cygnarowski
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='002201c7a345$2d161000$ca1ca8c0@klemens' \
--to=living-water@gmx.net \
--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