HP Support Forums

Join in the conversation.

Search the Community
turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
This HP Community is for Customer to Customer Product Support. First Time Here? Check Out Videos on How to Search, Register, Post and More.

QuickLaunch Button for MediaSmart Not Working after Windows 7 Upgrade. (1591 Views)
Reply
Reply
Topic Options
MRS95 Student
Student
MRS95
Posts: 1
Registered: ‎12-14-2009
Message 1 of 3 (1,591 Views)
Report Inappropriate Content

QuickLaunch Button for MediaSmart Not Working after Windows 7 Upgrade.

‎12-14-2009 07:02 AM

I've recently upgraded from Windows Vista 32-bit to Windows 7 64-bit. I've downloaded a large number of drivers from HP. Everything seems to be working, except for the little "touchpad" near the screen. The touchpad has a MediaSmart Quicklaunch button, a mute button, a volume control, and 4 buttons for the CD\DVD player (back, play/pause/ forward, stop) as well as a wireless on/off button. The volume, mute,and wireless buttons work, but not the QuickLaunch or CD\DVD controls. I have installed the recommended Quicklaunch application / drivers. Does anyone have an idea of what's wrong? My computer is a Pavilion dv4-1228ca Notebook.

 

Thanks.

0
Reply
0
Please use plain text.
 
mpremnas Student
Student
mpremnas
Posts: 3
Registered: ‎01-09-2010
Message 2 of 3 (1,425 Views)
Report Inappropriate Content

Re: QuickLaunch Button for MediaSmart Not Working after Windows 7 Upgrade.

‎01-09-2010 09:16 PM

I too am experiencing this on a dv1245, Win 7 Pro x64.

0
Reply
0
Please use plain text.
 
mpremnas Student
Student
mpremnas
Posts: 3
Registered: ‎01-09-2010
Message 3 of 3 (1,334 Views)
Report Inappropriate Content

Re: QuickLaunch Button for MediaSmart Not Working after Windows 7 Upgrade.

‎01-30-2010 02:33 AM

I had gone through all the step that HP lined out....it appears to be a software issue that will hopefully be addressed by windows in a future update.....

0
Reply
0
Please use plain text.