DriverPacks.net Forum - DriverPacks via TXTSETUP.SIF or nlite

Re: DriverPacks via TXTSETUP.SIF or nlite

2009-08-28T03:29:30Z

phaolo wrote:

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

M2 will create a folder named "OEM" at the same level as your I386 folder (Root of the final ISO). It will also add mass storage drivers from that pack to your I386 folder and update txtsetup.sif, dosnet.inf and setup.ex_

Best of luck and welcome to DriverPacks

Re: DriverPacks via TXTSETUP.SIF or nlite

2009-08-27T22:04:47Z

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

Re: DriverPacks via TXTSETUP.SIF or nlite

2009-08-27T20:17:28Z

All driver installations happen at the same time. During XP install, this is between T-37 and T-33 (37-33 minutes remaining...).
The methods only describe how the DriverPacks are packaged.
Method 1 (original, slower) takes all the DriverPacks, then .cab compresses them before including them in your XP source. This has the benefit of being available during a repair install. Slowest of all the methods.
Method 2 keeps the DriverPacks .7z compressed, then decompresses them before the T-39 stage of install. Fastest of all the methods.

Re: DriverPacks via TXTSETUP.SIF or nlite

2009-08-27T19:10:56Z

Ok ok, I believe you! I've only asked to know
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.

Re: DriverPacks via TXTSETUP.SIF or nlite

2009-08-27T17:56:13Z

phaolo wrote:

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

No. That is what causes the conflicts Mass Storage is a real PITA...
Trust me. It has taken us years of experience to get to here, and we still struggle with it everytime we update.

The rest of the packs OMG... Not a snowballs chance in h*ll...

phaolo wrote:

Ah, another thing, I already have my RunOnceEx procedures: is Method2 + Custom ok? I'd like to launch the finisher myself.

Custom is specificaly designed to be used if you want to call the finisher yourself...

Select custom and DriverPacks BASE will not add a call to the finisher... and you can add it anywhere you like .
That is what I do myself M2+Custom

Re: DriverPacks via TXTSETUP.SIF or nlite

2009-08-27T10:30:54Z

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.

Re: DriverPacks via TXTSETUP.SIF or nlite

2009-08-27T00:38:16Z

Well, I create a copy of my source just before I add DriverPacks just for that reason

no nLite is not sophisticated enough to add all of the DriverPacks drivers...
Sorry, but it absolutely WILL fail. nLite does not have the ability to deal with conflicting drivers, and there are a bunch
(If you want to add drivers for a single machine with nLite that is NP as long as you don't add DriverPacks too.)

You can uninstall DriverPacks by selecting no packs and hitting slipstream...
Although this is not recommended, it will uninstall the DriverPacks just fine.
- AS LONG AS YOU MADE NO CHANGES AFTER YOU ADDED THE DriverPacks! -
(see first line above for recommended method.)

On most modern HDD's copying a saved copy (reverting) is faster than uninstalling

DriverPacks via TXTSETUP.SIF or nlite

2009-08-26T10:55:10Z

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?