Not sure if this will help anyone, but I thought I would post that I was able to get Windows XP (sp2) up and running on my brand new dv6645us in less than a day!
Like just about any good computer user, I too am disgusted with Vista, and everything about it. So when I had to purchase a new laptop recently, I was extremely disappointed that XP was not offered on more new equipment.
If I had the time to wait, I would have probably would have just ordered a dell, or some other custom laptop with XP, but time just did not permit me right now.
I ended up with the dv6645us because it wasn't too outrageously priced, and I could have it "right now"!
The biggest feature / demand (at least to me) of this laptop, was that it has bluetooth built in. This is important to sync & have DUN access through my cel phone. I know I could just buy a dumb little usb BT. But for one, it sticks out the laptop, and my clumsy(lazy) self would just end up breaking it anyways, two, if I am going to be spending $500+ on a new laptop, it better have all the features that I WANT IT TO! (Why don't all the sales monkeys understand this?)
Anyways, on to the real info here.
I was able to remove that POS vista, and get XP installed on this thing in about a days worth of effort. And while the subject says 99.9%, to me it is 100%, because the other stuff not working (or tested yet), is not important to me or most (I would hope) other users out there.
The .1% consists of me not yet testing the included wireless remote & all of the "hard" buttons located just above the keyboard.
To get all the XP drivers downloaded & installed required only about half a dozen inf file edits. But most of the driver installs were just stock package downloads.
The only items requiring inf edits were the 3 Conexant HD audio & modem packages, and the Nvidia SMBus & wired NIC drivers.
There are no "other" or "unsupported" devices listed in my device manager (can provide a screenshot if asked).
The 5 in 1 memory card reader, Bluetooth, Wireless NIC (+ Utility), Touchpad, and even most of the "other/hard" buttons (volume +/- & mute) above the keyboard even worked fine with the base installers I was able to find (direct from hp, nvidia, or other places).
I want to thank the author of this page: http://www.nogodforme.com/HPDV6500T.htm as it was some help, not to mention pointing me to this forum, where I got a little more help from reading.
If enough people ask, I will probably make a similar page for my laptop XP install process, and tips.![]()
If you do have specific questions, please DO NOT PM or try and email me, ask your questions about this in the forum / thread, this way everyone will benefit from the discussion.
-
For those of you curious, the dv6645us (and maybe even the dv2610us too) has the following hardware makes/models, and could use the suggested drivers:
NVidia MoBo chipset:
nForce 560
(CPU-Z states it is the exact MoBo model: Quanta 30CF)
Used file: 12.15_nforce_520_winxp32_english_whql.exe directly from Nvidia.
Once extracted, installed, inf edits were then made & updated for just the SMBus & Ethernet drivers.
INF EDITS:
This is where things get much more difficult if you don't know what you are doing, or just aren't comfortable doing them. This can also be somewhat dangerous I guess, and will actually let you install any driver for any piece of hardware. Just because windows will actually let you install (any) driver, doesn't mean the device will actually work though. You should be confident when picking your drivers and making these edits. Since I was using the real NVidia drivers for the chipset that was identified by the CPU-Z utility, I was pretty confident with this driver choice.
After the Nforce drivers run through their install process, it usually leave the drivers uncompressed in a directory on your C: drive (probably C:\NVIDIA\something)
SMBus inf edit:
I opened up the SMBus\nvsmbus.inf file, and saw a large list of Hardware ID's under the [NVIDIA_SYS] section. I copied and pasted the last line of this section, and changed it to read:
%PCI\VEN_10de&DEV_01b4.DeviceDesc% = AMD_NO_DRV, PCI\VEN_10DE&DEV_0542
The way I came up with the new last four digit #'s, was to go into device manager, double-click on the unknown device "SMBus...", click on the "Details" tab, and scrolled through the first 3 options. I found that under the "Compatible Ids" area, a very similar id existed, and I just needed to change the last 4 (3 really) digits of the new line I had just made to 0524 (from 0446).
Now I just saved the inf with the updated info, went back to the "Driver" tab on the unknown device, and clicked "Update Driver". When needed, I pointed the procedure to the right place (c:\nvidia\12.15\smbus\), it found the right driver, and I would reboot if needed. Now since the device did not come up with a red X in device manager, I would say that it is working correctly.
Ethernet inf edit:
To get this driver loaded, I edited two inf files: Ethernet\nvnetbus.inf & Ethernet\nvenetfd.inf
For the first file (nvnetbus.inf), I went through, and found the [Standard] section of the file, and added this line:
%nvnetbus.DeviceDesc%=nvnetBus_Device, PCI\VEN_10DE&DEV_054C
Again, I knew to change the last 4 digits of the line to 054c since it was listed as the Hardware id in the device manager for the unknown Ethernet device.
For the second file (nvenetfd.inf):
I browsed through it, and saw that I would need to copy & edit the appropriate line under each of these three sections [ControlFlags], [Nvidia], [Nvidia.NTx86.5.1].
With the end of each new line under each of those 3 sections, the line would need to be changed to 054c as well.
Now I just saved the inf file(s) with the updated info, went into to the "Driver" tab on the unknown device, and clicked "Update Driver". When needed, I pointed the procedure to the right place (c:\nvidia\12.15\ethernet\), it found the right driver, and I would reboot if needed. Now since the device did not come up with a red X in device manager, I would assume that it is working correctly.
Since I was able to, I plugged in an ethernet cable to my little home network, and the device worked great (100 Mbit FD even!).
This concludes the first inf edit tips for the needed MoBo drivers. Next inf edits will be for the audio devices & modem.
Wireless 802.11b/g nic:
Broadcom 4311BG
sp36684.exe - Base Driver
sp36686.exe - WLAN Utility
5 in 1 Card reader:
Ricoh 5 in 1
(For this, I was able to just use the 5 in 1 Ricoh drivers meant from another pc: sp33604.exe.)
Video device:
nVidia GeForce 7150M / nForce 630M
I used driver 156.72 from over here
Note: (12-4-07)
It was brought to my attention that the drivers at my original link (above) no longer has the drivers available. I zipped up my copy I still have, and have made them available to download from here:
http://www.megafileupload.com/en/file/26949/156-72-nForce-zip.html
Bluetooth device:
Broadcom for HP.
Uses the WIDCOMM stack though, can be obtained form HP:
Newer Version (5.1):
sp34842.exe
Older Version (4.0):
sp32883.exe
Keyboard hard (quick launch) buttons:
** HP links broken, see 3rd note below a little ways **
I'm still messing with this, but I have found this much so far.
Install the HP Quick Launch Button drivers: sp34796.exe
This should get the device listed right in device manager.
To get the "on screen" volume controls to show up on XP Pro, I read this thread downloaded, and installed the MS IntelliType (6.1) drivers for the "MultiMedia Keyboard" (when asked) from Microsoft at this url:
http://www.microsoft.com/downloads/...71-8973-4F20-8C16-252DFB7D8F9E&displaylang=en
1st NOTE:
As a side note to this "on screen" volume display. The regular HP one just started working after a couple days, and I am unable to tell what got this working. I don't know if maybe the Microsoft DOT NET framework I installed actually got it working or not (this is the only thing I can think of). So I have uninstalled the MS IntelliType driver for now.
2nd NOTE:
After messing around with this a few more times, I downloaded, and installed (separately) the quicklink button drivers: 5.2, 6.0, 6.1, 6.2, & 6.3.
6.2 was what I found originally had found, and linked to up above. However, it does not function 100% (nor do any of those versions). However, the most important item to me was the on screen volume indicator. And it did not work right away in any version, except v6.1. So if you don't care about the "dvd" & "Q" button as I don't, and just want the on screen volume indicator as I did, you can download and install v6.1 of those drivers here:
sp33258.exe
3rd NOTE:
Apparently HP is too dumb to just add a link to the above linked pages telling people to get the critical update, and they are too lazy to just make a new version of this software with the critical update included.
DO NOT Forget to download and install the critical update that HP thinks is sooo important.
I have uploaded the files for your enjoyment.
Quick Link Buttons v6.3 (latest):
http://megafileupload.com/en/file/32721/sp36708-zip.html
Quick Link Buttons v6.1:
http://megafileupload.com/en/file/32723/sp33258-zip.html
After you download and install EITHER one of these files, be sure to install the HP CRITICAL UPDATE from here:
http://h20000.www2.hp.com/bizsuppor...scription.jsp?lang=en&cc=US&swItem=ob-56385-1
Again, The reason I post both version, is I know some people only like the latest versions of stuff, but I post the other (older) one because I found it to work better, and actually display the on-screen volume right after installing.
One (major) downside to the older version though, when it displays the on-screen volume level, it (temporarily) steels the window focus while the OSD is displayed.
HD Audio & Modem (Both Conexant) setup:
3 Steps to this part of the setup.
1) Download & Install the (UAA) Universal Audio Architecture drivers:
sp33867.exe
2) Download, and unzip the audio driver file:
sp35682.exe
Under the [Conexant] section of the wis30B2a.inf file, I added the following hardware id:
%HdAudioFunctionDriver.Waikiki5047.DeviceDesc% = HdAudModel,HDAUDIO\FUNC_01&VEN_14F1&DEV_5045&SUBSYS_103C30CF
This solved one of the "unknown devices" under device manager. After going to the device properties in device manager, and manually going through the "Upgrade drivers" process, and pointing that procedure to the correct directory where you updated the inf file to have the correct hardware id.
3) Download, and unzip the modem driver file:
sp35335.exe
Under the [ControlFlags] section of the WinXP\SprtHD5m.inf file, I added the following hardware id: ExcludeFromSelect= HDAUDIO\FUNC_02&VEN_14F1&DEV_5045&SUBSYS_103C30CF
AND under the [HSF_MODEM] section of the WinXP\SprtHD5m.inf file, I added the following hardware id:
%HSFModem% = ModemX, HDAUDIO\FUNC_02&VEN_14F1&DEV_5045&SUBSYS_103C30CF
After editing the inf file, go through the same "upgrade driver" process, be sure you point to the correct directory manually if you have to. This should solve the remaining "unknown device" issue.
Built-In WebCam:
It should just work in XP (w/SP2) in windows explorer. However, there are reports of some issues with 3rd party apps.
I was able to install this utility from HP:
sp35040.exe
I did have to manually start the installed exe file from \program files\hp webcam\hp webcam\xp32\VimicroCam.exe. That little utility did seem to work ok though, and it even recorded a test vid w/audio once config'd some.
You can also check out this thread:
http://forum.notebookreview.com/showthread.php?t=149463
And see if the drivers listed in there work for you. I have no idea, as I have not tested them with this model laptop, so good luck.
AMD Processor Drivers:
Apparently there are better drivers for the CPU itself. These drivers are suppose to have better handling of the dynamic CPU clock speed, and thus saving you battery life, which is very important. I didn't do any test of this theory, but it make sense from a logic stand point.
Anyways, you can visit the AMD website here:
http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_13118,00.html
Once that page is up, look for a title called (toward the bottom of the page):
AMD Athlon 64 X2 Dual Core Processor Driver for Windows XP and Windows Server 2003 (x86 and x64)
After you found that, download, and install the driver, you should reboot if asked.
Maybe more later... -
-
Very well done! I was able to follow your info and get my new dv6645us up and running in dual boot scenario with Vista/XP in just a few hours! Many thanks to The Dave.
There are, however, still a few items in my Device Manager on XP that come up unkown and I'm not sure what they are. They seem to all be for 1 or 2 devices though because there are 2 called "Unkown Device" and 2 called "PCI Device".
At first I thought they might be related to sound, because when I play an mp3 file in Windows Media on XP, I can't hear it. Codecs are installed, but the only audio device for playback available in Sound controllers is Bluetooth Audio. It seems like I'm still missing something related to the audio.
So, although everything seems to work, I'm just missing one or two more non-critical drivers. Any help with this would be much appreciated. -
this topic has been beaten to death, a simple search would reveal a 22+ page thread alone.
All hardward can be reverted to XP. Its not that difficult. -
But when I searched I found ZERO threads with the required inf edits that were needed for my laptop model #, let alone places to download all the drivers required for MY laptop model. The 22+ page thread seems to mostly cover intel chipsets, and not nVidia ones in detail. -
Thanks for the kind words and nice work on this thread. I'll add this thread to my guide because people are e-mailing me asking if I can help them with the AMD version. It's kinda hard because I went the Intel route.
The reason these kind of threads are needed, is because people don't know where to begin, and want their hand held. Yes, once you've done it the process is easy, but for a first timer, they need help. -
Dave,
Download and install quicklaunch buttons from the HP support website. This should get the remote and the media buttons working. -
Dave,
You are a life saver. Thank You for you hard work!!!! I just have to get this dumb webcam to work now.
Derek -
You can check out this thread:
http://forum.notebookreview.com/showthread.php?t=149463
And see if the drivers listed in there work for you. I have no idea, as I have not tested them with this model laptop, so good luck.
Also, i did try this utility from HP:
sp35040.exe
And it did seem to work ok (it even recorded a test vid).
Seeing as though I don't care much about the webcam, I have not looked into it much further than that though. If either of the two links I mentioned above help your problem out, please post back here, and let us know!
It wasn't too hard for me (The 5 years of the PC tech job through the windows 3.1/95/98/me/2000 era didn't hurt either (NT 3.5 & 4 were in there too!)), but I agree that guides like this do help most people out a lot. So I was happy to share it. Especially since most guides I found were dealing with Intel based systems, and not nVidia ones.
I do have a lot of the remote buttons working already, but it would be nice if I could get em all to work along with having the quickplay & dvd button customizable through the original HP utils. -
how do you get the info for the Hardware and also where on the inf file to put the hardware info
-
Hi Dave, how do i know the chipset for my machine
-
Hi Dave, how do i know the chipset for my machine my machine is a HP pavvilion dv6550ee
-
You have the nvidia nforce 600 series chipset. All AM based dv6500z & above series machines have the same hardware. The only difference would be the graphics card(integrated 7150M vs dedicated 8400M). You should be fine using the same drivers as Dave did.
-
http://www.cpuid.com/cpuz.php
After you download, and unzip the program, double click the exe file (and wait for it to start, it might take a minute or two). After it starts up, read all the info it displays, and make notes if you feel the need, but it should tell you exactly what is in your system.
-
I am having a dv 6000 series laptop (6602AU) and it is an AMD TL-58 processor based laptop. I was stupid enough to install XP without taking the proper recovery disks. Now Iam not able to find XP dirvers for this model. I am in a big fix now. Can someone please help me out ? Will the information provided by dave solve this issue.
Also I heard that installing XP will make the warranty void. Is it true ?
-Karthik -
Hi dave, I was having terrible time installing XP on my new HP 6602AU and now with your guide I was able to install all including the touch buttons. A million thanks to you dude! You simply rock!
Just curious, is it true that installing XP on this machine, voids the warranty ?
-Karthik -
-
thank you Dave, you are life saver!
i spend over 2 days try to figure out how to install XP on my DV9607us bought from staples, stuck at audio and chipset driver, they are in fact right in front of me, but without INF mod, i can not get them installed.
your method work like magic, i register the forum just to thank you.
if i did not find your post, i would stuck in vista hell for a long long time -
hi,
awesome guide btw....
i have the dv2620us and have everything up and running except the audio .....i installed the UAA ,unzipped the conexant drivers ,updated the inf and pointed the device to the driver...still no go....do i have the conexant hardware? -
if the driver won't install, you may try to recheck INF file.
this is my inf look like (DV9607US) after i add the 2nd line
[Conexant]
%HdAudioFunctionDriver.5045.DeviceDesc% = HdAudModel,HDAUDIO\FUNC_01&VEN_14F1&DEV_5045&SUBSYS_103C30B7
%HdAudioFunctionDriver.5045.DeviceDesc% = HdAudModel,HDAUDIO\FUNC_01&VEN_14F1&DEV_5045&SUBSYS_ 103C30CF
if the driver installed, but won't start, got something like error 10, it might not be the right driver -
says - wizard couldnt update driver because the hardware wasnt found
and
The drivers for this device are not installed. (Code 28) in the device manager
for both the modem and the audio devices...problem with UAA? -
[ControlFlags]
[HSF_MODEM]
if you edit audio driver INF correct, after UAA install, windows will find Conexant automatically.
code 28 is more than likely INF problem
can i see you problem device hardware ID?
and INF you point to? -
my audio inf looks like this
[Conexant]
%HdAudioFunctionDriver.Waikiki5047.DeviceDesc% = HdAudModel,HDAUDIO\FUNC_01&VEN_14F1&DEV_5047&SUBSYS_103C30B2 ;Vega 1.0, 1.1
%HdAudioFunctionDriver.Waikiki5047.DeviceDesc% = HdAudModel,HDAUDIO\FUNC_01&VEN_14F1&DEV_5047&SUBSYS_103C30A5 ;Titan/Altima, Thrifty
%HdAudioFunctionDriver.Waikiki5047.DeviceDesc% = HdAudModel,HDAUDIO\FUNC_01&VEN_14F1&DEV_5047&SUBSYS_103C30A0 ;Jakarta 3
%HdAudioFunctionDriver.Waikiki5047.DeviceDesc% = HdAudModel,HDAUDIO\FUNC_01&VEN_14F1&DEV_5045&SUBSYS_103C30CF
i point to the wis30B2a.inf
the device hardware ids are
HDAUDIO\FUNC_01&VEN_14F1&DEV_5045&SUBSYS_103C30D6&REV_1001
and
HDAUDIO\FUNC_01&VEN_14F1&DEV_5045&SUBSYS_103C30D6
help pls -
heeey thanks a lot ....got it!!!
-
hey whats 'Hp Integrated module'?
-
anybody else needs help please do the same
need hardware ID, and INF file, error code if any,
it is pointless to say i need driver help for my HP DV1234us machine, everybody has different model, without HW ID and INF, i can not do anything -
The INF edit's can be somewhat tricky since they have to be very precise.
One nice thing about it though, is that you only need to place one matching HARDWARE ID from the list in "Hardware ids" or "Compatible Ids" (in device manager) for the computer to see that the driver(inf) matches the hardware, and try to install the driver. The driver itself will not always work, especially when you are using the wrong driver, but it will install it if the id's match, which is why you have to edit the INF in the first place.
And, the HP driver install Wizard will never work after you have updated the inf, and re-run the wizard. You will have to manually choose "Update Driver" from the device manager, and point it to where the edited INF file you updated is actually at.
noobody: Glad to hear it worked for you, and thanks for helping out other users with this process too! -
Video driver link is down anybody have a different link?
-
TheDave, thank you so much for a help, everything is wonderful.
Just one thing: your link to "nVidia 7150M/n630 " driver version 156.72 doesn't work anymore and it's not possible to find this version in the net. Could you or somebody help with that? Because resolution is so bad, other driver versions doesn't help, booting windows Xp crashes.
Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -
I still cannot get my coprocessor driver to install. Everything else besides video is working awesome!
-
did you tried 163.75 here? -
Yes, i've tried 163.75. If you just start this program, it says that hardware doesn't match. But if you do manuall install throught Device Manager it finds 7150m/630m , instals drivers, but on BOOT of windows XP chrashes. I tried every driver release-the same. So the only chance is 156.72. Maybe somebody can upload it somewhere . My notebook is HP pavilion dv6610 , AMD X2 tk-55, 7150m/630m .
And problem with Coprocessor device exist too. -
try 156.55 here
this is the driver i am using now for 7150M
Coprocessor driver is under chipset/SMU/ edit smuc.inf
you may have to install quick launch to get rid of another unknown device
is it so hard to post hardware ID ? -
NOOBODY, thank you for your efforts, but i tried all versions of drivers 156.55 too, older, newer, tried to my mind everything, nothing helps
Sorry for this question, but what do you mean by saying Hardware ID? How and where to look for it?
Now i do not understand one thing: CPU-Z shows that my chipset is nForce 560, but computer finds chipset as nForce 630 , so now i do nopt understand...
Any ideas and help would be great. Problem with Coprocessor is OK now. -
I found out what is hardware iDs
So here they are:
PCI\VEN_10DE&DEV_0531&SUBSYS_30CF103C&REV_A2
PCI\VEN_10DE&DEV_0531&SUBSYS_30CF103C
PCI\VEN_10DE&DEV_0531&CC_030000
PCI\VEN_10DE&DEV_0531&CC_0300 -
Where is a good place to upload the file?
I still have my drivers I used. -
0531 is nvidia video driver, since you can not use 156.55, have to wait TheDave upload the file or www.laptopvideo2go.com server back online.
-
TheDave, please upload that file if you have it. The one for video, the link is down as he states above.
Best place to upload it...uhhhhh how big is it?
http://www.megafileupload.com/
should work, just please post the link! I think I have my laptop all set up except video!
I also have a pci device, and a unknown device in my device manager...not sure what they are though. -
Oh, I have the HP dv6636nr laptop.
-
to TheDave: would you please add to your first post
if anyone need help to get their driver straight, please post Hardware ID, INF they are working on and error code if any, just give out model number is NOT enough.
thank you again -
I was not asking for help with a specific problem, I simply posted my model number to let you all know his walkthrough works for this model as well.
All i need is the video driver he used, because the link is broken, that website is down. He mentioned he'd upload it, that is what I was hoping for. -
Working on the upload right now, hopefully be done soon. Finally DONE!
I will be sure and update the post #2 of this thread with the new link as well as post another msg at the end here for you guys.
darkanthesly: Thanks for the link to megafileupload, I had forgot what the exact site name was for a place like that. It rules that I don't have to waste a bunch of time filling out registration crap over there to just upload a file.
The file size BTW is 60MB, (120 unzipped)
Here is the link:
http://www.megafileupload.com/en/file/26949/156-72-nForce-zip.html
I will be updating post #2 with the link also. -
Dave, thank you, and I'm comfortable enough with my sexuality to tell you I love you.
And I am going to name my first son after you. -
Would either of you be able to provide the hardware id's from the device manager?
Got a hardware id for the unknown device?
-
Mr.Dave,
First i want to thank you so much, for fast and needed help.
Now everything works in 100 percent.
I want to say too: i love you TheDaveand my wife says "i let you love him because you've made to work XP on my laptotp:laugh: "
So now about Coprocessor: after install of AMD processor drivers , Coprocessor was appearing in the device list as not installed, so i had to do that manually as to my mind Noobody suggested.
It is nice to meet such a people like you Dave, wishing you luck and prosperity and of course big Christmas presents!!! Best wishes from Lithuania.
P.S. I wasn't able to find Coprocessor in the device list after it's install. -
i did some experiment about the final 0.1% work. say i get .08% of them right.
the success:
clean install windows media center edition 2005
install quick launch from HP
all the windows update, include wmp11 and MS .net 3.0 framework with security patch,
PowerDVD 5 (15MB) with MCE05 patch
DVD player in media center won't work until i installed nero 5518, i do not know the reason, maybe some kind decoder setup
or i can install powerDVD7 (200MB), then the dvd player in media center works fine, but i do not need all HD function, so i went back powerdvd5 + nero route
all the hard button on the right side and remote control works 100%
the failure:
now two more button (quick_play and DVD) on the left side is final huddle.
i download quick play from
here, create a 1028MB unpartitioned space at the end of HD, run setup, reboot, get an HAL.dll error, windows will not boot.
use the backup image, go back to MCE, run setup again then run HP sp34444, this time windows boot up as i push the dvd or QP button when my pc is off, but it go to regular windows instead of Windows XP Embedded.
i don't really think i am gonna carry around 8lb laptop as stand alone DVD player too often, so i give up this part.
the half baked solution:
on the new partition QP created, there is a folder called " AP_Pack", i copy and run them in the clean windows, the hard button (QP and DVD) on PC and on remote works wonderfully!
i upload the AP_pack (65MB) for anyone interested to try.
other thoughts:
install MCE05 is like shooting a moving target, it seem like media center, WMP and .net framework are all interconnected, i don't know which version is minimal requirement , change one thing, you get error from another AP, and newer version often take couple hundreds MB download,
to get quick play to work at stand alone partition , i may need to get old version bios, and roll back, it is too much risk and too little gain, so i gave up on that
other useful link
HP Notebook PCs - Installing QuickPlay Software
newer version of quick play
restoring HP quickplay
also this forum has couple good threads about quick play, search for it. -
I also installed MCE2005 on my DV6607NR and I still have some stuff left in my device manager even after i followed the guy, can someone tell me what hte SM Bus is and where I could find the driver for that?
-
-
XP Up & Running (99.9%) on my new dv6600 (AMD / nVidia based)
Discussion in 'HP' started by TheDave, Nov 8, 2007.