Re: Mouse Driver
Christian Erdmann
Look on the bottom of the wireless device for a Reset button. Resetting the device will disconnect and then reconnect the wireless connection. There might also be a Reset button on the USB receiver for your device.
For USB wireless devices, this might be as simple as unplugging the USB wireless receiver, waiting for about 10 seconds, and then plugging the USB wireless receiver back into the USB port. The wireless connection should be reestablished.
Under Windows Update, select Check for updates. Windows Update will tell you if you need any updates or not, and whether the latest updates were successfully installed.
There might not be any driver updates available.
The Microsoft Mouse and Keyboard Center is an app that helps you make the most out of your Microsoft keyboard and mouse. Mouse and Keyboard Center helps you personalize and customize how you work on your PC.
I had this same issue occurring and had no idea what was happening and tried everything until I stumbled across the second mouse driver. If I disabled just that device driver (not the other one that is the true mouse), then I had no more jumping problems.
The only thing I can think of is that this model of Dell Precision was not tested in the Fall Creator update back in OCT17 by Dell. Drivers were not updated, so either some other driver might work or there is no telling if something could hose the drivers all together. It also could be possible that Windows 10 is not supported for this machine all together.
Another possibility is that someone could have plugged something into the USB ports causing Windows to flake out for I/O device drivers. I did one more test and was able to read/write a flash drive, but not a desktop scanner or other brand/model keyboard and mouse.
I was having this same issue, just with a different model of keyboard/mouse (Dell machine and wireless keyboard/mouse combo) and after uninstalling the KB4074588 update like michellelieske suggested, the issue was resolved. I was able to remote into the machines and uninstall that way. My best guess is that it was a registry change made by the patch that caused the issue.
The issue was that most USB devices would not be recognized, as well as the touch screen would not work. The USB devices would return a code 28. For example, plugging in a mouse would cause the red light on it to appear for several seconds before turning off. I had tried disabling selective suspend by editing the registry and a lot of other unsuccessful items.
The only downside is the amount of memory it takes, since I've got no free upper memory blocks in that particular PC to load it into.
So my quesion is, is there any good replacement ? I know of CuteMouse, but it seems my copy of Windows /386 doesn't like it
and it still requires more than 3KiB of RAM.
I am aroused about any X86 motherboard that has full functional ISA slot. I think i have problem. Not really into that original (Turbo) XT,286,386 and CGA/EGA stuff. So just a DOS nut.
PS. If I upload RAR, it is a 16-bit DOS RAR Version 2.50.
Helix Software Company released a commercial application called Multimedia Cloaking in 1994. The package included "cloaked" substitutes for CD-ROM extensions, Disk/CD-ROM cache and mouse drivers. For the mouse driver, this meant a 1K stub in conventional memory and the bulk of the (Logitech Version 6.33) driver in extended memory.
If only more people knew about it, most of the memory issues back then would have gone away.
Anyway, I keep my eyes open for a copy of it. It could come in handy for that 386 I always wanted to build..
I actually used some viewer that would show me the free RAM and contiguous blocks and then I would load stuff in different order and manually specify stuff with EMM386 to get the most possible available.
The Logitech DOS mouse driver since MouseWare 6.50 was enabled to take advantage of CLOAKING as well, thereby reducing the mouse driver's memory footprint visible to DOS applications from 27 KB to 1 KB.
This may reflect a technology exchange between Logitech and Helix Software. It means that you may be able to use the cloaking for your mouse without having to get Helix Multimedia Cloaking. I have not checked to see whether this statement about MouseWare is true or not, but it's great news if true.
A really interesting thing that I saw when looking Helix up is that the cloaked drivers are supposed to run faster because they are running in 32-bit mode instead of 16-bit mode. Makes sense but not sure that it actually makes any real world difference.
I managed to get QEMM's advertised 634k free conventional memory in the past. Netroom likely requires a 386's MMU resources, all the cloaked drivers definitely required it. Also, QEMM had a similar feature called "stealth".
I never had compatibility problems due to QEMMs stealthing. If something did not run it was always some other option.
If you don't want to read the docu, I would recommend to use Optimize. The diagnostic routines after the passes are quite sophisticated and will setup a good config. Use only Partial for DOS-Up.
(If you really want to go for 'full' then you definitely should read the docu for implications)
Retronn.de - Vintage Hardware Gallery, Drivers, Guides, Videos. Now with file search
Youtube Channel
FTP Server - Driver Archive and more
DVI2PCIe alignment and 2D image quality measurement tool
QEMM works magic but some stuff like Dr. Sbaisto don't like it. I get 635K free on my DOS system and keep my older AUTOEXEC.BAT + CONFIG.SYS around just in case. Even with that setup, I had it at 623K free
UMBPCI generates the UMBS from Shadow-RAM and not from XMS. Often DMA in Shadow RAM is not supported which lets floppy disk access fail and disallows to load caching drivers like smartdrv to Shadow-RAM.
Sorry to dig up this topic - I actually used Cutemouse but its compatibility with DOS games is rather iffy. In fact, the first game I tried, the mouse went haywire when I pressed the right mouse button. I had to revert back to my old PS/1 mouse driver. Anyone know another low-memory mouse driver?
I use Ubuntu 14.04 on a laptop, usually with an external usb mouse and keyboard and screen connected. Sometimes, however, I unplug all of them and move the laptop and keep using it with the builtin keyboard and screen and touchpad.
At random times it happens that the touchpad stops working (but if I plug the usb mouse, the usb mouse does work). Though this happens very rarely, when it does it's a great annoyance, as I'm forced to reboot if I need the touchpad to work again.
Is there some workaround that I can try, such as killing some process that would automatically restart, or some command that would cause the touchpad driver to restart or refresh or something? Anything that may "wake up" the touchpad without having to reboot?
Next: Notice where it says id=X in one long column for every input device. You want to find the device id that corresponds to the input device you want to disable (Maybe something that sounds like "touchpad"). Then replace X in the following command with the id number representing the input device you want to disable:
Note: If you're not sure which device id you should use to disable the touchpad, then you can find out by testing random id's and seeing if your mouse pad still works. Make sure you are NOT DOING ANYTHING IMPORTANT. Save all your work and be prepared to restart your computer if you do something like disable your keyboard. (You may have trouble trying to enable it again if you can't type into the terminal.
Reason: I desperately needed an answer to this problem because the problems I was experiencing with my touchpad made doing any kind of work impossible. Suddenly, at some random moment when using my laptop, for apparently no reason, my touchpad goes into some kind of "special mode". Merely moving one finger on my touchpad would cause the screen to scroll, instead of actually moving the cursor of the mouse on the screen so it was impossible to get the mouse to hover over anything in broswer without considerable coordinating efforts to account for the scrolling screen and non moving mouse. I wanted to find a way, WITHOUT RESTARTING THE LAPTOP, to reset the touchpad. On the plus side, resetting the touchpad with the method above actually fixes my problem.
59fb9ae87f