Printable View
Ok, I have a comp here at the shop that went down completely, so I gutted it to bring up its replacement
Old specs: P100, 16MB, 1.2GB, Win95B
New Specs: PII 233, 48MB, 1.2G, Win2k(new DoD/USMC reqs)
After paring down Office 2k Pro to about 120MB, I still have a lot of software to go, and obviously the thing drags its @&$ on boot. Any suggestions on files to delete, process to kill, etc??
TYIA
EDIT: Currently 435MB/35% free space
get more ram!
Is it on a network?
I took every stick of ram available...and yes, it's on a network.
Are you suggesting to run software through an application server...?
no, just you can get rid of a ton of stuff if there is no network.
You might look at recycle bins and swap file sizes as well.
The problem is that you are running Windows 2000 on a machine with a 233Mhz CPu and 48mb RAM. Windows 2000 will operate with a P166 and 32mb RAM, but not quickly. It also does not help that the HDD is a standard IDE interface drive instead of an ATA100 or 133.
You can remove programs from the startup group, remove fonts, remove program entries from the HKLM\Software\Microsoft\windows\current version\run section of the registry (after exporting the current settings), stop un neccessary services, etc... Search google for 2k tuning settings, or start a new topic here for tips.
It's the 4.5 H.P. B & S that's the problem, my lawnmower's got one & it's horrible...;)
Noo nailed it with the ram. But since it's edo your gonna need a butload to make it worth it. I just dumped 64MB into a system that only had 32 (for a total of 96MB) and it made a night and day difference. But that was a 366mhz system too.Quote:
Originally posted by NooNoo
get more ram!
Is it on a network?
Start with the startup menu and remove anything not critical to system operation. MS Office usually leaves some crap in there that .01% of the users actually find some use for, but are relatively just resource hogs.
Afterwards, skip over to the registry under the HKLM\SOFTWARE\MICROSOFT\WINDOWS\CURRENT VERSION\RUN... keys and check to see if anything else gets loaded during Windows' initialization.
More coal, failing that, it's probably about ready for a new hamster :D
I sure wish I could follow the best advice and trash the SOB, but we are out of money until after January - Motor T. and other sections spent it all...like they needed $8000 worth of tires...
It seems to be running acceptably...considering the machine. It's certainly better than what it was running - 95B, never defragged, never scanned, and a 2yr-old version of McAfee on a P100 with 16MB of ram.
I pared down O2k to the bare necessities(hope he doesn't try to use Help...) and put the other progs on and had 236MB left. Now to teach him how to empty his IE cache.
Just set it to like 20MB or somthing like that. I do it on my machine and it prevents defrags (to some extent).Quote:
Originally posted by Archangel42069
Now to teach him how to empty his IE cache.