First post, by cyberwalker
The answer is running mouse.com from Microsoft VPC Additions or Integration Components Package.
Here are the general steps:
1. Boot up real DOS from a hard disk image. For example:
Z:>mount d c:\images
Z:>d:
D:>imgmount c "mywin311.img"
D:>boot -l c
2. Run mouse.com from Microsoft Virtual PC Additions or Integration Components Package ISO. It is the only mouse driver works so far I find.
If Windows 3.11 cannot find the mouse at first, starting something else like edit.exe may help DOS bring mouse out.
I find Windows 3.11 ( with SmartDrv.exe enabled) runs much faster through BOOT. You may need to turn WriteCache off (/X) in SmartDrv, or the disk image may get corrupted. To make DOSBOX consume much less CPU time while running Windows 3.11, you can try another tool IDLE.COM from VPC.
Edit:
In DosBox SVN of July 2K15 the Windows 3.11 mouse issue has been fixed; previously I was using the one of April.
SQLite compiled for DOS/DPMI