Thanks everyone for the responses . . The 'Program Files (x86) is
good to know and sounds like a good way to tell. I had checked the
inf files, and they were mixed, referenced both x86 and 64 bit int
hem..
Yeah, I had the thought later that some programs will install
even on 64bit and that driver files may include both x86 as
well as 64bit options...I tend to look for confirmation so
both the program files (x86) and /drivers properties would
be one way I'd look initially.
As a little more info, the system is booting up to a stop error,
0x0000c1f5
is there any dll/sys/exe file mentioned in the stop error?
I have a chart somewhere for MS stop errors if I can find it.
I found online in gateway support..
(just a copy, I know you can't boot it)
--
(STOP 0x0000C1F5)
This error is not covered in a Microsoft Knowledge Base article, but has
been known to occur. Research has shown that the System File Checker
procedure has been successful in resolving the error:
To run System File Checker from the Command Prompt:
1.. Click the Start button. In the Start Search box, type cmd.
2.. At the top of the list, right-click cmd.exe and click Run as
Administrator.
3.. At the Command Prompt, type sfc /scannow and let the process run.
Follow any prompts that may appear.
If that does not resolve the error, follow the procedures given in the
Knowledge Base article at
http://support.microsoft.com/kb/925810/en-us.
--
The really cool thing is I get the error booting to windows, to the HP
built in recovery partition, or EVEN to a Vista install DVD! Booting
to a PE environment with the hard drive hooked up either locks up on
boot, or gives the same stop error.
Very unusual, sounds a bit like maybe missing a driver
or a hardware item is blocking system/PE..but later on
you got a clean install working...guess is audio/video
or an aborted partial recovery/install by someone earlier.
Only way to access the drive is to slave it on an XP machine (did not
try a vista machine). From there I was able to clone the drive to
another drive, but trying that other drive still will not boot. I
tried cloning just the main partition to another drive, leaving off
the recovery partition, no go. I manaully copied in a backup registry
file, nope.
only important thing at moment would be customer specific
documents/email/pictures that may be inside initial install.
perhaps even license keys for installed progams.
that would assume the hard drive itself and data is
intact or at least functional.
Nice one huh? Any other ideas? Internet searches show that stop
error to not be well documented.
Typically (in xp and earlier) one would rename a few system files
then do a side by side install and troubleshoot original system
or move data to new install then delete the old one.
I installed vista clean to a new hard drive on the computer and it
boots and installed just fine.
-Brad
I'm wondering if drive or some part of it was locked or
encrypted...even possibly the PE locked up trying to read
the hdd...does the PE boot system with hdd removed?
Some virus or malware in root of drive may be present.
NT Canuck
'Seek and ye shall find'
