- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Lost driver during win 7 upgrade on satellite a505-s6960
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-15-2009 10:59 PM
Tried to find this in the forums and could not but apologize if this has already been answered.
I have successfully upgraded from Vista 64 bit to win 7 64 on my satellite a505-6960 bit, minus one annoying little driver being lost.
Above my keyboard the "touch" buttons that control- eco mode, media buttons, and volume control have lost the ability to light up even when I am on AC power. They have also lost the ability to beep when they are touched and letting me know that I pressed it. The bar above my touchpad that lights up when the touchpad is turned on and the satellite symbol on the bottom left corner of my laptop has also lost the ability to light up as well. I figured they are all related. Any help is appreciated.
Thank you.
Paul.
Re: Lost driver during win 7 upgrade on satellite a505-s6960
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-16-2009 05:42 AM
i should receive my win7 dvd in 2 weeks (hopefully) with all the issues around i guess i better stay with a dual boot (Vista working perfectly and Win7, until it gets properly fixed and working)
u500.
Re: Lost driver during win 7 upgrade on satellite a505-s6960
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-19-2009 04:29 PM
Wouldn't hurt to uninstall and reinstall the TVAP. I notice there are several listed. Try them all.
Toshiba Value Added Package (TVAP) for Windows 7/Vista (64) (Version 1.2.27_64 - Released 10/20/09)
Toshiba Value Added Package (TVAP) for Windows 7/Vista (64) (Version 1.2.27_64 - Released 09/03/09)
Toshiba Value Added Package for Windows 7 (64) (Version 1.2.26_64 - Released 10/07/09)
Mystery to me why the first two have identical version numbers. Won't be the first time.
Someone with a similar problem reported that downgrading the display driver solved it.

Feedback