Ah, thank you for the useful info.
M2+Custom seems perfect.
Bye for now smile

Ok ok, I believe you! I've only asked to know smile
Anyway, I don't imagine how you can survive new driver testing.. I go crazy with just program installers!  +_+


I'll add other 2 questions:

-when does the Method2 installation happen exactly? Automatically at the "F6 screen" or where?

-what file\folders will DriverPacks create on the iso? The previously tested Method1 added a $1 folder with many drive subdirectories.

Thank you for the answer, but what about the manual integration in txtsetup.sif?
Can that manage driver conflicts?

Anyway, before using DriverPacks I'll do a copy of the source as you suggest.
Ah, another thing, I already have my RunOnceEx procedures: is Method2 + Custom ok? I'd like to launch the finisher myself.

Hello,
I'm using DriverPacks to integrate MassStorage drivers after Nlite configuration.
The two programs, however, are not very confortable to use together and the "no-more-integration" rule after DriverPacks is a terrible limitation.

I hope this is not blasphemy for the project, but.. is there a way to translate DriverPacks to a nlite readable process?
Otherwise, is it possible to enable a manual integration via TXTSETUP.SIF starting from the pack?