Could you please post your DPs_BASE.ini and upload the original driver that came with that motherboard? Als you could try to integrate this specific driver using nLite.

Floppy wrote:

@Bâshrat the Sneaky

You are a very patient person smile

Thanks smile Sometimes it's difficult though.... wink *sigh

Please verify that these two lines ARE present in your txtsetup.org file (which is a backup of the txtsetup.sif file).

You need it for: SATA, SCSI, RAID, all combinations and other exotic mass storage controllers.

805

(7 replies, posted in Other)

Could you please post the content of your cmdlines.txt file?

And alternatively, you could indeed add it manually to your RunOnceEx.cmd file, but then you must choose 'custom' as your Finisher Method.

806

(2 replies, posted in Site & Forum Issues And Feedback)

The MySQL server is acting laggy as of lately, but I do not see how that could result in double posts.

Thanks.

This topic is now closed.

Toolman wrote:

Actualy it explaines nothing, because NT-compression is transparant to the 'bug' in the driverpack installation ...

Well, I haven't tested it yet, but I think that command changes the permissions of that directory (and its subdirectories and files), which would cause the copy error. You're the only one with this error, and apart from that: it's useless. It would be useful however to apply that command on the %systemroot%\DriverPacks directory.

ebin25 wrote:

same results with latest release

I'm aware of that.

Yes, since recently you can disable it, but you have to do it manually. (This question has been answered two or three times the past week... I really need that online manual system now... but it's still not ready.)
Open your DPsFnshr.ini and add the following entry to the [Settings] section:

splashScreen = false

That will disable it.

I have created a complete DriverPack extraction progress program, but in the end I found that it would simply not work, because too many things have not yet loaded at that point! Perhaps one day it will come nevertheless.

Did it work out?

Warning
You will not believe this!

...

It turns out that your HWID (PCI\VEN_8086&DEV_27C0) is simply not supported by the DriverPack Sound B. That's why it's not recognized. Ok, no problem, my bad I'll fix it.... but that's not true. It's not my bad: the 5.5.0.1035 driver, of which you say that it works, simply does not support your device! From the .inf files:

iaAHCI.inf

[INTEL_HDC]
; ICH6R - 82801FR (R)
%PCI\VEN_8086&DEV_2652&CC_0106.DeviceDesc% = iaStor_Inst, PCI\VEN_8086&DEV_2652&CC_0106

; ICH6M - 82801FBM (Mobile)
%PCI\VEN_8086&DEV_2653&CC_0106.DeviceDesc% = iaStor_mobl_Inst,PCI\VEN_8086&DEV_2653&CC_0106

; ICH7R/DH - 82801GR/GH
%PCI\VEN_8086&DEV_27C1&CC_0106.DeviceDesc% = iaStor_Inst,PCI\VEN_8086&DEV_27C1&CC_0106

; ICH7M 
%PCI\VEN_8086&DEV_27C5&CC_0106.DeviceDesc% = iaStor_mobl_Inst,PCI\VEN_8086&DEV_27C5&CC_0106

[INTEL_HDC.ntamd64]
; ICH6R - 82801FR (R)
%PCI\VEN_8086&DEV_2652&CC_0106.DeviceDesc% = iaStor_Inst, PCI\VEN_8086&DEV_2652&CC_0106

; ICH7R/DH - 82801GR/GH
%PCI\VEN_8086&DEV_27C1&CC_0106.DeviceDesc% = iaStor_Inst,PCI\VEN_8086&DEV_27C1&CC_0106

istor.inf

[INTEL_HDC]
; ICH7R/DH - 82801GR/GH
%PCI\VEN_8086&DEV_27C3&CC_0104.DeviceDesc% = iaStor_Inst_RAID, PCI\VEN_8086&DEV_27C3&CC_0104

; ICH6R - 82801FR
%PCI\VEN_8086&DEV_2652&CC_0104.DeviceDesc% = iaStor_Inst_RAID, PCI\VEN_8086&DEV_2652&CC_0104

; ICH5R - 82801ER
%PCI\VEN_8086&DEV_24DF&CC_0104.DeviceDesc% = iaStor_Inst_RAID, PCI\VEN_8086&DEV_24DF&CC_0104

; ESB - 6300ESB
%PCI\VEN_8086&DEV_25B0&CC_0104.DeviceDesc% = iaStor_Inst_RAID, PCI\VEN_8086&DEV_25B0&CC_0104

[INTEL_HDC.ntamd64]
; ICH7R/DH - 82801GR/GH
%PCI\VEN_8086&DEV_27C3&CC_0104.DeviceDesc% = iaStor_Inst_RAID, PCI\VEN_8086&DEV_27C3&CC_0104

; ICH6R - 82801FR
%PCI\VEN_8086&DEV_2652&CC_0104.DeviceDesc% = iaStor_Inst_RAID, PCI\VEN_8086&DEV_2652&CC_0104

So my question to you is: does it also automatically install this driver in Windows? And not only if you force this driver thanks to textmode setup?

P.S.: your HWID is not referenced in the latest driver either!

mikelm wrote:

http://support.microsoft.com/default.as … ;de;330132


this solves not the problem it self ..

It was just in order to help you with tracking the exact cause. I cannot predict what's going wrong, especially because so far you are the only one with this issue. You need to narrow it down.

I'm sorry but I hope you can understand that at this point there really isn't much I can do.

I think it's described in MSKB330132.

I think it's described in MSKB330132.

That bug has been reported somewhere else too, but it has not yet been submitted to the bugtracker. Please do so.

Note that it's a purely aesthetical bug: the paths are referenced correctly in the registry. Will be an easy fix.

Yesterday some one else reported the exact same problem. There must be some kind of bug in the Intel drivers (there is no such thing as Seagate drivers, HDD's do not need drivers), then. Let's hope Intel updates its drivers soon!

During the 39th minute? That's impossible. the DriverPacks Finisher is only executed during the first logon, i.e. AFTER setup. Additionally, this DPsFnshr.log shows that no exceptions were applied: after filtering the exceptions, it immediately skips to KTD, because no exceptions got through the filtering stage.

Are you sure this was at T-39 of setup? And did you perhaps automate the installation of the control panel yourself? Or is this not the correct DPsFnshr.log?

This is the changelog of DriverPack Sound B 6.10:

Bugfix release.

- 0000266: [DriverPacks Finisher] Critical error: "Could not delete element from array" (BashratTheSneaky)
- 0000264: [translations] Portuguese (Brazil) translation added (gugutz)
- 0000263: [slipstreamer] when using method 1, a faulty directory structure is created (BashratTheSneaky)

Do you see any references to nLite or autologin? I don't think so. These really are the only changes, so please do not accuse me of 'quietly updating the software shows that you were not admitting a bug but nevertheless fixing it'. That's really not true.

I'm glad it's solved for you, but I really do not know then what caused this problem for you, if this update solves the problem.

And I don't have the slightest idea what that desktop.ini issue is, but one of the testers reported this too during the 6.09 testing phase. But that was only him. I don't have the slightest clue what could cause this.

Ahhh RUSUPPCK.IN_, that's all I needed to know. I'll fix that in the next version. For now you can create a dummy file in the I386 directory and name it 'RVMUPPCK.INF'. I'm afraid you'll have to reslipstream your UpdatePack now though! (Not only the file has been deleted, but also the entries in dosnet.inf and txtsetup.sif).

Please submit this issue to the bugtracker!

820

(2 replies, posted in News)

Changelog
Bugfix release.

- 0000266: [DriverPacks Finisher] Critical error: "Could not delete element from array" (BashratTheSneaky)
- 0000264: [translations] Portuguese (Brazil) translation added (gugutz)
- 0000263: [slipstreamer] when using method 1, a faulty directory structure is created (BashratTheSneaky)

Known issues
- [driver issue] installing onto an nForce 3/4/5 mass storage controller results in a BSOD
- [driver issue] installing onto a Sillicon Image SiI3112 SATALink/SATARAID results in a BSOD

Remarks
- none


Download

Apparently that's the Russian UpdatePack (thanks Google smile ), never heard of it before. That's why it isn't detected! Can you tell me which .inf it uses (RyanVM's: RVMUPPCK.INF, Sereby's: SEREPACK.INF)? That's all I need to know to fix this problem.

Are you using any UpdatePacks? That hotfix will NOT be unslipstreamed if you are using an UpdatePack. Only if you have slipstreamed it using the DriverPack Sound B.

And what exact error do you get?

Solved in DriverPack Sound B 6.10, which will be online in a couple of minutes.

I will leave this topic open for jtdoom's question to [dk], after that I'll close it.

I agree with RogueSpear.

Please do this:
1) start with original Windows XP installation files
2) add autologin
3) test it
4) slipstream the DriverPacks
5) test it

I'm sure that at step 5, everything will still work fine. It must be caused by something external.

@fejker: did you download it BEFORE October 1, 19:30 GMT? Then it's normal. The wrong source got compiled, which includes the partially rewritten though not yet complete DriverPacks Finisher - it's not yet complete so it just doesn't work wink

@[dk]: you're right. The new DriverPacks Finisher works fine according to my testers so I'll be putting the new version online very soon wink