Multitouch Features with Windows 7

Multitouch as an overall technology has really taken the world by storm, although that really has a lot more to do with Apple than it does with Microsoft. When people consider the Apple accomplishments in the field of Multitouch, the immediate conclusion that is reached has to do with the idea of Multitouch technology on the iPhone, one of the most successful computer hardware mobile products ever created.

windows 7 unofficial logoMultitouch has almost single-handedly allowed Apple back into the game and that is exactly why Microsoft has decided to get very serious with it, dedicating the biggest change introduced in Windows 7 as being one that has a lot to do with Multitouch technology.

Specifically, Microsoft is going to be introducing Multitouch functionality into the Windows 7 system, a sure sign that Microsoft has a number of things planned for Multitouch at some point in the near future. This is not surprising news in the least, but it is definitely news that goes a long way towards showing intent on the part of the highest echelon of power at Microsoft.

By incorporating Multitouch technology into their main flagship product, Microsoft has stated a desire to move beyond specialty products like the Surface and towards mainstream products that everyone can afford to buy. One can expect these mainstream products to start including Multitouch functionality at some point in the near future, since the operating system that will be running on those products will most certainly be able to support it. Lets see how it goes.

How to manually Remove BHOs

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

You can identify a spyware program that is loaded by using BHOs. To do this, you can use the Microsoft system configuration utility (Msconfig.exe) and the Microsoft system information utility (Msinfo32.exe).

BHOs are Component Object Model (COM) components that Microsoft Internet Explorer loads whenever it starts. BHOs run in the same memory context as the browser. BHOs can perform any action on available windows and modules.

To manually remove BHOs, follow these steps:

1. Click Start, click Run, type regedit , and then click OK.

2. Locate and then double-click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects

3. Under the Browser Helper Objects key, you may see ClassIDs (CLSIDs) that have a format that is similar to the following:

{XXXXXXXX - XXXX – XXXX – XXXX – XXXXXXXXXXXX}

Note CLSIDs are 128-bit numbers in hexadecimal notation that are enclosed in a pair of braces.

4. Note the CLSID.

5. Locate and then click the following registry subkey:

HKEY_CLASSES_ROOT\CLSID\{ CLSID }\InprocServer32

Note { CLSID } is the CLSID that you noted in step 4.

6. In the right pane, double-click (Default).

7. Click Value data to see the path of the .dll file. The path may be similar to the following:

C:\Windows\ Program_Name .dll

Note Program_Name can be a spyware program or a legitimate program that is using a BHO.

8. If Program_Name is not a recognized or legitimate program, unregister the .dll file, and then remove the { CLSID } subkeys. To do this, follow these steps:

a. At a command prompt, type the following command to unregister the .dll file:
regsvr32 -u Path \ Program_Name .dll

Note Path is the path of the Program_Name .dll file that is contained in the Value data box in step 7.

b. Locate and then delete the following { CLSID } registry subkeys:

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects\CLSID\{ CLSID }

• HKEY_CLASSES_ROOT\CLSID\{ CLSID }

Note { CLSID } is the 128-bit number that you noted in step 4.

9. Exit Registry Editor.

10. Restart the computer

More Available Search:
General causes of “STOP 0×0000007F” errors
How to enable cookies
computer repair
Install standard VGA compatible driver

How to Configure Device Manager

This Post describe and provide computer repair help for how to Configure Device Manager to Display Detailed Information. If you require additional device information that is not typically displayed in Device Manager, you can configure Device Manager to show detailed information.

To configure Device Manager to show details:

1. Click Start, click Run, type cmd.exe, and then press ENTER.
2. Type set DEVMGR_SHOW_DETAILS=1, and then press ENTER.
3. Type start devmgmt.msc, and then press ENTER. In Device Manager the properties for a device should now provide a Details tab that contains additional information about the device.

You can view the Details tab to see the following device information:

* Device Instance ID
* Hardware IDs
* Compatible IDs
* Matching Device ID
* Service
* Enumerator
* Capabilities
* Devnode Flags
* Config Flags
* CSConfig Flags
* Ejection Relations
* Removal Relations
* Bus Relations
* Device Upper Filters
* Device Lower Filters
* Class Upper Filters
* Class Lower Filters
* Class Installer
* Class Coinstallers
* Device Coinstallers
* Firmware Revision
* Current Power State
* Power Capabilities
* Power State Mappings

NOTE: Not all of these properties will be populated for a given device. In other words, although all of these properties are listed, some may not contain information when viewing a particular device.

How to install the Recovery Console

In this section I am going to discuss about How to Install Recovery Console. You can install the Recovery Console on your computer to make it accessible if you cannot restart Windows. You can then select the Recovery Console option from the list of available operating systems for the duration of startup. Install the Recovery Console on important servers and on the workstations of IT personnel. This addition describes how to install the Recovery Console to your Microsoft Windows XP-based computer. To install the Recovery Console, you have to be logged on as an administrator.

Although you can run the Recovery Console by starting directly from the Windows XP CD, it is generally more suitable to set it up as a startup option on your startup menu. To run the Recover Console directly from the CD, see the "How to use the Recovery Console" section.

Follow the steps given below:
1. Insert the Windows XP CD into the CD-ROM drive.
2. Click Start, and then click Run.
3. In the Open box, type d:\i386\winnt32.exe /cmdcons where d is the drive letter for the CD-ROM drive. In the case of 'Microsoft Windows XP Professional x64 Edition, type d:\amd64\winnt32.exe /cmdcons where d is the drive letter for the CD-ROM drive.
4. A Windows Setup Dialog Box appears. The Windows Setup Dialog Box describes the Recovery Console option. To confirm the installation, click Yes.
5. Restart the computer. The next time that you start your computer, "Microsoft Windows Recovery Console" appears on the startup menu.

Alternatively, you can use a Universal Naming Convention (UNC)-established connection to install the Recovery Console from a network share point.

Note You may receive an error message that is similar the following:
Setup cannot continue because the version of Windows on your computer is newer than the version on the CD.
Resolve this problems get use Microsoft Support Recovery Console on a Microsoft Windows XP Service Pack 2-based computer

More Related Search
How to fix OS/2 Family API Calls Problems
How to Manage devices with Device Manager
How to edit the Boot.ini file in Windows Server 2003
Computer Help
Troubleshooting Device Conflicts with Device Manager

How to create the registry key to restrict access to the registry

The Security permissions set on this key define what Users or Groups can connect to the system for remote Registry access. The default Windows installation defines this key and sets the Access Control List to restrict remote registry access as follows:

Administrators have Full Control
The default configuration for Windows permits only Administrators remote access to the Registry. Changes to this key to allow users remote registry access require a system reboot to take effect.

1. Start Registry Editor (Regedt32.exe) and go to the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
2. On the Edit menu, click Add Key.
3. Enter the following values:
Key Name: SecurePipeServers
Class: REG_SZ
4. Go to the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers
5. On the Edit menu, click Add Key.
6. Enter the following values:
Key Name: winreg
Class: REG_SZ
7. Go to the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
8. On the Edit menu, click Add Value.
9. Enter the following values:
Value Name: Description
Data Type: REG_SZ
String: Registry Server
10. Go to the following subkey.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
11. Select "winreg". Click Security and then click Permissions. Add users or groups to which you want to grant access.
12. Exit Registry Editor and restart Windows.
13. If you at a later stage want to change the list of users that can access the registry, repeat steps 10-12.

How to fix OS/2 Family API Calls Problems

This post provide computer help, If windows does not support OS/2 Family API.Windows and Windows 95 do not support 16-bit Windows-based applications coded with OS/2 Family API (FAPI) calls. To fix this error follow the instruction.

FAPI works in the following manner:

1. The code contains references to OS/2 FAPI calls (such as DosOpen, DosRead, and so on).
2. When the program is loaded into OS/2 protected mode, the system loader dynamically links the FAPI calls to the OS/2 system-services DLLs (Dynamic-Link Libraries).
3. When the program is loaded into real mode (MS-DOS or OS/2 compatibility box), what actually gets loaded is a small program called the "FAPI Loader and Linker." It is this program that loads the real code; it dynamically links the FAPI calls to a special library of support routines that translate FAPI calls into 80x86 code and MS-DOS interrupts (INT 21H Function xx).


FAPI works well for programs that need to run in MS-DOS and OS/2 protected mode. The problem is that Windows uses the "New EXE Format" for programs, bypassing the standard MS-DOS entry point. For example, if a Windows program is run outside of Windows (in MS-DOS), the following message appears, and the program terminates:

This program requires Microsoft Windows

MS-DOS is not responsible for this message; the Windows program itself is responsible. The way the Windows program works is very similar to OS/2: it uses dual entry points into the .EXE file. In MS-DOS, a short program that prints the above message runs; however, in Windows, a true Windows-based application runs using the other entry point in the .EXE file.

Therefore, the problem is narrowed down to the following: if the FAPI Loader and Linker program is run using the standard MS-DOS .EXE file entry point, and Windows starts an application using a different entry point, the dynamic linking of the FAPI routines will not occur.

To avoid this problem, do the following:

Instead of using low-level MS-DOS calls (INT 21H Function xx) in a Windows-based application and OS/2 API calls (DosRead, DosOpen, and so on) in a Presentation Manager (PM) application, use the C run-time I/O routines for all of these applications.

This will work because the Microsoft C Compiler and the run-time libraries supply versions of the libraries that work in both OS/2 and MS-DOS. By moving C code to PM and to Windows, it will not be necessary to rewrite it, and the appropriate conversion routines will be supplied at link time.

Remove and reinstall all USB controllers

This post describes how to remove or reinstall Universal Bus Controller (USB) devices in windows XP.

If you have a problem with a USB device, try these methods first:
1. Unplug and then plug in the device.
2. If the computer prompts you for a device driver, read the information that was included with the device, or visit the manufacturer's Web site to see whether a driver is available.
3. Run Windows Update to obtain the latest fixes for Windows XP. When this is complete, plug in the device to see whether it is installed correctly.

Because USB devices are Plug and Play devices, there is little that you can do to control or configure them. However, you can trace most USB problems to one of the following conditions:
• Malfunctioning or incorrectly-configured hardware
• Malfunctioning, incorrectly-configured, or missing device driver
• Mismatched cabling
• Out-of-date firmware or basic input/output system (BIOS)
• Incorrectly-configured root hub
You can use the following troubleshooting tips to check for each of these conditions to help you resolve USB device issues.

To remove and reinstall all USB controllers, follow these steps:
1. Click Start, click Run, type sysdm.cpl in the Open box, and then click OK.
2. Click the Hardware tab.
3. Click the Device Manager button.
4. Expand Universal Serial Bus controllers.
5. Right-click every device under the Universal Serial Bus controllers node, and then click Uninstall to remove them one at a time.
6. Restart the computer, and then reinstall the USB controllers.
7. Plug in the removable USB storage device, and then test to make sure that the issue is resolved.

Related Search:
How to manually optimize the memory usage
Disk cleanup tools in windows XP
Computer Support Canada
How to use system restore
Computer Support Services