This test proved my theory! Most systems only went into screen saver, and the two panels that did sleep eventually woke up back to the login window. I am determined to get this brought up to Dell’s attention, hopefully second level or higher. So this issue is not related to drivers, BIOS revisions, or even limited to a few system models, it is definitely a mouse hardware issue. I then let the systems go idle and watched them for minutes. All the panels should have gone to sleep after 45 minutes, but instead only one did.
|Date Added:||8 March 2014|
|File Size:||29.15 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Most systems we deploy don’t have mousepads, and instead run on the bare desk. This test proved my theory! I never tested system sleep, but I’m sure they would also bring a system out of sleep.
Still no resolution, so I install the Lenovo mice and move on. All the panels should have gone to sleep after 45 minutes, but instead only one did. It was when I disconnected the mouse and keyboard that the panels went to sleep.
As of late September I have finally reached someone dell Dell above level 1, and am in the process of diagnosing the issue. Combining the high-sensitivity movement mode 4-LED with a mousepad produced much more than the normal amount of packets for Wireshark to capture. Fast-forward now to Septemberand this issue is still gnawing at me.
Now I have about 5 different production dates to test.
MOCZUL-DELL DELL MOUSE 6 BUTTON LASER MOUSE WITH USB CABLE – 6 BUTTON
It is truly fascinating watching a room of 20 systems where the panels are randomly changing states, intermittently coming out of screen saver to the login window, or panels going to sleep only to wake up again, never going into screen saver or never reaching sleep. Fast-forward a few months to April The best part in all this is that the mouse also affects non-Dell systems.
I attempted to get this issue raised to Dell through moczkl reps, but this also failed. I take these into the lab and they all cause the sleep problem, so this issue affects the whole model line, at least 16 months. The original Lenovo mice never had this problem.
DELL USB WIRED MOUSE MOCZUL-DELL
Most systems only went into screen saver, and the two panels that did sleep eventually woke up back to dwll login window. One of the last tests I did was also the most telling. I had a theory that the MOCZUL was incorrectly detecting movement, and by turning up the DPI setting button on the top of the mouse to its highest value, it would amplify this effect.
The problem was finally isolated to the mouse Sometimes they are enough to stop sleep, or screen saver. What seems to be happening is the packets that are being sent from the mouse don’t always push the panel out of sleep mode or out of screen saver, but instead seem to reset the internal timer for activating panel sleep. DefaultUser” screen saver for the login screen set to “blank” after 3 minutes.
In our training labs all the mice are on mousepads, but I’ve been testing on an anti-static mat when on my bench.
I contacted Dell first-level support through Chat, but this didn’t go very far. A WireShark capture with the USB plugin showed intermittent packets being received from the mouse when they were sitting idle. It also caused the same issue on the Lenovo system. I saw about packets in about 2 hours, compared to about 60 packets in moczlu hours on the same mousepad but running in normal sensitivity mode 1-LED.
Since I never found a resolution, I simply pulled mocul the Dell mice and replaced them with the old Lenovo mice, and the panels slept fine.
It may not be a safety issue, but certainly affects the systems ability to reach sleep consistently which causes higher power consumption and will reduce the life of panels that can’t reach mouxe mode. Putting the mouse on a rough nylon mousepad really brings out the issue.
To continue using , please upgrade your browser.
After the systems had sat idle for a few hours I noticed that only about half the panels were sleeping, where instead all should be. So this issue is not related to drivers, BIOS revisions, or even limited to a few system models, it is definitely a mouse hardware mouss.
We imaged these with a custom built Windows 7 image. I spent hours checking Windows settings, BIOS settings, trying fixes found mousse the internet, but the issue persisted.