windows xp on dv5t - all drivers installed

[Roamin]

My guess is that all the latest hp notebook come with AHCI always on. You cannot turn it off in bios, hence why you need files like ahcix86 to actually install windows xp.

I do not have a eSata drive , so i cannot test it.

Grats on the mute light.

[Roamin]

On a side note , for the remote , i have noticed that if i try different drivers (or maybe it was quicklaunch buttons) there comes a point where even when i uninstall the drivers , my remote doesn't have full functionnality. Also my 360 remote loses recognition even with drivers uninstalled. So my perfect fix is install a fresh xp , and never update the CIR drivers. In that case all the buttons work (with some registering "unset" in VLC) . I am still hunting down what would be registry keys for the media keys.

So fresh xp install , never update the remote drivers.

[Roamin]

For the IDT drivers, i think both packs were the same , but i think sp41398's installer might have problems, because for me it just wont install stacsv.

[fun2sh]

My IDT Audio Codec is also : 5.10.6087.0

I have uploaded the exact package i use to install the audio (a merge between 2 driver sets i found around the web) It uses 1040et_ses.rar for audio codec and sp41398 for stacsv.exe (WDM folder)

here is the package for idt audio drivers :

http://www.mediafire.com/download.php?mht2nj32dgz

xyzabxx : what is your exact model number for dv5?

edit: nvm found your model in another post , cant seem to find product specifications for that model though .. try those drivers and the registry keys, works for me every time.

Roamin,

After I tried the audio drivers from swsetup directory that came with the Lappy , I tried your this package as well. In both cases audio works but there is question mark on "Audio device on high definition Audio bus" and mute button is also orange after applying registry patch.

I also tries IDT driver pack from realtek site but still the same.

[fun2sh]

And YEh stacsv is loaded after the rboot

[xyzabcxx]

fun, this "Audio device on high definition Audio bus" probably is the Nidia HDMI driver. You can find it in swsetup\drivers\video.

if you are using the one from Roamin, then the IDT driver should be fine. Most likely it is the registry file that is not correct. Read muchas thread carefully.

[Roamin]

and you have added both keys in the registry ? they keys in controlset and the keys in software\IDT ?

Try to dump both registry and post them here , i will check them.

Again, im in #notebookreview.com on EFNET if you have questions.

[Roamin]

Here is a quick and crappy video of the mute button in action on windows xp :
width="425" height="344">


And fun: Yes i'm pretty sure that the Audio device with the ! in your case is the HDMI audio driver (to carry audio on your hdmi port).

What you want to see installed is in "Sound, video and game controllers" of the device manager , and it is "IDT High Definition Audio CODEC"




Notice the ATI HDMI Audio , thats the second High definition audio hardware, and the CIR Receiver, which was never installed after a format, the only way so far to get a 100% working remote.

[Roamin]

I have been making good progress on the remote to work with drivers. First of all, here is the drivers is used :

http://www.versiontracker.com/dyn/moreinfo/win/163230

I posted those on earlier pages , but maybe they went by unnoticed. Anyways , there is a crucial difference to me when i install the XP32 drivers from the link i just posted , or if i install the windows vista drivers like many of us did. Just run the dpinst.exe from the winxp32 folder. The difference is that the windows xp drivers detect extra hardware , and installs many HID devices, which are needed to get the remote to actually do anything.

Here is the bad driver for vista :




And here is what the device manager looks like after the winxp drivers :




Notice that everything installs by itself except the HID Keyboard Device that you need to specify from the "Dont search i will choose driver to install" If you install it has a HID compliant device , your remote will lose up,down arrows and a few more keys.

So with the correct xp drivers installed, install eventghost http://www.eventghost.org and add the HID plugins as follows :










Also add the other HID devices.




Once all the plugins are inserted (they are not all needed , at least for my remote , the second HID compliant adds nothing) Just press buttons on your remote and you will see in the log on the side buttons which i named in red like this :





You can add a keyboard plugin and see when you press up, down arrows on your remote.

There is a file , c:\windows\inf\input.inf that has keys that can be remapped , which are related to the remote. I need more time looking around to figure out if these will affect the remote or not.

What i understand from eventghost is that it is like there is nothing treating the HID commands received by our remotes in windows. Does this mean we are missing a service or some sort of event handler that will monitor all the HID compliant devices and respond accordingly? Or are the drivers only seeing input when we enable them with eventghost? I really think they are always working and nothing is checking their state.

Anyways, our remote works , just that events aren't triggered in windows. I'd like to know why they were assigned to keys before we install drivers , and they no longer are when you install them.

I have noticed that the HID compliant devices are directly tied with specific keys on the remote like the green button , quick play, dvd and the display key. Play/Pause being alone in the last HID device. Inside input.inf you can see remotes installed. Much more info from the input.inf file from this site :

http://www.promixis.com/forums/showthread.php?p=132780

[chubrk24]

Where do I find the drivers for the ATI HDMI Audio? Please help.