Bâshrat the Sneaky

Thanks Only one remark: it's 'RunOnceEx', not 'RunOnce'!

Maybe you're installing onto the PATA controller instead of the SATA controller of your mobo?

As for the hptmv6 problem: you should have deleted them, the hptmv6.sys entries are listed just before that. Then the rhpt3xx.sys problem: that's correct. Though both of them are reported earlier in this thread. Next time read and search before posting, please! Anyway, welcome to MSFN!

The instructions are included in the DriverPacks BASE

... and certainly not in the DriverPack General Discussion forum. Topic closed.

@Powerhouse: You can copy all of the DriverPacks just to the OEM folder, if you're using M2. Or to $OEM$\$1 if you're using M3. EXCEPTION: DP MassStorage: there are new entries for this one, you'll have to complete the slipstream process for this one again. You NEVER have to start all over again. Unless your disc is messed up of course @eben: hmm... please retry, with nothing but the DriverPacks. Strange... @digitalfrost: I'll investigate that one when my exams are finished @2forza: it IS a fix! djbe doesn't have the time to update Fedit ATM, he's also having his finals! @gilesw: that's already fixed. Though it hasn't been put online yet. @Siginet: you did NOT name it 'cmdlines_fix.exe', I did. It still was named 'cmdlines.exe'. I chose that name, because it was appropriate. Most people wouldn't even notice it, as it gets deleted and is only required during the slipstream process... as you said!

@mickmack: these are supported now No need for that driver! @gilesw: the driver in the DriverPack IS signed... @swgreed: this is the latest official XP MCE release, which is older than the regular XP: 71.84 VS 71.89. As you know, I stick to the latest official driver

It's been delayed because of a lack of time

Fixed all these. I wonder how that lonely 'hptmv6' entry got there

@cybpsych: that's a bug, it should be removed. Fixed in the next version. @2forza: it's not required. (PS: it's written by Siginet (it's a small compiled AutoIt script) and that means the icon choice depends on him. Maybe if you ask him kindly ) @midiboy: I'm aware of that. I just didn't have the time. That will follow in the next update

The update is less than 24 hours online and an update is already required: nVidia has updated their nForce 4 Chipset standalone driver to 7.12. Update will follow. @gilesw: I'll check it.

DriverPack MassStorage V5.07.3 Supported devices. Changelog: V5.07.3 (28 Jul 05) -New: support for VMware SCSI controller. -Updated: Intel SATA RAID drivers from 03/09/2005,5.0.0.1032 to 06/17/2005,5.1.0.1022. V5.07.2 (25 Jul 05) -New: support for Adaptec Embedded Serial ATA HostRAID Controller. -Updated: AMD IDE controllers from 07/01/2003,8.2.2.2 to 01/18/2005,8.2.8.0. -Updated: nVidia nForce 4 AMD Edition mass storrage controllers drivers from 02/11/2005,5.10.2600.0518 [5.18] to 05/17/2005,5.10.2600.0534 [5.34]. -Updated: Silicon Image SiI 3124 SATALink Controller driver from 12/12/2003, 1.0.0.7 to 12/15/2004, 1.3.0.14. -Updated: VIA SATA RAID controller driver from 09/24/2004, 5.1.2600.430 [430C] to 04/08/2005, 5.1.2600.430 [430G] (null update). V5.07.1 (06 Jul 05) -Updated: Silicon Image SiI 3112/3512 (non-RAID) from 10/10/2003, 1.1.0.53 to 06/14/2004, 1.2.0.57. V5.07(03 Jul 05) -New: support for nVidia nForce 4 Intel Edition mass storage controllers. -Updated: Intel SATA RAID drivers from 12/17/2004,4.7.0.6815 to 03/09/2005,5.0.0.1032. -Updated: nVidia nForce mass storage controllers drivers from 02/11/2005,5.10.2600.0518 [5.18] to 05/26/2005,5.10.2600.0535 [5.35]. Download

DriverPack LAN V5.07.3 Supported devices. Changelog: V5.07.3 (25 Jul 05) -New: support for AMD-8111 HyperTransport I/O hub 10/100 Ethernet. -Updated: nVidia nForce Ethernet (nForce 1/2 & nForce 3/4) drivers: since nVidia nForce 4 AMD driver update 6.66 the nVidia nForce 4 AMD & Intel Edition are identical. Therefor the old nVidia nForce 4 AMD Edition Ethernet driver has been removed, the other one has been kept. V5.07.2 (14 Jul 05) -Updated: Marvell Yukon LAN controller driver from 06/24/2005, 8.30.3.3 to 06/27/2005, 8.32.2.3. V5.07.1 (08 Jul 05) -Updated: Marvell Yukon LAN controller driver from 05/06/2005, 8.27.4.3 to 06/24/2005, 8.30.3.3. V5.07 (03 Jul 05) -New: added support for nVidia nForce ethernet (Intel). -Updated: Marvell Yukon LAN controller driver from 04/28/2005, 8.27.3.3 to 05/06/2005, 8.27.4.3. -Updated: SiS 190 & SiS 191 LAN controllers driver from 02/18/2005,2.0.1039.1030 [1.03b] to 05/24/2005,2.0.1039.1040 [1.04]. Download

DriverPack Graphics B V5.07 Supported devices. Changelog: V5.07 (08 Jul 05) -New: support for VIA/S3G P4M800/CE UniChrome Integrated Graphics (P4M800) onboard graphics. -Updated: Intel Graphics 82852/82855 GM/GME, 82865G, 82915G/GV/910GL, 915GM/GMS, 910GML, 82945G from 04/05/2005,6.14.10.4299 [14.12] to 06/08/2005,6.14.10.4332 [14.14]. -Updated: VIA/S3G K8M800 integrated graphics (K8M800) driver from 03/12/2005, 6.14.10.0214 to 05/17/2005, 6.14.10.0223. -Updated: VIA/S3G PM880, PM800, CN400 UniChrome integrated graphics (CN400 PM800 PM880) driver from 09/23/2004, 6.14.10.0178 to 02/24/2005, 6.14.10.0211. -Updated: XGI Volari V8 from 09/20/2004,6.14.10.1060 [1.06] to 02/02/2005,6.14.10.1080 [1.08]. -Updated: XGI Volari V3 from 11/16/2004,6.14.01.1100 [1.10] to 01/11/2005,6.14.01.1120 [1.12]. Download

BTS DriverPack Graphics A V5.06 Supported devices. Changelog: V5.06 (12 Jun 05) -New: ATI Radeon Mobility support! (at last!) (complete ATI Radeon Mobility support, not only the X700 and X800 support that's been added recently!) -Updated: ATI Radeon drivers from 03/22/2005, 6.14.10.6525 [5.4] to 05/12/2005, 6.14.10.6542 [5.6] Download

DriverPack Chipset V5.07.2 Supported devices. Changelog: V5.07.2 (25 Jul 05) -New: support for ALL AMD chipset drivers. -Updated: ATI IGP drivers from 5.6 to 5.7. -Updated: ALi/ULi chipsets drivers from 2.096 to 2.0964 -Updated: nVidia nForce 1, 2, 3, 4, 4 Intel Edition drivers from 5.10, 6.53, 7.13 to 5.10, 6.66, 7.13 (null update). V5.07.1 (11 Jul 05) -Updated: ALi/ULi chipsets drivers from 2.0.9.5 to 2.0.9.6. -Updated: Intel Chipsets drivers from 7.0.0.1025 to 7.0.0.1030. V5.07 (05 Jul 05) -New: support for ATK0110 ACPI utility (found on many ASUS motherboards: ACPI controller). -New: support for ITE CIR (Consumer InfraRed remote control). -New: support for VIA IR (InfraRed). -Updated: VIA Hyperion 'mach' driver from 10/02/2002,5.1.00.0230 to 10/02/2002,5.1.00.0240. Download

The label is called PU instead of CPU. ← Thanks! Will fix it this noon, when I get home from my exam latin. (If I can manage to access my pc ) I still have to update the updating mechanism, at the side of my website at least. I didn't have the time to do that yesterday evening. Also that will updated this noon.

For those who've already downloaded it BEFORE this post: redownload it or copy the Methods_V506.7z of the current download. A small fix regarding Siginet's cmdlines_fix.exe has been implemented in the new download.

BTS DriverPacks BASE V5.06 Supported devices. Changelog: V5.06 (12 Jun 05) -Fixed: [DPB] RUN_ME.cmd: when you had slipstreamed RyanVM's UpdatePack 1.2 or higher and then slipstreamed some DriverPacks, but NOT DriverPack Sound A, the KB888111 hotfix files would be removed, while their entries in the txtsetup.sif and dosnet.inf would be kept. The result was an error during setup. -Fixed: [DPB] RUN_ME.cmd: BTS_DPs_autocopy.cmd wouldn't be called, because of a typo. -Fixed: [DPB] RUN_ME.cmd: if you choose to use RunOnceEx for the finishing batch file, it wasn't listed as the first one. (Thanks, Siginet!) -Fixed: [DPB] BTS_DPs_M3.cmd: the DriverPacks (in their 7-zipped form) were kept at %SystemDrive%. -Fxied: [DPB] BTS_DPs_M3.cmd: some unexplainable idiotic bug: just after the DriverPacks were extracted, they would be deleted... -Fixed: [DPB] BTS_DPs_finish.cmd, KtD: ending the WatchDriverSigningPolicy.exe process didn't work because of a typo. -Updated: [DPB] 7za.exe from 4.18b to 4.20 -Fixed: [DPC] RUN_ME.cmd, M3: if you're using DriverPack Chipset, Intel's .inf files wouldn't be copied to $OEM$\$$\inf. -Fixed: [DPSA] RUN_ME.cmd: it's possible that in some cases you had multiple entries of the KB888111 files in your txtsetup.sif and dosnet.inf. Download Known issues -Bug|non-critical: [DPB] all methods: in winnt.sif: if a section is being updated with new and/or updated entries, it will add a new section if the cases of the sectionname aren't identical. -To-do [DPB]: update the html files with links to one for DriverPack CPU, as well as a page for it... -To-do [DPM]: the Promise misery... making a driver of myself would be the only 'easy' and 'painless' way to solve it. REMARK: I had no time to test it extensively! And I didn't have the time to open the other dp topics... for tomorrow

This seems to be correct.... Fixed that right away. Will be fixed in V5.06!

Still working on it. It makes things - the least what you could say - more complicated. As this is a commonly known fact, the Promise drivers are ONE BIG MISERY. Though I've just noticed (some of you might have noticed this earlier) that NONE of them is signed in a valid way. So my solution is simple in theory, quite hard in the reality: I'll put all of them together in ONE huge driver. But I'll release first the current DriverPacks as they are, because that is some huge job... Might take some time untill it's finished.

@bernl: ok thanks. The more specific HWIDs, the better! @theutlass: on which mobo are you using it? Could you please post also your HWID? That might help in the future. @berni: so changing the order makes the difference for you? Are you VERY sure about that?

Hmm.... two possibilities: case a: you messed up something, whether it is manually, whether you did something with nLite or... case b: this really IS a bug. If this is the case, I need the HWID of your VT8237 Controller!

[offtopic] RETROROMANIAN? What kind of language is that? Some sort of ... 'neo-latin'? [/offtopic] @OliverMaltby: is it solved now or..?

Then please post your HWIDs!