fake setup call himself instead original "setup.exe" - Setup

[Yuni]

I upgraded windows XP and find this message [b]"fake setup call himself instead original "setup.exe" - Setup Abort".

I can't go into windows. It means I could not use that computer anymore. I don't know how to do. Please let me know how to enter windows.

Yuni

[amit_talkin]

i have the same problem...any solution?

[Innocent Devil]

wow ,what a message, how it happened ??

[LeveL]

It happens using Bashrat The Sneaky's Driverpacks when you try to

do a repair installation. You must have removed the OemPreinstall=Yes

from the WINNT.SIF file or something.

You need to at least have these sections and commands in I386\WINNT.SIF

[Data]

MsDosInitiated=No

[unattended]

OemPreinstall=Yes

[GUIRunOnce]

command9="%SystemDrive%\DPsFnshr.exe"

The vicious circle is - if you have an [unattended] section there, you

will lose the ability to do a repair install.

Edited March 25, 2007 by LeveL

[rajesh.kumar]

yes indeed it is due to the driverpack. this happened when i ran xp setup from inside windows and rebooted to continue finish the repair install. this way, i can select repair install even if my cd is unattended, and consequently, this problem of "setup calling himself" pops up and terminates the installation. i had this problem lastweek so i prepared a uA without driverpack and repaired.

any solution if driverpack is used?

[rajesh.kumar]

Will this issue get the attention of "The Sneaky". He could give some solution.

i often wanted to repair my brother's computer without reformating it.

Sorry, forgot to celebrate Annual Day in my previous post for this topic.

Edited March 28, 2007 by rajesh.kumar

[couges]

I have also had the same problem, and I would also like the repair option (I guess I want everything).

I have also had problems wih text mode mass storage devices.

If there is a solution out there, I would be very keen to know.

What we then build is the ultimate unattended.

Regards

Couges

Edited March 30, 2007 by couges

[LeveL]

Make a dual multi boot CD, one unattended with drivers, one not

unattended without drivers, so it has the option to repair... visit

http://flyakite.msfn.org/ to do that.

[rajesh.kumar]

ok there seem to be a solution in the driverpack forum.

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

[DizzyDen]

And even more in depth explanation and solution is in

Driver Pack Discussion Regarding Fake Setup and Solution

The files mentioned in that thread, with some editing to clean them up even more (always lookin for ways to clean my code more) is attached here.

See the !ReadMe.txt file.

_XPCD_ROOT.7z

[rajesh.kumar]

thank you dizzyden

[DizzyDen]

thank you dizzyden

No problem at all....

I guess you found it to work flawlessly also.

Glad to have helped, have some mod's if ya'd care to have them...

Mostly stuff to clean the code, and minimize creating intermediate files. Although the routine stays pretty much the same.

[rajesh.kumar]

i'd be much glad to know the modifications too

[rylo85m]

I still cant find a fix for this error message, please can somebody give some specific and clear guidlines, the links dont seem to work, do u think its easier to just remove my hard drive, back it up onto a clean computer and format the whole thing. this error message just wont go away

Thanks

[ilko_t]

From the given link above in driver packs forum, post Nr.3:

Add this to 'i386\presetup.cmd' in your CD image:

DEL /F %systemroot%\system32\setupold.exe

OR if you already have a hung up repair install going - boot into Repair Console from the XP CD and delete the 'setupold.exe' file from the C:\windows\system32 folder then reboot.

Have you tried this?

Edited July 25, 2007 by ilko_t