How to Restore Previous Versions of the Registry in Windows 7

If you want to manually restore a specific section of the registry from a previous System Restore snapshot, or access some specific keys from an older version of the registry, you can do so by getting access to those files and then exporting sections from them. Here’s how to do it in Windows 7 or Vista.

Since Windows 7 and Vista utilize Shadow Copy, otherwise known as Volume Snapshot Service, to power the “Previous Versions” feature, there are snapshots of important files taken over time, including registry hives, so we can access the older versions of registry files this way without having to do a full System Restore.

This article was jointly written by myself and Ramesh from WinHelpOnline, who has also covered how to do the same thing on Windows XP.

Access Previous Registry Hives from Shadow Copy

Important Note: before we get started, we should really give you a disclaimer: you should not use this technique unless you know what you’re doing and are willing to deal with possible problems, or at least have some good backups of your files. Still here? Read on.

The first thing you’re going to want to do is disable User Account Control, because you can’t really access the folders otherwise. Once you’ve done that and rebooted, open up a new Windows Explorer window and head to the following folder:

C:\Windows\System32\Config

Right-click anywhere in the white space area of the folder, choose Properties from the menu, and then click the Previous Versions tab. Once you’re there, double-click the appropriate folder (Hint: Look at the Date modified field to decide which version of the files you want to restore.)

Note: If you’re using Windows Vista Home editions and you want to do this, you’re going to need to use Shadow Explorer to get to these files.

Select the registry hive files you need, and copy them to a folder of your choice.

Click OK when you see the Windows Security prompt.

And now you should have a folder containing the backup registry keys.

Now that you have the backup versions of the registry, you can use them to access the older version.

Loading a Registry Hive and Accessing Specific Keys

At this point you can load the entire registry hive into the registry, which will make it a sub-key of one of the main sections, and allow you to access settings from the older version. Open up the Registry Editor using regedit.exe in the Start Menu search or run boxes, click on HKEY_LOCAL_MACHINE or HKEY_USERS, and then use File –> Load Hive.

You’ll be prompted to give the new hive a name—for this example I just used test.

And just like that, you can see the new key with the contents from last week’s backup copy. So, for instance, if one of the settings or license keys for an application was lost, we can find it by browsing through the keys for that application. You’ll have to manually make the changes if you’re doing just a few keys.

If you are trying to use this method to restore large chunks of the registry, you can export a key, modify the exported file to have the correct key path instead of Test, and then import it again. It’s a bit of a pain, but might be helpful if you need to.

Once you’re done, you should make absolutely certain to delete this entire key, or else it’s going to add a lot of extra bloat to your registry that you really don’t need.

Access the Previous Version’s Registry Keys Through the Command Line

Instead of loading the registry key using the GUI and adding all those keys to your current registry, you can use the RegFileExport tool from Nirsoft to access and extract the data from the backup files directly—you’ll just need to know the exact key that you’re looking for

So, for example, if you wanted to access the list of currently installed programs from the Programs and Features dialog. You’d run a command like this against the saved backup copy of the SOFTWARE registry hive—assuming you have the command-line application in the same directory as the backup file:

regfileexport SOFTWARE ExportedKey.reg "HKEY_LOCAL_MACHINE\SOFTWARE\
Microsoft\Windows\CurrentVersion\Uninstall"

This will generate a regular .reg file that you can either double-click to enter the contents into the registry, or you can open it up and find specific keys that you might want to use.

This method can actually be used to easily restore sections of the registry, should you need to. It’s probably most useful for restoring the sections pertaining to a specific application.

Again, you should be very careful when editing the registry, but at least you know a lot more than you did before.

Read More

Windows error code explanations

SUMMARY

This following information lists the Microsoft error codes that may be reported by Device Manager, with suggestions for possible resolutions. To view error codes, follow these steps:

Click Start, point to Settings, and then click Control Panel.
In Control Panel, double-click System.
Click the Device Manager tab.
Double-click a device type (for example, double-click Mouse) to see the devices in that category.
Double-click a device to view its properties. If an error code has been generated, the code appears in the Device Status box on the General tab. In some cases, there will be a Solution button (Windows 98 only).

Code 1
This device is not configured correctly. (Code 1)

To update the drivers for this device, click Update Driver. If that doesn't work, see your hardware documentation for more information.
Solution button: Update Driver
This code means that the system has not had a chance to configure the device. To resolve the problem, follow the instructions in the Device Status box. In addition, you may be able to resolve this issue by removing the device in Device Manager, and then running the Add New Hardware wizard from Control Panel.

Code 2
Depending on which device is failing, you may see either of two different messages. This code means that the device loader (DevLoader) did not load a device. When this device is a Root Bus DevLoader (for example, ISAPNP, PCI, or BIOS), the following message is displayed
Windows could not load the driver for this device because the computer is reporting two bus types. (Code 2)

Contact your computer manufacturer to get an updated BIOS for your computer.

Where is ISAPNP, PCI, BIOS, EISA, or ACPI.

Solution button: None
When the device is not a root bus DevLoader, the following message is displayed
The device loader(s) for this device could not load the device driver. (Code 2)

To fix this, click Update Driver to update the device driver.

Where is the DevLoader such as FLOP, ESDI, SCSI, and so on.

Solution button: Update Driver
In addition to following the recommended solution, try removing the device from Device Manager, and then running the Add New Hardware wizard.

Code 3
The driver for this device may be bad, or your system may be running low on memory or other resources. (Code 3)

To update the drivers for this device, click Update Driver. To check your computer's memory and system resources, right-click My Computer on your desktop, click Properties, and then click the Performance tab.
Solution button: Update Driver

As an alternative, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.

Code 4
This device is not working properly because one of its drivers may be bad, or your registry may be bad. (Code 4)

To Update the drivers for this device, click Update Driver. If that doesn't work, run Scanregw.exe (click Start, click Run, type Scanregw.exe, and then click OK) to check your registry.
Solution button: Update Driver

This code indicates that the .inf file for this device may be incorrect or the registry may be damaged. This error code is displayed if the .inf file specifies a field that should be text, but is binary instead.

In addition to following the recommended suggestions, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, please contact the hardware's manufacturer for an updated .inf file.


Code 5
The driver for this device requested a resource that Windows does not know how to handle. (Code 5)

To fix this, click Update Driver to update the driver for this device.
Solution button: Update Driver

This code indicates that there was a device failure due to the lack of an arbitrator. If a device requests a resource type for which there is no arbitrator, you receive this error code.

To resolve this problem, update the driver as suggested, or use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.


Code 6
Another device is using the resources this device needs. (Code 6)

To fix this, shut down your computer, turn it off, and then change the resources for this device. When you have finished, start Device Manager and change the resource settings for this device
Solution button: Hardware Troubleshooter

This code means that there is a conflict between this device and another device.

To resolve this error code, see the "Troubleshooting Conflicting Hardware" topic in Windows 95 Help, or see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q133240
TITLE : Troubleshooting Device Conflicts with Device Manager

Code 7

The message text that is displayed for this error is specific to the driver or enumerator. If the driver does not provide information as to why it failed, the following message is displayed:
The drivers for this device need to be reinstalled. (Code 7)

To reinstall the drivers for this device, click Reinstall Driver.

Solution button: Reinstall Driver

This code means that no configuration can be performed on the device.

If the device works correctly, you do need not to perform any steps to correct the code. If the device does not work correctly, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code and the device does not function properly, check with the hardware manufacturer for an updated driver.


Code 8

Several different error messages can be displayed for this error code. This code means that the device loader (DevLoader) for a device could not be found. For example, the .inf file for the device may refer to a missing or invalid file.

The following error situations are included in this error code:

A system DevLoader is one that is part of Vmm32.vxd, and typically begins with an asterisk (*). If the DevLoader is a system DevLoader, the following text is displayed
This device is not working properly because Windows cannot load the file that loads the drivers for the device. (Code 8)

To fix this problem, run Windows Setup again using your Windows CD-ROM.
Where is the system DevLoadert that cannot be found.

Solution button: None

If this is not a system DevLoader and the DevLoader cannot be found (the file is missing), the following text is displayed
This device is not working properly because Windows cannot find the file that loads the drivers for the device. (Code 8)

To fix this problem, click Reinstall Device to reinstall this device.
where is the DevLoader that is missing.

Solution button: Reinstall Driver

If this is not a system DevLoader and it can be found on the disk (the file does exist), the following text is displayed:
This device is not working properly because the file that loads the drivers for this device is bad. (Code 8)

To fix this problem, click Update Driver to update the drivers for this device."
Where is the name of the DevLoader.

Solution button: Update Driver

If the DevLoader entry is a software key for this device that is missing or an empty string, the following text is displayed:
Device failure: Try changing the driver for this device. If that doesn't work, see your hardware documentation. (Code 8)"
Solution button: Update Driver

For most cases, the resolution is to reinstall or update the driver. As an alternative, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, contact the hardware's manufacturer about updated drivers.

When the problem DevLoader is a system DevLoader, Windows should be re-installed because this driver is built into the Vmm32.vxd file.


Code 9
The text for this error code varies, depending on whether or not the device is BIOS/ACPI enumerated. If this is a BIOS or ACPI enumerated device, the following text is displayed:
This device is not working properly because the BIOS in your computer is reporting the resources for the device incorrectly. (Code 9)

Contact your computer manufacturer to get an updated BIOS for your computer.
Solution button: None

If this is not a BIOS or ACPI enumerated device (such as an add-in adapter or a device that was plugged in to the computer), the following text is displayed:
This device is not working properly because the BIOS in the device is reporting the resources for the device incorrectly. (Code 9)

Contact the device manufacturer to get an updated BIOS for your device.
Solution button: None

This code means that the information in the registry for this device is invalid.

It may be possible to resolve this error by using Device Manager to remove the device and then running the Add New Hardware tool in Control Panel. If you continue to receive this error code, contact the hardware's manufacturer for the proper registry settings or updated drivers.


Code 10

If the device has a "FailReasonString" value in its hardware key, that string is displayed as the error message. The driver or enumerator places this registry string value there. If there is no "FailReasonString" in the hardware key, the following generic error message is displayed:
This device is either not present, not working properly, or does not have all the drivers installed. (Code 10)

Try upgrading the device drivers for this device.
Solution button: Update Driver

To resolve this error code, make sure the device is connected to the computer correctly. For example, make sure all cables are plugged in fully and that all adapter cards are properly seated. Follow the suggested solution button and update the device driver. It may be possible to remove the device and redetect it using the Add New Hardware wizard.


Code 11
Windows stopped responding while attempting to start this device, and therefore will never attempt to start this device again. (Code 11)

For more information, look up ASD in Windows Help.

Try upgrading the device drivers for this device.
Solution button: Update Driver

To resolve this error, run the Automatic Skip Driver utility from the System Information tool. If the problem persists, contact the hardware manufacturer for updated drivers.


Code 12
This device cannot find any free resources to use. (Code 12)

If you want to use this device, you must disable another device that is using the resources this device needs. To do this, click Hardware Troubleshooter and follow the instructions in the wizard.

Where is a resource type (IRQ, DMA, Memory, or I/O).

Solution button: Hardware Troubleshooter

This code means that one of the resource arbitrators failed. This can occur if the device is software configurable and it does not currently have a resource (if the system is out of resources). For example, all the interrupts are in use, or the device requests a resource that is currently in use by another device that will not release the resource.

To resolve this problem, follow the instructions in the Hardware Troubleshooter. In addition, see the "Troubleshooting Conflicting Hardware" topic in Windows 95 Help, or see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q133240
TITLE: Troubleshooting Device Conflicts with Device Manager

Code 13
This device is either not present, not working properly, or does not have all the drivers installed. (Code 13)

To have Windows detect whether this device is present or not, click Detect Hardware.
Solution button: Detect Hardware

This code indicates that the device driver did not find the hardware.

To resolve this error code, follow the recommended solution. As an alternative, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.


Code 14
This device cannot work properly until you restart your computer. (Code 14)

To restart your computer now, click Restart Computer.
Solution button: Restart Computer

To resolve this error code, shut down Windows, shut down your computer, and then turn it back on.


Code 15
This device is causing a resource conflict. (Code 15)

To resolve the conflict, click Hardware Troubleshooter and follow the instructions in the wizard.
Solution button: Hardware Troubleshooter

This code means that the device's resources are conflicting with another device's resources, likely caused by re-enumeration.

To resolve this problem, follow the instructions in the Hardware Troubleshooter. In addition, see the "Troubleshooting Conflicting Hardware" topic in Windows 95 Help, or see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q133240
TITLE: Troubleshooting Device Conflicts with Device Manager



Code 16
Windows could not identify all the resources this device uses. (Code 16)

To specify additional resources for this device, click the Resources tab and fill in the missing settings. Check your hardware documentation to find out what settings to use.
Solution button: None

This code means that the device was not fully detected. When a device is not fully detected, all of its resources may not be recorded.

To resolve this error code, click the Resources tab in Device Manager to manually enter the settings.


Code 17
The driver information file is telling this child device to use a resource that the parent device does not have or recognize. (Code 17)

To fix this, click Update Driver to update the drivers for this device.
Where is the .inf file for the device.

Solution button: Update Driver

This code means that the hardware is a multiple-function device and the .inf file for the device is providing invalid information on how to split the device's resources to the child devices.

To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, please contact the hardware's manufacturer about an updated .inf file.


Code 18
The drivers for this device need to be reinstalled. (Code 18)

To reinstall the drivers for this device, click Reinstall Driver.
Solution button: Reinstall Driver

This code means that an error has occurred and the device needs to be reinstalled.

To resolve this issue, follow the recommended solution. If that does not work, try removing the device from Device Manager and then running the Add New Hardware Wizard in Control Panel.


Code 19
Your registry may be bad. (Code 19)

To check your registry, click Check Registry. If the registry is bad, Windows will restart your system and go back to a previous registry that is good.
Solution button: Check Registry

This code means that the registry returned an unknown result.

To resolve this issue, follow the recommended solution, which will run Scanreg.exe. If this does not resolve the issue, type "scanreg /restore" (without quotation marks) from a command prompt. Finally, remove the device from Device Manager, and then redetect it using the Add New Hardware tool in Control Panel.


Code 20
Windows could not load one of the drivers for this device. (Code 20)

To fix this, click Update Driver to update the drivers for this device.
Solution button: Update Driver

This code means VxD Loader (Vxdldr) returned an unknown result. For example, there could a version mismatch between the device driver and the operating system.

To resolve this issue, follow the recommended solution. If that does not work, try removing the device from Device Manager and then running the Add New Hardware Wizard in Control Panel.


Code 21
Windows is removing this device. (Code 21)

Close this dialog box, and then wait a few seconds. If this problem continues, restart your computer.
Solution button: Restart Computer

This code means that the device has a problem that may be resolved by restarting your computer.

To resolve this error code, shut down Windows, turn off your computer, and then turn it back on.


Code 22

The text displayed for this error code differs depending on the circumstances.
If this device is disabled because you disabled it using Device Manager, the following text is displayed:
This device is disabled. (Code 22)

Click Enable Device to enable this device.
Solution button: Enable Device

If the device is not started, the following text is displayed:
This device is not started. (Code 22)

Click Start Device to start this device.

Solution button: Start Device

If the device is disabled by a driver or program, the following text is displayed:
This device is disabled. (Code 22)

You can't enable this device because it has been disabled by a Windows driver.
Solution button: None
This code means that the device is either disabled or has not started.

To resolve this error code, follow the recommended solution. For the third case, try removing the device in Device Manager, then redetecting it using the Add New Hardware wizard. If the problem persists, try a clean boot to rule out software interference. If the error persists, contact the hardware manufacturer.


Code 23
The text displayed for this error code differs depending on the Circumstances.
If this device is a secondary display adapter and the primary display adapter was located, the following text is displayed:
This display adapter is functioning correctly. (Code 23)

The problem is with the main display adapter. To view the properties for the main display adapter, click Properties."
Solution button: Properties

If this device is a secondary display adapter and the primary display adapter cannot be located, the following text is displayed:
This display adapter is functioning correctly. (Code 23)

The problem is with the main display adapter. Fix the main display adapter, and then this display adapter will work.
Solution button: None

If this device is not a display adapter, the following text is displayed:
The loaders for this device cannot load the required drivers. (Code 23)

To update the device drivers, click Update Driver.
Solution button: Update Driver
This code means that the device loader delayed the start of a device and then did not inform Windows when it was ready to start the device.

To resolve this error code, verify the settings for the primary display adapter in Display properties. Try removing the primary and secondary display adapters from Device Manager, and then rebooting to allow Windows to re-enumerate these devices. Verify that the drivers are current and installed correctly.

For devices other than display adapters, follow the recommended solution. If that does not work, try removing the device from Device Manager and using the Add New Hardware wizard to redetect the device.


Code 24
The text displayed for this error code differs depending on the type of device (legacy or Plug and Play).
If this device is a legacy (root detected) device, the following text will be displayed:
This device is either not present, not working properly, or does not have all the drivers installed. (Code 24)

To have Windows detect whether this device is present or not, click Detect Hardware.
Solution button: Detect Hardware

If this is a Plug and Play device, the following text is displayed:
This device is either not present, not working properly, or does not have all the drivers installed. (Code 24)

Try upgrading the device drivers for this device.
Solution button: Update Drivers
This code means that the device was not found (for example, it is missing or is not working properly).

To resolve this error code, follow the recommended solutions. If the device still does not work, make sure the device is connected to your computer correctly. For example, make sure all cables are correctly installed, or that the adapter cards are properly seated in their slots.


Code 25
Windows is in the process of setting up this device. (Code 25)

To complete the setup, click Restart Computer to restart you computer.
Solution button: Restart Computer

This problem typically exists only during the first and second boots after Windows Setup copies all the files. As such, if this code is identified, it is likely an incomplete installation.

To resolve this issue, follow the recommended solution. Reinstalling Windows may be required, depending on whether or not the reboot resolves the issue.



Code 26
Windows is in the process of setting up this device. (Code 26)

To complete the setup, click Restart Computer to restart you computer.
Solution button: Restart Computer

This code means a device did not load. There may be a problem in the device driver or not all the drivers were installed.

To resolve this error code, follow the recommended solution. If this does not work, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, check with the hardware's manufacturer or the Microsoft Software Library for an updated driver.



Code 27
Windows can't specify the resources for this device. (Code 27)

Click the Resources tab, and then select the basic configuration for the resources this device uses. To see which resources this device uses, see the documentation for this device.
Solution button: None

This code means that the portion of the registry describing possible resources for a device does not contain valid entries. For example, the device is marked as configurable, but the configuration information in the .inf file is set to hardwired.

To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If the device still does not work, consult the hardware manufacturer for updated drivers or further assistance.



Code 28
The drivers for this device are not installed (Code 28).

To reinstall the drivers for this device, click Reinstall Driver
Solution button: Reinstall Driver

This code means the device was not installed completely.

To resolve this issue, follow the recommended solution. If that does not work, try removing the device from Device Manager and using the Add New Hardware wizard to redetect it. You may need to obtain updated drivers if the error still occurs.



Code 29
This device is disabled because the BIOS for the device did not give it any resources. (Code 29)

You must enable the device in the BIOS. See your hardware documentation for details, or contact your computer manufacturer to get an updated BIOS.
Solution button: None

This code means that the device has been disabled because the device does not work properly and cannot be made to work properly with Windows. This code may also be present if the device is intentionally disabled in the BIOS.

You may be able to resolve this error code by enabling or disabling the device in the computer's CMOS settings. Windows cannot override this setting. Please contact the computer's manufacturer for assistance with using the computer's CMOS configuration program.



Code 30
This device is using an Interrupt Request (IRQ) resource that is in use by another device and cannot be shared. You must change the conflicting setting or remove the real-mode driver causing the conflict. (Code 30)"
Solution button: None

This code means that an IRQ cannot be shared. This may occur when a PCI/EISA SCSI controller is sharing an IRQ that is also in use by a real-mode device driver that Windows cannot change.

To resolve this error code, remove the real-mode driver that is using the same IRQ as this device. The real-mode driver may be loading in the Config.sys or Autoexec.bat file.


Code 31 (new in Windows 98)
This device is not working properly because is not working properly. (Code 31)

To view the properties for and see why it is not working, click Properties."

Where is the dependent device that must be fixed in order for this device to work properly.

Solution button: Properties

This code appears when a device is dependent on another device to be functioning correctly. This does not include devices that are enumerated by the parent device.

The Properties button displays the properties for the other device. More than likely, the other device will also have one of these Device Manager error codes. Follow all the recommended solutions. If the devices still do not work, remove them from Device Manager and use the Add New Hardware wizard to redetect them. Finally, consult with the hardware manufacturer for updated drivers.


Code 32 (new in Windows 98)
Windows cannot install the drivers for this device because it cannot access the drive or network location that has the setup files on it. (Code 32)

To fix this problem, click Restart Computer to restart your computer. If that doesn't work copy all the setup files onto your local hard disk, and run setup from there.
Solution button: Restart Computer

This code indicates that the installation disk or CD-ROM was not available to install the drivers. For example, the CD-ROM drive or network connection is not available. This error typically occurs during the first or second reboot after all the files are copied during Setup.

To resolve this issue, first attempt to restart as suggested. If this does not resolve the problem, determine why the installation disk or CD-ROM is not available. Typically, these devices also have Device Manager codes (such as the CD-ROM controller or network adapter). Resolve the issue to gain access to the installation disk or CD-ROM prior to resolving this conflict.


Code 33 (new in Windows 98)
The message text that is displayed for this error is specific to the driver or enumerator. If the driver does not provide information as to why it did not work, the following message is displayed:
This device isn't responding to its driver. (Code 33)

For more information, contact your hardware vendor."
Solution button: None

This code typically is displayed when the hardware has failed.

Additional query words:

Keywords : kbenv kberrmsg kbhw win95 win98
Version : WINDOWS:2000,95
Platform : WINDOWS
Issue type : kbinfo

Read More

Computer with know USB trouble

The following list of machines have know USB issues. If you are unfortunate enough to be the owner of one of these lemons, follow the directions at the end of each computer model or contact the manufacturer.
E-Machine Model 336e

Unknown problems with USB devices.

The issue was resolved model 336i.

Contact the vendor.
Dell

Dell has stated in Dell knowledge base document FA1021802, that a USB device such as a scanner or printer may not be detected or function correctly when connected to the USB port of a Dell Latitude or Inspiron PC (it may occur on other models as well).

Various communication errors may occur, including device initialization and device not found errors.

Some Dell computers do not provide enough voltage from the USB ports to power some USB devices.

Dell recommends purchasing a powered USB hub to provide the USB devices with enough power to operate correctly. A USB keyboard with built in hub is not a solution and can worsen this problem.

Dell Inspiron 2650 has a known issue with the onboard O2Micro cardbus controller. Problems with cards attached to the controller are resolved by a patch found here

O2Micro Cardbus Controller Patch Information
Hitachi Visionbook Plus 4000 Series

USB is disabled on these machines due to problems on the laptop with power. The laptop does not properly support high-powered or bus-powered devices.

Work Around by using a different interface to connect the device to the PC, i.e. parallel, PS2 or Serial.
IBM 300GL or IBM 300PL

USB ports on 300GL/PL PCs may experience a communication problem known as jittering.

Contact IBM about replacing the motherboard.
NEC NX series

NEC NX series computers are equipped with a Legacy mode USB BIOS that allows the USB keyboard to work in real-mode. After suspending and then resuming the computer, or waking up the machine by using a USB keyboard/mouse, USB devices will not work after the computer is resumed.

This phenomenon is known as Plug/Unplug. Unplug the USB device that is not responding, wait 30 seconds, and reattach the device.
Quantex Computer

The USB is not enabled in the BIOS

Enter the CMOS Setup (BIOS)
Advanced Chipset
Enable USB by placing checkmark next to Passive Release.

Warning: Do not change any other settings in the BIOS, as doing so could cause other computer hardware not to work. Contact the PC vendor or manufacturer if you need assistance.
Toshiba laptops

Some older Toshiba laptops shipped with USB ports that used the NEC USB Host Controller HW Rev 000 and 001. This USB Host Controller has known issues that can not be corrected.

The following Toshiba laptops have this known problem:
Satellite 220, 300,310
Satellite Pro 440, 460, 470, 480
Portege 300
Tecra 520, 530, 540, 550, 750 CDT

Toshiba laptops with Revision 002 and later USB host Controllers do work correctly

Read More

Clean Install of Windows

A clean install of the OS is often the only way to get your system back on the right track or started on the right foot. The following is a simple guide on how to save your important stuff, get the job done right and make the transition as painless as possible.

A clean install of the Operating System is indicated when:

A New Motherboard is Installed

Upgrading Operating Systems (Avoids a lot of headaches later)

Irreparable Registry or System file corruptions exist in the existing Windows installation

HAL (Hardware Abstraction Layer) installed incorrectly (Win2000 & XP only)

Back-up Your Data

Before doing a clean install of Windows you will need to back-up your data files.

Backup your Email and Outlook Express Accounts

Outlook Express Data How To

Save your Documents

Create a new folder on the removable media of your choice i.e. Backup Documents

Left Click My Documents

Click Edit

Click Select All

Click Copy

Paste to the new backup folder that you created

Save your Internet Favorites

Open My Computer

Win 9x - Click on Windows folder of the bootable hard drive

Win XP & 2K - Click on My Documents

Right Click and Copy the Favorites Folder

Paste to the new backup folder that you created

Disconnect ALL peripheral devices except keyboard and mouse

Note: Don't forget to save information, pictures, scanned documents or other files like patches and updates that are stored in other locations.

Wipe the Hard Drive

Identify your hard drive make and model

Download the Wipe or Zero Utility from the Hard Drive Manufacturers Web Site. Wiping or Zeroing the drive will return it to factory fresh condition.

IBM

Western Digital

Seagate

Maxtor

Quantum

Fujitsu

When complete you will need to partition and format the hard drive. If you are going to use a single partition Windows will format and partition the hard drive during the OS installation process.

Multiple partitions can be made by using the manufacturers hard disk utilities or DOS.

Updating the BIOS

Updating the BIOS to the latest version is always a good idea when you are having system problems.

BIOS Agent - Free Software Reports Your BIOS Configuration from Windows

Go to your manufacturers web site. Some of the majors are listed below:

Abit

AOpen

Asus

BioStar USA

BTC (Behavior Tech)

ChainTech

Diamond

DFI

Epox

FIC

Gigabyte

Intel Corporation

JetWay

Lucky Star

MicroStar

PC Chips

Shuttle

Soyo

Tyan

Additional Motherboard Links

Download and install the latest officially released version of the BIOS that was specifically written for your motherboard. Follow the manufacturers installation instructions carefully.

Further BIOS assistance can be found here:

Wim's BIOS Page

BadFlash

BIOS Agent - Free Software Reports Your BIOS Details and Configuration

CTBIOS - Small DOS program that identifies the BIOS and motherboard - Program is in German but, you'll get the idea.



Make a BOOT Disk with CDROM Support

Download the boot disk image and click on the program file to extract to a floppy

Download Floppy Image

Removing ACPI

Reinstall Windows by starting the system using the boot floppy with CDROM support.

From the A:\ prompt start Windows from the CDROM

D:\setup /p i (When D:\ is the drive letter of the CDROM)

If your hard drive is running from a High Point, Promise or ATA 66 or 100 controller, the drive will not be recognized at bootup and you will need to come back a letter.



Drivers

Windows Me is the last version of the Win98 Operating System. Many Win98SE peripheral drivers will work on systems running the Me operating system, some will not. If you are experiencing problems with a USB device that requires non-native drivers, check with the manufacturer for a WinMe version of the software and drivers

Follow the Help directions for your Operating System and make a boot disk. Just in case you need it.

Reinstalling the Operating System

In the BIOS set the Drive Boot order to CD Only

Shut down and reboot

Follow the on screen prompts to install Windows

Installing Windows With ACPI Disabled

(Helps to resolve some USB problems)

Win 9X and ME

Boot Using the Boot Up Floppy

From the Command Prompt Type (Drive Letter):/Setup /p i

Win XP and 2K

Boot from the CD

When Windows begins to Detect the Hardware Press the F5 Key and choose the Standard PC HAL

When the installation is complete and before Windows starts for the first time, reset the Boot Devices in the BIOS so that Windows can boot from the hard drive.

Clean Install Using a Windows Update Version

Install as if Full Version

When Windows Install Wizard asks for verification of a previous version, place the previous version CD in the CDROM and follow the on screen prompts*

Read More

Open Device Manager

You can open Device Manager in any of the following ways:

• Using the Windows interface
  
  
• Using a command line
  
  
• Using Computer Management
  
  
• From a remote computer
  
  

Using the Windows interface

The following procedure allows you to open Device Manager through the Windows user interface.

To open Device Manager by using the Windows interface

1. Click Start, and then click Control Panel.

2. Click Hardware and Sound.

3. Click Device Manager. One of the following occurs:

   • If you are logged on as the built-in Administrator account, Device Manager opens.
     
     
   • If you are logged on as a user that is a member of the Administrators group, then the User Account Control dialog box appears, and you must clickContinue to open Device Manager.
     
     
   • If you are logged on as a standard user, a message appears indicating that you cannot make any changes to the devices. Click OK to open Device Manager in read-only mode.
     
     

Using a command line

The following procedure allows you to open Device Manager from any command prompt.

To open Device Manager by using the command line

• At a command prompt, in the Start Search box, or in the Run box, type the following command:

  mmc devmgmt.msc

  One of the following occurs:

  • If you are logged on as the built-in Administrator account, Device Manager opens.
    
    
  • If you are logged on as a user that is a member of the Administrators group, then the User Account Control dialog box appears, and you must clickContinue to open Device Manager.
    
    
  • If you are logged on as a standard user, a message appears indicating that you cannot make any changes to the devices. Click OK to open Device Manager in read-only mode.
    
    

Using Computer Management

The following procedures allow you to open Computer Management, which includes Device Manager as one of its components.

Note
This procedure works only on Windows Vista. On Windows Server 2008, these steps start the Server Manager program. To start Computer Manager on Windows Server 2008, use the steps in the next procedure by using the command prompt.

To open Computer Management by using the Windows interface

1. Click Start, then right-click Computer, and then click Manage.

   One of the following occurs:

   • If you are logged on as the built-in Administrator account, Computer Management opens.
     
     
   • If you are logged on as a user that is a member of the Administrators group, then the User Account Control dialog box appears, and you must clickContinue to open Computer Management.
     
     
   • If you are logged on as a standard user, Computer Management opens.
     
     

2. Click Device Manager in the navigation pane.

   One of the following occurs:

   • If you are an administrator, Device Manager appears in the details pane.
     
     
   • If you are a standard user, a message appears indicating that you cannot make any changes to the devices. Click OK to open Device Manager in read-only mode in the details pane.
     
     

To open Computer Management by using the command line

1. At a command prompt, in the Start Search box, or the Run box, type the command:

   mmc compmgmt.msc

   One of the following occurs:

   • If you are logged on as the built-in Administrator account, Computer Management opens.
     
     
   • If you are logged on as a user that is a member of the Administrators group, then the User Account Control dialog box appears, and you must clickContinue to open Computer Management.
     
     
   • If you are logged on as a standard user, Computer Management opens.
     
     

2. Click Device Manager in the navigation pane.

   One of the following occurs:

   • If you are an administrator, Device Manager appears in the details pane.
     
     
   • If you are a standard user, a message appears indicating that you cannot make any changes to the devices. Click OK to open Device Manager in read-only mode in the details pane.
     
     

From a remote computer

To open Device Manager on a remote computer

1. Open Computer Management using either of the procedures in the previous section.

2. On the Action menu, click Connect to another computer.

3. In the Select Computer dialog box, do one of the following:

   • In the Another computer text box, type the name of the computer to access, and then click OK.
     
     
   • Click Browse, and then click Advanced to find the computer you want. Click OK when you have selected the correct computer.
     
     

   If the connection is successful, the name of the computer appears in parentheses next to the Computer Management label in the upper left.

   Note
   Access to Device Manager on a remote computer in this manner is "read-only." You cannot make any changes to devices or their settings.

Read More

Computer Icon

New icon sets Vista Web Design Icons (5 icons) Author: Iconshock - Icon Sets Posted: October 6th, 2010 Education Icons (6 icons) Author: Iconshock - Icon Sets Posted: October 5th, 2010 Toolbar Icons (6 icons) Author: AvoSoft Posted: October 4th, 2010 Green Stuff Icons (5 icons) Author: Seanau.com Posted: October 2nd, 2010 Pool Ball Icons (16 icons) Author: barkerbaggies Posted: September 30th, 2010 Speech Balloon Orange Icons (26 icons) Author: Iconexpo Posted: September 30th, 2010 Speech Balloon Grey Icons (26 icons) Author: Iconexpo Posted: September 30th, 2010 Um Icons (187 icons) Author: Mattahan Posted: September 29th, 2010 Multipurpose Alphabet Icons (260 icons) Author: Supratim Nayak Posted: September 28th, 2010 Speech Balloon Green Icons (26 icons) Author: Iconexpo Posted: September 27th, 2010 Red Orb Alphabet Icons (51 icons) Author: Icon Archive Posted: September 27th, 2010 Bag O Tiles Icons (27 icons) Author: barkerbaggies Posted: September 27th, 2010

Read More

What's the Difference Between JPG, PNG, and GIF?

As we keep building on old image technology, types of file formats keep piling up, each with their own nuances and uses. JPG, PNG, and GIF have become the most common of these because of their compatibility with modern web browsers, broadband speeds, and the needs of average users. But what sets them apart from each other?

JPG

JPG was a filetype developed by the Joint Photographic Experts Group (JPEG) to be a standard for professional photographers. Like the method ZIP files use to find redundancies in files to compress data, JPGs compress image data by reducing sections of images to blocks of pixels or “tiles.” JPG compression has the unfortunate side effect of being permanent, however, as the technology for the file was created for storing large photographic image files in surprisingly small spaces, and not for photo editing. JPGs have become the de facto standard image of the internet because they can be compressed so much. A typical JPG can be compressed at a ratio of anywhere from 2:1 to as high as 50:1, depending on your settings. Particularly back in the days of dial-up internet, JPGs were the only viable way to send image information. However, because of the lossy nature of JPG, it is not an ideal way to store art files. Even the highest quality setting for JPG is compressed, and will change the look of your image, if only slightly. JPG is also not an ideal medium for typography, crisp lines, or even photographs with sharp edges, as they are often blurred or smeared out by anti-aliasing. It is common to see these things saved as JPG, simply because the filetype is so ubiquitous. [caption id="" align="alignnone" width="520" caption="Close up of a high quality JPG."][/caption] [caption id="" align="alignnone" width="520" caption="Close up of a very lossy JPG."][/caption] The Joint Photographic Experts Group developed lossless JPG technology to combat this serious problem of quality degradation. However, because of dial-up speeds and general lack of interest in high quality non-degrading files, the JPG-LS standard never caught on. It is possible to download plugins that allow users to open and save the lossless JPG2000, and some programs, like Apple’s Preview application, can read and save JPG2000 directly out of the box. JPGs support 24-Bit RGB and CMYK, as well as 8-bit Grayscale. I personally do not recommend using CMYK color spaces in JPGs. It’s also important to note that Grayscale JPGs do not compress nearly as much as color ones do.

GIF

GIF, like JPG, is an older filetype, and one generally associated with the internet as opposed to photography. GIF stands for “Graphics Interchange Format” and employs the same lossless LZW compression that TIFF images use. This technology was once controversial (for patent enforcement issues) but has become an accepted format since all patents have expired. [caption id="" align="alignnone" width="520" caption="Close up of an 8-bit color GIF."][/caption] GIF is by nature an 8-Bit color file, meaning they are limited to a palette of 256 colors, which can be picked from the RGB color model and saved to a Color Look Up Table, or CLUT. There are, however, standard color palettes, like the “Web Safe” palette. Apart from support for transparency, GIF also is supports animations, limiting every frame to 256 preselected colors. While GIF is not lossy like JPG, conversion to 8-Bit color distorts many images, using dither filters to optically blend, or “diffuse,” colors, similar to halftone dots or pointilism. This can radically alter an image for the worse, or, in some cases, create an interesting effect. GIF is not ideal for modern photography, nor image storage. At small sizes with very limited color tables, GIF images can be smaller than JPG files. But at most ordinary sizes, JPG compression will create a smaller image. They are largely out of date, useful only to create dancing babies or to sometimes create rough transparencies.

PNG

PNG stands for Portable Network Graphics (or, depending on whom you ask, the recursive “PNG-not-GIF”). It was developed as an open alternative to GIF, which used the proprietary LZW compression algorithm discussed earlier. PNG is an excellent filetype for internet graphics, as it supports transparency in browsers with an elegance that GIF does not possess. Notice how the transparent color changes and blends with the background. Right-click the image to see. This is actually one image that is on four different background colors. PNG supports 8-bit color like GIF, but also supports 24-bit color RGB like JPG. They are also non-lossy files, compressing photographic images without damaging image quality. PNG tends to be the biggest of the three filetypes and isn’t supported by some (usually older) browsers.

Which to use?

From left to right, these files are: 24-Bit JPG Compressed, 8-Bit GIF, 8-bit PNG, Full Quality 24 Bit JPG, and 24-Bit PNG. Note that the file sizes increase in this same direction. PNG is the largest image type for bigger images as it contains unneeded information for transparency in an extra channel. 8-Bit PNG is an option, but GIF is smaller. Neither one are good options for photography, as JPG is much smaller than lossless PNG with only minimal loss of quality. And for storage of high resolution files, JPG compresses to tiny proportions, with quality loss only visible on close inspection. In short:

• PNG is good option for transparency and non-lossy, smaller files. Larger files, not so much.
• GIF is largely a novelty and only useful for animation, but can produce small 8-Bit images.
• JPG is still the king for photographs and photo-like images on the internet.

Read More