Bâshrat the Sneaky

Which ones are that? Besides the nForce 2 mobo's. EDIT: topic moved to DriverPack MassStorage subforum.

So what changes did you make to your txtsetup.sif? Or did I overlook that post? :s And as I said, it's NORMAL that the standard Windows drivers are used for the nForce2 Ultra controller!

Search before posting. Download the DriverPacks BASE, open the readme and thou shall find! Topic closed.

sw nVidia drivers? You mean the 'SW IDE' aka 'IDE' drivers? That's just the old name for the nvatabus.sys driver So it IS included.... P.S.: an nForce 2 Ultra is exactly what I've got here: it gets detected as a plain old IDE device: it uses the generic IDE drivers of Windows at text-mode setup, after Windows has been installed, the nForce 2 PATA driver will get installed!

hehe original topic title The selection of the driver indeed depends upon the HWID, and I can set that in the txtsetup.sif file. Only *I* have to take note of compatibility issues, while you can simply erase all but yours if you want to...

Seems to be correct. Will be fixed in the next version, but this is of course not critical.

Please do the following: -reslipstream SP4 in your Windows 2000 -slipstream the mraid35x & 3wareDrv100.sys driver using nLite's SATA/RAID slipstream module -report back: no errors anymore or... Those 2 problems should be impossible to solve for me. And both should support Windows 2000 without any hiccup... EDIT: forgot to say: never seen somebody with this problem. And topic moved to DriverPack MassStorage.

1. in theory only Windows XP is supported, though in reality most drivers support both 2K & XP 2. I don't have any experience with ghost images so I cannot help you.

Aha well it seems you're using method 2. You should have told me that in the question! And... the entries you quoted there, are the only ones you need for method 2 .

Oh crap forgot to reply. Those chipset drivers are already included (And it's indeed the .zip file you pointed at.) Those JMicron drivers are on my todo list now.

hehe... Please let us know.

Are you using RunOnceEx to clean things up? Or is there a cleanup included in the install\batch.bat batch file?

This should work just fine :s

For DriverPack LAN, depending on what method you are using: NO CHANGES to any files except for driver installation method related things. If you don't know what's that all about, this overview might help you. EDIT: moved to DriverPack General Discussion.

It will recover the back-upped versions of dosnet.inf, drvindex.inf, txtsetup.sif & winnt.sif. So YES, it will overwrite your settings. Topic moved to DriverPacks General Discussion. EDIT: I see you have to rerun everything because of the updated DriverPack Sound? Well this one can just be copied, replacing the old one. Note that this is NOT the case for every update! EDIT: @JuMz: please update your signature; it's in violation with this board's rules: the maximum is FOUR lines! EDIT: this question has been added to the DriverPacks FAQ

Thanks for that tip, Alanoll But everything is running flawless now

GOD BLESS YOU :thumbsup: And... **** those are stupid mistakes!!! A lame excuse, but it must be the 450 lines in one day that made me overlook it :| Thanks P.S.: it DID work now

Hi, first of all I'd like to thank Wraith for such a versatile utility! But I seem to have some (beginner?) troubles with it. I've configuredmy include-Items.xml (see the attachment), and my include-StdConfig.xml (also attached). There are 2 main possibilities I think, that may be causing all this: 1) I've included variables, but also variables that use variables. I don't know if this is causing the problems. 2) I was trying to use an include-Items.xml (I know I can rename it...) WITH the 'configs' entry in the 'item' tag, while I was using GFXinstall. But when I retried with SelectInstall, it didn't work neither! So here are my .xml files you need to find my problem. (no registration information is included) Thanks in advance! include_Items.xml include_StdConfig.xml XPlode.xml

IMPOSSIBLE I've assigned your HWID to the si3112 controller only... Please ATTACH your txtsetup.sif file.

Aaaaaaaaarrrrgggghhhhhh I'm sick of it. I'm going to call nVidia EDIT: I'd still like to hear the voice of some nForce 4 JBOD & RAID users!

It's fixed in the new DriverPacks BASE indeed

Good luck, XPero & SiMoNsAyS! Two of the greatest designers together... that MUST have success! The update has been posted: http://www.msfn.org/comments.php?shownews=13964 P.S.: thanks, XPero

Download link is fixed.

DriverPack Sound A V5.08 Supported devices. Changelog: V5.08 (31 Jul 05) -Fixed: nVidia nForce APU's control panel archive was missing. Download

BTS DriverPacks BASE V5.08.1 Changelog: V5.08.1 (13 Aug 05) -Fixed: [DPB]: M1 : winnt.sif: the OemPnPDriversPath would not get written to the winnt.sif file because of an error in the syntax of the Fedit call. -Fixed: [DPB]: M2, KtD: winnt.sif: the Driver Signing Policy disabling entries in the winnt.sif would not get written because of an error in the syntax of the Fedit call. -Fixed: [DPM]: all methods: because of a typo, the wrong nvraid.sys driver would be compressed & copied to the I386 folder. By fixing this, the NVRAID problem might be fixed again. V5.08 (07 Aug 05) -Updated: [DPB]: Fedit.exe: from 1.2.2.3 to 2.0.0.0. Thanks again, djbe! -Removed: [DPB]: cmdlines_fix.exe: thanks to Fedit 2's new functions, this fix is no longer needed! (I want to thank you again, Siginet, for this very handy fix!) -Fixed: [DPB]: all methods: winnt.sif: if a section was being updated with new and/or updated entries, a new section would be added if the cases of the sectionnames weren't identical. -Fixed: [DPB]: all methods, KtD: the temporary files of the DriverPacks slipstreamer were not deleted afeter completing the slipstream process. Download (temporary offline) download (temporary direct download) nVidia nForce mass storage users: please retry ***again*** with this version! nForce 4 AMD mass storage controller RAID 1 reported to work! Known issues -Bug|critical: [DPM]: nVidia nForce mass storage controllers: hopefully solved in this version. -To-do [DPB]: add an option to enable KtD for certain DriverPacks only. -To-do [DPM]: the Promise misery... making a driver of myself would be the only 'easy' and 'painless' way to solve it. 50% complete now.