Discussion on:
View:
Show:
I have begun to use http://ninite.com/ to create an install script which then runs and installs much of the free programs that I use. It is a lot quicker than doind it manually.
I have also heard that using a tool to back up the drivers that the system is using before a reinstall is a good idea to prevent having to find them, unless they are part of any problem that you are having. It helps that I slipstream more drivers and updates into my Win media using nlite or equivalents as well.
I have also heard that using a tool to back up the drivers that the system is using before a reinstall is a good idea to prevent having to find them, unless they are part of any problem that you are having. It helps that I slipstream more drivers and updates into my Win media using nlite or equivalents as well.
Dunno about the spelling of the title, but I usually partition a drive in an OS and Data partition. When performance problems start, I just reload the image, perform the necessary updates and re-image for next time if necessary. Usually takes me about 2 minutes to start the process and it's done after 30 to 60 minutes. Nothing like a nice clean fresh OS partition to speed things up 
I always partition the hard drive into a system and a data partition. I tried doing a triple partition -- OS, apps, and data -- but that turned out to be more trouble than it was worth. Having two partitions has saved my users from disaster several times, when the OS got hosed, but the data partition wasn't affected. I love being able to change tears to smiles when they find out they haven't lost everything.
Keeping data separate from the operating system is something I wish more manufacturers set up their computers to do.
A clean re-install and data restore will revitalize the PC to it's original glory. But, the cause of the problem might be hiding in the backed up files. Or, most end users will later do the same thing that caused the original problem.
A competent technician should let the customer know their options; backup and re-install or hunt down the culprit and fix it (with the caveat that the final solution might be to do a re-install anyway).
If you hunt down and find the cause of the problem, the end user can be aware of what NOT to do next time. Hunting down the cause might prevent the problem from rearing its ugly head again.
In either case, be honest with yourself and the customer. Also, be aware of your environment. In a corporate environment, speed is of the essence. Unless otherwise specified in some SOP manual, time spent hunting down the cause shouldn't exceed the time required to do a re-install/restore.
A competent technician should let the customer know their options; backup and re-install or hunt down the culprit and fix it (with the caveat that the final solution might be to do a re-install anyway).
If you hunt down and find the cause of the problem, the end user can be aware of what NOT to do next time. Hunting down the cause might prevent the problem from rearing its ugly head again.
In either case, be honest with yourself and the customer. Also, be aware of your environment. In a corporate environment, speed is of the essence. Unless otherwise specified in some SOP manual, time spent hunting down the cause shouldn't exceed the time required to do a re-install/restore.
Nope, I disagree. Installing the OS is a small fraction of the battle.
And by blindly doing OS re-installs rather than tracking a problem to its source you are just perpetuating your own ignorance. The solution may have been as simple as a registry setting, stopping an unneeded service, or clicking an option box. The next time you run into the same problem you have one tool in your bag - reinstall. Now THAT is what I call wasted time.
And by blindly doing OS re-installs rather than tracking a problem to its source you are just perpetuating your own ignorance. The solution may have been as simple as a registry setting, stopping an unneeded service, or clicking an option box. The next time you run into the same problem you have one tool in your bag - reinstall. Now THAT is what I call wasted time.
Many good points under my original post. The clean install is not as easy as it sounds (Side note: It is on my Linux systems). On Windows, imaging can help, but on a two or three year old OS, getting all the updates can add a couple of hours to the task.
In the old days, defragmentation was key because disks were small and space was at a premium, meaning that new files and programs didn't always have enough room to put the entire file in one contiguous area on the disk. This meant extra seek/read time when retrieving the file and extra wear on the disk servo and read/write heads (yeah, I used to BUILD hard drives). This is much less a problem now (except for the windows SWAP file, which REALLY should be its own partition like *nix) because disk sizes are so much larger, there is better error control on both the hardware and software end of things, and seek times are generally faster (unless you are using a 5400 RPM disk).
You can defrag if you want, but I usually find that simply cleaning up the startup area to remove TSR's (that's Terminate and Stay Resident for you non-DOS people). Get rid of things like Updaters (Google, Apple, Adobe, Java, etc.), printer tray icons (HP is notoriously bad for these), and other startup items and you'll find your PC's startup time dramatically reduced. msconfig is a great tool for seeing what loads on startup, but it isn't so great on disabling/removing things (hint to Microsoft!). IMHO, I can take 5 minutes to clean up the startup on someone's PC, another 5 to look at installed programs, and 5 more to disable unnecessary services and it is a significant improvement, whereas defrag takes hours (days on the ultra-large 500GB+ hard drives) and I rarely notice much of a difference.
You can defrag if you want, but I usually find that simply cleaning up the startup area to remove TSR's (that's Terminate and Stay Resident for you non-DOS people). Get rid of things like Updaters (Google, Apple, Adobe, Java, etc.), printer tray icons (HP is notoriously bad for these), and other startup items and you'll find your PC's startup time dramatically reduced. msconfig is a great tool for seeing what loads on startup, but it isn't so great on disabling/removing things (hint to Microsoft!). IMHO, I can take 5 minutes to clean up the startup on someone's PC, another 5 to look at installed programs, and 5 more to disable unnecessary services and it is a significant improvement, whereas defrag takes hours (days on the ultra-large 500GB+ hard drives) and I rarely notice much of a difference.
Don't forget the page file. The page file by default is set with a smaller start limit, and a larger end limit. This allows the page file to expand if necessary and causes the page file to fragment.
Set both entries to the higher limit, defrag the disk after cleanup, delete the page file, then reboot the system. The page file will be recreated and most times defragged too.
You can also use Sysinternals (now Microsoft) pagedefrag utility, but it does not work on Vista or Win7 yet. An added benefit is that it will also defrag the registry, and yes, the registry can fragment too.
Set both entries to the higher limit, defrag the disk after cleanup, delete the page file, then reboot the system. The page file will be recreated and most times defragged too.
You can also use Sysinternals (now Microsoft) pagedefrag utility, but it does not work on Vista or Win7 yet. An added benefit is that it will also defrag the registry, and yes, the registry can fragment too.
Swap file size is something that Windows actually does really well, just let your swap be system managed instead of hard set to a lower/upper. According to the people that started sysinternals anyhow (pretty sure it was him/them).
Definitely run pagedefrag automatically at startup though too.
Definitely run pagedefrag automatically at startup though too.
Allowing Windows to manage the swap file can lead to heavy file fragmentation.
I never leave it to Windows to manage this - I always set my Min and Max swap file values to be the same. (This also negates the need to run pagedefrag at each boot.)
To me, there's more benefit to minimizing maintenance tasks and running as few processes at boot as possible.
I never leave it to Windows to manage this - I always set my Min and Max swap file values to be the same. (This also negates the need to run pagedefrag at each boot.)
To me, there's more benefit to minimizing maintenance tasks and running as few processes at boot as possible.
I've found Windows sets a pretty static page file with all our systems. It's rare that pagefiledefrag takes longer than a few seconds to give a chance to skip then report that all relevant files are already a single data block. How is it that Windows changes the swap size enough to make fragmentation be an issue?
My suggestion I tell people - if your system SEEMs to be running slow and it's a few years since it was bought.... Re-install Windows.
Reinstalling gives you a fresh installation. No hickups. No issues. Most anti-malware software will remove the crap, but the system is nener the same.
Last time I re-did Win XP, I ended up with about 10GB of free disk space even after re-installing all the apps.
[Any time you uninstall an app, crap is left behind on the hard disk and the registry.]
Reinstalling gives you a fresh installation. No hickups. No issues. Most anti-malware software will remove the crap, but the system is nener the same.
Last time I re-did Win XP, I ended up with about 10GB of free disk space even after re-installing all the apps.
[Any time you uninstall an app, crap is left behind on the hard disk and the registry.]
If it's been years since the PC was bought, the material used to "just" re-install will created a dated and exploitable code base that will be tricky and tedious to safely update and secure.
It may not even be safe to install (e.g. if OS installation material pre-dates 137G safety on a PC that now has a larger hard drive) and because you've done nothing to exclude bad hardware, the result may be an unbootable mess.
For examples, consider a failing hard drive, or bad RAM. A PC that has had bad RAM for a few months has a 95%-OK code base before you "just" re-install Windows; now it has 100% of that code base written through the lens of bad RAM.
So even before you consider the adverse impact on the user (which you may consider punitively acceptable, if you've become sufficiently burned-out and cynical), this is a bad idea. Certainly not a service I'd pay for.
It may not even be safe to install (e.g. if OS installation material pre-dates 137G safety on a PC that now has a larger hard drive) and because you've done nothing to exclude bad hardware, the result may be an unbootable mess.
For examples, consider a failing hard drive, or bad RAM. A PC that has had bad RAM for a few months has a 95%-OK code base before you "just" re-install Windows; now it has 100% of that code base written through the lens of bad RAM.
So even before you consider the adverse impact on the user (which you may consider punitively acceptable, if you've become sufficiently burned-out and cynical), this is a bad idea. Certainly not a service I'd pay for.
Registry cleaners? No thanks!!
I also am not very impressed with defragmentation on today's fast drives unless a user has been doing loads of installing/uninstalling. I am though loathe to do a reinstall unless there's hardly any software on there - which of course is usually not the case.
If it's XP, put Sysinternals PageDefrag on and watch the Software registry hive go from 1000 fragments down to 1! Also I configure the paging file manually with a decent minimum size so it should normally always be in one chunk (when used with the former util).
I also am not very impressed with defragmentation on today's fast drives unless a user has been doing loads of installing/uninstalling. I am though loathe to do a reinstall unless there's hardly any software on there - which of course is usually not the case.
If it's XP, put Sysinternals PageDefrag on and watch the Software registry hive go from 1000 fragments down to 1! Also I configure the paging file manually with a decent minimum size so it should normally always be in one chunk (when used with the former util).
Stop unwanted services: Wirless Zero Configuration, Thems...
Disable Visuals Effects...
Disable Visuals Effects...
Wireless Zero Configuration should not be disabled if you use a wireless device on the system.
In some cases the device will have its own service that runs but will commonly disable WZC by default anyway.
I personally prefer WZC over the software that comes with WiFi devices as I feel its smoother and easier to configure.
In some cases the device will have its own service that runs but will commonly disable WZC by default anyway.
I personally prefer WZC over the software that comes with WiFi devices as I feel its smoother and easier to configure.
1. Check startup items (msconfig)
2. Use ccleaner to delete temp files and check registry
3. Check for malware (MBAM)
4. Defrag
2. Use ccleaner to delete temp files and check registry
3. Check for malware (MBAM)
4. Defrag
Check your Ram size in relation to the applications you install and run.Uninstall them if necessary,increase ram size then reinstall.This is in addition to the other tips discussed.
/r implies /f therefore /f isn't needed when CHKDSKing.
CHKDSKing before a DEFRAG is often a good idea, repairing indexes is allot harder is DEFRAG has moved all your files around!
CHKDSKing before a DEFRAG is often a good idea, repairing indexes is allot harder is DEFRAG has moved all your files around!
pay attention if you are doing a chkdsk on a raid systems.. -r tends to freeze the check resulting in a degraded raid..
...that no one has mentioned the most obvious and beneficial option: Delete Windows and install Linux. Operation usually speeds right up after that.
Even as a linux fan I do still need to use Windows occasionally, I use VMPlayer under Unbuntu to run a windows VM when I do, a fresh fast install everytime, no viruses or malware and can be thrown away when finished.
Remove windows and install Linux. I recommended Linux for a friend. He liked, but...
No drivers for his capture card. No drivers for his plantronics digital audio headset, no drivers for his magicjack, no drivers for his HD2900 ATI card, unable to use HDMI, unable to capture / export with the video card, unable to use the e-SATA hd (lot of errors).
So he is happily back to windows 7 64bits and he is happy.
I have a VAIO laptop now with raid0 / solid state drive. I cannot install Linux there either, the raid is giving problems.
No drivers for his capture card. No drivers for his plantronics digital audio headset, no drivers for his magicjack, no drivers for his HD2900 ATI card, unable to use HDMI, unable to capture / export with the video card, unable to use the e-SATA hd (lot of errors).
So he is happily back to windows 7 64bits and he is happy.
I have a VAIO laptop now with raid0 / solid state drive. I cannot install Linux there either, the raid is giving problems.
Even though the title didn't clarify it, the article was obviously written specifically for Windows-based PCs and their users/techs.
Your comment would be better suited to an article about maintaining or switching to Linux.
...and no, I'm not a Windows/Microsoft fanboy. I actually prefer Linux (at home, I usually use a dual-boot laptop), but it has its limitations, just as Windows does.
Your comment would be better suited to an article about maintaining or switching to Linux.
...and no, I'm not a Windows/Microsoft fanboy. I actually prefer Linux (at home, I usually use a dual-boot laptop), but it has its limitations, just as Windows does.
not off-topic. Installing Linux should have been the 6thtyip of speeding up a slow PC and get rid of all the **** mentioned in the first five
Yes the above measures are fine and it is surprising how many users neglect maintenance but less surprising when you remember how microsoft presented NTFS as not requiring regular defraging, etc.Still they left it on the system tools, I wonder why?
Roy.
Roy.
But it would not surprise me a bit if Bill took money from some developer to leave it off and let them handle it. Lack of such a tool in an operating system that DESPERATELY NEEDS such a tool is not an oversight. (I guess we are talking NT here.)
The defragmenter that you do get from MS is not particularly good. Maybe Bill developed a crappy one on purpose, too...
The defragmenter that you do get from MS is not particularly good. Maybe Bill developed a crappy one on purpose, too...
chkdsk X: /f /r, isn't working. its giving ""
'chkdsk' is not recognized as an internal or external command,
operable program or batch file.
""
error to me. (On windows Vista)
(I replaced X with C)
'chkdsk' is not recognized as an internal or external command,
operable program or batch file.
""
error to me. (On windows Vista)
(I replaced X with C)
Make sure you are typing it correctly.
chkdsk is a valid command. Try type chkdsk /? from the command prompt. The program resides in the c:\windows\system32 directory.
chkdsk is a valid command. Try type chkdsk /? from the command prompt. The program resides in the c:\windows\system32 directory.
Ok, It is working. Actually, i was executing this command right from user account, one have to change directory to c:\windows\system32.
(cd c:\windows\system32)
And also open command prompt as administrator.
Thanks.
(cd c:\windows\system32)
And also open command prompt as administrator.
Thanks.
This list has been posted 500 times on 500 different websites. No new information here.
The original list may not be completely new, but there is a lot of good information in the subsequent comments.
Of course, if you already know everything, you are a most fortunate fellow.
Of course, if you already know everything, you are a most fortunate fellow.
Get Linux, dump windoze. That automatically makes your PC faster and you never need to defrag or use anti-virus (save money). So get a clue and use a better operating system first.
This is trivial, but I find that as the swap file on my W2K machine gets larger, the machine runs more slowly. A restart -- usually needed once a week -- clears things.
I agree about the clean reinstall. It will often resolve all sorts of problems. Unfortunately, it can require days of work if you have a lot of installed apps.
I agree about the clean reinstall. It will often resolve all sorts of problems. Unfortunately, it can require days of work if you have a lot of installed apps.
That really slowed me down plus I don't do that many searches anyway. When I do search I use the dog and just wait a few seconds more.
The indexer does take a lot of system resources - especially on XP and Vista. They got a lot better in 7, but unless you use the search feature or store a LOT of documents locally, this is one to disable.
Yup . . . it always helps quite a lot. The other obvious maintenances and tweaks are no-brainers for sure, but disabling indexing always improves my performance.
Up until search 4.0 I would agree with you, but this version does have some value particularly if you use Outlook. It searches your PST files and presents the individual mail/calendar items within the search results. I have found this particularly useful. (I probably store too much in the PSTs rather than saving it as a file). And the v4 indexer is much less intrusive than in previous versions, throttling itself way back when user activity is detected. In my situation the benefits outweigh the costs.
A general ideal practice is to always seperate the OS partition from the user file's disk. Also, the disk partitioning utilities that ships with windows vista and windows 7 provides even more flexible ways to create additional partitions for user files and an important folder like the Program files that consumes space. You can mount the program files elsewhere on another partition. This always ensure that your OS partition size is always kept small and manageable and doesnt increase whenever an installation is done.
Olukorede Aguda
Olukorede Aguda
I have thought about doing this, but would the partition for the OS need to be C:? I do not want to change the default drive letter from C: to D: everytime I install a new program. I have heard of this being done, and wondered why computers do not come from the factory like this.
If you do the remap, so that the folder
C:\Program Files
Actually references D:\Program Files
Programs won't know the difference.
In the other way, when you install a program, always choose custom and change where it installs. Only a few programs don't allow themselves to be seperated, like virus scanners.
I traditionally install OS and scanner tools and such, things that always need to be running, services, etc. To my C drive. Games, files, documents, etc. I install to a different drive.
This keeps the excess programs away from the OS and makes rebuilding the computer much easier.
C:\Program Files
Actually references D:\Program Files
Programs won't know the difference.
In the other way, when you install a program, always choose custom and change where it installs. Only a few programs don't allow themselves to be seperated, like virus scanners.
I traditionally install OS and scanner tools and such, things that always need to be running, services, etc. To my C drive. Games, files, documents, etc. I install to a different drive.
This keeps the excess programs away from the OS and makes rebuilding the computer much easier.
Disable the themes services and remove all the ring and bells of effects in the Screen Control Panel addon.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
