'Changed (for shorter paths)'
Woo hoo!
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
'Changed (for shorter paths)'
Woo hoo!
http://forum.driverpacks.net/viewtopic. … 348#p33348
Related post above...
please join our discussion there
Welcome to DriverPacks!
that is what DriverPacks BASE does... no sense in duplicating features of the main app in an add-on .
careful what you wish for. lol
in the FAQ section http://forum.driverpacks.net/viewtopic.php?id=2461
in the /DriverPacks BASE folder/Docs/DriverPack_reference_wnt5_x86-32.ini
just ask if you need me!
wow... at first i thought you were going to say you were digging that hole LOL!
Glad you're back online
Slipstreaming the textmode MassStorage only covers the TEXTMODE part, you also need to leave the OEM folder with MassStorage Drivers so the WINDOWS drivers get installed.
Don't remove the OEM folder and all should work fine.
This is good advise... you will in many/most instances also need the PnP drivers...
so load mass text and regular mass
Trying the nightly or even an older mass storage pack is also good...
here is a couple of related posts from the testing team forum...
I think what happens is;
1- We try to add a devpath entry over 1MB
2- The 'add reg' fails and 'nothing' is put in as the path value, IE the devpath reg value is blank, empty, "", Null.![]()
Since no device path is set then windows setup only installs the included windows drivers... continueing normaly
(except none of the DriverPacks have been searched)this can be tested by extracting a set of packs that is known to fail...
1- Manually run devpath on the extracted packs
2- Checking the registry
why not simply implentanting a 2 step Driverpack Installation into Base
First Step: extracts all DP's but installs only MainDP's (only MainDP's Paths into Registry)
Second Step: after setup, before finisher, execute all 3rdDP's?So we can save a lot of Space in the Reg for the expanding MainDP's.
Sorry if it's a stupid idea ;-)
that can be done too...
use DriverPacks BASE for main packs and call SAD for the 3rd party DriverPacks...
However i wish to know if my postulate is correct first
PS no it is not a stupid idea. It is an excellent idea
.
Please tell me if my postulate is correct using the method described above (if you have a moment).
Jeff
Add DriverPacks as it is supposed to be added and you will have no problems...
(the method you are using is not supported, nor will it work...)
see the tutorial in my signature
Welcome to DriverPacks
moved to the PE forum...
I am beginning to belive we have exceeded the max size allowed for a registry entry in windows XP...
working on verifying this now... (I belive the max size for a single reg entry is one megabyte)
sorry we have had no feedback on this...
mr_smartepants fix should be valid... (but the alps pad is not a video driver so don't look for it to be added )
You could post your results to save someone else who may wander in here
By Helping with the packs you are in the best possible situation to make sure they are as you like them ... (shrugs)
PS. has anybody seen SamLab lately? beginning to worry about him
future.siginet?
Why don't you help me with the packs?
I only have 2 hands and not to much time.
Agreed... Teamwork is the key let's work together
Outstanding!
In general, I have the feeling that driverpacks development/updates are far to slow to really be very useful. Usually if a new driver comes out, integrating that into a new pack should not take more than 5 minutes (just replace the driver inside, expand the driver files, create a new pack by script, bingo).
At least for the Vista/W7 driverpacks that should be the case. It is probably much more complicated for XP, I know.
ROFL - So should I add you to the NT6 team now?
I agree...
They have diliberately made scripting the process a manageable thing.
That's Good for some one who can script .
there will also be an audience for a GUI
- Sure it is a smaller audience because scripting dism it is not as daunting as what was needed for nt5.
Siginet has always been big on scripts and plugins, DriverPacks has an API mode too..
I'm sure it will be a great alternative to writing scripts... thinking... perhaps it would generate scripts !
1) Do DriverPacks replace old/default drivers supplied with WinXP disk? If yes, is it possible to remove default drivers with nLite first and then add DriverPacks? If not, does it mean that DriverPacks install together with default drivers?
For the most part no... most drivers included with windows have not been updated since they were included . There are a few that are included because they were neccessary for certain reasons. Don't ever delete the included drivers with nLite or other method.
2) How can I get more info on DriverPacks? I can see there are several Graphics (and Sound) driverpacks (A & B) and no matter which one I choose, I can see ATI and nVidia drivers inside both packs... Which one should I choose?
Graphics A is Gaming Graphics B is Business (Quadro vs GeForce) C is the older drivers (Catchall) and are considered unlikely to ever be updated again / archive. Like Voodoo graphics drivers.
2) I use an all-in-one .NET installer merged using info found at MSFN forums. It contains all versions of dotnet up to 3.5 SP1 and installs through RunOnceEx (it's actually the first soft in the ROE list followed by other software). So, if I choose to install DP graphics pack for ATI or nVidia and want respective panels installed together with drivers, which method of integration should I choose - GuiRunOnce (winnt.sif) or ROE?
Why are there two "2)"s in your post???
Both will likely fail... .net needs to be installed before the ATI control panel... a reboot is a good idea too. .net idealy would be installed prior to GUI mode setup... IE in WinPE mode setup like from svcpack.inf . most all in one packs will not install from svcpack setup... some will... I install roguespears .net2 from WinPE for just that reason. I then install the rest of teh .net packages from GUI mode
. You can do this many ways that are all correct... i offerd how i do it only as a single example of at least one way that does work. Everyone here likely does it differently except that we all install .net before we run the DriverPacks Finisher.
Welcome to DriverPacks. Excellent questions.
umm...
what is the difference between a Ford truck and a Toyota truck?
what is the difference between Solaris and red hat?
difference between red and green? (they are both colors ain't they - Duh)
OT questions are not appreciated, I don't see where you were having DL trouble.
Nor that you had any other DriverPacks related comments for that matter.
Google 7zip and look it up, we are not your mom and are not going to hold your little hand. LOL
read this forums rules - especially posting guidelines
if you can't find http://www.7-zip.org/ and read their home page on your own you don't need to be here. (your not ready)
Once again, if it works for muiz it must work for the rest of the world ...
Sorry but I am doing my own W7 driverpacks now because yours do not work for me ...
Hey if you are feeling generous you can Post them on the nightly server and we will get them tested and released for everyone
We are listening...
Good things are on the horizon, fear not...
Wim, myself, siginet, mr_smartepants, Muiz, and some other well known players are planning to develop a tool collaboratively, even more so than RVMIntegrator / Driverpacks / Autoimage were in the past. (Yes Wim is going to have some time for us again)
Please post your observations (good or bad) here - We're listening intently.
-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
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...
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
Welcome to DriverPacks lararefaeli
LOL
lararefaeli, That issue was marked [Solved] over a year and a half ago
But thanks for playing!
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.net Forum » Posts by OverFlow
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.285 seconds, 5 queries executed ]