15-JSZ-[Kensington Bluetooth Issue]-26th MAR-2007
I copied the missing file from the laptop to the desktop, and was searching for the folder it's supposed to live in. Noticed that this folder was compressed, so I unzipped it and placed the file copy there.
Ok what was the missing file bth.sys
Do a search on the Laptop to see if the file really did get copied into the correct folder. I need to know what really got accomplished not what you thought
For the record, I am sticking with the software that came with the hardware, and which is running successfully on the laptop.
That is what I wanted you to do This will keep the variables down. Kind of starting over again
Uninstalled and reinstalled the software.
That was good to do New baseline established Now the Dongle was not connected
while you installed the Bluetooth Program. Is that correct?
I know this sounds goofy, but the software installation package indicated a successful installation even though I got an error message indicating that the Windows installer was terminating.
Nothing is silly Just need to interpret/translate the message -
It seems to me that at least part of the problem is that the dongle is powering down just as Windows starts up. The LED remains illuminated all through bootup, and then goes off immediately before the Windows logon screen appears.
That was what was concluded before. We may be better off than what you think Lets try this way again to connect the dongle
1. Leave Dongle disconnected and free as many rear ports as you can
2. Power Up Desktop
3. Let Windows install & settle down
4. After Windows is up and running
5. Connect Dongle to Rear Port The initial connection sometimes works better at boot up And sometimes it is better to make initial connection after Windows is up & running Its a crap shoot
6. Dongle should illuminated in Powered State
7. Remain on while in Detection State
8. The USB Port is informing the USB Host of new Device
9. Now USB Host is reporting to Device Manager the new device
10. Device Manager tells Control Panel PnP of new device
11. PnP has to locate the USB driver that the Port & USB Host has installed
12. Now the Device Manager - USB Host assigns PC Resources to the USB Port to communicate to the Dongle so now a communication link is established with information being supplied by the drivers
13. New Device Notification pops up
14. Communication should begin Dongle should be blinking changing colors or whatever/however it indicates communication At first the resources are assigned Interrupts endpoints resets status requests plus whatever
15. If the correct driver is installed & PnP has located it properly then more activity can be seen
16. This is where the failure occurs Before the driver was there but the descriptive details of inf file was missing so failure occurred
17. We should get past this and now your new attempt failed probably because of Noise High inrush or whatever Hopefully things are more settled now & installation takes place??
18. Now we still may not have the correct driver match up
19. Instead of scanning for new hardware try updating Driver in Device Manager
20. If it fails again on this try I would expect Device Manager should have an Unknown Device
or some failure listed Before there was not any indication
21. Try it without that 6 ft cable
You may have to set connections to Auto Detect
1. Click Start
2. Browse to Settings
3. Open Control Panel
4. Open Internet Options
5. Click on Connections Tab
6. Click on LAN
7. Check Set to Automatically detect settings
8. Click OK
twice to close 2 folders
9. Close Control Panel
I do not think that this matters in this case, but networking is not my bag Also I did check your DHCP Client services was set to Automatic
It is a matter of having the correct drivers and inf files and following the correct sequence
PS Run Everest Device Report again and attach as J SZ -Device#4- see if I see anything enlightening ??
Edited by Jack123, 26 March 2007 - 12:58 AM.