Hello.

As many want, I'd like to integrate sata drives into my custom Xp dvd too.

I've already found the msfn guide about it but I'm wondering:

what does Vista use for being able to completely avoid driver setup unlike Xp? Isn't possible to slipstream the same drivers for the most used brands? Which ones?

Isn't there a generic standard sata driver usable for all?

I've found a site "DriverPacks" that offers collections for download.

Is that safe and is a good idea to slipstream those?

Driver Packs is a good place to start. That being said I must say that using the SATA Drivers for your particular Motherboard is best. Ya know the one on the disk you got with your mobo, unless you have a Dell, HP or any other brand that you don't get an actual install disk. I slipstreamed them in with all the others using nlite, and haven't had a problem with the SATA drive at all.

Ah thank you ExTruckie. I'll check DriverPacks mass storage collection (only 6 mb!).

The idea is to integrate base sata drivers so I'll be able to use my dvd on many systems without extra..floppies (lol).

I'll see if I can slipstream the drivers with the nlite option

Follow the tutorial at the driverpack site. Nlite will not install the driver packs. There is a utility built into Driverpack DB that does all that. Check it out brfore you try to add the driver pack.

Edited January 10, 200917 yr by ExTruckie

Ah yes, I'm just reading that I'll have to use the DriverPack Base program.

Anyway I think that Nlite can't istall it because all .ini files have been removed from each drive folder and put together in the first file.

That is bad as I don't like very much to mix methods

Uh the mass storage pack shouldn' cause conflicts if I install better drivers in the future, right? (like updates, more correct versions, chipset, ecc)

The driver packs themselves will be updated every time you use the DriverPackDB. Just remake your dvd every few months and you'll be fine. Also all the unused driver installed will just take up a little space, but will not cause any problems. In actually the drivers that change the most are the multimedia ones, ie: video and sound card, and video changes a few times a year.

If I can't avoid Base program, what is the correct order of operations?

Is this ok:

1-start with fresh copy (better specify lol)

2-slipstream SP3 with nlite

3-add a custom manual entry in TXTSETUP.SIF (I have to)

4-integrate Driverpacks with Base program

5-integrate KB patches with nlite

6-do rest of nlite operations till the final ISO is created

No conflicts or overwriting, right?

Driverpacks ALWAYS go last before making ISO.

You mean this right?

1-start with fresh copy

2-slipstream SP3 with nlite

3-add a custom manual entry in TXTSETUP.SIF

4-integrate KB patches with nlite

5-integrate Driverpacks with Base program

6-do rest of nlite operations till the final ISO is created

Or you mean that Driverpacks is never before nlite?

5-do rest of nlite operations

6-integrate Driverpacks with Base program

7-create final ISO (I'll use another program then as I always get problems when restarting with nlite at that point)

p.s: uh interesting the wpi! Is it some kind of advanced runonceex with choice?

Edited January 11, 200917 yr by phaolo

You mean this right?

5-do rest of nlite operations

6-integrate Driverpacks with Base program

7-create final ISO (I'll use another program then as I always get problems when restarting with nlite at that point)

p.s: uh interesting the wpi! Is it some kind of advanced runonceex with choice?

This one is correct. Run and close Nlite and then run Driverpacks Base.

p.s: uh interesting the wpi! Is it some kind of advanced runonceex with choice?

Effectively, yes. It has it's own subforum here (under member contributed projects).

Ok, thank you ExTruckie and the others for the help

I'll try DriverPacks, then I'll check WPI to make a new configurable dvd

Mm..what's the best method to use for DriverPacks integration?

I've selected the first to avoid copying files to the hdisk, but now I'm not so sure of the choice..

What does the second method create exactly?

Unfortunately I won't be able to try the installed drivers until I buy a new pc with satas..

EDIT:

Ouch.. method 1 seems to start together with runonceex..that's BAD

It also copies the folder called D on main drive and creates some dirs inside I386

Edited January 14, 200917 yr by phaolo

You mean this right?

5-do rest of nlite operations

6-integrate Driverpacks with Base program

7-create final ISO (I'll use another program then as I always get problems when restarting with nlite at that point)

p.s: uh interesting the wpi! Is it some kind of advanced runonceex with choice?

This one is correct. Run and close Nlite and then run Driverpacks Base.

guys, what program you use to make bootable ISO after integrating Driverpacks?