- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
I have this same problem on my pavillion dv6. sent it to warranty repairs twice they have replaced the keyboard, touch pad and mother board, worked about a week after last repair which took two weeks. I am sending it back on feb 10 for more replace parts and see if it works. I searched the web and I have not found any solution and hp won't even acknowledge the problem althoughit it is not limited to the hp product. Reconfigureing and downloading drivers etc. has done nothing but waste time. I am using usb mouse with touch pad disabled for now even that acts strange with the touch pad enabled.
I have a garment pattern CAD soft for china. I don't konw it connect to Rollup Digitizer .where I can to try connecting Rollup Digitizer .I think
Rollup Digitizer is very easy carrier . I like very well.I live in New York
can you sent E-mail to me email@example.com
This is a suggestion, not necessarily a solution;
Go to the Device Manager (you know how) and disable all HID's ... like mice, keyboards that you don't absolutle need to start your computer.
In your environment, also remove / turn off any fluorescent lamps.
Why not MOVE the computer from there as a final possibility? Use the other computer's HID's.
... hey this is baffling!
I've had a similar problem - I unplugged the tablet from the PC and back in again, the PC recognised it as new and reinstalled it straight away (this is on XP). The first time the driver stopped responding I had unplugged the tablet because intended to deal with problem later. Plugged back in - worked. Twice now. I've restarted to see if the driver stopped again and if I would have to re-plug the tablet, didn't need to, I guess it's a solution to keep in mind next time this comes up.