Tech Support > Microsoft Windows > XP - stop/remove repair process
XP - stop/remove repair process
Posted by roberto on December 21st, 2005


I've started a machine on a repair process route (XP Home). When I
boot it, it starts the "Setup" process but hangs looking for a folder
'asms' and won't respond to the information '\\D:\i386' (D is the
CDRom). I no longer want the repair process to be completed. Since it
hasn't really run, just initialized and copied files) I figure I've
done no real damage yet. But I can't find where the "Setup" is
initiated so that I can reverse it/remove it. Anybody have any ideas
of where to look and what to change so the machine just boots into it's
current system without running the repair???

Thanks in advance for the info.

Roberto

Posted by Dixonian69 on December 21st, 2005


"The file 'Asms' on Windows XP Professional CD-ROM is needed" error message
when you install Windows XP
http://support.microsoft.com/default...;EN-US;Q311755

"roberto" wrote:

> I've started a machine on a repair process route (XP Home). When I
> boot it, it starts the "Setup" process but hangs looking for a folder
> 'asms' and won't respond to the information '\\D:\i386' (D is the
> CDRom). I no longer want the repair process to be completed. Since it
> hasn't really run, just initialized and copied files) I figure I've
> done no real damage yet. But I can't find where the "Setup" is
> initiated so that I can reverse it/remove it. Anybody have any ideas
> of where to look and what to change so the machine just boots into it's
> current system without running the repair???
>
> Thanks in advance for the info.
>
> Roberto
>
>

Posted by Alias on December 21st, 2005


Roberto,

Look in the root directory of drive C: for any .log or .txt files that say
something like Setup or Repair or something that would indicate a repair
process. Look at the date/time stamp of those files and move all of them to a
different folder if you can.

You may have to boot into DOS in order to move those files. Once you move
them, try rebooting. If all goes well, put each one back individually so as
not to upset Windows until you find the one that's controlling the repair
process. Once you identify the correct file, go on and delete it permanently.

-Alias

"roberto" wrote:

> I've started a machine on a repair process route (XP Home). When I
> boot it, it starts the "Setup" process but hangs looking for a folder
> 'asms' and won't respond to the information '\\D:\i386' (D is the
> CDRom). I no longer want the repair process to be completed. Since it
> hasn't really run, just initialized and copied files) I figure I've
> done no real damage yet. But I can't find where the "Setup" is
> initiated so that I can reverse it/remove it. Anybody have any ideas
> of where to look and what to change so the machine just boots into it's
> current system without running the repair???
>
> Thanks in advance for the info.
>
> Roberto
>
>

Posted by roberto on December 21st, 2005


Thanks. I've actually used a Bart'sPE 'Ultimate Boot Disk' that
someone made to clean out a huge amount of Virus, Trojan, and Spyware
infestation in the machine. So now I'd like to see if it can boot past
the initial problem on the original OS - but the repair process I've
initiated is getting in the way. I'll keep your info handy in case I
need to continue the repair process.

Roberto

Posted by roberto on December 21st, 2005


Thanks. I'll try your suggestion when I get back home and have time to
work on the machine. 'Tis the holidays and I have honey-doos to manage
.. . .

Posted by roberto on December 22nd, 2005



Alias wrote:
> Roberto,
>
> Look in the root directory of drive C: for any .log or .txt files that say
> something like Setup or Repair or something that would indicate a repair
> process. Look at the date/time stamp of those files and move all of them to a
> different folder if you can.
>
> You may have to boot into DOS in order to move those files. Once you move
> them, try rebooting. If all goes well, put each one back individually so as
> not to upset Windows until you find the one that's controlling the repair
> process. Once you identify the correct file, go on and delete it permanently.
>
> -Alias
>
>

Well, it was a nice thought. But I found no such .log or .txt files at
the root of C:. I looked also in the WINDOWS and System32 folders for
a file that might be associated with a repair action and nothing struck
me as appropriate. May have to take the painful way around this.
Thanks anyway.