Discussion Locked

Windows 2000 Pro: System process hog!

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

In installing a Hayes Accura modem into a (currently) dual-booting HP Brio (the OSs are on separate partitions), I switched from win95 to startup win2K (as I have several times over the course of this week), and win2k took over 2 hours to startup!
Consulting the Task Manager revealed that the hog was the System process which was taking up 99% of the CPU!
If anyone has any experience of this, and would care to shed any light on the phenomenon, I would be most grateful!

9 replies

by phil.hall

A few questions for clarification:
(1) what's the system (CPU, memory, chipset)?
(2) is the partition on which Windows 2000 is installed formatted as FAT (16 or 32) or NTFS?

by Member 32255452

The same setup as it was before the problem started, and the same as fully functional installations on the same network.
It's registered as a Pentium Model 3 with 96MB RAM (Chipset not available at present).
The partitions are both FAT32.
It is unclear how the Processor type, RAM or partition format will affect your answer, please explain.

by dmiles

You have the dual-boot configuration set up on the same drive
What other programs do you have loading at Startup

A lot of this depends on what other software you have loaded on your machine

Do you have anti-virus,installed on the system,it isa hog for resources

Consider upgrading the memory to your system

by Member 32255452

No, and it is a clean installation - this doesn't consider the fact that the machine has been happy running both sides in a dual-boot config for several weeks.
The memory has been upgraded AVS: Yes, but of course that isn't the problem is it? (Hint: Please read the question.)

by jim

As with all windows os 2000 uses a ton of memory on startup. 96meg today is not enough. a minimum should be 128 and 256 would be much better. Cost less than $60. a second point w2k needs more disk space on startup. It may have worked ok before you started to add programs but as soon as you start adding to the registry requirements change. Best solution is add memory.

by Member 32255452

Seriously, folks - generalizations don't help when this level of analysis has been helpfully provided. Please be aware of the facts given and consider your answers carefully.

A successtful response could lead to more than just techpoints.

by phil.hall

Well, Ray, if you think our probing questions to assist you (when you didn't provide adequate information in the first place) are "smart arse," then perhaps you should simply take the malfunctional computer to a local shop (or shoppe) and let them charge you an arm and a leg for the service. (We assist for free and out of the generosity of our natures.)

Now, to answer your post to (I assume, me). The chipset is important to know because there are known issues with certain motherboard chipsets. I also asked how much RAM you had since (a) you didn't say in the first place, and (b) Win2000 is a pig (and that is putting it mildly); additionally, I asked as to the format of the drive (NTFS vs FAT) for a reason: NT/2000 loves NTFS more than FAT. Converting the drive can help with some issues.

I noticed that you listed the CPU as a Pentium model 3, is that to say it is a "Pentium 3" or is a "Pentium" model chip? This is important to know as if the speed of the processor is less than, say, 233, putting Windows 2000 on it would have been inadvisable.

But all that is moot...

But you say things were peachy until the modem was added. Is this an internal or external modem? If it's external, then you need to make sure that your BIOS settings are correct, and that the serial port is even visible to Windows 2000, which it may not be, or the serial port could be simply misconfigured (wrong baud rate, etc.) Additionally, you may wish to see if there's Registry corruption (there'sfreely available software utilities that will check that for you.)

On the Windows 2000 side, hit F8 to get the boot menu at startup and select the last knows good configuration. Then reinstall the modem on 2000's side.

This discussion is closed to new replies.