Please let me know where i can find the PCI sample drivers for XP.

Take a look at PCIDRV sample from the WDK.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply


"Senthil" <ecedhil@gmail.com> wrote in message
news:259a25e2-782f-4ab9-bc21-7e2f1aac9767@f3g2000hsg.googlegroups.com...

Hi Don,

Thanks for the Help.
I have a WinDDK of XP which is released in May2003 ...
I am not able to find this example in this driver.

Please let me know which version of DDK do I need.

On Dec 11, 6:34 pm, "Don Burn" <b...@stopspam.windrvr.com> wrote:

On Dec 12, 9:38 am, Senthil <eced...@gmail.com> wrote:
Get the latest WDK here:

http://www.microsoft.com/whdc/DevTools/ddk/

Older DDKs are available through MSDN.

Stephan

Hi ,

I am trying to debug the PCI sample available in the DDK using windbg.
I am not able to map the symbol file the >pdb file for this.
Please let me know how I can proceed with this.

Regards,
Senthil.

Put PDB to some directory, and ensure it is in the WinDbg's symbol path.

Then do:

.reload /f mydriver.sys
x mydriver!*

the latter should print all symbols.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"Senthil" <ecedhil@gmail.com> wrote in message
news:9213ef19-7465-4d2f-a4fe-559b4c5798a8@k2g2000hse.googlegroups.com...

On Jan 15, 4:31*pm, "Maxim S. Shatskih" <ma...@storagecraft.com>
wrote:
Hi Maxim ,

Thanks for the reply.
I have copied the contents of the .sys and pdb file from \WinDDK
\6000\src\kmdf\pcidrv\sys\hw\objchk_wxp_x86\i386 to D:/PCI.
and here is the result when I try to do the steps

kd> .sympath
Symbol search path is: SRV*d:\DebugSymbols*http://msdl.microsoft.com/
download/symbols;d:\PCI
kd> .reload /f PCIDRV.sys



"PCIDRV.sys" was not found in the image list.
Debugger will attempt to load "PCIDRV.sys" at given base 00000000.

Please provide the full image name, including the extension (i.e.
kernel32.dll)
for more reliable results.Base address and size overrides can be given
as
.reload <image.ext>=<base>,<size>.
DBGENG: PCIDRV.sys - Partial symbol image load missing image info
DBGHELP: No header for PCIDRV.sys. Searching for dbg file
DBGHELP: d:\PCI\PCIDRV.dbg - file not found
DBGHELP: d:\PCI\sys\PCIDRV.dbg - path not found
DBGHELP: d:\PCI\symbols\sys\PCIDRV.dbg - path not found
DBGHELP: .\PCIDRV.dbg - file not found
DBGHELP: .\sys\PCIDRV.dbg - path not found
DBGHELP: .\symbols\sys\PCIDRV.dbg - path not found
DBGHELP: PCIDRV.sys missing debug info. Searching for pdb anyway
DBGHELP: Can't use symbol server for PCIDRV.pdb - no header
information available
DBGHELP: PCIDRV - private symbols & lines
d:\PCI\PCIDRV.pdb - unmatched
Unable to add module at 00000000


I dont have an dbg file in this folder.

Regards,
Senthil.

Old PDB mismatching the current SYS

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

On Jan 16, 8:45*pm, "Maxim S. Shatskih" <ma...@storagecraft.com>
wrote:
Hi,

I tried reinstalling the DDK and rebuild the PCI drive folder in the
client machine.
Then I installed the same driver in the target machine.
Then also I am getting the same result. There is no change in
behaviour when I do the .reload.

Senthil.

What is the version of the driver that is loaded? If it isn't the current
date, then maybe system file protection is protecting that driver. Read the
newsgroups and documentation for ways to replace the driver with your own
version. If the version being currently used is not the same as the one
shipped with the version of XP you are using, probably SP2, then a Windows
Update may have replaced it and the source won't enable you to build an
identical version.

"Senthil" <ecedhil@gmail.com> wrote in message
news:44fa2a74-99b1-40f0-8dda-c2f3c2511514@p69g2000hsa.googlegroups.com...
On Jan 16, 8:45 pm, "Maxim S. Shatskih" <ma...@storagecraft.com>
wrote:
Hi,

I tried reinstalling the DDK and rebuild the PCI drive folder in the
client machine.
Then I installed the same driver in the target machine.
Then also I am getting the same result. There is no change in
behaviour when I do the .reload.

Senthil.

On Jan 22, 1:02*am, Senthil <eced...@gmail.com> wrote:
What makes you think that pcidrv.sys is even loaded? Do an lm command
in windbg and see if the driver has been loaded. Do you have the right
hardware plugged in? You need a Plx9xxx device for this driver.