Bâshrat the Sneaky

Check the article in uAwiki.

Other: me. If you build it yourself, you know it's done well and it gives you the ability to choose all your components and buy them at the lowest price.

Gelukkige verjaardag, Martin

If you guys can wait 2 hours or so, you'll get a new version

You should START the installer/setup, but not finish/proceed it. You can derive the type of installer simply by looking at it in most cases. Other possibilities: right-click it and look in its properties or extract it and see what kind of files you get (e.g. data1.cab, data2.cab, data1.hdr, etc identifies an InstallShield setup) or looking at its extension: some MSI installers have as file extension .msi.

@Chertoianov: that should be fixed in the next update of DriverPack Sound. Probably your HWID is just not yet supported in the curent version of the Realtek AC'97 sound driver! @newsposter: are you sure you didn't enable the KtD option? (Keep the Drivers)

We need more voters!

Strange... it should have been working! To be sure, I added your revision to the HWID, please try again with DriverPacks BASE V5.07.5, which should be online in a matter of hours.

The easiest solution is to slipstream everything again and choose to delete the drivers this time. (No need to worry, the DriverPacks BASE handles the removal of the previous DriverPacks )

Hehe... Just choose RunOnceEx as installation method (The last settings you can enter when executing RUN_ME.cmd)

Note that some drivers might not work properly if you only include them that way. (i.e. drivers that include 'filter' drivers, these are only installed AFTER textmode setup and will not work during textmode setup. So if you only include the mass storage drivers for the textmode part - using that method - it *might* not work properly after Setup has completed.) But yes, that's also possible. In the example below I assume that you are NOT using an unattended Windows disc. 1) Slipstream DriverPack MassStorage like you would always do it, use method 1 (easiest in this case). 2) Navigate to the I386 directory and DELETE the winnt.sif file. 3) Find the $OEM$ directory (next to the I386 directory) and delete it. 4) That's it.

GuiRunOnce, RunOnceEx: check the guide. Keep the Drivers: keep the drivers AFTER the installation is complete => keep the drivers forever. It might indeed be fixable if you ATTACH your HWIDs. Check my sig for a tool to do that.

Please ATTACH your HWIDs. Check my sig for a tool to do that.

It's still present in the copy_sys_files_to_temp.cmd. Shouldn't it be removed from there as well? ← ****... that's correct. New update is coming!

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. Download

BTS DriverPacks BASE V5.07.5 Changelog: V5.07.5 (28 Jul 05) -Fixed: [DPB]: KtD, M2: fixed the annoying Driver Signign Policy popups. -Fixed: [DPM]: slipstream_DPM.cmd: nvcchflt.sys entries for dosnet.inf were still added. -Fixed: [DPM]: slipstream_DPM.cmd: nVidia nForce drivers failed to install during textmode setup. 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 [DPM]: the Promise misery... making a driver of myself would be the only 'easy' and 'painless' way to solve it.

Check my previous post again, I just edited it.

Then I know the cause... you have SPACES in your path... EDIT: now I see what you did wrong: you should copy THE CONTENTS of the UWXPCD_ROOT folder, not the folder itself!

In general, Windows 2000 & Windows XP drivers are compatible or even identical. Some drivers even support Windows (Server) 2003. But there is NO driver that is compatible with MSDOS AND Win 9x AND Win 2k AND Win XP...

The quotes are correct, that's for sure. So you used method 1... and everything did get copied... well then it should work IMO! But then again... I don't have any experience with network installations, so I can't make it hard... Users with network installation experience, please give us a hand!

Did you place the DriverPacks in the 'DriverPacks' folder? You should NOT decompress them. Which DriverPacks are you using?

Ok . but problem in this: I can install and AHCI and RAID my mb support it!!! As i understand then DP checks HWID and recognize that can apply and RAID and AHCI and do it Am i wrong? Maybe the way to open iastor and delete all strigs exclude SATA AHCI ? Later today i post my HWID (mmm where i can find it?) ← It *should* work just fine as it is now. This problem has been solved a long long time ago (though not in a galaxy far far away LOL). Please check my signature for a small tool that gives you your HWIDs

OK, grrrreat

Very strange story, penetreerbeer (BTW... fantastic nickname LOL). Well I have to say I did NOT modify the nVidia ForceWare drivers in any way, so I have not the least clue on how to solve this problem. Google also doesn't report any problems. So maybe another reinstall may not have that problem? Do you overclock your GPU, through software, BIOS, Vmod or ...?

That would NOT work through a network install, I think. I'm not very sure... I've never been in the ability to do a network install. (lack of PC's )