Forum Home
Press F1
Thread ID: 79420	2007-05-19 11:36:00	Windows 2000 slowdown	Boothienz (12290)	Press F1

Post ID	Timestamp	Content	User
551215	2007-05-22 05:27:00	Will you please describe this statement a little more fully? .............The boot goes fine until the taskbar is loaded, then it's as if the processor kicks back to about 1%. Eventually (45+minutes) the desktop might be complete. From there everything takes ages........ What do you mean that the CPU drops to that percentage or you think it's only using that much....or what am I asking here? :cool:	SurferJoe46 (51)
551216	2007-05-23 12:05:00	Will you please describe this statement a little more fully? What do you mean that the CPU drops to that percentage or you think it's only using that much....or what am I asking here? :cool: Finaly managed to get a few minutes on my wife's PC to get back to this thread. I'm very limited with free time at the moment, so apologies if I make you wait for a response. Anyway... What I was suggesting is that it is just as if the computer will perform tasks, but it's going to take about a hundred times longer to do anything. However, in answer to whether I "think it's only using that much" - in actual fact, Task Manager will show System Idle Process at 99% and a few other processes having had a matter of seconds in CPU time. Before you ask "Which processes?" - I don't know, I'd have to go and boot the PC and wait 45 minutes. I'm going to have to get some more info in response to questions that have come in, when I can get back to the machine. Hopefully tomorrow (about 20 hours from now). Thanks again.	Boothienz (12290)
551217	2007-05-23 12:14:00	If you can run Task Manager, allbeit very slowly, you must be able to see which process is using all the system resources. Which one is it? Sorry if it looks as if I've ignored this question. I only had ten minutes to check and reply to the thread yesterday. In answer to the question - I'll have to get the machine fired up tomorrow to check that, but basically as stated above, System Idle Process shows 99% every time I check Task Manager. The other 1%, I can't recall - but there are no tasks with any significant time allotted to them. I guess if I watched Task Manager constantly I might see some changes at the point where some action finally occurs. Hope you have stuck around long enough to see this reply ;)	Boothienz (12290)
551218	2007-05-23 16:15:00	Sorry if it looks as if I've ignored this question. I only had ten minutes to check and reply to the thread yesterday. In answer to the question - I'll have to get the machine fired up tomorrow to check that, but basically as stated above, System Idle Process shows 99% every time I check Task Manager. The other 1%, I can't recall - but there are no tasks with any significant time allotted to them. I guess if I watched Task Manager constantly I might see some changes at the point where some action finally occurs. Hope you have stuck around long enough to see this reply ;) I am still here, and hopefully there are others too....I need to go out of town for the rest of the day today, and won't be back for quite a long time ...at least till 10PM my time (-8GMT)...but I WILL return. Still don't really know what you are seeing in the TM..we can talk later.	SurferJoe46 (51)
551219	2007-05-24 00:46:00	You can't really test a PSU with a multimeter (especially a digital MM). It will either "work" or not, because the meter won't see voltage dips which might cause problems. (SNIP) I'd have a look at that bootlog file. It might give a hint. I've tried to find a bootlog on the drive (2gig) with the system which still works (so I would know where to look on the bad one) and can't find it anywhere. Where would it be??	Boothienz (12290)
551220	2007-05-26 03:28:00	It's in the root of the boot disk, C:\ . It might be hidden, though I don't thinks so. There's probably an extension on it ... it's a plain text file, so Notepad is fine to look at it. It seems to be rewritten at each boot, saying whats happening, and it might need an option set in boot.ini . But it's a long time since I've looked at it. Have a look at this Google list (www.google.co.nz/search?hl=en&q=bootlog+w2k&meta=). And to be extra sure, here's what Microsoft (support.microsoft.com/kb/239780) say about it. You get a bootlog if you do an F8 Safe Boot.	Graham L (2)
551221	2007-05-26 22:52:00	It's in the root of the boot disk, C:\ . It might be hidden, though I don't thinks so. There's probably an extension on it ... it's a plain text file, so Notepad is fine to look at it. It seems to be rewritten at each boot, saying whats happening, and it might need an option set in boot.ini . But it's a long time since I've looked at it. Have a look at this Google list (www.google.co.nz/search?hl=en&q=bootlog+w2k&meta=). And to be extra sure, here's what Microsoft (support.microsoft.com/kb/239780) say about it. You get a bootlog if you do an F8 Safe Boot. Thanks for the reply I had done a "find files" search and couldn't find it. After weighing up all of the advice that came in I decided that I couldn't ignore the repeated suggestions that it is a power supply problem, even though I cannot logically picture what might be happening to cause the systems to go awry. Of course it's not possible to measure the voltages properly with a digital multimeter, apparently, which means there is not alot I can do. I could take it to a technician to check, but that might cost more than it is worth, and may not be the problem amyway. I decided, therefore, to start all over by nuking the 20gig and doing a fresh install. I am keeping a complete log as I go. I started last night, before I read your post, so there was no way to search again for the bootlog. I had already formatted the other faulty installation (13gig). So far I have installed SP4, and Windows Installer3.1 and BITS2.0 from Update. These are necessary to download from new Update site. This morning I did a custom search for updates, and selected only 3 cumulative or rollup packages to begin with. Half way through the 12mb my dialup was disconnected! We have a broadband as well, but it's at my wife's PC and I haven't got a router sorted yet. When she goes out I will run a cable to the modem and try again. Thanks for the reply, I will still try to find that bootlog, in case I have more problems. I think I will call an end to this thread, and just report back on any progress or further trouble through a new thread. Thanks to all who have tried to help - especially SurferJoe46, who I'm sure has stayed up late armed with Twinkies and coffee, trying to solve the mystery ;-))	Boothienz (12290)
1 2 3 4