First post, by baer
I recently upgraded from 0.73 to 0.74 and for some reason there seems to be a problem regarding the initial numlock state.
I'm running DOSBox in Windows Vista x86 SP2. My keyboard numlock is always on. When I launch 0.73, the numlock works fine right off the start (ie it is active in DOSBox too). With 0.74 however, the keyboard led is lit but DOSBox behaves as if numlock is off. I have to push the numlock key twice to 'sync' the led with with DOSBox's internal numlock state.
Furthermore there is another problem with the mouse support. The middle button only works as long as DOSBox's internal mouse driver is used. I'm running a configuration that boots a real DOS off a harddisk image and therefore I have to use my own mouse driver. In this configuration the middle mouse button does not work.
I found the problem in mouse.cpp, line 158. It SHOULD be:
Bit16u mdat = (data & 0x07) | 0x08;
The original 'and' mask of 0x03 destroys the middle button state information!
Ok, so that is solved! Now back to the first problem: the numlock thing. For a reason which I don't know, my build does not show that numlock problem! I used the information on the Wiki to configure the source code and my development environment is MS Visual C++ 2008 Professional.
Regarding the numlock problem, I think the first step would be to create a build with exactly the same settings as the binary download was done. Where can I find information on how to configure the source so that I achieve exactly the same build as the one which is available for download? Or has the numlock problem in 0.74 already been solved? Again, it was no problem in 0.73.
The middle mouse button problem has been there forever, I guess. But the fix for that is here in this post!
Thank you for the good work and thanks for any info on how to configure the sources.