Just a silly post-integration question

Hi,
welcome to DriverPacks.

I will assume you made the ISO bootable, and that would make the DISC you made from it bootable as well.
If you just want to look at how it works for you, you could install Vitual PC 2007 from Microsoft, and let it run setup from that ISO you made. (When it finishes, do not activate that install..)

But, you will want to use it on real hardware and to do that you run setup from that disc.
You made a selection of drivers BEFORE you integrated.
Windows setup will use those added drivers and should find your hardware by its own sweet self now.

I wished we could say there will never be problems with driver conflicts, but we do try to avoid conflicts when we build the DriverPacks archives.

When you look at supported device links in the overview page, you are able to tell what is in it, and then you select the packs you want.

You should also know you can modify the content of the archives and repack them with a new higher version number.

For instance, at the moment I am working on WLAN because it needs some pruning.
The current release is DP_WLAN_wnt5_x86-32_712.7z
WLAN does not have an INI..

I let 7zip unpack it .. so it created a new folder wich has the name of the PACK..
Then I renamed that folder by changing the number to a higher number.
it was still January, so that became DP_WLAN_wnt5_x86-32_801forpruning.7z

(you can see I also added forpruning, which immediately tells me this is not a released pack..)
I pruned some 72 doubles.
This pack has NO INI, so when I use 7zip, I Hit F2 on the folder, CTRL-C to copy the name of folder, and then I select the D folder to zip it up.
I CTRL-V pasted DP_WLAN_wnt5_x86-32_801forpruning.7z into the name field, and then changed 801 into 802.
Viola, I have a new WLAN I can test.

Mass storage is a special pack.
It has an INI.
when you discover that a particular driver creates a problem for you, you can edit the pack.
You use 7zip to unzip it into a folder.
Rename it, and give that new folder a higher version name
An example, 802 (year/month) becomes 8021 (year/month/revision).
And if it was 8021 to begin with it would change to 8022.

what can you do now? You can edit that INI.
When you remove INI sections and leave the folder intact, there is a high probability that everything works after you repack the INI and D folder.
BUT, when you remove a folder, you had better also edit the INI and delete the corresponding section.
If you remove D\M\D2 then you search for section [D2] in the INI.
Please delete the section if you removed the folder.
(By the way, [D2] contains that wretched LSI_SAS.EXE which is case sensitive in suprising ways.)
We fixed the issue for server 2003, but it still acts up for windows 2000? It is a SERVER 2000/2003 driver.. Can I disable it for windows 2000 and expect it to work in Server 2000?)

I will briefly mention that in Mass storage you could edit INI to disable a driver.
you could paste
ms_1_exc_disableIfOS="w2k"
at the bottom of the [D2] section.

another alternative is that you change
[D2]
ms_count=1
into
[D2]
ms_count=0

(zero disables the section, but leaves the driver intact for PnP.)

After you do the edits and/or pruning in that new mass storage folder you use 7zip to repack..
You select the D folder and INI file, and rightclick to use 7zip on selection.
It will automatically suggest the name of the folder, which was already renamed to higher version..
settings for 7zip are Ultra/LZMA/compact.
(look at RAM usage.. The new version of 7zip is not going to let you use almost two Giga while packing it up.. )Viola..

===========================
Chipset is another special case.
It has no visible INI.
BUT. A CRITICAL error can happen if you modify CHIPSET (reduce it), and it can happen whether you use QSC or not.
A few folders were hardcoded in the method one slipstream module, and if you touch the affected folders, whammo, you get a CRIT.

==================
Sound and graphics have INI as well, and the creators know how difficult these packs are.
The INI sections are ESSENTIAL to all sound and graphics drivers they was written for.
Without them, they will not properly install.
-------

when you repack you must include the edited INI.
btw, you should NEVER change the INI's name.
in 7zip, we use ULTRA compression,LZMA, and COMPACT.
I read somewhere that not using COMPACT can be an issue with repacked DriverPacks.

Thanks very much, guys, for this inforrmation/tutorial. Really, the work performed is tremendous!
I'm gonna give it a try. As I understood, and following your post OverFlow, I should be able to put all the drivers in my XP installation CD. If there's not enough space, I think I saw somewhere a post to put all the drivers on a dedicated CD that XP will recognize when installing.
Thanks again!