Sam44
01-28-2012, 04:38 PM
-HP ProBook 5310m
-Intel GMA X4500HD
Mobile Intel 4 Series Express Chipset Family
-HP Dockingstation
Q834ET/FQ834AA/HSTNN-S01X
-KVM Switch Aten CS682
-Win 7 Prof. 32-bit
-Kaspersky Internet Security
all drivers are up-to-date
My problems:
If I plugged in the usb cable from the docking station into the laptop the docking station disconnect serveral times like i unplugged the USB cable out of the notebook. But it do it automatically and look like I was unpluged the usb cable!
It need 15 attempts (plug/unplug/plug/unplug...) and after that it working only for a while...sometime longer, sometime shorter.
Since installing the display link software the monitor get black for a second if I plug in/out the USB cable or connect the power cable from the laptop.
Attempts to solve the problems:
set Aero Design
install latest graphic driver
update display-link software
buy a new usb cable
install windows (more that once)
buy a second power cable
check all HOWTOs from DisplayLink.org
What could be the problem? I think it must be a interaction between display-link and...another driver...?
.
-Intel GMA X4500HD
Mobile Intel 4 Series Express Chipset Family
-HP Dockingstation
Q834ET/FQ834AA/HSTNN-S01X
-KVM Switch Aten CS682
-Win 7 Prof. 32-bit
-Kaspersky Internet Security
all drivers are up-to-date
My problems:
If I plugged in the usb cable from the docking station into the laptop the docking station disconnect serveral times like i unplugged the USB cable out of the notebook. But it do it automatically and look like I was unpluged the usb cable!
It need 15 attempts (plug/unplug/plug/unplug...) and after that it working only for a while...sometime longer, sometime shorter.
Since installing the display link software the monitor get black for a second if I plug in/out the USB cable or connect the power cable from the laptop.
Attempts to solve the problems:
set Aero Design
install latest graphic driver
update display-link software
buy a new usb cable
install windows (more that once)
buy a second power cable
check all HOWTOs from DisplayLink.org
What could be the problem? I think it must be a interaction between display-link and...another driver...?
.