Re: stopping XP reinstall
- From: Greg Kirkpatrick [SBSC,MCTS-Vista,MCITP] <greg@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 16 Jul 2008 21:07:01 -0700
I hope these struggles are amusing to someone.
If I knew which driver to disable, I would have. I tried over many hours,
turning off successive drivers and startup items, and removing .SYS files,
before I began the repair install.
As for my question about aborting the XP (re)install, I know there is a way,
because I have done it previously, however I cannot find my notes on the
procedure. Since the reboot (following the copying of files from the CD) had
not been successful, the installation had not really started yet, and it
should have been possible to abort it then.
Following the directions for removing all the drivers created after
8/13/2001 had the effect of another error, this one crying for the absence of
NTFS.SYS -- and having already gone through this during my previous
diagnostics, I realized the instructions were out of date, and added back all
the files whose "Company" name was "Microsoft". Only then would XP Setup
resume.
Then, Setup stops, asking for the location of the file ASMS -- which doesn't
exist, but a directory named ASMS exists in the I386 folder on the XP CD.
When I finally clicked CANCEL, Setup stopped for good.
I was able to find this Knowledge Base article on the ASMS error:
"The file 'Asms' on Windows XP Professional CD-ROM is needed" error message
when you install Windows XP
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q311755&ID=KB;EN-US;Q311755&LN=EN-US&rnk=23&SD=gn&FR=1&qry=&src=DHCS_MSPSS_gn_SRCH&SPR=WINXP&;
Having followed the steps to delete the UPPERFILTERS and LOWERFILTERS keys
from the appropriate registry entries, and rebooted, Setup began again, and
while it asked for the ASMS file again (I removed the CD), I was able to
point the installation to C:\WMC2005\I386 (because I had long ago copied the
installation files to the hard drive) and things went relatively smoothly
after that.
That is, until Setup went to BSOD at the 37 minute mark.
This time, a Complete memory dump was created (which wasn't happening with
earlier crashes, despite the option being selected there), so now I have
something to look at using Debugging Tools for Windows.
The "alphabet soup" was left off my original note, as I entered the
newsgroup via the Google backdoor. When I reentered via the Microsoft
Community links, it asked me to log in, and thus added my regular "name". I
decided long ago to put my credentials next to my name, rather than have a
signature (like yours).
I earned my alphabets, as I'm sure you earned yours (MS-MVP).
"Shenan Stanley" wrote:
Greg Kirkpatrick wrote:.
My customer has a Windows XP Media Center 2005 machine which
developed a BSOD as it was booting past the Windows splash screen.
At least it could still boot into Safe Mode. After attempting
several diagnostics (including perusing memory dumps from a month
ago, no recent ones created), I decided to attempt a repair install
from the CD. After copying files, it rebooted, and before getting
to the installation screen, the BSOD appeared again. (STOP:
0x0000007E (0xC0000005, etc.))
Now it cannot boot into safe mode, as it gives an error message that
Windows Setup cannot run in Safemode.
I have a PE disk that I can use to access the files -- which ones
do I need to delete so XP Setup does not restart? Then I could
boot into Safe Mode again, and continue the attempts to repair this
beast.
Shenan Stanley wrote:
Replace the memory with known good memory and try to continue your
repair installation.
Greg Kirkpatrick [SBSC,MCTS-Vista,MCITP] wrote:
If RAM was an issue (it's not, I have tested it with Windows Memory
Diagnostic and MEMTEST86), then replacing it could be all that
would be necessary, not a full repair install. Anyway, that wasn't
my question, nor is that relevant for this particular problem.
My question remains: following the screen where the XP installation
files
are copied from the CD to the hard drive (during a repair install),
and before the appearance of the screen (following reboot) where
those files begin to be installed -- what are the steps to cancel
XP installation?
With Windows ME, 98, and 95, one could simply wipe out a folder and
correct AUTOEXEC.BAT -- and various notes in other
newsgroups/forums indicate a similar step with BOOT.INI (using
BOOTCFG.EXE in Recovery Mode) -- which I have done, but it still
persists in attempting to continue the repair install.
I realized, after the fact, that I haven't tried the Driver
Verifier utility in Windows XP
(http://support.microsoft.com/?kbid=244617&sd=RMVP), and I would
like to do so, if only I could break out of this loop, and get back
to Safe Mode.
Alphabet soup added for effect...? *grin*
In any case - I suggest Method 5 - continue install...
http://support.microsoft.com/kb/330182
(If you think you know what driver may be causing the issue - just diable
that service.)
For your direct question - I am not so sure you can - I believe that you had
gotten pretty far into the repair.
--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
- Follow-Ups:
- Re: stopping XP reinstall
- From: Shenan Stanley
- Re: stopping XP reinstall
- References:
- stopping XP reinstall
- From: Greg Kirkpatrick
- Re: stopping XP reinstall
- From: Shenan Stanley
- Re: stopping XP reinstall
- From: Greg Kirkpatrick [SBSC,MCTS-Vista,MCITP]
- Re: stopping XP reinstall
- From: Shenan Stanley
- stopping XP reinstall
- Prev by Date: Re: stopping XP reinstall
- Next by Date: Re: stopping XP reinstall
- Previous by thread: Re: stopping XP reinstall
- Next by thread: Re: stopping XP reinstall
- Index(es):
Relevant Pages
|
Loading
