Hello all. I have Win2000 Pro installed on a home network
computer and it keeps locking up within 5 minutes of
starting. Doesn't matter what program you're using... A
little more on the entire story is below, if needed....

I installed a new 80GB hard drive & Win98 SE on a home
network computer. My "server" runs XP. I kept loosing
the network connections between 98 & XP, so I installed
Win2000 on the 98 computer. Had a hard time getting it to
load properly, and ended up reformatting the hard drive &
loading Win2000. THEN, I got a continuous re-boot loop.
Finally reinstalled Win2000 again and everything seemed
fine. NOW, the computer will only run for about 5
minutes, then totally locks up.

Any suggestions? I'm thinking about just purchasing
another XP upgrade & loading that to see if the problem
goes away!!! URGGHHH! I HATE MICROSOFT!

Check Event Viewer and Device Manager for errors and or non-starting
devices.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows]
Microsoft Certified Professional [Windows 2000]
http://www.microsoft.com/protect


"Char" wrote:
| Hello all. I have Win2000 Pro installed on a home network
| computer and it keeps locking up within 5 minutes of
| starting. Doesn't matter what program you're using... A
| little more on the entire story is below, if needed....
|
| I installed a new 80GB hard drive & Win98 SE on a home
| network computer. My "server" runs XP. I kept loosing
| the network connections between 98 & XP, so I installed
| Win2000 on the 98 computer. Had a hard time getting it to
| load properly, and ended up reformatting the hard drive &
| loading Win2000. THEN, I got a continuous re-boot loop.
| Finally reinstalled Win2000 again and everything seemed
| fine. NOW, the computer will only run for about 5
| minutes, then totally locks up.
|
| Any suggestions? I'm thinking about just purchasing
| another XP upgrade & loading that to see if the problem
| goes away!!! URGGHHH! I HATE MICROSOFT!

Dave Patrick wrote:
> Check Event Viewer and Device Manager for errors and or non-starting
> devices.

Yup, on a home computer it "could be anything". Most likely it's a dodgy
computer. Win2k does not like flakey hardware such as loose PCI cards or
poorly seated CPUs. It never goes wrong on good hardware.

One other thing to check is, did you repartition and reformat the hard
drive first, before installing Win2k? If not you should, but you'll lose
any data that's not backed up.

--
Gerry Hickman (London UK)

Another thing you may want to check is to make sure you have the latest VIA
or Intel Chipset drivers. This had bitten me before with Windows 2000.

Good luck,
Rob

"Gerry Hickman" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Dave Patrick wrote:
> > Check Event Viewer and Device Manager for errors and or non-starting
> > devices.
>
> Yup, on a home computer it "could be anything". Most likely it's a dodgy
> computer. Win2k does not like flakey hardware such as loose PCI cards or
> poorly seated CPUs. It never goes wrong on good hardware.
>
> One other thing to check is, did you repartition and reformat the hard
> drive first, before installing Win2k? If not you should, but you'll lose
> any data that's not backed up.
>
> --
> Gerry Hickman (London UK)

R Dunn wrote:

> Another thing you may want to check is to make sure you have the latest VIA
> or Intel Chipset drivers. This had bitten me before with Windows 2000.

Good point! If it's a very new system, it's possible the low level
chipset drivers won't get installed at all by Windows 2000. You either
have to install them from the manufacturer's website or roll them into
an unattended build - I use the latter option which works with both
Intel and AMD.

--
Gerry Hickman (London UK)

Thanks for all the advise. The computer is actually an
older one. It's got an AMD 700 mhz processor. When I
first tried to install Win2000, it kept locking up. I
removed the RAM first to test hardware, and that was the
problem. I'll let you all know how it turns out. Thanks
again.

>-----Original Message-----
>R Dunn wrote:
>
>> Another thing you may want to check is to make sure you
have the latest VIA
>> or Intel Chipset drivers. This had bitten me before
with Windows 2000.
>
>Good point! If it's a very new system, it's possible the
low level
>chipset drivers won't get installed at all by Windows
2000. You either
>have to install them from the manufacturer's website or
roll them into
>an unattended build - I use the latter option which works
with both
>Intel and AMD.
>
>--
>Gerry Hickman (London UK)
>.
>