you said yourself that it worked

this is a built in function of DriverPacks BASE

added MS Office and other important softwares in it.

mentioned tweak worked very fine, after ADDing and as well as UPDATE all previous drivers, EVEN 2nd time around . so, even if, some new person, have the similar problem, should be able to figure out what needs to be done, if they read this thread/page, as i've tried to write in details . worked for my case at least .

wish there were some thorough guide to Add/Upgrade DriverPacks at least manually, even 2nd time or any time ... for multiple reasons, like, as many cannot keep all the stages of their own previous disc(s) modifications what they have done in their life, in their same computer, or with them, all the time, or those who don't want to spend time on modifying what was already done once, and do those again & again.

~ Tareek . 2010-Mar-30,00:42,U-08:00.

@ overflow / jeff ... thanks, nothing but good wishes for you, your projects.

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

in a later post/comment i told mr_smartepants that i have an OEM SysBldr XP and i will make ANOTHER installation out of it.

these are two different thing.

most likely the DP packs those i've integrated, did not have VMWare display drivers in it, so VMWare SVGA display adapter wasnt gettin detected inside VMWare VM.

so now installing on a real machine.

SysBldr-XP-CD have hologram seal on it . it was sealed in a yellow envelop.

IT CAME FROM MICROSOFT TO FRY'S.

i have even seen the postal details of it.

i was vey happy with it, as it reduced the time of installing those separately.
made many spin-off from that too.
i took pic with my phone, can upload or send as attachment to u, if u want to, but not public post.

SysBldr XP CD doesn't have any winnt.sif ! but has txtsetup.sif & dosnet.sif . it doesnt have any references to nLite or Driverpacks, i think MS manually upgraded this . but 1 thing i noticed though, in txtsetup.sif structure that, many sections often have few emty lines in it ! ... just like what i've seen in the txtsetup.sif that was modified by the DPBase . nLite modification 1 stage before the DP integration, didnt place empty lines in the same sections.

as you elaborately & mr_smartepants adviced ... i have already started to work on building a new installation from that SysBldr-XP-CD . many thanks again, for all the pointers, to both of you, and your helpful articles .
and above all ... for being patient with me.

its just a standard MS OEM XP home SP3 slipstreamed source...

Exactly as it should be.  That's how I receive mine.  The system-builder OEM disc is a single-use license.  The license can't be broadly deployed like the SLP-OEM license can.  Once used, the license is tied to the hardware and can't be transfered.  Those discs only come with WMP9/IE6 integrated.
If he got it from Fry's, then maybe it was in Fry's parking lot...

its just a standard MS OEM XP home SP3 slipstreamed source...
I am begining to think the worst... if you know what i mean.
(he has no original source to revert to / pie rat)

also we have not gotten the full story from him yet...
http://www.msfn.org/board/topic/142719- … _p__914648

i bought OEM system builder XP disc its pre-integrated with SP3, WMP11, DirectX 9.0c from Fry's.

That's impossible!  MS doesn't distribute discs with those contents.  If Fry's is selling discs like that, then Fry's is breaking the rules too by redistributing modified discs.
If Fry's modified the contents, then legally Fry's must also support them, not MS.  That's how I interpret the System-builder OEM license.
Can you post a photo of the disc?  Is it hologramed?  I'd be VERY curious to see what they did to it.

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.

Future DPBase version will be made to work with an installation files at any stage ? so that DriverPacks can be integrated, upgraded or undo ?

the problem is changes were made after DriverPacks was added.
- It is plastered all over our site "Do NOT make changes after you add DriverPacks". "DriverPacks must be the last step in your process."
Failure to observe this caution results in an unrecoverable source.

The fix is to start over with a clean source... A copy from before DriverPack MassStorage was added. (Before step #2)
Best Practice =  Start over "Clean" by copying your original hologramed XP disc to HDD... Work from there.