VOGONS


First post, by funkysascha

User metadata
Rank Newbie
Rank
Newbie

Hi, I have an dos application on a start disk. if i use this disk as boot disk, i won't have a mouse-arrow in the application, but the mouse is obviously working. but it is useless without seeing the mouse arrow.... so i copied everthing to a local drive and tried it with dosbox. the result: dosbox delivers a "fatal error -> invalid mouse-driver". i'm using win xp. has anyone an idea?

Reply 1 of 9, by ErikGG

User metadata
Rank Member
Rank
Member

Hi,

There is no direct solution to such a problem, the best thing you can try is a CVS DOSBox version.

You should mention the applications name. There might be someone out there with a sollution to the problem for that program.

If it is a bootdisk then I would recommend using WinImage to make an IMG file from your bootdisk and boot the image. See Readme for more info on the boot command, but this might not solve the mouse problem.

Hope this helps,

Erik.

Reply 2 of 9, by funkysascha

User metadata
Rank Newbie
Rank
Newbie

the appilcation name is "BRUKAN". it was writen custom-made in 1994. and i do not have the source code...

the idea of using the boot command doesn't work. now i got the message "fatal error: mouse-driver not loaded". using the cvs version from http://www.aep-emu.de/cvscompile/dosbox.htm makes no difference.

i think the mouse language causes my trouble. but i have no idea to fix this problem...

i'd be grateful for more ideas?

Reply 3 of 9, by ErikGG

User metadata
Rank Member
Rank
Member

It seems to be a mouse driver problem, a DOS driver that needs to be loaded. You could try out
http://ykhwong.x-y.net/
Under "Data", page three you can find the '[Util] Device Loader'. This programbundel can load simple drivers / Sys-files. It doesn't allow all drivers to be loaded there the DOSBox doesn't allow everything DOS once did.

I would also suggest to use ykhwong's CVS build. This build has the ability to turn the mouse driver completely off and has some more features then some CVS builds around.

As for the "mouse language" you mentioned, this can't be the problem because DOSBox converts the old DOS functions to the new Windows functions and vise versa. You'll get the same problem even by popping in a USB mouse or an old serial mouse, as long as Windows itself can use it. DOSBox simulates an old mouse driver, that is best compatible with all games, and then translates it to your new mouse.

I'm out of idea's, as I'm not that well known with the old DOS experience. Maybe sombody else might popup with the sollution.

Erik.

Reply 4 of 9, by funkysascha

User metadata
Rank Newbie
Rank
Newbie

hi erik,

i appreciate your help.

ykhwong's cvs is very nice. but it doesn't work. it seems there is no way...

btw: the programm start in win xp, but without the mouse. in dosbox it delivers always the fatal error message...

sascha

Reply 5 of 9, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

> in dosbox it delivers always the fatal error message...

The program (screenshot!) or dosbox itself?

Reply 6 of 9, by funkysascha

User metadata
Rank Newbie
Rank
Newbie

here are 2 screenshots of my strategy to run the program...

sascha

Reply 7 of 9, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

I think ykhwong's build has some way to partially disable the mouse.
If it's disabled you could try to load some other mouse driver
(old msmouse or old cutemouse might work).

Hard to tell what exactly causes the message.

Reply 8 of 9, by funkysascha

User metadata
Rank Newbie
Rank
Newbie

unloading the mouse driver works with the command "mouse /U".
then the loading of cutemouse seems to work too, 'cause afterwards the program runs, BUT without a mouse (msmouse doesn't work)

so we are one step further, but the program is still not useable

Reply 9 of 9, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Don't know what that /u does, might or might not be enough to fully
disable the mouse. In either case try to find older versions of mouse
drivers, msmouse worked fine for me (newer msmouse not).

If you can compile the dosbox sources you could remove that revectors
the mouse interrupts on gfx mode changes, then the mouse should
be fully unloaded.