Select the product you need help with

Certain R2 PC cards are incorrectly enumerated as memory cards

Article ID: 319326 - View products that this article applies to.

This article was previously published under Q319326

SYMPTOMS

Certain R2-based PC cards may be incorrectly enumerated as memory cards (MTD-0002) if the PCMCIA CIS window was mapped in a high range (greater than 0xFF000000 in the system physical memory). Also, the card may not function correctly if it was assigned a memory resource in that range.

Back to the top | Give Feedback

CAUSE

This behavior is caused by a bug in the Pcmcia.sys module.

Back to the top | Give Feedback

RESOLUTION

Service pack information

Windows 2000

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

260910

(http://support.microsoft.com/kb/260910/ )

How to obtain the latest Windows 2000 service pack

Windows XP

To resolve this problem, obtain the latest service pack for Microsoft Windows XP. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

322389

(http://support.microsoft.com/kb/322389/ )

How to obtain the latest Windows XP service pack

Hotfix information

Windows 2000 hotfix

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time       Version        Size    File name
   -----------------------------------------------------------
   08/28/2001  02:33 P.M.                 34,772  ntdetect.com 
   11/26/2001  07:39 P.M.  5.0.2195.4689  59,216  pci.sys 
   04/13/2002  05:52 P.M.  5.0.2195.5581  109,488 pcmcia.sys

Windows XP hotfix

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table.

   Date         Time       Version      Size    File name
   -------------------------------------------------------
   04/16/2002   11:27 A.M. 5.1.2600.42  115,584 PCMCIA.SYS

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows 2000 Service Pack 4. This problem was first corrected in Windows XP Service Pack 1.

Back to the top | Give Feedback

MORE INFORMATION

The bug mentioned in the "Cause" section of this article occurs because the math that was used to compute values to address the memory window (CIS or common) was flawed. The "base" value of the memory window that needs to go into a host controller window register is the offset of that window in the system physical memory minus the window offset on the PC card. However, care was not taken to avoid a carry into the twenty-fourth bit position. This occurs only with certain values of physical memory positions, and it also depends on the memory window offset on the card. Additionally, it appears to affect only certain PC cards.

Note This issue does not occur if the memory window (CIS or common) was mapped somewhere within the first megabyte of the system physical memory, which is the preferred resource request range for the memory windows of R2 cards. But this mapping itself may cause other problems in card installation (generally error code 12) if there are not enough memory resources in that range of the physical memory (A0000 through FFFFF). The first megabyte of system physical memory is typically divided as follows:

0 through 9FFFF: Reserved
A0000 through DFFFF: Used to map ROMs of devices with ROM onboard. Also used to map memory windows for earlier versions of devices.
E0000 through FFFFF: Used to map the System BIOS. Some smaller BIOS systems use a smaller range.

For more information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the following article number to view the article in the Microsoft Knowledge Base:

265173

(http://support.microsoft.com/kb/265173/ )

The Datacenter program and Windows 2000 Datacenter Server product

For more information about how to install multiple hotfixes with a single reboot, click the following article number to view the article in the Microsoft Knowledge Base:

296861

(http://support.microsoft.com/kb/296861/ )

How to install multiple Windows updates or hotfixes with only one reboot

Back to the top | Give Feedback