DriverPacks.net Forum - [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-23T14:26:15Z

A workaround for the "Microsoft UAA Bus Driver for High Definition Audio" - error popup during setup is integrating Serebys update pack (german) as described here:
http://forum.driverpacks.net/viewtopic. … 1000#p1000

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-20T13:08:34Z

@ruudboek
@Bashrat

I can confirm that SVCPACK.IN_ is broken after the slipstream process. The unpacked SVCPACK.INI contains nonsense.
I use the german Version of WinXP pro.
Unfortunately replacing the broken SVCPACK.IN_ does not solve the Problem for me.

I replaced the broken one with this one (in compressed form):

[Version]
Signature="$Windows NT$"
MajorVersion=5
MinorVersion=1
BuildNumber=2600
[SetupData]
CatalogSubDir="\i386\SVCPACK"
[ProductCatalogsToInstall]
KB888111.CAT
KB913425.CAT
KB883667.CAT
[SetupHotfixesToRun]

But still the "Microsoft UAA Bus Driver for High Definition Audio" - error pops up during setup...Argh....

Any further hints what could solve this problem?

Greetz,

Rockbow

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-11T22:05:44Z

@Bashrat,

ok, i have just sent it to your gmail account.

Ruud

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-09T17:49:49Z

What's the file encoding for your original SVCPACK.IN_? Please send it to me so I can try to reproduce and fix this.

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-07T21:41:08Z

@Bashrat,

Ok, i solved this problem.
First i tried the installation with the Dutch version of the KB888111 without success.
After that i had a look at SVCPACK.IN_.
I extracted the SVCPACK.IN_ and opened the resulting SVCPACK.INF.
To my suprise i noticed that the contents of SVCPACK.INF was the following:

??????????????????

Then i extracted the SVCPACK.IN_ from my my original XP folder and opened the SVCPACK.INF.
This was the original contents:

[Version]
Signature="$Windows NT$"
[SetupData]
CatalogSubDir="i386\hotfixes"
[ProductCatalogsToInstall]
[SetupHotfixesToRun]

Apparently the slipstream of the driverpacks corrupted my SVCPACK.IN_
After replacing the corrupted SVCPACK.IN_ with the one from my working US based unattended XP CD the problem was solved, no Microsoft UAA Bus Driver for High Definition Audio" error popped up and sound was functioning.

Ruud

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-07T20:01:27Z

It's language independant. Or at least that's what I've been told. I think the other languages will only affect the name of the device in the device manager and the registry imports it does (which I do NOT apply, since they're not necessary).

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-06T21:08:53Z

That's not true, you can find a 51.2 mb KB888111 hotfix package right here :

http://support.asus.com/download/downlo … ;model=W3V

If you extract it, you will see a list of folders representing different languages.
The dutch kb888111xpsp2.exe is under the folder NL.

Ruud

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-06T20:57:52Z

afaik KB888111 hotfix is language independant and exists only in english language.

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-06T20:36:05Z

@Bashrat,

can you tell me with what tool you cabbed the KB888111 hotfix? I can then try to cab the Dutch version of the KB888111 and try the installation with that.

Ruud

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-06T16:52:00Z

Could the problem be that the KB888111 hotfix is english and not dutch?

Ruud

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-05T20:56:25Z

I've already posted this on a previous post. I notice a bit of a discrepancy in how Sneaky's HDA hotfix works. I too use my own through third party and integrate through nlite. DPBase detects this and thus will not apply HDA. However, I tried slipstreaming vanilla and Bashrat's HDA hotfix is superior to what I have. I have since suggested to Bashrat if he can force HDA slipstreaming as it is complete and actually works.

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-05T20:28:43Z

Wel i presume the next version of the driverpack Base is 6.0.6, i have tried it, but i am also still getting the same error on my dutch windows xp ("Microsoft UAA Bus Driver for High Definition Audio" is left as "PCI Device" with !-mark after unattended install).
I posted the error earlier in this topic :

http://forum.driverpacks.net/viewtopic.php?pid=625#p625

Ruud

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-02T21:43:03Z

Problem 3 is solved in the next DriverPacks BASE!

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-01T22:33:39Z

WOW. Yes on the DPs_fnsh.cmd. Still there.

Re: [SOLVED] 6.05.2 problems: KTD, Finishing, HD Audio, popups, CMDOW.EXE

2006-06-01T22:29:21Z

BÃ¢shrat the Sneaky wrote:

Problems 1+2 were fixed in 6.05.2

I have to disagree on this. Because I did extract DPs_fnsh.cmd manually from archive and it's old version..? DPs_BASE_6052.exe, 1317691 bytes, md5sum 44f4da9f89f7ad91d860715c2adafbd5. This contains bin\finish.7z, 29.5.2006 23:10, 596407 bytes, md5sum 599bcd78f4378f036238a877afe647d1. Finish.7z contains DPs_fnsh.cmd, 29.5.2006 21:17, 12492 bytes, md5sum be45d65e63800e07516027dfb96a7d18. Open DPs_fnsh.cmd in editor and problem is still there: "IF %CDDRIVE%==: GOTO KTD_M1". CDDRIVE is not set previously -> ERROR. I've downloaded DPs_BASE_6052.exe multiple times so it's not due broken proxy on ISP or anything like that. Could you verify that one on server is proper version? Even tried another ISP in another country!

BÃ¢shrat the Sneaky wrote:

Problem 3 is not related to the HDA fix (KB888111). I don't know what device that is though. Will look it up later.

I'm going to disagree on this one too . PCI IDs of device lacking driver matches one in INF included on KB888111 and slipstreamed to I386 by DP base. Reinstalling driver for it then properly detects it's HDA bus and installs drivers - asking for media which it shouldn't do (problem 4).

BÃ¢shrat the Sneaky wrote:

The .log file SHOULD stay by the way

Moving it to %WINDIR% might make things bit cleaner? Doesn't matter for me tho.

laura wrote:

About problem No.4. Maybe he is talking about HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion key SourcePath ?

CurrentVersion\Setup\SourcePath. Yep. That's the one I meant. I still need to check exactly what's set on registry. Anyway Windows prompts for missing file while it's present in C:\Windows\System32\drivers and in D:\I386. Path it suggests is just "D:" which is obviously incorrect. Of course this might be just some Windows oddity and not DP problem at all.

I'll look into these later myself (unless Bashrat fixes everything before that which seems quite likely based on amount of changes he's done lately )