- Dec 5, 2006
- 145
- 0
- 76
Hi All,
So my wife dropped a glass dish on the laptop with the screen closed and cracked the OEM screen. No accidental damage coverage so I ordered a replacement screen by laptop MOD # and it worked but no touch. It didn't even detect a touchscreen was installed. So I return it and ordered from a different retailer this time the exact same P/N as the OEM screen. Plugged it in and hooked it up before taping everything together. Now I have display(again) and it detects touch compatibility(making progress) but touching the screen doesn't register. I have messed with all the software side items drivers, oem tests, etc.. with no change. I know that I seated the plug well when I dropped the screen in unfortunately it's already in the shell with stretch tape. Is there some secret squirrel option that needs to be turned on or am I just looking at a reseat on the plug ? Maybe a display cable replacement? The odd part is it isn't working in the HP OEM diagnostic tests either outside of windows which pushes me towards it being a hardware issue.
So my wife dropped a glass dish on the laptop with the screen closed and cracked the OEM screen. No accidental damage coverage so I ordered a replacement screen by laptop MOD # and it worked but no touch. It didn't even detect a touchscreen was installed. So I return it and ordered from a different retailer this time the exact same P/N as the OEM screen. Plugged it in and hooked it up before taping everything together. Now I have display(again) and it detects touch compatibility(making progress) but touching the screen doesn't register. I have messed with all the software side items drivers, oem tests, etc.. with no change. I know that I seated the plug well when I dropped the screen in unfortunately it's already in the shell with stretch tape. Is there some secret squirrel option that needs to be turned on or am I just looking at a reseat on the plug ? Maybe a display cable replacement? The odd part is it isn't working in the HP OEM diagnostic tests either outside of windows which pushes me towards it being a hardware issue.