missing file (hdaprop.dll) when installing windows xp home

hi
this issue can exist with vanilla dutch, and sp1 dutch sources.
Slipstreamed to sp2, they still have svcpack.in_ which does not convert well.

SP2 dutch, and all english versions, have no issue. The svcpack.in_ in SP2 Dutch lists a few hotfixes, and the file converts well during DriverPacks streaming. (SP2 English lists a few hotfixes too... FAIK, prior to Sp2, there were no real hotfix entries in svcpack.)

Just suppose you are working with a source that was once Dutch vanilla, you can pput a good one from an English in the source, or you unpack it, convert it yourself (This can be done with notepad, actually. When you save as, look at "codering" ), then makecab it, and save a copy for later use in a goodansi folder, for instance.

For one reason or another, the uni2ansi tool in DriverPacks does not always process the file
(unproven theory.. but FAIK, it happens when a WINNT.SIF is present in the source.)

I have also seen that when the file had already been processed by me, or by Ryan's integrator, then there is no issue no more..
just my 2 cents..

Well, RVM once had an advanced option to convert to ansi, and I did that.
I then saw betas which set convert to ansi as default.
It could be that RVM in its current release does not do that by default, and I believe the advanced selection screen for this is gone.

I'll download the latest version.
since you use RVM, and it does not work.. You may have to use notepad to fix the svcpack.in_ file.

Last edited by Jaak (2008-04-06 11:14:47)

The latest RVMI 1.5.1 had that advanced option removed.

I'm not sure if the RVMI converts them automatically or not.
You could ask here: http://siginetsoftware.com/forum/showthread.php?t=299

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

Hi
Does that original OEM CD have a i386\SVCPACK folder?
It will have i386\svcpack.in_  and you could expand that, then look at it with notepad, and when you use save as, it will show what coding it currently has. If it is UNICODE, it explains the problem.

then, look at i386\svcpack.in_  in the slipstreamed source (or on the DVD you burned) and expand that.. then open the expanded svcpack.INF  in notepad.
If it reads garbage, it means the file dpsbase worked on was in unicode.

now, if the original OEM was ANSI, and the burned DVD reads garbage... some program made the file unicode before base ran.

That file should be readable and must mention 888111 for the soundpacks to work.

Last edited by Jaak (2008-04-07 06:10:11)

I'm having the same problem with hdaprop.dll and some more hdafiles after that.
This even happens when I only select the masstorage drivers (so no sounddrivers at all).

This is what I've done:

-XP SP1 CD
-Integrated SP2 and did some tweaks with nLite
-Integrated RyanVM's Dutch updatepack 2008.4 with RVM Integrator (latest version, does indeed miss the ANSI option)
-Integrated drivers with Driverpack Base (latest version)

Driverpacks Base v7.05.2 (think this was the newest I could download)
RVM Integrator 1.5.3

oh and I'm using Windows XP Pro by the way, but that shouldn't make a difference...

(btw is the quick reply box broken? cannot post smth through that)

Last edited by Lag (2008-04-17 17:31:19)