Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

c:\windows\system32\presetup.cmd file not found

- - - - -

  • Please log in to reply
8 replies to this topic

#1
captainamer71

captainamer71
  • Member
  • 9 posts
  • Joined 19-February 05
Ok I followed the directions exactly inside Installation_Instructions.htm which came with what I downloaded with the latest release. I did IT exactly. I used Nlite BUT nothing was removed on put in a unattended install. and before I slipstream the driver packs it installs with out any problems and runs fine. In virtual pc 2004 that is.

But once I slipstream the driver packs in using either method 1 or 2 it will not install and I get this.

"C:\windows\system32\presetup.cmd file not found
C:\windows\system32\setuporg.exe file not found

cause

Presetup.cmd not in i386 uxpcd
setuporg.exe no in i386 uxpcd

check txtsetup.sif in i386 folder"

This comes up after the system rebooted for first time after the winxp logo and right before it shows up that it is installing. in the light blue screen.

I have started over from scratch 6 times and tried each thing I can come up with. And I searched on here and the nlite forum. and I can not find anything for the last two days that has todo with this. :no:

I have tried and tried. I saw that it is said that to test the drivers you can not use virtual pc or vmware. but I assumed it would atleast install? I would very much like to get some idea that i am not gonna be :realmad: by jacking up my only pc. I have made several Unattended installs for winxp but never put the driver pack in one of them and Set my mind to it that I will get it to work and fit all on one cd. somehow.

If anyone has any suggestion or a fix that would be real nice if you could let me know.

If you have anything negative you could also be real nice and keep that to yourself.

Have a nice day or night. :thumbup


How to remove advertisement from MSFN

#2
Siginet

Siginet

    Windows XP PowerPacker Creator

  • Member
  • PipPipPipPipPip
  • 739 posts
  • Joined 22-January 05
Have you checked inside of txtsetup.sif with notepad?

This error can be caused if txtsetup.sif had not been edited.

Open txtsetup.sif and search for presetup.cmd

just under presetup.cmd should be setuporg.exe

If those entries do not exist

Then go back to the top of the txtsetup.sif file and search for the first instance of:
[SourceDisksFiles]

Then just under it add:
presetup.cmd = 1,,,,,,,2,0,0
setupORG.exe = 1,,,,,,,2,0,0

So it should look like:
[SourceDisksFiles]
presetup.cmd = 1,,,,,,,2,0,0
setupORG.exe = 1,,,,,,,2,0,0

Make sure presetup.cmd and setuporg.exe exist in the I386 directory as well.

If you checked all of this and still have the problem post back and we'll see what we can do to help.

You can also try my "PowerPacker" app to see if it will help you. The link is in my signature. ;) Good Luck!

Posted Image
For those of you interested in my next software venture you can check it out here:
www.ITTechware.com


#3
captainamer71

captainamer71
  • Member
  • 9 posts
  • Joined 19-February 05
presetup.cmd and setuporg.exe are not anywhere.... what makes those files? or how do I get them? thanks for the help.

#4
Siginet

Siginet

    Windows XP PowerPacker Creator

  • Member
  • PipPipPipPipPip
  • 739 posts
  • Joined 22-January 05

presetup.cmd and setuporg.exe  are not anywhere.... what makes those files? or how do I get them?    thanks for the help.

<{POST_SNAPBACK}>


OK. What probably happend is you skipped the most important step.

First you need to go to Bashrats site and make sure you get The DriverPack Base.

Execute the file and it will extract a bunch of stuff.

You should see a "DriverPacks" folder.

That folder is where you should download all of the driverpacks. (I would suggest skipping the Mass Storage DriverPack for now, untill you get a working disk.)

Once you have downloaded all of the driverpacks to the "DriverPacks" directory... Click on the file called "BTS_DPs_Slipstreamer_V505x.cmd"

Go through all of the steps.

Your best bet in my opinion (For Now) is to choose Method 2.

It will grab all of the files it needs and put them in a directory called "UWXPCD_ROOT"

Copy all of the contents inside of the directory "UWXPCD_ROOT"

And put it at the root level with your I386 directory.

Now you need to click on "RUN_ME.CMD"

I have had most success latley with the "RunOnceEx" option.
It will ask for a number... I usually put 937 (Which is default).

KtD option is if you want to keep the drivers on the system after install is complete.
This is still in Experimental Stage so I would select "NO" (For Now). But from what I hear it seems to work fine.

Let the script finish all the way. when it is done you should be ready to make your ISO.

If you run into any other troubles try to look in the file "Readme.htm" that is extracted from the DriverPacks Base. It goes into a bit more detail.

Or if you still have troubles post back here. Good Luck.

Posted Image
For those of you interested in my next software venture you can check it out here:
www.ITTechware.com


#5
captainamer71

captainamer71
  • Member
  • 9 posts
  • Joined 19-February 05
Ok I have two seperate FULLY working copies of winxp that I have done everything to. Now I am following your directions exactly. in virtual pc. after the files are copied and it reboots when it gets done with the windows xp black screen it flashes to the blue screen of the install and then I get a blue screen with a error in it. I am doing this on two seperate computers with two copies of win xp pro sp1a that Do physically install and run perfect. Any Idea why the driver packs are messing it up? Guess I should just be happy that I have what I have. Or do the driver packs just not work that well. seems like they are kinda buggy. I run the runme.cmd and it says can not open file repeatedly but it does not give any errors and it finishes saying nothing about how it just jacked up my winxp files lol.

Oh well

#6
Siginet

Siginet

    Windows XP PowerPacker Creator

  • Member
  • PipPipPipPipPip
  • 739 posts
  • Joined 22-January 05
Could you specify the error you get?

The error should say a filename or something in it. That would help to point you in the right direction.

It sounds like you have it working... but one of the drivers aren't loading right.

If you aren't installing the Mass Storage drivers this doesn't happen often. The times when I have encountered a problem the most, (without mass storage drivers) is on some Dell computers. I get the portsys error. This error is caused by a sound driver. You can read more about it in the DriverPack Sound section. Allthough I haven't been getting that error latley I have seen a few others claiming to have had a problem with it.

Don't give up... you are almost there. ;)

Posted Image
For those of you interested in my next software venture you can check it out here:
www.ITTechware.com


#7
lakersforce

lakersforce
  • Member
  • 1 posts
  • Joined 12-March 08
And here I am three years later having the same question. To the best of my knowledge I have followed the advice given in this thread, to no avail but a headache. My problem is excactly as described above. But a picture speaks a thousand words:

Attached Files

  • Attached File  fail.jpg   32.53KB   21 downloads

Edited by lakersforce, 12 March 2008 - 03:59 PM.


#8
J'Tok

J'Tok
  • Member
  • 1 posts
  • Joined 06-May 06

And here I am three years later having the same question. To the best of my knowledge I have followed the advice given in this thread, to no avail but a headache. My problem is excactly as described above. But a picture speaks a thousand words:


I'm having the same problem. Was a solution ever found?

#9
googy_spots

googy_spots
  • Member
  • 1 posts
  • Joined 19-February 09
SOLUTION:

For the experts:

Manually copy SetupORG.exe and presetup.cmd from the i386 folder to the WINDOWS\SYSTEM32 folder. Restart the computer and continue with setup.

Complete Intro:

I got this error while working with a difficult laptop, a Fujitsu Siemens L1310G. The normal boot process with a XPSP2 with DriverPacks and Nlite was not working. The DVD drive was uncooperative, probably dirty or damaged, it would not boot even with a Verbatim DVD-R. The last 4.5 Gigs of the hard drive became a FAT32 partition. All the sources for the install were copied there. The first part became a 70 Gig partition of FAT32. The DOS system on D: was transferred to the first partition and it became C:.

C: 70 Gigs (installation destination)
D: 4.5 Gigs (Copy of slipstreamed install from DVD)

Booting off C:, I went to D:\I386 and entered WINNT to begin setup.

The DOS-based portion of XP Setup was unable to copy SETUPORG.EXE and PRESETUP.CMD. I choose continue.
Setup finished and restarted the computer, then the error showed up as the previous poster indicated.

I pressed OK at the error, let the computer reboot, choosing to boot into DOS. On the boot-menu the DOS options looks like 'Microsoft Windows', meaning the DOS version was v7.1. It may also say 'Previous Operating System on C:'.

COPY D:\I386\SETUPORG.EXE C:\WINDOWS\SYSTEM32
COPY D:\I386\PRESETUP.CMD C:\WINDOWS\SYSTEM32

Restart the computer and allow it to continue setup.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN