Pre setup cmd file not found

Please update your post with the info listed in "read before you post" (rule #0) linked in my signature.

Tutorial linked in my signature.

Failure to include DPs_BASE.log automaticaly means you will recieve no support.
If you want no sarcasm, then read the rules that you had to agree to sign up.
please note rule #0. Always include your log, and DriverPacks BASE version in your title! Not done...

also from official Forum Rules and Posting Guidelines.

If you want help with the basics go to http://www.msfn.org/board/ they will hold your hand, we won't.

If you fail to read the tutorials and follow read before you post you get sarcasm or worse.

Sarcasm is not used based on a perceived level of experience, but rather for showing a lack of resourcefulness, (Did you try to help yourself?) or failing to demonstrate some effort was made to help us to help you. (omission of key details like your DPs_BASE.log)

While I agree with you that everyone must start somewhere, not everyone is lazy.
As stated in the rules MSFN is where you start.

You are expected to already be familiar with everything in this guide.
    http://unattended.msfn.org/unattended.xp/

No sarcasim was used in this post at your request .

PS Nobody could possably help you with only the meager details you have provided in your first post.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

still no log? You are quite dense

you need to learn to read.

My name and address are plastered everywhere, come on over...
If you bring your PC with you I'll fix that too, my rate is $165 per hour

Um no i never have had to ask for help, when i started in 1968 there was no one to ask.
When i worked for the phone company and we rolled out the first installs of DSL in the world not even Cisco had the answers. They said "hey when you figure it out please let us know" And I just had to figure it out myself. I have always been the one that people came to when NOBODY else could find the answers. So no, I have no sympathy for you.

Conversely everything you need is well documented.... In multiple places, all you have to do is look / read.
you obviously just want free help, and are totaly unwilling to do anything to help yourself. Including read.
We don't hold peoples hands at DriverPacks.net

Either provide the info listed in Read BEFORE you post or recieve no help, it is up to you... I'm not going to ban you.
In fact I went out of my way to help you... I even showed you where to find your answers, in spite of you not following the rules or reading the documentation.

Throw another temper tantrum if you like!

An intelligent person would simply provide the missing details and read the linked to info... (Kinda missed the main idea, didn't ya?)

PS you're right courtesy is a two way street and you neither said please or thank you...
nor did you show us any courtesy, IE you did not try to help yourself and prevent the waste of our time.
nor did you say anything nice about us or our FREE project at all
I showed you way more courtesy than you showed us... which was none. (post your log dude!)

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

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

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

It's either that OR unattended install. Don't like it? Complain to MSFT about it.
Honestly, I can't even remember when I used repair last time - and then it was just to check out what it does.
I ususally find that systems in need of repair are so much fubar that the best idea is to setup them again, clean, with all updates and drivers applied.
Works faster, too, I think, because repair is not always going ti fix things from what I've gathered so it would require some manual intervention anyway.

YMMD, of course.

Very, VERY bad idea doing it that way around!
Honestly!
The first thing you should do if you don't already own an SP3 disc: Integrate the silly SP3 before you do anything.
Best is to use nLite for this if you are going to use it anyway.
So here goes, you start up nLite, select your source (disc in drive to have it copy over to the HDD), then select integrate SP and make ISo as the only options!
That ISO you can reuse for each iteration, so back it up somewhere on your HDD.
Now you can either mount the image using Daemon Tools etc or extract it using 7-Zip etc
Im probably not the only 1 who is struggling and would appreciate your help v much. and continue with the nLite process.
Reason for this is simple:
If you remove anything before SP3, SP3 may add it again, but incomplete, resulting in errors.
Reason #2: nLite can't set stuff for things not present.
SP3 was a major overhaul and some options may only be available if SP3 has been detected by nLite.
You could also integrate the update packs using nLite - why utilize more tools than you need to?
Keeps the error probability down, too.
I am not 100% confident, as I'm not using RVM's but Sereby's, but I think even that works with nLite, too.

Good luck!

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!