Comparing Registry Cleaners

There's been some recent discussion on the forum about Registry cleaners and it seems that many people consider them to be some kind of cure-all for slow machines or intermittent problems. Looking at the availability and marketing of such programs, it's easy to see why. A quick search found nearly 70 different offerings, including 25 or so free versions, though some of those offer free scans only. Curing the so-called 'problems' then costs money.

There are many sites offering comparisons of Registry cleaners - though most, it has to be said, are far from independent and their conclusions should be viewed with some degree of suspicion.

So, are they actually necessary? Personally, I'm with those that have their doubts. This is a quote from Wikipedia...

Most notably, critics say there is no reliable way for a third party program to know whether any particular key is invalid, redundant or neither. Poorly designed registry cleaners may not know for sure whether a key is still being used by Windows or what detrimental effects removing it may have. This has led to examples of registry cleaners causing loss of functionality and/or system instability. 

That said, problems can occur when Registry entries become corrupted or changed by malware or viruses, though I've yet to see any product that will cure those problems. Most products use a set of algorithms - effectively a set of instructions based on rules determined by the writer, and as every product is different, so will be the results.
There seems to be a view that the more 'problems' a program finds, the better it is. Again, that would depend on what the software writers have set as the search criteria. Some programs are much more aggressive than others, though whether they need to be is questionable. I get the feeling sometimes that the marketing of the product demands such fantastic results to supposedly raise it above others in the market.

It is true that uninstalled programs have a habit of leaving redundant entries behind which will eventually clutter the Registry, and cleaning it from time to time can only help. Whether it speeds up the operating system is debatable. It's also true that, as with a hard drive, data becomes fragmented - hence the appearance of products that will defrag the Registry. Again, in theory, that should speed things up, but probably only by a few milliseconds.

The majority of Registry defrag products run within the Windows environment which is hardly ideal when there are so many programs running and needing to access the Registry. The ideal option is to defrag before Windows loads, in the same way that chkdsk does. My preferred option is to use PageDefrag which does just that - either at each boot up, or on a one-off basis.

I recently had to clean out a machine loaded with XP SP2 after they clicked on a nasty.  It's now clean, but as it has never had even a defrag in 4 years, I thought I'd run a few tests comparing some Registry cleaners. The choice is based on what I had available so isn't in any way definitive, merely something to satisfy my curiosity.

I only compared four products, because to have an accurate comparison, I needed to restore each system from a backup image after each test, and that takes more time than I had available.

Products tested were Registry Mechanic, Ccleaner, Eusing and RegCure - each one in its latest version. The first stage was to simply run the scan options to see what the results were. The number of 'problems' found was as follows....

Registry Mechanic 1678
Ccleaner 963
Eusing 658
RegCure 858

Next stage was to run the fix option and restart. Results as follows....

Registry Mechanic
Refused to start reporting config/system error

Ccleaner
Started up OK, most programs ran fine, but froze when IE was started.

Eusing
Started up and ran OK. Tried most programs without problem.

RegCure
Started up and ran OK. Again no problems running programs.

Trying to compare what each program had actually done would also have taken far too much of my time, but the wide variation in 'problems' found would tend to confirm a more aggressive set of algorithms in Registry Mechanic and Ccleaner, leading to subsequent system problems.

Comparing the last 2, Eusing and RegCure, they performed much the same, being less aggressive, but one is free and the other isn't! That's not to say that under different circumstances on another machine, the results would be the same. It would depend on the system configuration and what software was installed.

Hopefully, what the tests achieved lends weight to the argument that Registry cleaning software can cause more problems than it cures, so should always be used with caution.

Let me add that I have no interest, commercially or otherwise, in any of the products tested, nor should the test results be seen as favouring one product over another.

I'm simply reporting what I found.

In my opinion, the best advice is NOT to run ANY registry cleaner, any time, anywhere!! 

Read more...

Fitting Broadcom WLAN card into Toshiba laptop

I post this here as a future point of reference to anyone installing a Broadcom 802.11g WLAN PCI network card in a Toshiba laptop that formerly had an Askey or Agere card fitted - both of which are now unavailable. Just plugging it in and loading the driver doesn't work. All you'll get is a 'No wireless networks detected'. That's because Toshiba configure the connector differently to other manufacturers.

The fix sounds strange but it works perfectly.

You need to cover contacts 11 and 13 on the card. All the contacts on the back of the card are numbered evenly, and on the front of the card, all contacts are odd numbers. You could cover contacts 11 & 13 with electrical tape, but it tends to slide off on insertion. I chose to simply cover them with a small strip of paper fixed with superglue which, if ever necessary, can be removed using a solvent. A more permanent solution would be to scrape the copper away very carefully.

To identify the correct contacts, holding the card with the connector strip at the bottom, you count left to right starting with 1, 3, 5, etc. Contacts 11 and 13 are right next to each other. See  image below for more detail.

Read more...

Useful advice for older Toshiba laptop users

I recently did a complete reinstall of XP on an old Toshiba Satellite laptop. The actual model was a P10-804, but that's not too important. All drivers were downloaded from the Toshiba site and all worked fine except the wireless card would not connect to a WPA protected signal. The original Toshiba driver was written before WPA was implemented so the only choice was WEP, which wasn't acceptable.

A search indicated that there was a driver available from a company called Agere a few years ago, but they've since been taken over by LSI and there is no trace of anything Agere on their site! After 4 days of dead links and discontinued websites, I eventually tracked it down. It was on a forum on a thread that was closed 3 years ago, but thankfully it worked. Downloaded it, updated the driver and the first time I tried to connect, I entered the WPA code and it connected immediately.

This same driver works for any laptop fitted with a wireless card designated as MPC13A-20/R and includes Toshiba, Gateway, Sony and others. The Toshiba part number is PA317U-1MPC, which is shown on base.

The driver can be downloaded from here

http://www.fileden.com/files/2009/12/25/2702341/windows_drivers_sr02-2.3.zip

I should add that these drivers will only allow connection via WPA. They will not increase connection speed from 11Mbps to 54Mbps. To do that, the card needs to be replaced with a later model, like a PA3299U-1MPC.

Once downloaded, unzip to a suitable location. There is no installer, so you need to go to Device Manager, right click the card entry and select Update Driver then navigate to the files you downloaded.

Read more...

Creating a bootable BitDefender Rescue USB drive

This tutorial is for creating a bootable USB Flash Drive containing BitDefender Rescue for use on a computer that will not boot up to Windows due to damage caused by virus, trojans, worms or rootkits.
It was compiled in association with EvilFantasy, a qualified Malware Removal expert and fellow volunteer at Help2Go.

Important! 

The loading process might take some time with a number of long pauses. Don’t think that it has stalled or isn’t working as it should. You just need to give it some time to finish.
Make sure your USB drive is already plugged in so that it is detected and selected automatically.
Read this tutorial carefully before beginning.

If you don’t know what you are doing or have any questions, stop and ask someone who does know! You can do damage to your  computer if the instructions are not followed correctly. I take no responsibility if the computer ends up damaged from using this tutorial, though it has been thoroughly tested, so be warned! 

Creating the BitDefender Rescue USB drive

Download the BitDefender Rescue CD to your desktop.
Choose the download titled BitDefenderRescueCD_xx.x.x_xx_xx_xxxx.iso, which is the first .iso link.

Download the Windows version of the UNetbootin – Universal Netboot Installer to your desktop, then double click the file to open it.

You’ll see the following screen. Select the options as shown.

Important! Check that the correct drive letter is selected for your USB Drive. If not, you may overwrite important data!

Click on OK to load the next screen. This shows each stage of the creation process. There will be some long pauses as the large files are extracted and copied, so be patient.

Once completed, you’ll see the following screen…

Do not click on the Reboot Now button! Simply click on the Exit button and remove the USB drive. The BitDefender Rescue USB drive is now ready for use.

Using the BitDefender Rescue USB drive

To use the bootable USB drive, simply plug into a USB port on the infected computer, and and then start the computer. During the boot process, choose USB or Removable Drive as the first boot option from system BIOS, or use the F8, F12 or ESC key during the boot process for the BIOS screen to choose the boot options. The choice of  F8, F12 or ESC key will depend on the make and model of the computer. Look at the screen when the startup first begins to determine what option you need to choose. Tapping the key during startup will activate the boot options.

If the above method does not work to boot the USB then see here. Common USB BIOS boot options. Beware!! Changing settings in the computer BIOS should only be attempted by skilled users. If you are unsure of what to do then ask someone who is.

You should not have to change any of the options during the boot process. Just let everything load and the scan will begin. On the very first menu, do not select  Console Mode  unless you are an advanced Linux user.

When the scan is complete, let BitDefender remove or quarantine anything found and then exit the BitDefender scanner.

Right click an empty space on the desktop and choose Exit from the menu. You will see Linux go through an unloading process. At the end, it will tell you to remove the CD from the CD/DVD drive but, using this method, you will remove the USB Drive instead. Next press the Enter/Return key on your keyboard to Exit and turn off the computer.

Restart the computer normally.

Note: If the booting from USB option isn’t available on your computer, you’ll need to boot from the CD/DVD drive using a CD burned from the BitDefender Rescue Disk.iso file that you downloaded originally.

You can also run a rootkit scan by double clicking the ChkRootKit icon from within the Linux/BitDefender desktop. Rootkits can be hard to remove so if a rootkit is found, try asking for help in removing it by visiting one of the computer help forums shown below.

Help2Go 

Computer-Juice

Computer Hope

Glitch PC

MajorGeeks

Ultimate Geek TaskForce

Please note

I am not qualified to advise you on removing any malware or visuses you may find,
so please don't ask. Instead, try posting your problem at one of the above forums.

Read more...

Adding Windows 7 computer to an existing XP/Vista network

One of the many new innovations included in Windows 7 is a much improved system of home networking called HomeGroup. As well as offering easier and more diverse allocation of permissions to shared content, access is protected by a password which, for small business networks, is a necessity.

As soon as Windows 7 is installed, it creates a default HomeGroup. If it detects an existing HomeGroup, you will be given the opportunity to join, but you will need the password. For home and small business users, HomeGroup is an excellent tool, but there is a problem.

HomeGroup only works when all other machines on the network have Windows 7 installed, which in the short term, may not be the case. There will be many situations where the network has XP or Vista machines as part of the network, in addition to Windows 7. So, how is it possible to get them all to work together?

Actually, it's not that difficult. The trick is to avoid the HomeGroup option which, by default, users are led into when trying to add a Windows 7 machine to an existing network, and do the following instead. These instructions assume that all machines are connected to a common hub/router, either cabled or wirelessly, and that all necessary permissions exist. If you are adding the Windows 7 machine to an existing network, that should already be the case. As this is aimed at home users, only the Workgroup option will be addressed.

First thing to do is note the name of the existing Workgroup, together with the password, if applicable. For this example, we'll use MSHOME, which is the Windows default. If yours is different, change as necessary.

On the Windows 7 machine, click on Start and right click Computer, then Properties. That will open the following window.

At the bottom of the window you'll see Computer name, domain, and workgroup settings. Click on Change Settings. This window will open.

Under the Computer Name tab, click the Change button. In the next window, select Workgroup and enter the name you copied earlier. Click on OK and you'll be prompted to restart.

You should now see your XP/Vista machines shown on the network, and shared files/folders will be accessible, but you may need the network password if one has been allocated. The Windows 7 machine will appear on the rest of the network, but when you try to access any shared files/folders, you'll probably be asked for a password. That's because, by default, Windows 7 requires you to enter one.

To turn that option off, open Network and Sharing Center and, in the left column, click on Change Advanced Sharing Settings. That will open the following window.

Scroll down to Password Protected Sharing, select Turn off Password Protected Sharing, then Save changes at the bottom of the window. You can change other settings in that same window, such as Printer Sharing, etc.

One final word, don't forget to set the sharing options on the Windows 7 machine.

Words and images, copyright arraknid 2009

Read more...