When your pc goes wrong it is usually time to pay someone to fix it, or call in a big favour from your favourite computer geek of a friend. Sometimes though it's not always necessary to fall back on these two alternatives to repair your pc. There are an abundance of tools supplied with Windows, or for free download which you may be able to use to fix your own pc.
The first thing to realise before you start looking into fixing your own pc, is that most of the time it's a software fault, and not very often hardware related, so don't break out the hammer and chisel to open up the case just yet. It's time to stop, and consider when the fault first manifested itself. Had you just installed some new software or updates to your existing software? Have you downloaded a new Internet Explorer plugin or did anything request permission to install itself while you were surfing? Have you updated a device driver or installed some new hardware?
If the answer to these questions is "Why Yes, what harm could that possibly do?" then it could be that the culprit is a conflict with the new program or update. If so, then you could try using the software's uninstall link, or the "Add/Remove Programs" section in the Control Panel (Control Panel is linked from your start menu usually). If this doesn't work, you can always bring out the big gun, and use the "System Restore" utility. This can be found in the Start > Accessories > System Tools folder. This can be extremely scary the first time you use it with all kinds of warnings and texts to read, but basically it will roll back your computer to one of the previous dates it has stored. It doesn't delete documents or emails, just removes any software installed after the date you're going to reset to.
Sometimes your pc won't even get as far as Windows, but you can always try the "Safe Mode" (if it is setup). As your pc is starting up, keep tapping the "F8" key and you should get to a screen where you can select a variety of startup methods. Ignore all but the "Start In Safe Mode" option, and select the appropriate number for it and press "Enter". This stops a lot of unimportant stuff from loading up and may just allow you to get into Windows to use one of the options above (uninstall or System Restore). In this mode however you will not have access to many of your usual services, such as networks, or internet connections, and you may also find your soundcard drivers won't be loaded so you get no sound. Don't panic, this is normal, and after you reboot from Safe Mode to normal mode your peripherals should all return to normal.
A majority of the pc repairs I have carried out in my capacity as geeky friend have been as simple as using the tools and techniques above. There are also plenty of other tools hiding inside Windows menus, which can be used to help you repair your own PC. Like the ones above they can seem intimidating the first time, but they are quite safe to use, and rarely cause a problem. Just don't tell my friends about these tools, I like the feeling of superiority when I can fix their pc's with just a few clicks of the keyboard and mouse.
About The Author:
Douglas Titchmarsh tackles pc problems for friends, and maintains a PC repair related blog at http://www.douglastitchmarsh.com/PCPROBLEMS.blog and recommends PC Safety 101 ebook at http://www.thediscountebookstore.com/index.php?act=viewProd&productId=42
www.healthsector.com
www.christianmaters.com
Thursday, 26 March 2009
How To Speed Up Windows XP
The default install of Windows XP includes features and processes most users don't need. If you're involved in gaming or multimedia, and you can't afford a top-of-the-range PC, here are a few tips to get the most out of your machine.
For beginner users:
1. Go to: Start > Control Panel > Display > Settings.
Select: Resolution 800 x 600 pixels and Colour Quality Medium (16 bit).
Click: Apply.
What it does: Reduces system overhead. Less work for your CPU.
2. Go to: Start.
Right click: My Computer.
Select: Properties > 'Advanced' tab > Performance > 'Settings' button > 'Visual effects' tab.
Select: Adjust for best performance.
Click: Apply.
What it does: Removes unimportant cosmetic effects, thereby reducing system overhead.
3. Go to: Start.
Right click: My Computer.
Select: Properties > 'Advanced' tab > Performance > 'Settings' button > 'Advanced' tab.
Select: Processor scheduling > Programs.
Select: Memory usage > Programs.
Click: Apply.
What it does: Prioritises _your_ programs over those that XP _thinks_ are important.
4. Go to: Start > Control Panel > Display > Themes.
Select: Windows Classic.
Click: Apply.
What it does: Cleans up the desktop.
5. Go to: Start > Control Panel > Display > Desktop.
Select: Background - None.
Click: Apply.
What it does: Cleans up the desktop.
6. Go to: Start > Control Panel > Display > Appearance.
Select: Windows Classic Style.
Click: Apply.
What it does: Cleans up the desktop.
For Medium Users:
7. Go to: Start
Right click: My Computer.
Select: Properties > 'Automatic Updates' tab.
Select: Turn off automatic updates.
Click: Apply.
What it does: Stops Microsoft messing with your computer at inconvenient times. You can re-enable this when _you_ feel like an update.
8. Go to: Start > Run.
Type: msconfig
Select: 'Startup' tab.
Action: Untick all boxes, except those you are certain you need to start when XP boots up.
Click: Apply.
What it does: Stops programs starting when XP does. Frees up system resources.
For Advanced users:
9. Run your favourite program.
Click these buttons on your keyboard simultaneously: ctrl + alt + del (Control + Alt + Delete).
Click: 'Processes' tab.
Right click: The process of your favourite program.
Select: Set priority > Realtime.
What it does: Diverts CPU resources to the selected program.
10. Go to: Start > Run.
Type: services.msc
Right click: Any service you are sure you won't need, like 'Automatic Updates', 'Help and Support' or 'Indexing Services'.
Select: Properties > 'General' tab > Startup type > 'Manual' or 'Disabled'.
Click: Apply.
What it does: Stops processes starting when XP does. Frees up system resources.
Warning: Change one setting here a day. Reboot your system after each one. Run your most popular programs. If they're running normally, try disabling another service the next day. This is to make sure you don't turn off something important. If you're not sure, leave them alone.
Related programs:
Tune XP http://www.driverheaven.net/dforce/
This is freeware and simple to use.
X-Setup Pro http://www.x-setup.net/
This has a 30 day trial, and is for more advanced users.
Enjoy!
About The Author:
T. O' Donnell ( http://www.tigertom.com/secured-loans-uk.shtml ) is a credit broker and curmudgeon living in London, UK.
www.richempire.com
www.marriagecorner.com
For beginner users:
1. Go to: Start > Control Panel > Display > Settings.
Select: Resolution 800 x 600 pixels and Colour Quality Medium (16 bit).
Click: Apply.
What it does: Reduces system overhead. Less work for your CPU.
2. Go to: Start.
Right click: My Computer.
Select: Properties > 'Advanced' tab > Performance > 'Settings' button > 'Visual effects' tab.
Select: Adjust for best performance.
Click: Apply.
What it does: Removes unimportant cosmetic effects, thereby reducing system overhead.
3. Go to: Start.
Right click: My Computer.
Select: Properties > 'Advanced' tab > Performance > 'Settings' button > 'Advanced' tab.
Select: Processor scheduling > Programs.
Select: Memory usage > Programs.
Click: Apply.
What it does: Prioritises _your_ programs over those that XP _thinks_ are important.
4. Go to: Start > Control Panel > Display > Themes.
Select: Windows Classic.
Click: Apply.
What it does: Cleans up the desktop.
5. Go to: Start > Control Panel > Display > Desktop.
Select: Background - None.
Click: Apply.
What it does: Cleans up the desktop.
6. Go to: Start > Control Panel > Display > Appearance.
Select: Windows Classic Style.
Click: Apply.
What it does: Cleans up the desktop.
For Medium Users:
7. Go to: Start
Right click: My Computer.
Select: Properties > 'Automatic Updates' tab.
Select: Turn off automatic updates.
Click: Apply.
What it does: Stops Microsoft messing with your computer at inconvenient times. You can re-enable this when _you_ feel like an update.
8. Go to: Start > Run.
Type: msconfig
Select: 'Startup' tab.
Action: Untick all boxes, except those you are certain you need to start when XP boots up.
Click: Apply.
What it does: Stops programs starting when XP does. Frees up system resources.
For Advanced users:
9. Run your favourite program.
Click these buttons on your keyboard simultaneously: ctrl + alt + del (Control + Alt + Delete).
Click: 'Processes' tab.
Right click: The process of your favourite program.
Select: Set priority > Realtime.
What it does: Diverts CPU resources to the selected program.
10. Go to: Start > Run.
Type: services.msc
Right click: Any service you are sure you won't need, like 'Automatic Updates', 'Help and Support' or 'Indexing Services'.
Select: Properties > 'General' tab > Startup type > 'Manual' or 'Disabled'.
Click: Apply.
What it does: Stops processes starting when XP does. Frees up system resources.
Warning: Change one setting here a day. Reboot your system after each one. Run your most popular programs. If they're running normally, try disabling another service the next day. This is to make sure you don't turn off something important. If you're not sure, leave them alone.
Related programs:
Tune XP http://www.driverheaven.net/dforce/
This is freeware and simple to use.
X-Setup Pro http://www.x-setup.net/
This has a 30 day trial, and is for more advanced users.
Enjoy!
About The Author:
T. O' Donnell ( http://www.tigertom.com/secured-loans-uk.shtml ) is a credit broker and curmudgeon living in London, UK.
www.richempire.com
www.marriagecorner.com
Developing Software by the 15% Rule
Writing software on a consulting basis can often be a losing proposition for developers or clients or both. There are too many things that can go wrong, and that ultimately translates into loss of time and money. The “15% rule†we’ve come up with is intended to create a win-win situation for both parties (or at least make it fair for everyone). Clients generally get what they want, and development shops make a fair profit. It’s not a perfect solution, but so far it seems to be working for us.
This may come as a surprise to some, but we make very little money selling software licenses. The vast majority of our revenue comes through consulting services–writing code for hire. Having now done this for several years, we’ve learned some hard lessons. On a few projects the lessons were so hard we actually lost money.
A few months ago I put together somewhat of a manifesto-type document intended to address the difficulties we’ve faced in developing software for clients. I’m pleased to say that it’s made a noticeable difference so far for us. My hope is that this blog entry will be read by others who develop software on a consulting basis, so that they can learn these lessons the easy way rather than the way we learned them.
What follows in this article is a summary of one of the main principles we now follow in developing software–the 15% rule. If you’d like, you’re welcome to read the full “Our Approach to Software Development†document.
For the impatient, the 15% rule goes like this…
Before undertaking a development project we create a statement of work (which acts as a contract and a specification) that outlines what we’ll do, how many hours it will require, and how much it will cost the client. As part of the contract we commit to invest up to the amount of time outlined in the document plus 15%. That is, if the statement of work says that the project will take us 100 hours to complete, we’ll spend up to 115 hours (but no more). As to where-fores and why-tos on how this works, read on.
Those that have developed software for hire know that the end product almost never ends up exactly as the client had pictured. There are invariably tweaks that will need to be made (that may or may not have been discussed up front) in order to get the thing to at least resemble what the client has in mind. And, yes, this can happen even if you spend hours upon hours fine tuning the specification to reflect the client’s wishes. Additionally, technical issues can crop up that weren’t anticipated by the programming team. In theory, the better the programming team the less likely this should be, but it doesn’t always end up that way (Microsoft’s Vista operating system is a sterling example). These two factors, among others, equate to the risk that is inherent in the project. Something isn’t going to go right, and that will almost always mean someone pays or loses more money than originally anticipated. The question is, who should be responsible to account for those extra dollars?
Up until relatively recently, we would shoulder almost all of the risk in our projects. If the app didn’t do what the client had in mind, or if unforeseen technical issues cropped up, it generally came out of our pockets. For the most part it wasn’t a huge problem, but always seemed to have at least some effect (the extreme cases obviously being when we lost money on a project).
This seems kind of unfair, doesn’t it? The risk inherent to the project isn’t necessarily the fault of either party. It’s just there. We didn’t put it there, and neither did the client. As such, it shouldn’t be the case that one party shoulders it all. That’s where the 15% rule comes in.
The 15% rule allows both parties to share the risk. By following this rule, we’re acknowledging that something probably won’t go as either party intended, so we need a buffer to handle the stuff that spills over. By capping it at a specific amount, though, we’re also ensuring that the buffer isn’t so big that it devours the profits of the developers.
For the most part, the clients with whom we’ve used the 15% rule are just fine with it. It is a pretty reasonable arrangement, after all. We have had the occasional party that squirms and wiggles about it, but, in the end, they’ve gone along with it and I think everyone has benefited as a result.
Todd Wilson is the owner of http://www.screen-scraper.com, a small software development firm focused on web data extraction.
By Todd Wilson on: 2006-08-29 23:52:44
www.financialfreedom.com
www.testedonlinejobs.com
www.felyweb.com
This may come as a surprise to some, but we make very little money selling software licenses. The vast majority of our revenue comes through consulting services–writing code for hire. Having now done this for several years, we’ve learned some hard lessons. On a few projects the lessons were so hard we actually lost money.
A few months ago I put together somewhat of a manifesto-type document intended to address the difficulties we’ve faced in developing software for clients. I’m pleased to say that it’s made a noticeable difference so far for us. My hope is that this blog entry will be read by others who develop software on a consulting basis, so that they can learn these lessons the easy way rather than the way we learned them.
What follows in this article is a summary of one of the main principles we now follow in developing software–the 15% rule. If you’d like, you’re welcome to read the full “Our Approach to Software Development†document.
For the impatient, the 15% rule goes like this…
Before undertaking a development project we create a statement of work (which acts as a contract and a specification) that outlines what we’ll do, how many hours it will require, and how much it will cost the client. As part of the contract we commit to invest up to the amount of time outlined in the document plus 15%. That is, if the statement of work says that the project will take us 100 hours to complete, we’ll spend up to 115 hours (but no more). As to where-fores and why-tos on how this works, read on.
Those that have developed software for hire know that the end product almost never ends up exactly as the client had pictured. There are invariably tweaks that will need to be made (that may or may not have been discussed up front) in order to get the thing to at least resemble what the client has in mind. And, yes, this can happen even if you spend hours upon hours fine tuning the specification to reflect the client’s wishes. Additionally, technical issues can crop up that weren’t anticipated by the programming team. In theory, the better the programming team the less likely this should be, but it doesn’t always end up that way (Microsoft’s Vista operating system is a sterling example). These two factors, among others, equate to the risk that is inherent in the project. Something isn’t going to go right, and that will almost always mean someone pays or loses more money than originally anticipated. The question is, who should be responsible to account for those extra dollars?
Up until relatively recently, we would shoulder almost all of the risk in our projects. If the app didn’t do what the client had in mind, or if unforeseen technical issues cropped up, it generally came out of our pockets. For the most part it wasn’t a huge problem, but always seemed to have at least some effect (the extreme cases obviously being when we lost money on a project).
This seems kind of unfair, doesn’t it? The risk inherent to the project isn’t necessarily the fault of either party. It’s just there. We didn’t put it there, and neither did the client. As such, it shouldn’t be the case that one party shoulders it all. That’s where the 15% rule comes in.
The 15% rule allows both parties to share the risk. By following this rule, we’re acknowledging that something probably won’t go as either party intended, so we need a buffer to handle the stuff that spills over. By capping it at a specific amount, though, we’re also ensuring that the buffer isn’t so big that it devours the profits of the developers.
For the most part, the clients with whom we’ve used the 15% rule are just fine with it. It is a pretty reasonable arrangement, after all. We have had the occasional party that squirms and wiggles about it, but, in the end, they’ve gone along with it and I think everyone has benefited as a result.
Todd Wilson is the owner of http://www.screen-scraper.com, a small software development firm focused on web data extraction.
By Todd Wilson on: 2006-08-29 23:52:44
www.financialfreedom.com
www.testedonlinejobs.com
www.felyweb.com
Subscribe to:
Posts (Atom)
