Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR BIOS:INT15:Unknown call ax=BF02 - When the mouse pointer is activated as Autocad pointer #5226

Open
2 tasks done
aca18d opened this issue Sep 26, 2024 · 13 comments
Open
2 tasks done
Labels

Comments

@aca18d
Copy link

aca18d commented Sep 26, 2024

Describe the bug

Once Dosbox-x has loaded Autocad R12 for DOS, the user has to click on the screen to activate the Autocad mouse pointer.
After clicking, it moves ###jerkily### and the Linux shell shows the following:

LOG: 609525 ERROR BIOS:INT15:Unknown call ax=BF02
LOG: 1002893 ERROR MOUSE:Unhandled videomode 6D on

Steps to reproduce the behaviour

  1. Start Dosbox-x and mount the C disk.
  2. Go to C: and set the CPU emulation as Pentium 133
  3. Start Autocad (everything ok so far)
  4. Click on the screen to catch the Autocad Pointer
  5. It moves jerkily

Expected behavior

Mouse pointer moving smoothly.

What operating system(s) this bug have occurred on?

Tinycore Linux 15 - 32 bit on Pentium II

What version(s) of DOSBox-X have this bug?

v2024.07.01

Used configuration

It's impossible to set any config file since clicking on the Configuration Tool or Mouse Sensitivity menu makes Dosbox-x to CRASH straightly.
The Linux shell shows the following:

Illegal instruction

Output log

No response

Additional information

No response

Have you checked that no similar bug report(s) exist?

  • I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

  • I agree to follow the code of conduct and the contributing guidelines.
@aca18d aca18d added the bug label Sep 26, 2024
@maron2000
Copy link
Contributor

The said error doesn't matter.
Working fine on Windows VS SDL1 & SDL2 with default config, the same errors are found in the log.
image

@aca18d
Copy link
Author

aca18d commented Sep 27, 2024

The same OS and Dosbox-x version work fine on VirtualBox hosted by Slackware 15 as well.
But I'd need to know why they don't on a real Pentium II hardware.
And why the Config Tool can't show and calling it makes Dosbox-x crashing.
Many thanks

@aca18d
Copy link
Author

aca18d commented Oct 3, 2024

May Xvesa be the problem and need additional settings?

@aca18d
Copy link
Author

aca18d commented Oct 15, 2024

Setting "serial1=serialmouse" along with a serial mouse plugged to COM1 has no effect.
If at least the mouse worked properly it would be very appreciated.
I think nobody is better than the Dosbox-x staff to help me.

@maron2000
Copy link
Contributor

Can you try any other software or a game that uses the mouse?
I don't think this issue is regarding the setting of DOSBox-X, since it is working on other platforms without complicated tweaks.

Or maybe try external mouse drivers such as CuteMouse or vbmouse instead of the DOSBox-X built-in driver.

@aca18d
Copy link
Author

aca18d commented Oct 16, 2024

I've tried:

  • Lotus 1-2-3 4.0
  • Norton Commander 5.5
  • Lotus Symphony Release 3.00

As for Autocad, everything (except Lotus) works fine on my modern PC (Intel i5 10600), with or without VirtualBox.
Regarding Lotus: the main program freezes, just its Help (Qstart) works.

And as for Autocad, the mouse pointer moves in great jerks on my old laptop (Pentium II 300 MHz).

Installing Vbmouse before launching Autocad has no effect.

@maron2000
Copy link
Contributor

Lotus 1-2-3 4.0 is already reported in #2711 that you have to set CPU to core=normal.
I asked you to test on your old laptop, can I understand that mouse is working for everything except AutoCAD and Lotus on your old laptop?

@maron2000
Copy link
Contributor

So I created a VMware virtual machine and installed Tiny Core Linux ver15.
Indeed mouse is far from controllable with the built-in mouse driver, but vbmouse driver worked quite well.
(Don't capture your mouse but just hover your mouse on the DOSBox-X window.)

On AutoCAD 12, the mouse motion factor needs to be tuned. The following values works on my VM, but you may need to fine tune for your PC.

I see that the DOSBox-X package of Tiny Core Linux use SDL 2.24.0 which is quite old, which may be a cause of this flaw.

image

Acad.000.mp4

@aca18d
Copy link
Author

aca18d commented Oct 16, 2024

Lotus 1-2-3 4.0 is already reported in #2711 that you have to set CPU to core=normal. I asked you to test on your old laptop, can I understand that mouse is working for everything except AutoCAD and Lotus on your old laptop?

To clarify better, that's might be useful to other readers:

  1. All the above mentioned programs on Dosbox-x 32 bit,
    hosted by Slackware 15 64 bit (Intel i5 10600): everything works fine.

  2. All the above mentioned programs on Dosbox-x 32 bit,
    hosted by TinyCore 32 bit,
    in its turn hosted by VirtualBox,
    installed on Slackware 15 64 bit (Intel i5 10600): everything works fine.

  3. All the above mentioned programs on Dosbox-x 32 bit,
    hosted by TinyCore 32 bit,
    installed on real Pentium II hardware: all of them moves THEIR mouse pointer in great jerks. The Dosbox-x pointer moves always fine.

On AutoCAD 12, the mouse motion factor needs to be tuned. The following values works on my VM, but you may need to fine tune for your PC.

I've tried all the Cutemouse versions (BIOS [19], hardware [20] and combined [21]) and Vbdos. While the "hardware" Cutemouse doesn't work, the remaining give almost equivalent results.
Setting the motion factor to 1, 3, 2 has reduced a bit but not eliminated the jerkiness.

I see that the DOSBox-X package of Tiny Core Linux use SDL 2.24.0 which is quite old, which may be a cause of this flaw.

If it's easy to compile and I don't damage anything I'd build and install a recent version of it.

===========================

Meanwhile I want to say
thank you for the time
you have devoted to me :)

===========================

@aca18d
Copy link
Author

aca18d commented Oct 19, 2024

So, the latest SDL 2.30.8 has compiled without any error on the Pentium II.
After installing it and launching Dosbox-x I get the following message:

LOG: Early LOG Init complete LOG: DOSBox-X's working directory: /mnt/sda2/dosprogs LOG: Logging init: beginning logging proper. This is the end of the early init logging LOG: Logging: No logfile was given. All further logging will be discarded. LOG: DOSBox-X version 2024.10.01 Commit 70ade1c (Linux SDL2 32-bit) LOG: Prevent capture: 0 Illegal instruction

Anything I can do?
Many thanks

@maron2000
Copy link
Contributor

That should be a problem of your compiler.
You may want to ask the package builders of Tiny core linux for assistance.

@maron2000
Copy link
Contributor

tiny core linux has some explanation in their package source code.
Seems many things should be modified, you can ask the tiny core linux guys for more assistance.
http://tinycorelinux.net/15.x/x86/tcz/src/dosbox-x/

@aca18d
Copy link
Author

aca18d commented Oct 20, 2024

tiny core linux has some explanation in their package source code. Seems many things should be modified, you can ask the tiny core linux guys for more assistance. http://tinycorelinux.net/15.x/x86/tcz/src/dosbox-x/

Yes, that's for Dosbox-x.
They use the lncursesw instead of lncurses and have updated their version of Dosbox-x, that was more than one year old, upon my request as an attempt to solve my mouse problem.
I had followed that instruction and everything worked great on my i5 10600 but not on my Pentium II, as I had already described above.

Then, since you stated that the problem may be an old version of SDL2, I've compiled the latest version.
The compilation has succeeded without any problem, the compiler is gcc 13.2.
The instruction to do that is simple, and so is the installation.
But it gives that error (I just did it on Pentium II).

Using the old SDL 2.24 instead, everything works but the mouse pointer on Pentium II.
No problem on i5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants