David, Thanks for the suggestion. I am copying windbgfb this mail. Here is
the info asked for.
Opened log file ‘e:\ndiskd.log’
kd> .reload
SYMSRV:
e:\symbols\web\ntoskrnl.pdb\C95EC79CFBFB4220AF2B6E9D09551A1F2\ntoskrnl.pdb -
OK
DBGHELP:
e:\symbols\web\ntoskrnl.pdb\C95EC79CFBFB4220AF2B6E9D09551A1F2\ntoskrnl.pdb -
opened
DBGHELP: nt - public symbols -
e:\symbols\web\ntoskrnl.pdb\C95EC79CFBFB4220AF2B6E9D09551A1F2\ntoskrnl.pdb
Loading Kernel Symbols
…
…
Loading unloaded module list
…
Loading User Symbols
…
kd> !sym noisy
Noisy mode on
kd> !ndiskd.protocols
SYMSRV: e:\symbols\web\ndis.pdb\B4F2B56027DA4FF6B8B65BE1481EEC5C2\ndis.pdb
- OK
DBGHELP: e:\symbols\web\ndis.pdb\B4F2B56027DA4FF6B8B65BE1481EEC5C2\ndis.pdb - opened
DBGHELP: NDIS - public symbols -
e:\symbols\web\ndis.pdb\B4F2B56027DA4FF6B8B65BE1481EEC5C2\ndis.pdb
Protocol ffb97008:
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** ***
*************************************************************************
Cant get offset of Name in Protocol block!
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** ***
*************************************************************************
kd> lml
start end module name
804d4000 806c6980 nt (pdb symbols)
e:\symbols\web\ntoskrnl.pdb\C95EC79CFBFB4220AF2B6E9D09551A1F2\ntoskrnl.pdb
fc3b3000 fc3dbe80 NDIS (pdb symbols)
e:\symbols\web\ndis.pdb\B4F2B56027DA4FF6B8B65BE1481EEC5C2\ndis.pdb
kd> .reload /f ndis.sys
SYMSRV: e:\symbols\web\ndis.pdb\B4F2B56027DA4FF6B8B65BE1481EEC5C2\ndis.pdb
- OK
DBGHELP: e:\symbols\web\ndis.pdb\B4F2B56027DA4FF6B8B65BE1481EEC5C2\ndis.pdb - opened
DBGHELP: NDIS - public symbols -
e:\symbols\web\ndis.pdb\B4F2B56027DA4FF6B8B65BE1481EEC5C2\ndis.pdb
kd> lmv mndis
start end module name
fc3b3000 fc3dbe80 NDIS (pdb symbols)
e:\symbols\web\ndis.pdb\B4F2B56027DA4FF6B8B65BE1481EEC5C2\ndis.pdb
Loaded symbol image file: NDIS.sys
Image path: NDIS.sys
Checksum: 0002F9E8 Timestamp: Thu Aug 29 02:09:23 2002 (3D6DE4C3)
Unloaded modules:
kd> !lmi ndis
Loaded Module Info: [ndis]
Module: NDIS
Base Address: fc3b3000
Image Name: NDIS.sys
Machine Type: 332 (I386)
Time Stamp: 3d6de4c3 Thu Aug 29 02:09:23 2002
Size: 28e80
CheckSum: 2f9e8
Characteristics: 10e perf
Debug Data Dirs: Type Size VA Pointer
CODEVIEW 21, 4cac, 4cac RSDS - GUID: (0xb4f2b560, 0x27da,
0x4ff6, 0xb8, 0xb6, 0x5b, 0xe1, 0x48, 0x1e, 0xec, 0x5c)
Age: 2, Pdb: ndis.pdb
CLSID 4, 4ca8, 4ca8 [Data not mapped]
Image Type: MEMORY - Image read successfully from loaded memory.
Symbol Type: PDB - Symbols loaded successfully from symbol server.
e:\symbols\web\ndis.pdb\B4F2B56027DA4FF6B8B65BE1481EEC5C2\ndis.pdb
Load Report: public symbols -
e:\symbols\web\ndis.pdb\B4F2B56027DA4FF6B8B65BE1481EEC5C2\ndis.pdb
kd> !sym quiet
Quiet mode on
kd> .logclose
Closing open log file e:\ndiskd.log
-----Original Message-----
From: David Holcomb [mailto:xxxxx@microsoft.com]
Sent: Monday, December 16, 2002 11:00 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: ndiskd.dll not working for XP SP1. Can someone in
microsoft help ?
You should send these kinds of questions to xxxxx@microsoft.com.
Send them the output from the following:
.reload
!sym noisy
!ndiskd.protocols
lml
.reload /f ndis.sys
lmv mndis
!lmi ndis
!sym quiet
-----Original Message-----
From: xxxxx@NAI.com [mailto:xxxxx@NAI.com]
Sent: Monday, December 16, 2002 9:18 AM
To: Kernel Debugging Interest List
Subject: [windbg] ndiskd.dll not working for XP SP1. Can someone in
microsoft help ?
Guys,
ndiskd.dll is not working for Windows XP SP1. I had this problem
for Windows XP and guys at microsoft had to fix the symbols for
ndis.sys file at symbol server. The same thing happened again, can
someone at mircosoft please help me and fix the symbols for ndis.sys
for Windows XP SP1. here is the output i get when i do
!ndiskd.protocols. I deleted my cached symbols and got them new but
still the same problem.-Srin.
kd> !ndiskd.protocols
Protocol 80dc41c8:
************************************************************************
*
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
***
***
**********************************************************************
***
Cant get offset of Name in Protocol block!
************************************************************************
*
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
***
***
************************************************************************
*
************************************************************************
*
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
***
***
**********************************************************************
***
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%
You are currently subscribed to windbg as: xxxxx@nai.com
To unsubscribe send a blank email to %%email.unsub%%