
- Mouse drivers dosbox windows 3.1 install#
- Mouse drivers dosbox windows 3.1 drivers#
- Mouse drivers dosbox windows 3.1 driver#
NOTE: Most Logitech products will work with no. Click on the Downloads tab and select your operating system in the drop-down to check if software is available. Keyboard: On a label on the bottom of the product. It works well enough for me so I thought I'd share this with people. Mice: On a label inside the battery compartment, underneath the batteries or on the bottom of the product.
Mouse drivers dosbox windows 3.1 driver#
So I modified dosbox int 33h,3 to always return an absolute value between set min and max (mapped into the display width/height in use), and set min=0,max=8191, and had the mouse driver just do shl 3 on the values before returning them to windows. Windows 3.1 wants absolute positions as values with the full range of 0-65535 that it maps into whatever the display width/height is. Below are some screenshots of software running in vDosPlus. The mouse driver uses PS2 callback for mouse button data and int 33h,3 for positioning. However, most todays Windows is now 64-bit, and to run DOS programs you need a DOS emulator. Known bugs: It sometimes unintentionally drags items, just clicking a few times on-the-spot should clear it. Then just run "win".įor old installations it should be enough to just replace the pnd and the mouse driver. Drop my new MOUSE.DRV into the system folder. You will need to create a folder for your Windows 3x 'C:' drive.
Mouse drivers dosbox windows 3.1 drivers#
Downloads for these drivers can be found below.
Mouse drivers dosbox windows 3.1 install#
You will also need to install display and audio card drivers to have sound or more than 640x480, 16 colors. Then backup your MOUSE.DRV in C:\WINDOWS\SYSTEM (= cd windows\system + copy mouse.drv mouse.old). 065 or higher and the Installation files for Windows 3.1, 3.11 or Windows for Workgroups 3.11.

It asks you to restart windows, I said later and exited windows (be sure to be in windowed mode when exiting windows). When it asks for win.cnf point it to C:\WINDOWS\SYSTEM.

After installation use the S3 driver patcher I posted above to create an S3 driver directory (or copy an old directory), run windows and change the video driver, point to C:\S3 (or whatever you picked). Usage: Run winbox_r2.pnd, create/pick a folder for your C drive, copy your W3.1 installation files in a directory there, run windows 3.1 install (the mouse might act weird with the original mouse driver, dont worry). tar.bz2 of the dosbox source used so I'm complying with dosbox licenses). So, I've written an absolute positioning mouse driver that is based on Windows 3.1 DDK sample mouse driver code and made modifications to dosbox for this hack to work properly, so I wont (atleast yet) be releasing the mouse driver source, but I think i can release a binary: and while I'm at it, a new revision of winbox with some mouse code that might break many games (none tested), but works with my new driver: (the pnd includes a.
