My advice was meant for the author of this thread, not for you and is called troubleshooting. A hard reset often jogs a notebook that will not start into operating as it should. Often a new member who has started a thread will use the advice given and find that it resolves their issue. The same new member may never even post to his or her thread again to let people who responded know if a suggestion helped or not. We accept that as part of the nature of the forum culture.
wifi wouldn't work. Tried reinstalling driver. Rec'd blue screen of death. downloaded iso to usb. Installed to new partition. wifi still doesn't work. Would like to get a link to download recovery to reinstall all HP drivers needed. Win8 original OS. Installed w10 last year. A clean install would be fine. It's my moms laptop and needs a way to communicate with family members. And apparently... HP only helps if you pay for tech support.
With the wealth of drivers and software from the 2000t model you pointed me to, I forgot that there were of course SOME drivers and software available for my 2000 model at its download page... including Bluetooth drivers! It turns out that the driver is the identical package that I'd found elsewhere (sp61937, version 9.2.10.22 dated 2013-05-08).
I tried finding the BIOS firmware update file using the official HP website. However, when I enter the serial number for my laptop, the HP website comes back with "can not find any drivers for this product", so how am I supposed to update my BIOS? (BIOS F.47).
I am using a HP 2000 Notebook PC running Windows 10. I have downloaded an installed the Arduino software. When I plug the Arduino into the laptop it does not see it. The power is on and the blue light is on. Any suggestions?
Make sure Windows 10 is fully up to date first. Initial Arduino drivers were problematic and have been fixed by subsequent updates. I turned updates off on my tablet because they quickly consumed all of my disk space. There is no way to shunt update files to an SD card yet so this is problematic. If you still have plenty of disk space, make sure your version of Windows 10 is fully up to date before trying this procedure (of course, you could always to it again AFTER updating).
Cards and drivers listed on this page have been tested by card vendors or product teams, and results have been reviewed by Autodesk product teams. The tests verify that the hardware supports the product features. Cards and drivers not listed may still work with the product, but Autodesk has not yet received or verified test results.
Download the latest and official version of drivers for HP 2000-369WM Notebook PC. This driver package is available for 32 and 64 bit PCs. It is compatible with the following operating Systems: Windows 8 (32-bit), Windows 8 (64-bit), Windows 7 (32-bit), Windows 7 (64-bit). Don't worry if you don't know what's your operating system. HP website will automatically detect your device and select the best installer for your OS.
Download the latest and official version of drivers for HP 2000-350US Notebook PC. This driver package is available for 32 and 64 bit PCs. It is compatible with the following operating Systems: Windows 8 (32-bit), Windows 8 (64-bit), Windows 7 (32-bit), Windows 7 (64-bit). Don't worry if you don't know what's your operating system. HP website will automatically detect your device and select the best installer for your OS.
The device works as a bi-directional gateway so it is also possible to send messages from PC applications to the NMEA 2000 network. That allows, for example, sending of AIS data from a PC USB receiver to a chart plotter, as well as control over the autopilot and the vessel's other equipment. It also supports using a PC as an 0183 to NMEA 2000 converter if you have some NMEA 0183 equipment connected to one of the other PC ports.
The Gateway:
The Gateway is designed for operation in an NMEA 2000 network and is compatible with a wide range of equipment supporting this protocol. Raymarine SeaTalk NG, Simrad SimNet,and Furuno CAN networks are branded versions of NMEA 2000 and differ only by connector type.Garmin uses the NMEA 2000 Micro connector in its devices, which is compatible with the DeviceNet Micro connector.
It could be a Realtek HD Audio Device. Right click the device in Device Manager with the Yellow Exclamation mark, select Properties and under the Details tab select Hardware IDs ( in 2000 it could be named Device Instance ID) in the dropdown box. The driver you find has an inf file. In that file you need the Vendor, Device, and Subsys numbers. Copy and Paste the first line into your next post. From what I have googled this should work in Windows 2000.
How To Find Drivers For An Unrecognized Device
1. Open Device Manager (Control Panel>System>Hardware>Device Manager)
2. The hardware whose drivers are missing will appear as Unknown device, so it's easier to locate the device.
3. Right click on the unknown device and click on Properties.
4. Under the Properties window click on Details tab and select Device Instance Id from the drop down box.
5. You should see a code similar to this
PCI\VEN_8086&DEV_27DC&SUBSYS_30868086
&REV_01\4&1E46F438&0&40F0
6. The portion of the code highlighted in RED is the Vendor ID and the portion highlighted in GREEN is the Device ID. In this example:
Vendor ID = 8086
Device ID = 27DC
7. Once you have obtained both the IDs, proceed to
It could be a Realtek HD Audio Device. Right click the device in Device Manager with the Yellow Exclamation mark, select Properties and under the Details tab select Hardware IDs ( in 2000 it could be named Device Instance ID) in the dropdown box. The driver you find has an inf file. In that file you need the Vendor, Device, and Subsys numbers. Copy and Paste the first line into your next post. From what I have googled this should work in Windows 2000.
How To Find Drivers For An Unrecognized Device
1. Open Device Manager (Control Panel>System>Hardware>Device Manager)
2. The hardware whose drivers are missing will appear as Unknown device, so it's easier to locate the device.
3. Right click on the unknown device and click on Properties.
4. Under the Properties window click on Details tab and select Device Instance Id from the drop down box.
5. You should see a code similar to this
PCI\VEN_8086&DEV_27DC&SUBSYS_30868086
&REV_01\4&1E46F438&0&40F0
6. The portion of the code highlighted in RED is the Vendor ID and the portion highlighted in GREEN is the Device ID. In this example:
Vendor ID = 8086
Device ID = 27DC
7. Once you have obtained both the IDs, proceed to
There you can either search for the vendor from the vendor ID or directly get information about the device along with the vendor name by searching with the device ID.
this works for xp should work for you.
Not all features are available in all editions or versions of Windows. Systems may require upgraded and/or separately purchased hardware, drivers, software or BIOS update to take full advantage of Windows functionality. Windows is automatically updated and enabled. High speed internet and Microsoft account required. ISP fees may apply and additional requirements may apply over time for updates. See
IBM PC DOS (commonly called The IBM Personal Computer DOS and IBM DOS), an acronym for IBM Personal Computer Disk Operating System, is a discontinued disk operating system for the IBM Personal Computer, its successors, and IBM PC compatibles. It was manufactured and sold by IBM from the early 1980s into the 2000s. Developed by Microsoft, it was also sold by that company as MS-DOS. Both operating systems were identical or almost identical until 1993, when IBM began selling PC DOS 6.1 with new features. The collective shorthand for PC DOS and MS-DOS was DOS, which is also the generic term for disk operating system, and is shared with dozens of disk operating systems called DOS.
Later, a group of Microsoft programmers (primarily Paul Allen, Mark Zbikowski and Aaron Reynolds)[25] began work on PC DOS 2.0. Completely rewritten, DOS 2.0 added subdirectories and hard disk support for the new IBM XT, which debuted in March 1983. A new 9-sector format bumped the capacity of floppy disks to 360 KB. The Unix-inspired kernel featured file handles in place of the CP/M-derivative file control blocks and loadable device drivers could now be used for adding hardware beyond that which the IBM PC BIOS supported. BASIC and most of the utilities provided with DOS were substantially upgraded as well. A major undertaking that took almost 10 months of work, DOS 2.0 was more than twice as big as DOS 1.x, occupying around 28 KB of RAM compared to the 12 KB of its predecessor. It would form the basis for all Microsoft consumer-oriented OSes until 2001, when Windows XP (based on Windows NT) was released.[25]
df19127ead