Hi,

I am stuck with a similar problem (as mentioned below in one of the
older postings). Driver works with XP and 2K. Infact it works with
WinME installed on PC where I use PCI-Cardbus(Ricoh) controller to
insert my cardbus wireless lan controller. It doesn't work with WinME
(on IBM Thinkpad A21m laptop).

My NdisMQueryAdapterResources() returns only one resource i.e.
interrupt. Using debugger command 'pci' I see that BAR seems to be
mapped. No difference when I use NdisMPciAssignResources() wrt number
of resources but here I get IO enabled in addition to BusMaster and
Memory (i.e. control word 0x7 in NdisMPCIAssignResources() against 0x6
in NdisMQueryAdapterResources() .

There is one imp print in the debugger in the reboot that follows
crash because of pci-bar not getting mapped. It says"VPICD Severe
Perf Warning: interrupt #9 is supriousing. Get the owners of the
devices on that interrupt to look at their code." This problem exists
till I don't shutdown the m/c and start. Device manager shows that
'SCI IRQ used by ACPI bus' is the interrupt
that prompts that warning. My device is on interrupt 0xB. Don't know
whether this problem is linked to above resource allocation problem.

Hi Daum,

Found you query in this ng. Did you get the solution for this ?

I couldn't find post-followup-message in your posting hence creating a
new thread.

Went through "Another NDIS, PnP, PCI question" thread in
"comp.os.ms-windows.programmer.nt.kernel-mode" which is related
problem but changing eeprom contents from 'other controller' to
'ethernet controller' did not help.

Thanks,
Ashirwad.

>From: daum (daum999@yahoo.com)
>Subject: [Q] Resource allocation problem at WinMe : physical memory
>start .address always 0.


>View this article only
>Newsgroups: microsoft.public.development.device.drivers
>Date: 2003-05-30 10:57:44 PST


>Subject : [Q] Resource allocation problem at WinMe : physical memory
start
>address always 0.


>Hello, everyone.

>I'm developing CardBus NDIS D/D at WinMe, and i have one problem
during
>MiniportInitialize.

>The problem never occurred at Win2K or WinXp.
>It is a problem concerned about resource allocation.
>My Card has 2 memory windows and their sizes are 0x40000 and 0x4000.
>(I think the memory size was reasonable because it is below 1MB)

>After NdisMQueryAdapterResources was called, it returns the status
with
>NDIS_STATUS_SUCCESS.

>But, the start address of the physical memory-CmResourceTypeMemory-
was
>always 0.

>Of course, the memory Length was all OK : 0x40000 and 0x4000.
>And, the returned Flags value was 0x0; so, it was non-prefetchable.
>Please remind that the problem occurred only at WinMe not Win2K or
WinXp.
>I'm not sure it will occur at Win98Se.

>Thank you for your help in advance.

>//DAUM
>This is the only article in this thread

Re: NdisMQueryAdapterResources() : resource allocation problem at WinMe by Stephan

Stephan
Tue Jul 20 05:37:03 CDT 2004

So you are saying NdisMQueryAdapterResources() vs.
NdisMPciAssignResources() return different results for individual
resources? And that is only in WME, right?

I am not aware of any such problems yet, but if they actually exist, I
doubt MS will fix that. Instead, if NdisMPciAssignResources() solves
the problem for WME, you can use this function in WME and
NdisMQueryAdapterResources() otherwise. See here for how you can
determine the OS (and NDIS) version:


http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=3f1c5334.3358939%40news.t-online.de

(Note: The link mentioned there has changed to
http://msdn.microsoft.com/library/en-us/network/hh/network/103prog_123c3b1d-c431-4829-9943-fd060d3ebe07.xml.asp)

Stephan
P.S.: The mentioned original thread is here:

http://www.google.com/groups?hl=en&lr=&ie=UTF-8&selm=%23y3ueTtJDHA.1360%40TK2MSFTNGP10.phx.gbl
---
On 19 Jul 2004 09:26:04 -0700, ash@athenasemi.com (Ashirwad) wrote:

>Hi,
>
>I am stuck with a similar problem (as mentioned below in one of the
>older postings). Driver works with XP and 2K. Infact it works with
>WinME installed on PC where I use PCI-Cardbus(Ricoh) controller to
>insert my cardbus wireless lan controller. It doesn't work with WinME
>(on IBM Thinkpad A21m laptop).
>
>My NdisMQueryAdapterResources() returns only one resource i.e.
>interrupt. Using debugger command 'pci' I see that BAR seems to be
>mapped. No difference when I use NdisMPciAssignResources() wrt number
>of resources but here I get IO enabled in addition to BusMaster and
>Memory (i.e. control word 0x7 in NdisMPCIAssignResources() against 0x6
>in NdisMQueryAdapterResources() .
>
>There is one imp print in the debugger in the reboot that follows
>crash because of pci-bar not getting mapped. It says"VPICD Severe
>Perf Warning: interrupt #9 is supriousing. Get the owners of the
>devices on that interrupt to look at their code." This problem exists
>till I don't shutdown the m/c and start. Device manager shows that
>'SCI IRQ used by ACPI bus' is the interrupt
>that prompts that warning. My device is on interrupt 0xB. Don't know
>whether this problem is linked to above resource allocation problem.
>
>Hi Daum,
>
>Found you query in this ng. Did you get the solution for this ?
>
>I couldn't find post-followup-message in your posting hence creating a
>new thread.
>
>Went through "Another NDIS, PnP, PCI question" thread in
>"comp.os.ms-windows.programmer.nt.kernel-mode" which is related
>problem but changing eeprom contents from 'other controller' to
>'ethernet controller' did not help.
>
>Thanks,
>Ashirwad.

Re: NdisMQueryAdapterResources() : resource allocation problem at WinMe by Stephan

Stephan
Tue Jul 20 07:50:01 CDT 2004

On Tue, 20 Jul 2004 12:37:03 +0200, "Stephan Wolf [MVP]"
<stewo68@hotmail.com> wrote:

> Instead, if NdisMPciAssignResources() solves
>the problem for WME, you can use this function in WME and
>NdisMQueryAdapterResources() otherwise. See here for how you can
>determine the OS (and NDIS) version:

Note that I am not sure if WHQL will accept that, though.

Stephan

Re: NdisMQueryAdapterResources() : resource allocation problem at WinMe by ash

ash
Thu Jul 29 06:24:18 CDT 2004

Hi,

NdisMPciAssignResources() is not working for me. On A21m IBM Thinkpad
on WinME I am unable to get PCI resources, whichever call I use. I
tried a workaround. Assign PhysicalIoSpace.HighPart to 0 using
NdisSetPhysicalAddressHigh() and get PhysicalIoSpace.HighPart using
NdisReadPciSlotInformation(). Then do the regular NdisMMapIoSpace().
This non-standard way works. Please comment.

Thanks,
Ashirwad.

"Stephan Wolf [MVP]" <stewo68@hotmail.com> wrote in message news:<n65qf01p4do7nno9oh93fhkq0v15qrl8hr@4ax.com>...
> On Tue, 20 Jul 2004 12:37:03 +0200, "Stephan Wolf [MVP]"
> <stewo68@hotmail.com> wrote:
>
> > Instead, if NdisMPciAssignResources() solves
> >the problem for WME, you can use this function in WME and
> >NdisMQueryAdapterResources() otherwise. See here for how you can
> >determine the OS (and NDIS) version:
>
> Note that I am not sure if WHQL will accept that, though.
>
> Stephan

Re: NdisMQueryAdapterResources() : resource allocation problem at WinMe by bburgin

bburgin
Thu Jul 29 17:45:28 CDT 2004

------=_NextPart_0001_1078FC18
Content-Type: text/plain
Content-Transfer-Encoding: 7bit



I would suggest installing the debug version of NDIS.VxD in Windows ME. To
do this and to obtain the debug binary, see KBs 241517
(http://support.microsoft.com/default.aspx?scid=kb;en-us;241517) and 279356
(http://support.microsoft.com/default.aspx?scid=kb;EN-US;279356).

Be sure to enable all debug spew: systems = 0xffffffff, level = 00000000.

HTH,

Bryan S. Burgin
bburgin@microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_1078FC18
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20
\par
\par I would suggest installing the debug version of NDIS.VxD in Windows ME. To do this and to obtain the debug binary, see KBs 241517 (http://support.microsoft.com/default.aspx?scid=kb;en-us;241517) and 279356 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;279356).
\par
\par Be sure to enable all debug spew: systems = 0xffffffff, level = 00000000.
\par
\par HTH,
\par
\par Bryan S. Burgin
\par bburgin@microsoft.com
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par }
------=_NextPart_0001_1078FC18--