Search options (Page 102 of 213)

I am not aware of any coupon or known discount...
It certainly would not hurt either one of us to mention we that refered you to them!

Perhaps you could be the first of many to recive a coupon or discount

- It never hurts to ask!

Best of luck to you.

Doh... One should not code when one is tired

KTD is not the way to go for many reasons all of which SAD is the answer for.

Lets use your scenario for an example  network card replacement
The tech is at the PC (self installing cards are still years away )
two possabilities exist have ODD or not.
if ODD is present drop SAD Disc in and run.
if ODD is unavaliable a SAD folder could have been left on the drive at install (KTD).
    a SAD M2 Folder weighs in at like 320 MB for the main packs,
    Physx and Language packs are 100 MB more if needed.

With a KTD setup the drivers take almost 2 GB...
and the driver will likely not install properly
- this is a result of the way KTD was designed, it has a few flaws.
- These flaws are addressed with SAD

Here is some related INFO it outlines SAD as a full replacement for KTD
Useing an M1 source for SAD gives you all the functionality of the MS DPInst.exe and the DriverPacks Finisher at the click of a button

Leaving the SAD M1 folder on the machine when it is loaded will provide BETTER than KTD results.
http://forum.driverpacks.net/viewtopic. … 710#p29710

hint
Install M1 with base
  (make sure you turn on QSC so you only have to cab them once )
edit the Finisher INI (DPsFnshr.ini) and add this line
DPsRootDel  = "false"
  this is very important because the finisher will then not delete the folders - (and we have KTD)

the simplest solution is to execute the single move that windows normaly would.

move %SYSTEMDRIVE%\$win_nt$.~ls\$OEM$\$1 to %SYSTEMDRIVE% and call it a day

a "move" should happen quickly enough it's not a "copy"
Then DriverPacks should continue normaly without further issues...

this would be accomplished by adding one line near the top of presetup

REM +==========================================================================+

If exist "%systemroot%\system32\setupold.exe" DEL /F "%systemroot%\system32\setupold.exe"
start /wait move /y "%SYSTEMDRIVE%\$win_nt$.~ls\$OEM$\$1\." to "%SYSTEMDRIVE%\"

REM +==========================================================================+

It might not be a bad idea
to force people to the overview page to get to the Slipstream button (or even the credits page )

But I tend to think of things in terms of "What is the least number of "clicks" neccessary".

We could then make the argument that reviewing the summary page should be a requirement.

If you then wanted to change one thing you could go there from the tree and back. That would really only add one additional click so... I don't see it as a show stopper if implemented.

I'll keep an open mind on this, and we'll see what people think

what if i am useing teh same config everytime? like i do. i just open base and hit the button
Or for people who only want to change one thing, then hit the button. They can go straight two the page they want, change the one thing and hit slipstream... ?

you did not tell us what you did... so i will assume you used KTD

KTD is not neccessary. dont use it, if you must use it then tell us why and we will see what can be done.

Thanks for keeping us in the loop!

the error is because the packs folder structure and ini are not correct.
the files need to be in a subfolder like [1] or something
IE D\CPU\1\

and the INI updated to reflect a proper folder structure

IE

[DriverPack]
platform	= "wnt5_x86-32"
name		= "CPU"
rootDir		= "D\CPU"
; OPTIONAL
classes		= "System"
driverCount	=
decompSize	=
compSize	=


[1]
; REQUIRED
exc_count		= 1
; OPTIONAL
exc_1_tagFiles	= 0
exc_1_+hwids	= 1
exc_1_+hwid1	= "ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_35"
exc_1_-hwids	= 0
exc_1_+infFiles	= 0
exc_1_-infFiles	= 0
exc_1_commands	= 1
exc_1_command1	= "%SystemDrive%\pmtimer.exe"

Since the odds are one in a thousand you will actually need this driver it is not much of a problem.

I agree... RogueSpear is a hero. We will miss him greatly.
I really love the Tab for driverpacks with all the selections on one page.
Code... did somebody say code... hmmm

You can not successfully add DriverPacks with nLite. This is plastered everywhere on this forum...
Some lunatics have even attempted to argue the point, they of course just learned the same thing the hard way.
If you could add the packs with nLite then we would not need to bother with providing DriverPacks BASE

After you have done all your changes with nLite and only creating the ISO remains.
All your changes are complete - only then - run DriverPacks BASE add the driverpacks and create the ISO.
Make no changes to your files after DriverPacks... If you make changes after DriverPacks you will create problems.

This is outlined in great detail in the tutorial... This also covered in every forum at DriverPacks.net

I admit the tutorial is a little old... but every thing there is still valid.
Some of the newer features have not been documented yet
but you don't need them for what you wish to do.

I would create a copy of the source folder after you are done making your changes.
Then add DriverPacks to the copy of the source.
in this way if you need to make changes you can fall back to the pre DriverPacks source and make a new copy
Make your changes to the copy
add DriverPacks last
create ISO.
  - DriverPacks can be uninstalled from DriverPacks BASE (select no packs and hit slipstream) but the above method is better still.

Before you Post please take the time to read "Read BEFORE you post" in my signature below.
Please note the format and minimum requirements / info we need.
Please take the time to Search the forum, RTFM, and the FAQ and stickied topics in forums related to your issue.
I have a dollar that says your queston (any driverpacks related question) has already been answered somewhere here at the DriverPacks.net forum.

Slipstream is the update of the original OS's installation files.

if you SlipStream XP SP2 with SP3 then the result of the sliptream is XP SP3.

you now have a windows XP source that was "upgraded" or "slipstreamed" with SP3.

SlipStreaming is a term used to describe the process of replacing files in the windows installation with newer versions of the existing files.

I hope that helps!

Jeff