How to fix Application Errors

Fix Corrupt Registry Files Yourself

Thursday, July 31st, 2008

In a computer, the registry is like the behind-the-scenes custodial staff that helps keep your computer and programs running smoothly, and stores information for your applications. If a member of the custodial staff were to quit, then your plans would not run as smoothly; just the same, if your registry files were to become corrupted or deleted, then you’d have some problems running your computer and the applications and programs installed on it. To recover from a corrupted registry, you can either use software to do it for you or boot into the registry yourself. I’m going to talk about how to recover the system on your own, and while this method doesn’t guarantee the full recovery of the system to its previous working state, you should be able to recover at least some files and information.

This method is typically used when all other methods have failed-if there’s an automatic system recovery, that is best, as manually booting into and editing your registry may result in many problems with your computer. But if you’re going to do it yourself, you can use two programs: Recovery Console, and System Restore. After the process, your computer should return to a state very near its state before the system error.

First, you need to start the Recovery Console, and then create a temporary folder. Then, you back up all of the current registry files to that new folder location and delete the current existing registry files (be SURE that you’ve backed them up first!) and copy the registry files from your repair folder to System32/Config. In this way, you’ve created a registry that your system can use at startup so that you can actually boot up your computer to complete the rest of the steps. Be sure that you are logged in as an administrator, because otherwise you won’t have access to the files and processes that you’ll need to access. Restart your computer in safe mode by pressing F8 as it is rebooting, and then make sure you unhide files and folders by selecting to Show Hidden Files and Folders, and also do not hide protected operating system files. Then, go to the System Volume Information folder located on your C drive that contains the system restore points on your computer (this is where you will need administrator access), and then you’ll need to copy the snapshots to the Windows/TMP directory.

Finally, you want to reboot the computer and restart Recovery Console yet again, and then replace the repair files with your now-current backup of the computer’s registry. Then, again, restart Windows in the normal (not safe) mode, and then use System Restore to find a good system backup point to return to. You can do this by going to Start, All Programs, and then clicking on Accessories, and System Tools. Under that, you’ll need to hit System Restore, and then Restore to previous Restore Point. This is correct, and then you should be done!

For more details on this process, go to support.microsoft.com/kb/307545.

Common Error Messages with Outlook Express

Tuesday, May 27th, 2008

Q. What are the most common problems with Outlook Express?

A. Users of Outlook Express are probably quite used to various error messages that occur from time to time. These can make little sense, but are actually quite common. One of the most frequently seen error message looks like this:

Outlook Express could not be started because Msoe.dll could not be initialized

There are a few others, but they are pretty much variations on a theme.

Q. Why do these errors commonly occur?

A. At times, there may simply be a glitch that causes OE to malfunction temporarily. In other cases, the software may be corrupted. This is common after a bad shutdown or if your computer crashes while OE is open. However, there are a few easy fixes that you can try.

Q. How do I fix this problem?

A. First, close OE and then shut down your computer. Do not use the Restart function, but do a complete shut down. Let it sit for a few minutes and turn it back on. Restart OE. If the problem occurs again, you may have a corrupted file. If not, it was merely a fleeting error and nothing to be worried about.

If the problem does keep occurring, here’s what you can do. First, close OE and then reopen it and select work offline. You don’t want any new mail messages coming in during this process. Go to File/Folders/Compact and run the compacting tool. This will usually solve minor problems and allow OE to rebuild it’s file structure. Once again, close OE and restart it.

Now, if the problem keeps occurring, chances are that your main DBX file is corrupt. Save any important email addresses and close OE. Now, go to your hard drive/program files/outlook express/Store folder. Look for all the DBX files in this folder. Create a new folder and put all of these files into it. Now, reopen OE and let it rebuild its own structure. It may take a few minutes to complete.

Although this fix is very effective, it will remove your old mail in most cases. However, it is usually the best way to get OE back on track.

Q. How do I keep from having this happen again?

A. Although you really can’t make OE behave beautifully you can take steps to minimize the damage it causes if you do get an error. Go back to where you found your DBX files and save all of them to a USB drive. Now, if the error occurs again, you will be able to simply use these files to overwrite the ones that are corrupt. Try to backup these files once a week or more often if you have a heavy volume of email. That way you can reduce the amount of mail that you lose if a crash occurs. Always remember to shut down OE properly by using the File/Close feature. Never leave OE open when you shut down your computer, since this is the number one cause for DBX file failures.