Search options (Page 93 of 213)

then why didn't it work?   you tell me...

I already know why
because backup files existed in your supposedly clean source.
if it was a clean source then the backups would not exist...
if they did not exist they could not be used to restore...

IE txtsetup.sif cant be restored if its backup is not found...
If the backup is not found that will throw an error in DriverPacks BASE too...
Base knows if it has previously been run on a source and expects to find its backups if it has.

so i know you made changes to a source that you had previously run DriverPacks on
- it's THE ONLY WAY lines could be removed from txtsetup.sif by DriverPacks BASE
since restoring a backup is the only way BASE will remove lines from txtsetup then you could not have possably started with a clean source...
Since I know changes were made to your source after you ran base the first time then you absolutely have orphaned files in your source and probably more corruption yet to be discovered.

clean source means copy from OEM MS CD and start CLEAN... you absolutely have not done this, I can tell just by the results you are getting.

Thanks a million for the excellent details, trouble shooting, testing and the link

it's a perfect post sir!

you win the DriverPacks hero of the day award!

and since you seem comfortable with the packs testing team access seems to be in order too.

given the fact that many many drivers share common names and have internal references to those names.

you would need a good hex editor and about 6 months of testing and a few hundred available testers...
until the updates came out for those drivers... then you would be back to square one. many of the most popular drivers are released monthly... so you could never keep up with the workload.

it is likely that after you hex edited the driver and related support files many of the drivers would simply fail to function as expected... signing is required to install many drivers your method will absolutely break signing so many more of your drivers would fail on signing issues. so now we have the set that cannot be edited (leaving you with choose one driver or another not both) and then anything that insisted on signing could simply not be included so you would loose 20 to 30 percent of your drivers right out of the chute... the remaining 80 percent would likely be unstable if hacked. A hacked driver would certainly not be eligible for any type of support.

So I will repeat myself you can have limited success on a limited range of hardware very limited.

I will not say it is not possable
- because it is possable
- It would take so much time and effort to deal with it that windows 8 would be out before it was done...

there is NO PRACTICAL WAY to make this work... sorry

I like the idea... really it is good thinking - it just won't be a good thing.

Perhaps if you tell us why you want this then we can offer you a better (more viable) solution than this

the DriverPacks BASE tutorial for the DriverPacks is in my signature...

Basic Q&A about drivers and OS install is here http://unattended.msfn.org/unattended.xp/

Please find and use the Search feature of our forum...

Please read the sticky posts in this forum...
Especialy the very first one at the top... 

Thread closed
- demerit awarded

It is a shame that people will have to pay more for a decent OS than for a basic PC...

yes finisher creates and deletes %SystemDrive%\tmp.

this folder is not part of a normal windows installation.
if you have specified this folder in your build thien it will be deleted by the finisher.
Use a different name (Temp) or
create it after the finisher runs or...

We have been useing this folder for the finisher for 5 years with no complaints
there are some other issues as well
the spaces i put in for readability are not parsed well in win2k command shell
there is an extra command  & %%i
-> @ IF Exist "%%i:\$OEM$\$1\D\"   SET "DPLoc=%%i:\$OEM$\$1" & Set "M=1" & %%i

the Tool is / was designed to be a template / example
It is to be replaced with a more proper executable in the next release of DriverPacks BASE

http://forum.driverpacks.net/viewtopic.php?id=71
- [beta] - Option for install by HWIDs tool or dp_inst_tool
  - Add GUI for Driver selection menu
  - convert two (three) tools to a single classier and proper EXE
      the script / tutorial dp_inst_tool has outlived it's usefulness

There is a newer tool that extracts from the DriverPacks only drivers that match teh HWID on the target machine. (Released only to testing team members)

There has been interest in a GUI for attended installs for some time    http://forum.driverpacks.net/viewtopic.php?id=2075

So the new EXE will have a GUI to select/deslect individual DriverPacks with a timeout default feature
and option to do a HWIDS specific extraction from the DriverPacks
and the existing dp_inst_tool functionality.

WarmSnow also has an advanced tool for doing this...
http://forum.driverpacks.net/viewtopic.php?id=2403
and Jaws too
http://forum.driverpacks.net/viewtopic.php?id=2936
General discussion about goal of tool
http://forum.driverpacks.net/viewtopic.php?id=2751
Please have a look around our forum.

Thanks for submitting your observations and your version to our audience.

Have a great day

Jeff

you could use runonce to call a simple autoit script that will launch word then click next and then close word.

Discussions of how to circumvent WGA ect... are normaly against the rules.
since this is clearly a corporate deployment issue we will allow a limited amount of leeway as long as the discussion does not lead to circumventing WGA / Activation Wizard...

yes we will make sure the driver is added to DriverPack MassStorage...

I assume you will be willing to test a nightly for us?

Thanks for reporting your issue - it makes DriverPacks better for everyone!

What is your HWID? (tool in my signature)

perhaps the model number of your MB...
perhaps a vague hint as to your process...
or some remote clue as to what the result was...
did you use DriverPacks BASE? what version?
What packs did you use? (versions and names)
you said your pack - Did you make your own Driver Pack???
how did you use them?
are you installing from and ODD or RIS?
are you installing windows 2000, Windows XP, or Windows 2003 server.
What service pack of that OS are you installing. did you slipstream the SP or is it original.
Is it an unattended install?
do you have a DPs_BASE.log or an DPsFnshr.log or a setupapi.log?  where are they?
did you use any tools other than nLite on your source?

If you need help then you need to help us to help you...
if you cant even tell us what you did or provide simple and basic details then I will simply close this thread.

not being good at English is one thing, and I certainly have no problem with someone not being good at English.
You must however at least attempt to tell us important details about your issue.

This is DriverPacks.net not the Psychic.network

read the rules
(please note that putting [Help me] in the title is specifically forbidden)
Please read the Link in my signature "Read BEFORE you post"
if you will use that guide it will save us both time and grief...

We want to help...
Do you want to be helped? Step up to the plate and do your part

This site is for the support of the DriverPacks
I have not even seen ANY info yet that would even remotely suggest you have ever even used the DriverPacks or DriverPacks BASE

Thanks for reporting!

You have helped us to help you!
Look for your bug / fix to be in our next release!

We like that

Jeff

then why do you need our help?