Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have Dosbox 0.74 installed in a fully updated Manjaro Linux desktop. Even though it worked fine before, there is a relatively recent problem which is that Dosbox can capture my mouse clicks, but *not* mouse movements.
I can tell because I can click my mouse to skip intro screens in games, but my mouse cursor's movements is not captured by Dosbox. This appears to be a broader problem because I also experience the same thing when running DOS games from GoG which runs from GoG's own packaged Dosbox. I made sure that mouse "autolock" is set to true in my Dosbox configuration, but that didn't help.
Congrats on having Dosbox do anything for you. Is yours a USB mouse, or serial port?
Dos, i.e. IBM PC-DOS or m$ M$-DOS (same thing, basically) really was awful.The few peripheral parts it knew about (serial & parallel ports, the 16 bit ISA bus, and the firmly allocated I/O and interrupts with zero feedback, memory over 640k needing a driver) are all 15-20 years obsolete. What it DIDN'T know about (PCIE, PCI, USB 1/2/3, sd cards, advanced file systems, PNP devices, Gigs of ram, DECENT Graphics cards, fast multicore cpus & dsps, etc.) are what we use today. The later Dos versions had emm386.exe whose function in life was to make extended memory (over 1 MB) pretend to be expanded memory (=a few k of ram on an ISA card with an address between 640k and 1023k because Dos did funny thgings with the A20 line seeing as nobody ever was going to want more than 1MB of ram :-/).
I'd try to give it the mouse on a pretend serial port or check what wheeze it's using to get around that usb -->serial port issue.
Dosbox has always worked just fine for me, have you had many problems with it before?
Quote:
Originally Posted by business_kid
Is yours a USB mouse, or serial port?
Quote:
Originally Posted by business_kid
I'd try to give it the mouse on a pretend serial port or check what wheeze it's using to get around that usb -->serial port issue.
What is a wheeze? My physical mouse is connected via USB, but that has never been a problem. AFAIK Dosbox does not present the physical mouse to programs it runs as USB so is there something else to check? Thanks.
Uh, business_kid, do you even know what DosBox is? It's an emulator, like ZSNES, and it runs on modern OSses and modern hardware. It doesn't make you deal with any of the issues that you mentioned.
I followed that link and it appears to describe my problem. I tried setting "autolock" to FALSE as suggested and it worked for me when trying some Dosbox programs but not others. When it doesn't work well, I mean that the mouse cursor would only be captured for a small part of the program's screen. If I move my mouse cursor outside of that area, it jumps out of the Dosbox window and back into my host system. Very strange.
Anyways, I guess it is indeed a problem with xorg as suggested in that thread. But the update to xorg 1.20 happened months ago and I no longer have the package cache to downgrade it...
Quote:
Originally Posted by michaelk
Maybe contact the dosbox developers and see if they might have any ideas.
Thank you for suggesting this! After some searching I came across a very similar thread on the Dosbox forums:
Uh, business_kid, do you even know what DosBox is? It's an emulator, like ZSNES, and it runs on modern OSses and modern hardware. It doesn't make you deal with any of the issues that you mentioned.
Yeah, installed it a while back and it was just a PITA. I could have used it - then.
I've since reluctantly dragged myself into this millenium, ditching/selling old machinery along the way.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.