- Joined
- Nov 5, 2018
- Messages
- 2,975
I have this old junky Dell Inspiron 3147 convertible. Honestly all I wanted to do is watch videos from my NAS on before I go to sleep, surprisingly enough the video is pretty darn good, the touch screen is awesome for what it is especially since it was free. So as not to disturb my GF I have a pair of noise reduction Bluetooth headphones. Although most users couldn't get the system to take 8gb of RAM, I have a pile of high quality modules and got one that works well in the system.
So now you know the setup. So this Dell was originally shipped with an Atheros/Quallcomm, blah-blah 1707 wireless card w/Bluetooth. Bluetooth is a jokes and keeps disconnecting which makes the Dell kick over to the speakers and gets me in trouble. SO I go down in the workshop nd dig out an Intel 7265 wireless card (which is FAR better). Now here's where it gets whacked. First silly me thinks "Oh I'll just uninstall the old card, software and drivers, put the new card in (now get this) use the exact Windows 10 drivers for this card listed on Dell's site for this model. WRONG!!! I then reloaded Win 10 and tried the same procedure and used the drivers from Intel, still no Bluetooth, just an unknown entry in the device manager.
In a last ditch effort, I loaded the system with Win 8.1 as it was delivered, loaded the Intel driver set and guess what, the Bluetooth worked great! So then I figured I would try to upgrade the 8.1 install to 10 so I did. Not only did the Intel wireless work, Windows update loaded the divers that enabled Bluetooth in Windows 10. Now I have read that there is a possibility that 8.1 "sees" it has a serial port device and 10 carries that over in the upgrade. Unfortunately when 10 sees it as a "virgin" it wants to configure it as a PCI-e for whatever reason.
The only reason I am sharing this story is if you ever run into similar situation you might not have to bang your head against the wall as I did.
Not that many of you will encounter this, but be aware there were subtle but drastic changes to how Windows now natively deals with serial data. A lot of the networking hardware I setup and maintain still has serial console ports, slow as all get out by today's standards, but still work just fine. Many of the RS-232 to USB adapters won't work with Win 10 + 11 as well.
So now you know the setup. So this Dell was originally shipped with an Atheros/Quallcomm, blah-blah 1707 wireless card w/Bluetooth. Bluetooth is a jokes and keeps disconnecting which makes the Dell kick over to the speakers and gets me in trouble. SO I go down in the workshop nd dig out an Intel 7265 wireless card (which is FAR better). Now here's where it gets whacked. First silly me thinks "Oh I'll just uninstall the old card, software and drivers, put the new card in (now get this) use the exact Windows 10 drivers for this card listed on Dell's site for this model. WRONG!!! I then reloaded Win 10 and tried the same procedure and used the drivers from Intel, still no Bluetooth, just an unknown entry in the device manager.
In a last ditch effort, I loaded the system with Win 8.1 as it was delivered, loaded the Intel driver set and guess what, the Bluetooth worked great! So then I figured I would try to upgrade the 8.1 install to 10 so I did. Not only did the Intel wireless work, Windows update loaded the divers that enabled Bluetooth in Windows 10. Now I have read that there is a possibility that 8.1 "sees" it has a serial port device and 10 carries that over in the upgrade. Unfortunately when 10 sees it as a "virgin" it wants to configure it as a PCI-e for whatever reason.
The only reason I am sharing this story is if you ever run into similar situation you might not have to bang your head against the wall as I did.
Not that many of you will encounter this, but be aware there were subtle but drastic changes to how Windows now natively deals with serial data. A lot of the networking hardware I setup and maintain still has serial console ports, slow as all get out by today's standards, but still work just fine. Many of the RS-232 to USB adapters won't work with Win 10 + 11 as well.