Bâshrat the Sneaky

@Ghostrider: you're a Multi-Boot CD/DVD user, I cannot predict what you have in the root of your disc. Win51 however is not present at all discs, so that's why I've changed it into that. I've mentioned it in the Multi-Boot tutorial clearly:

dammnnnn... I'll fix it ASAP... EDIT: it seems I do NOT have that error in my version??? I 7zipped the WRONG VERSION /me slaps himself in the face. EDIT2: attached the correct version (2 hours difference since last change, I forgot to update the one in my release folder...) EDIT3: fixed file removed. Use V5.04.6 of the DPs BASE instead. It includes more fixes and improvements.

Ehm... you have the .7z file, right? Well, then you have to put it in the 'DriverPacks' folder of the DriverPacks BASE... That's it... Run the batch files and your DriverPack will be slipstreamed

I'll add them EDIT: topic closed.

You can slipstream it or you can install it as a regular app. The choice is up to you

... and to which controller is that HDD attached? I thought it had 2 controllers: a VIA and a SiI one. EDIT: try this (probably it will be this): open your txtsetup.sif and search this line: PCI\VEN_1106&DEV_3149= "viasraid" and change it to: PCI\VEN_1106&DEV_3149= "viamraid" I'm very curious... Note that will only make any difference if the HDD is connected to the VIA controller

The viaSSSSraid driver is used for the hwid that ends with 3149... Check your TXTSETUP.SIF It should work flawlessy. But I asked you to CHANGE it to viaMMMMraid, just to test. (compatibilty issues) EDIT: it should be txtsetup.sif instead of winnt.sif

It might help if the both of you would post on what hardware setup you're trying to install

Cool wallpaper I didn't expect you to be Dutch... (when I saw your nicknames)

Well... that's 'theoretic coding' or something I guess

You're totally missing something You'll have to edit the txtsetup.sif and dosnet.inf and drvindex.inf accordingly AND put the file in the I386 directory BUT drvindex and dosnet.inf are already edited by my DPs BASE, as I said earlier, I included another version of the ulsata driver. However, if I were you, I'd copy your file in the I386 folder, preferably in CABbed form, especially delete my file. If you've done that, open the txtsetup.sif file and search for 'ulsata', untill you get to the hardwareids. Compare those to the ones in your .inf file and if they're the same you're set. If they're different, overwrite them using the ones from your .inf file!

The alliide.sys error is a known bug. It doesn't occur for everyone though... Please check the I386 folder and tell me IF you have the file or not. It's slipstreaming and how could that give trouble? Please try RyanVMs marvellous updatepacks, they're really easy in use, certainly in combination with nLite. A virtual machine can NOT be used for driver testing!!! You will have to test it on a real life machine! However, for all other installations it's perfect to test. I'd recommend VMware, it's alot faster than VPC (couldn't believe it myself at first, but it's true ).

Probably that's the problem... It *used* to be an unproperly extracted SFX archive, now it's this... But the question is: how can we solve it? CRAP I just typed here an entire explanation why this could NOT be the cause, untill I had to look in the .cmd file for details. Then I noticed that it COULD be caused the way you said Check this: START /WAIT %C%CR\CTZAPXX.exe /S START %C%CR\CR.exe -y -o%S% Two possible solutions: START %C%CR\CTZAPXX.exe /S START %C%CR\CR.exe -y -o%S% or START /WAIT%C%CR\CR.exe -y -o%S% START %C%CR\CTZAPXX.exe /S I think the second one is the best.

@crosis23: I'm afraid you didn't read the tutorial quite right... If you want to add MassStorage drivers that have to be used at textmode setup, you'll have to do more than just collecting your drivers and making a DriverPack of them... I DID integrate the ulsata driver, but it's possible that your motherboard is not yet supported by the driver I used. Maybe there's a newer one at ASUS' site - I'll check that out tomorrow. About the DPs BASE that ran perfectly: 1) it's ultra.sys that was being removed and 2) it's ran perfectly, but in fact the driver you added isn't slipstreamed correctly - at least not if you want to use it at textmode setup, as I said earlier. Driver.cab is 5.25 MB???? Then you must have nLited your CD/DVD! Driver.cab isn't touched by the DPs BASE Please try the new V5.04.5 of the DPs BASE, it *might* be solved then. Thank you for the compliment

@erik_demon: I'm like ONE minute to early with posting this new version I guess... P.S.: just out of curiosity: what's in DP Erik? Err 1: don't know how to solve it. Note that I added it to ForceCopyDriverCabFiles Err 2: is already fixed in new version 5.04.5 Err 3: yes, and I've reproduced it a long time ago, fixed it. I don't get that error anymore. Please tell me which command is wrong...

BTS DriverPacks BASE V5.04.5 Download

eh.... HUH? Can't help you with that one...

Don't forget that you have to import regtweaks at T-12 if you want them to be applied to ALL users!

@celo: yip that one is working! But I want to ask you a favor... First test it with everything default. If that works, please redo the test, but change this entry in the txtsetup.sif file PCI\VEN_1106&DEV_3149= "viasraid" to PCI\VEN_1106&DEV_3149= "viamraid" and let me then know if it still works. I REALLY need you to do this!

@tchuyev: that last problem can easily be solved: just disable the SiI controller while installing Windows XP

@Toolman: that won't make the difference... It must be something else.... @Ghostrider: let's say 1 time method 1 with all DPs uses 250 MB. If you use method 1 five times, the space used on the CD/DVD will still only be 250 MB...

I'm quite curious for the results of this poll Half a year ago or so I did the same, method 1 did win. But back then method 2 still gave some troubles, so I wonder if method 1 will still win? Personally I prefer method 2!

The ForceWare 74.90 are not yet official afaik. I guess they're available for download at guru3d as always? And it took so long for the 5.3 Catalysts because I had exams.

celo, please tell me which mobo you have.

I knew this was going to be tricked, but I never expected this Nice find