Dell Touchpad Stops Functioning after Windows Update

Users encounter non-functioning touchpad after a Windows Update called: IdeaCom Technology Inc IdeaCom Touch Screen. Both affect Windows XP and Vista platforms. Moreover, there have been reports with multiple system manufacturers who are experiencing this issue.

To fix this, follow the following steps to undo the update (these are keyboard strokes in case the user can no longer his/her touchpad or doesn’t have any external mouse available):

1. For Vista: Press the Windows logo key to open the Start menu and then type device. For XP: Press the Windows+R to open the Run window and then type devmgmt.msc and press Enter.
2. In Vista, use the Down arrow key if necessary to select Device Manager from the search results list and press Enter. (If XP, skip to step 4.)
3. If you see a UAC prompt, press the Left arrow key to move the focus to the Continue button, and then press Enter. (Step 3 only applies with Vista)
4. Press Tab to move the focus into the device list. Use the Down arrow key to move to the Human Interface Devices category, press the Right arrow key to expand that category, and then use the Down arrow key to select the IdeaCom device.
5. Press Enter to open the shortcut menu for this device (or use Shift+F10, which is the universal keyboard shortcut that simulates a right-click, and then use the arrow keys to select Properties from the menu and press Enter).
6. From the Device dialog box, press Ctrl+Tab to move through the tabs until the Driver tab is visible.
7. Note that the R is underlined on the Roll Back Driver button text, indicating that it is an accelerator key. Press Alt+R to begin the driver rollback.

Plugging an external mouse should allow cursor movement. If the customer has a mouse, then perform the following steps after plugging in the mouse:

1. Open My Computer and go to the following location: C:\windows\system32\drivers.
2. Find a file named idcphid.sys and rename it to idcphid.old.
3. Now uninstall the IdeaCom HID Touch Screen (PS/2) driver under Human Interface Devices in Device Manager.
4. Restart computer.

That should completely remove the Windows Update and should revert to original touchpad/mouse properties before the update.

New Vista updates available for compatibility and reliability issues.

Issue Description:
On OptiPlex™ systems with the AMD Radeon HD Pro and Radeon 2400 XT, the following symptoms may occur:

System freeze: Displays as a black or blank screen.
Video corruption: If one or more displays are connected, the screen displays black or white vertical lines across.
Blue screen error: STOP 0xEA with the ati2dvag module as the source.
NOTE: Ati2dvag means the computer has caught the ati2dvag bug. This bug seems to affect ATI video cards.

Solution:
OptiPlex computers require updates to the driver and Video BIOS if the following conditions are true:

The computer was manufactured prior to October 12th, 2007
The computer has an AMD Radeon HD 2400 PRO or HD 2400 XT video adapter

To resolve the potential bluescreen error and computer lockup, update to at least version 8.42 of the AMD graphics driver. Use the following link on the Dell support website for downloading the updates:

Radeon HD 2400 PRO Windows® XP driver: R168671.EXE
Radeon HD 2400 XT Windows® XP driver: R168681.EXE

Computers showing corrupt video can be resolved with an updated Video BIOS (VBIOS). Use the following link for downloading the BIOS update for the adapter in your computer:

Radeon HD 2400 PRO Video BIOS: R169419.EXE
Radeon HD 2400 XT Video BIOS: R169410.EXE

Microsoft Hotfix updates to VISTA for Direct X 10 and Mutiple Graphics Card (SLI) problems

Problem:
Microsoft Hotfix updates to VISTA for Direct X 10 and Mutiple Graphics Card (SLI) problems.

Discussion:
Two Hotfixs that may be of extreme interest to your customers.

Microsoft has released two hotfixes for the issues with Direct X 10 Games and Multiple Graphic card usuage in Vista. This will probably be more apparent for the XPS lines but any game running in Vista may be affected.

Virtual address space usage in Windows game development

http://support.microsoft.com/kb/940105

Systems with large amounts of ram (2GB or more) may actually be affected more than systems with less ram due to this limitation. ( 2 GB+ ram machines are going to see this help a lot more than our basic 512mb machines)

When a DirectX 10 application runs on a Windows Vista-based computer that has multiple graphics cards, the computer does not use the secondary graphics card

http://support.microsoft.com/kb/936710/

For those SLI machines this may be critical for game errors and general issues.

You can easily get the download link emailed to you to test out the fixes yourself or give the link to the customer to get without having to call MS for any hotfix that is published and public

https://support.microsoft.com/contactus2/emailcontact.aspx?scid=sw;en;1410&WS=hotfix

Availability of the Windows Vista Secure Digital (SD) rollup package

INTRODUCTION
This article describes the new features and the fixes that are contained in the Windows Vista Secure Digital (SD) rollup package.
Back to the top

New features that are enabled in this package
The following new features are enabled in this package: • Support for SD High Capacity (SDHC) cards that are 8 gigabytes (GB) or larger in Windows Vista.
• Support for dual voltage (1.8-volt and 3.3-volt) Secure Digital/MultiMediaCards (SD/MMC) cards in Windows Vista.
• Support for Secure Digital Input Output (SDIO) cards in Windows Vista.

SDIO cards use an interface that adds functionality for a range of devices, such as GPS devices, Ethernet adapters, Wi-Fi or Bluetooth adapters, modems, scanners, fingerprint readers, bar-code readers, IrDA adapters, FM radio tuners, TV tuners, digital cameras, hard drives, and so on.
Note Specific hardware is required to take advantage of these new features. For example, the computer must have a supported SD Controller to use SDHC, SDIO SD, or MMC cards.
Back to the top

Issue that is fixed in this package
In addition to the new features that are enabled, this package fixes a problem in which the SD card may occasionally stop responding after a Windows Vista-based computer resumes from sleep (S3) or from hibernation (S4).
Back to the top

MORE INFORMATION
To install the Windows Vista SD rollup package, visit the following Microsoft Web site:
http://windowsupdate.microsoft.com (http://windowsupdate.microsoft.com)
The following files are available for download from the Microsoft Download Center:

Update for Windows Vista (KB936825)
Download the KB936825 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=E42FC131-6A76-4B27-934A-FB19DD323DAB)
Update for Windows Vista for 64-bit systems (KB936825)
Download the KB936825 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=B4DFE7B5-F2B8-47F1-982F-7EFA1A1BC83E)

Release Date: May 8, 2007

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 (http://support.microsoft.com/kb/119591/) How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

HOW TO: Enable the build-in Administrator account in Windows Vista

Problem:
HOW TO: Enable the build-in Administrator account in Windows Vista.

Resolution:
To enable the build-in Administrator account, follow these steps:
1. Click Start, and then type cmd in the Start Search box.
2. In the search results list, right-click Command Prompt, and then click Run as Administrator.
3. When you are prompted by User Account Control, click Continue.
4. At the command prompt, type net user administrator /active:yes, and then press ENTER.
5. Type net user administrator , and then press ENTER.
Note: Please replace the tag with your passwords which you want to set to administrator account.
6. Type exit, and then press ENTER.
7. Log off the current user account.

Error message when you start a Windows Vista-based computer after you change the SATA mode of the boot drive.

Problem:
Error message when you start a Windows Vista-based computer after you change the SATA mode of the boot drive: "STOP 0x0000007B INACCESSABLE_BOOT_DEVICE"

Symptom:
Consider the following scenario. In the BIOS setup of a Microsoft Windows Vista-based computer, you change the Serial Advanced Technology Attachment (SATA) mode of the boot drive to use the Advanced Host Controller Interface (AHCI) specification. You then restart the computer. In this scenario, you receive the following error message: STOP 0x0000007B INACCESSABLE_BOOT_DEVICE.

Discussion:
This issue occurs if the AHCI driver (Msahci.sys) in Windows Vista is disabled. This driver must be enabled before you change the SATA mode of the boot drive.

Resolution:
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.To resolve this issue, enable the AHCI driver in the registry before you change the SATA mode of the boot drive. To do this, follow these steps: 1. Exit all Windows-based programs.
2. Click Start, type regedit in the Start Search box, and then press ENTER.
3. If you receive the User Account Control dialog box, click Continue.
4. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci
5. In the right pane, right-click Start in the Name column, and then click Modify.
6. In the Value data box, type 0, and then click OK.
7. On the File menu, click Exit to close Registry Editor.

Screensaver not working on a VISTA-based computer.

Problem:
The screen saver does not work when you use a Microsoft wireless pointing device on a Windows Vista-based computer

Description:
When you use a Microsoft wireless pointing device that uses Microsoft IntelliPoint software on a Windows Vista-based computer, you may notice that the screen saver of the computer does not work even though it is configured to run.

Solution:
To resolve this issue, plug in a wireless receiver, and then check for updates.
To do this, visit the following Microsoft Windows Update Web site: http://windowsupdate.microsoft.com/
Install the Optional Hardware Update that is named Microsoft HID Non-User Input Data Filter.
Microsoft Link: http://support.microsoft.com/kb/911895

System boots directly to Windows Advanced Options Menu.

Problem:
System boots directly to Windows Advanced Options Menu

Description:
System wont boot directly to Windows Vista, whenever the system restarts it boots to the Windows Advanced Options Menu.

Solution:
1. Run Msconfig
2. Select the Boot Tab
3. Uncheck Safe Boot
4. Click Apply, then Click Close
5. Restart the system for the changes to take effect

Why Does Microsoft® Windows Vista™ Report Less than the Actual Amount of Memory Installed?

Problem:
Why Does Microsoft® Windows Vista™ Report Less than the Actual Amount of Memory Installed?

Discussion:
Windows Vista automatically allocates a certain amount of memory for system use. The amount varies but is at least 1 MB. Only the unallocated memory is reported by Windows Vista programs (e.g., Welcome Screen, System Information, System).

Resolution:
On a system configured with 4 GB of random-access memory (RAM), Microsoft® Windows® reports 3.0 to 3.8 GB of available memory. The same behavior is seen in Linux and other operating systems, as this is a limitation of 32-bit addressing used in IA-32 systems.

Note: At this time, Dell portable systems reserve 1 GB of memory for input/output (I/O) space in the basic input/output system (BIOS), making the total memory available 3,000 MB, which equals 3 GB. This is set in the BIOS and cannot be changed by the user.

You may be prompted to activate Windows Vista on a computer on which Windows Vista was already activated by a Volume License or OEM installation

Problem:
You may be prompted to activate Windows Vista on a computer on which Windows Vista was already activated by a Volume License or OEM installation.

Symptom:
You may be prompted to activate Windows Vista on a computer on which Windows Vista activation was not previously required. For example, this problem may occur on a computer where Windows Vista was preinstalled by an OEM or by using a Volume Licensing installation. The problem does not occur on Retail versions of Windows Vista. For example, the problem does not occur if you purchased Windows Vista and installed the operating system on a computer yourself.

Although this problem rarely occurs, it may occur during typical use of a Windows Vista-based computer.

Discussion:
This problem may occur because a specific system setting is removed when a program runs with administrative credentials. The removal of this system setting may cause a BIOS validation check to fail. The BIOS validation check is part of the system activation process. Therefore, you may be prompted to activate Windows Vista, even though the system did not previously require activation. For example, this problem is known to occur when you use Intuit QuickBooks 2007. However, this problem may also infrequently occur when you install other programs or device drivers.

Note This problem does not occur because of an issue in the installed program or device driver. This problem is caused by a system problem in Windows Vista.

Resolution:
To resolve this problem if it has already occurred, use one of the following methods:

*If you have been prompted to activate Windows Vista, and you have not used the product key to manually activate Windows Vista, install update 931573, and then restart the computer.

*If you have been prompted to activate Windows Vista, and you have used the product key to manually activate Windows Vista, install update 931573, and then activate Windows Vista by telephone.

Note If Windows Vista was preinstalled by an OEM, the product key appears on a sticker on the case of the computer.

For more information about how to activate Windows Vista, click the following article number to view the article in the Microsoft Knowledge Base:

925616 (http://support.microsoft.com/kb/925616/) Error message when you start Windows Vista: "Your activation period has expired"

*To prevent this problem, install update 931573. To do this, visit the following Microsoft Web site: http://windowsupdate.microsoft.com (http://windowsupdate.microsoft.com)

The following files are available for download from the Microsoft Download Center:

Windows Vista
Download the Update for Windows Vista (KB931573) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=5549C98D-421A-4F77-97F3-4E82A4D6471B)

Windows Vista for 64-bit Systems
Download the Update for Windows Vista for 64-bit Systems (KB931573) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=C4BC5D31-3CEA-4992-84D7-334D29580EF1)

Release Date: January 30, 2007

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: 119591 (http://support.microsoft.com/kb/119591/). How to obtain Microsoft support files from online services.

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

iTunes 7.3 Vista installation issue

Symptom:
In some instances, the iTunes and QuickTime Installers may unexpectedly quit during the "Preparing to Install" stage of the installation with the following message:

"The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2738."

In some cases, the error message may read

"iTunes could not be installed because Visual Basic Script (VBScript) is not installed or has been disabled. Make sure VBScript is installed, turn off script blocking in anti-virus and personal firewall software, reregister VBScript, and the install iTunes."
Discussion:

This error occurs when the vbscript.dll file is not properly registered with Windows Vista.

Products affected

* iTunes 7.0 or later
* QuickTime 7.1.3 or later
* Windows Vista

Solution:
The iTunes and QuickTime Installers uses a technology called "Windows Installer", provided by Microsoft. If you see this error, it may be because the Windows Installer technology is unable to process the Visual Basic Script embedded inside the iTunes and QuickTime Installers.

If the VBScript is installed, it might not be registered within Windows Vista. To re-enable the VBScript engine, follow these steps:

1. Click the Pearl.
2. In the "Start Search" field, type: CMD, on the menu above Right Click CMD and Click "Run as Administrator". A UAC prompt will appear, click Continue.
3. In the command window tyoe the following command: C:\Windows\System32\regsvr32 vbscript.dll
4. A message should appear stating that the "DllRegisterServer in C:\WINDOWS\system32\vbscript.dll succeeded."
5. Click OK then type: exit to close the command window
6. Try installing iTunes or QuickTime again.

This document will be updated as more information becomes available

Note: The issue involved the customer not being able to install iTunes after download. The customer was using a Vista OS and had previously contacted Apple/iTunes before contacting Dell and got a "as long as you are downloading 7.3, you should have no problems with Vista" answer. (For the record, Apple only has 7.3 on their site as of now.)

Apple's knowledge base provided the following link :( http://docs.info.apple.com/article.html?artnum=304405 ) and the above fix was developed from that article.