Yuni Posted March 23, 2006 Share Posted March 23, 2006 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 Link to comment Share on other sites More sharing options...
amit_talkin Posted August 24, 2006 Share Posted August 24, 2006 i have the same problem...any solution? Link to comment Share on other sites More sharing options...
Innocent Devil Posted August 24, 2006 Share Posted August 24, 2006 wow ,what a message, how it happened ?? Link to comment Share on other sites More sharing options...
LeveL Posted March 25, 2007 Share Posted March 25, 2007 (edited) It happens using Bashrat The Sneaky's Driverpacks when you try todo a repair installation. You must have removed the OemPreinstall=Yesfrom 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, youwill lose the ability to do a repair install. Edited March 25, 2007 by LeveL Link to comment Share on other sites More sharing options...
rajesh.kumar Posted March 25, 2007 Share Posted March 25, 2007 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? Link to comment Share on other sites More sharing options...
rajesh.kumar Posted March 28, 2007 Share Posted March 28, 2007 (edited) 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 Link to comment Share on other sites More sharing options...
couges Posted March 30, 2007 Share Posted March 30, 2007 (edited) 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.RegardsCouges Edited March 30, 2007 by couges Link to comment Share on other sites More sharing options...
LeveL Posted April 13, 2007 Share Posted April 13, 2007 Make a dual multi boot CD, one unattended with drivers, one notunattended without drivers, so it has the option to repair... visithttp://flyakite.msfn.org/ to do that. Link to comment Share on other sites More sharing options...
rajesh.kumar Posted April 30, 2007 Share Posted April 30, 2007 ok there seem to be a solution in the driverpack forum.http://forum.driverpacks.net/viewtopic.php?id=669 Link to comment Share on other sites More sharing options...
DizzyDen Posted May 26, 2007 Share Posted May 26, 2007 And even more in depth explanation and solution is inDriver Pack Discussion Regarding Fake Setup and SolutionThe 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 Link to comment Share on other sites More sharing options...
rajesh.kumar Posted June 4, 2007 Share Posted June 4, 2007 thank you dizzyden Link to comment Share on other sites More sharing options...
DizzyDen Posted June 4, 2007 Share Posted June 4, 2007 thank you dizzydenNo 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. Link to comment Share on other sites More sharing options...
rajesh.kumar Posted June 6, 2007 Share Posted June 6, 2007 i'd be much glad to know the modifications too Link to comment Share on other sites More sharing options...
rylo85m Posted July 25, 2007 Share Posted July 25, 2007 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 awayThanks Link to comment Share on other sites More sharing options...
ilko_t Posted July 25, 2007 Share Posted July 25, 2007 (edited) 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.exeOR 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 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now