Search options (Page 54 of 213)

Good... you started over!

We get a lot of people who download their sources from torrents nothing personal...
it is simply a matter of odds and receiving certain key phrases in response to certain questions. You were starting to "sound like" something you were not... my mistake. IE the only reason not to start over is if you can't .

If you do the things in the order / steps with the tools we recommend then you will have no issues, We get over three million downloads a week. We almost never get any reported issues, and the ones we do receive are user error. Lets face it if it is working for hundreds of thousands of users installing on millions of PC's, and an issue is only reported once the odds are hundreds of millions to one the issue is us. IE we have had over 300 million downloads in the last two years, most of those are corporate deployments (tens or hundreds of machines installed per download) and only two, non critical, bugs found. We can be pretty sure where the problem exists .

Let us know if you need any more help...

Welcome to DriverPacks, best of luck and have a great day!

Jeff

Tareek...

If DriverPacks BASE was not the last step in your process then "All else has failed" .
I did not just say "Start over" because i don't want to help you, if it were possible I would have pointed you to the documentation to do so. Since you won't accept a simple straight forward answer, let me elaborate.

DriverPacks BASE makes backups of files... when DriverPacks BASE is run a second time those backups are restored. If any changes to the source are made then the files associated with those changes are abandoned and the files are orphaned. IE (In Example) We backup txtsetup.sif, then you add something, that change then updates txtsetup (it has to), when we restore our backup of txtsetup, any changes made after DriverPacks to txtsetup are then lost when DriverPacks BASE restores the backup... and the files have no references to them anymore (abandoned). Source=FUBAR. there are several other things that occur that are similarly awful. there is no way around this issue. If you make changes after we create our backups, or if the backups are corrupted or missing, then changes can not be undone... PERIOD. I did not just say it because i don't want to help you, if it were possable i would have pointed you to the documentation.

If the backup files are missing, corrupted or modified, then even worse scenarios exist. as far as i can tell from your post those backups are missing AND changes were made after they were created. Sorry about your luck, start over from your Fry's OEM system builder XP disc, and save yourself time and mass amounts of grief.

Since / If changes were made after DriverPacks BASE was run and the backup files are missing an uninstall is not at all possable... now or in any future versions of DriverPacks BASE. Not manually not automatically not programatically.

The only way a DriverPacks BASE slipstreamed source can be updated is: IF DriverPacks BASE was the last thing done to your source.
IF DriverPacks BASE was the last thing done to your source then it can update itself 99% of the time.
- Most of the time but not always -

The only way to be absolutely certain that your source is 100% valid is to start clean, any other avenues will result in an exponential rate of probability of you having a corrupted source. Even if DriverPacks was the last step in your process a margin of error does exist.

Does your Fry's disc include the DriverPacks? If not you're home free! If so you may still have one available option... depending on whether or not it was the last step in their process...

The best thing to do is to make a backup BEFORE you run the DriverPacks slipstream. In this way you can revert to a copy of the pre DriverPacks source. Make any updates you wish and then slipstream DriverPacks to a COPY of your updated source. NEVER EVER WORK ON YOUR ORIGINAL FILES / SOURCE. That is just common sense to any experienced tech / programmer.

No new development is planned for DriverPacks BASE. It is considered a completed project, it is 7 years old and works flawlessly.
I have several bug fixes done in a nightly version and have 90% completed updates to the update checker module.
I have a few tweaks for the BartPE module planned, but for the most part BASE will only recieve bug fixes from now on.
We only had two bugs reported in the last year or two... So after my next release (soon) there will be no more planned updates or new features. ("If it ain't broke, don't fix it"). All of my efforts are to be devoted to our new tool for the integration of DriverPacks into Win7 and Vista. (I hate Vista with a passion so Vista support will be a low priority in the development)

http://unattended.msfn.org/unattended.x … 8ad63a789/
All questions answered in that guide are considered off topic for this forum . (this is posted in our rules)
Just about anything you could possibly want to know is covered either in that guide or in their forum.
DriverPacks got it's start at MSFN . Beginner level questions are appropriate at MSFN's forum. mr_smartepants and I are members there too.

DriverPacks BASE does ID your OS on the location screen... right under where the path is displayed...
validating an install disc is not a worth while task, mostly because there are so many different sources.
Three main types: Home, Professional, Media Center.
Four Service pack levels
and several distributions; Retail, MSDN, Volume License, Corporate, and an untold number of OEM provider versions like Dell, Sony, Toshiba, Compaq, HP, ETC...

Resulting in an almost infinite number of "valid" possabilities...

IE Just consider that the 3 main types to the exponent of the four SP levels (0~3) alone would be Eighty One possabilites 3^4 = 81
   take 27 to the exponent of at least 4 main distributions 81^4 = 43,046,721 ... forty three million possabilities, AT LEAST!
   Take 43 million and multiply that times the number of files on an XP install disk and the result is an insane number...
    - Let us know if you need help with that project, We will be glad to supply testers to see if your application works or not.
   If there is a Hologram on the disc, then it's a good one. that works every time, and is a lot easier.
   Or if you download it directly from MSDN, then it is a good one .
   
   not to put to fine of a point on it but if you have to wonder whether or not your source is valid, then it is not valid .

Good thinking though... It is a nice idea, it is just not something that could be implemented in a reasonable amount of time.

If I understood you correctly... Then we are glad you solved your issue

as a matter of fact there is...

It was a request from another one of you crazy sysprep dudes...

http://forum.driverpacks.net/viewtopic.php?id=2700

Implemented by me in BASE 8.09

edit the Finisher INI (DPsFnshr.ini) and add this line
DPsRootDel  = "False"

{Shhhh... it's a secret switch }

Personally i don't see much point...
after the drivers are installed it's just taking up space and fragmenting the HDD.

I did remove MakePNF from DriverPacks BASE but only in the nightly versions
that fix has not made it into an official release yet...

DON'T use KTD!
KTD uses MakePNF,
MakePNF = BOOM!

In case you haven't heard I would rather be tied to the railroad tracks in front of a speeding locomotive than use sysprep. But I digress...

Best Practice for DriverPacks with SysPrep is SAD... If i did not give a hoot about my image size at all then I would:

Open BASE Create a SAD folder Selecting only CPU and M1 this will create a valid folder structure.
Then I would extract all the remaining packs to the DriverPacks.net folder (this should extract all the packs to DriverPacks.net\D\)
Then i would copy all the files and the \D\ folder from the DriverPacks.net folder to the root of your HDD that you intend to image.
Then extract DevPath from DriverPacks BASE\bin\wnt5_x86-32\M2.7z
Then Run DevPath C:\D
- This adds the entire folder structure (all sub-folders added recursively) to the DevPath registry entry.
- Now all the drivers are available to minisetup - this is what KTD was intended to do, but doesn't .
- Verify that the first entry is still %SystemRoot%\INF in the registry - I have had reports that it goes missing .
Add a call to dp_Inst_tool.cmd somewhere... runonce, guirunonce, whatever you like.
- DP install tool will make a second pass on the machine to check for missing drivers then run the DriverPacks Finisher and finally removes the entire DriverPacks setup from the target.

If you wish to update a machines drivers at any time after the install then SAD M2 may be run from a thumbdrive, ODD or Network Share.

nice catch on the makepnf bigfoot!
make pnf is not just bad, it is awful!

Yep screwed up there I corrected DevPath to be C:\SOFTWARE\DRIVERPACKS\D

NOOOOO!!!!!!!

there is a limit to the amount of characters you can add to a registry entry!!!

your path looks like %SystemRoot%\inf;C:\SOFTWARE\DRIVERPACKS\D;C:\SOFTWARE\DRIVERPACKS\D\G\A1;C:\SOFTWARE\DRIVERPACKS\D\G\A2

when you use a path like C:\SOFTWARE\DRIVERPACKS\D\ you add 25 characters to EACH entry if you add all drivers with over 1000 folders you add an extra and unneeded 25,000 characters (on top of the existing path lenght of the packs themselves) to the registry entry which has a limit of either 16k or 64k depending on who you believe. If you exceed the limit then NO drivers are installed at all... or sometimes only the first ones that do actually fit, most times none are added if the limit is exceeded. the main packs themsleves are nearly 16k, 16k+25k=BOOM!

We see this issue quite often whe too many 3rd party DriverPack are added. (using the minimal path of c:\d\)

Always keep your path as short as humanly possible IE C:\D\ 
Why do you think we do it that way?... don't you think we would rather call it c:\DriverPacks.net\D\ ?
Ever notice that ALL the folders are one or two characters? don't you think we would rather name them like Intel or Nvidia?
there is a REASON for everything!!! - KISS method - don't change stuff until you know what it does or why it is.

Welcome to DriverPacks.net!
If i have guessed correctly based on "hardware independent Windows XP image" 
Sounds like SysPrep, Um... nope, not in the right forum...
SysPrep would belong in "Universal Imaging"
NBD its tough to figure that out, - I'll move it

We can't possably help you without you providing the requested info. (IE Read BEFORE you post AKA Rule #0)
Rule #0 was presented to you when you clicked / affirmed that you had read and agreed to our rules... you did read that right?

Since devices are installed by their HWIDs (and not by name)
you won't find anything here listed by name (since the name is not relevant)

If you wish to discover why a particular device did not install,
or if it is included, then you must provide it's HWID.
Since devices are matched to drivers by their HWIDs it is the ONLY relevant info.
to you, to us, to the device and to the driver...
Since that is not what you searched for... no surprise you found nothing
- I am quite happy about the fact that you did in fact attempt to search... well done! - most people don't.)

Also from rule #0
Can we reproduce your issue just based on the info contained in your first post?
I have no idea What OS you are using... XP OK... But is that with no SP?, SP1?, SP2?, SP3?, is that OEM, MSDN or Retail?... I suppose i might assume that you were using Professional... but you know what happens when one assumes if it is slipstreamed with a SP, or did the original disc provide the current SP level. if you did apply a SP how? Were there other patches applied to the image? If so how? manually, RVMI, nLite, Serabys, hfslip, other? What was your process? did you use OLSP? did you do a -bsmd... have you used OEMpnpPath? Did you use DriverPacks BASE? are you using SAD. have you implemented KTD? Did you read any of the other SysPrep related topics here? Did you use one of them as a guide? How exactly did you implement the packs? Which packs did you implement? What were there versions? Did you get them from us?

Basically you have not provided not one single useful bit of info for us to use to help you...

MINIMUM requirements are a DPs_BASE.log and your HWIDs (HWIDs tool in my signature)  Please read "Read BEFORE you post." AKA rule #0
Fill in the blanks... Then we will see if we can help.

Hint we have about three million downloads a week and nobody else is reporting this driver as missing, think about it for a second. Then... explain in detail what YOU did so we can figure out what you did differently than thousands of other people. . - If you want help we need details...

Here is an analogy i am really fond of... suppose I were to ask you
"Why won't my car run?"
- Not much to go on is it? (you dont even know if i have an electric car, or internal combustion)
- That is the same thing you just did to us
check out the links for HWIDs tool and read before you post in my signature
It would probably also be in your best interest to read the stickied threads in universal imaging

We will probably have to wait for an updated driver...
My best guess it that there is a bug in the sound driver that only appears with dpinst.exe and not with setup.exe.

Bigfoot made a suggestion in post 12...
you could use Vernalex Sysprep Driver scanner to add it to the sysprep OemPnPDriversPath and see if that works

if you have time check to see if there is a newer driver for that device... If so we can update the pack and see if that fixes it!
be sure to test it and make sure it works or no sense in adding it to the pack

Translation farsi

translation  persian...

what a piece of work! LOL

apparently there are LOTs of languages spoken in Iran, most of them i could not find tranlators for...
This is starting out to be the kind of fun FalconFour provided... wonder where Frodo is???

There are dozens of languages spoken in Iran. The following are the languages with the greatest number of speakers (Data from the CIA World Factbook):

    * Persian, Luri, Gilaki and Mazandarani 58%
    * Azeri and other Turkic languages 26%
    * Kurdish 9%
    * Balochi 1%
    * Arabic 1%
    * Other language which comprise the remaining 5%, include Armenian, Assyrian and Brahui, etc.
    * Total population 71,800,000(2008 est.)
http://en.wikipedia.org/wiki/Languages_of_Iran

Heads-up Muiz!!!

I added code tags for you - please edit your post to see how that is done. It makes the thread a lot easier to navigate.

I notice the folder states \XP STD SP2 but DriverPacks BASE reports XP Professional Retail with SP3 was found?

Why did you enable KTD? This is almost NEVER neccessary, was there a specific reason?

The extraction can take quite a long time depending on available RAM and the speed of your machine. IE if your VMWare shell is configured to use a small percentage of a single CPU with only 128 meg of RAM and a small swap file, then it will take seemingly forever.  It does have to extract around two gig of files from solid archives. I use VMWare 5 two CPU 512 meg of RAM and Input grabbed high and input ungrabbed normal. Extraction takes around 7 to 10 minutes. there should be a 7zip progress bar.

Did you make ANY changes after you ran DriverPacks BASE? (never do that, it may explain your initialy reported error. )
I notice presetup cmd is now being found, so the initial problem no longer exists?
- Presetup is responsible for extracting the archives, therefore it is no longer missing .
Let me know if the install failed... it seems like whatever your mistake was the first go around no longer exists.

Welcome to DriverPacks.net

Jeff

There is a limit to the number of Mass Storage drivers you may add to a sysprep image. NTFS.SYS = You exceeded it (Out of memory Error)

the finisher does not install drivers - I repeat the DriverPacks Finisher does not install drivers.
the finisher installs related software for ALREADY INSTALLED drivers...
IE if the finisher finds an ATI card it installs the ATI control panel.
If it finds a sound blaster it installs/runs the SBSetup.exe, it "Finishes" installing drivers (that are already installed) where it is required.

the finisher DOES NOT install drivers ... if it did we would have named it "installer" not "finisher" LOL

DP_Inst_Tool.cmd does install drivers