Sometimes those old Windows CDs are really worth a lot.
| I forgot to add that the "full" install (as opposed to the
upgrade install) said
| it could not find a previous copy of windows. Perhaps that
is another symptom of
| installing an upgrade over the OEM XP Home edition.
|
| Fortunately I found an old NT Workstation 4.0 CD, which
was accepted. The XP Pro
| install CD is an upgrade CD.
|
|
| | > Resolution:
| >
| > After trying almost everything I could think of (turned
off audio, modem, lan,
| > USB in BIOS setup; copied CD to disk and tried to
install from disk), I chose
| > "boot from (install) CD" and selected INSTALL (repair
did not work; continue
| > installation did not work). That worked without a hitch,
although I lost all my
| > previously installed stuff.
| >
| > I did a lot of Internet searching and found similar
problems but no solutions.
| > Most people seemed to think this a hardware issue. A few
thought it was an
| > upgrade install over OEM version of XP Home. That seems
to be the case here. It
| > would seem that if hardware were an issue, the same
problem would occur when
| the
| > installed scanned devices in either an update or full
install.
| >
| > BTW, the documentation says the motherboard is Micro ATX
for factor, Intel
| > Pentium 4 processor, Award BIOS.
| >
| >
| >
| > | > > You are hinting at it there. What happens is the
eMachine is an OEM
| > > installation with custom hardware. The drivers may
only exist on that
| > > OEM installation CD and is not natively supported by
Windows XP. So in
| > > effect, he needs the drivers from his OEM CD
incorporated onto his
| > > Windows XP Pro CD.
| > >
| > > ASUS is the best IMO. Have owned 4 ASUS boards and 2
ABIT boards. Those
| > > have both been awesome. Will never use ECS or Soyo
again. I do find it
| > > funny he blames it on the motherboard when it isn't
even the motherboard
| > > that is causing the problem

| > >
| > > Nathan McNulty
| > >
| > > Jim Macklin wrote:
| > >
| > > > I was thinking you might have had a printer or
scanner
| > > > connected.
| > > >
| > > > The only thing I can think of is that EMachine may
have used
| > > > some hardware that is not supported by the XP Pro
upgrade
| > > > and it hangs while trying to identify the device or
find a
| > > > driver.
| > > >
| > > > I'm not sure, but there may be a log file that would
let you
| > > > determine the device(s) that are causing the
problem, maybe
| > > > one of the MVPs will chime in.
| > > >
| > > > Have you thought to try a clean install using the
upgrade
| > > > CD? I don't know what type of media you have to use
as
| > > > proof, but an old W95 or 98 CD will do.
| > > >
| > > >
| >
| >
|
|