microsoft.public.windowsxp.device_driver.dev
  Home FAQ Contact Sign in
microsoft.public.windowsxp.device_driver.dev only
 
Advanced search
December 2006
motuwethfrsasuw
    123 48
45678910 49
11121314151617 50
18192021222324 51
25262728293031 52
2006
 Jan   Feb   Mar   Apr 
 May   Jun   Jul   Aug 
 Sep   Oct   Nov   Dec 
2008 2007 2006  
total
microsoft ... dev Profile…
RELATED GROUPS

POPULAR GROUPS

more...

 Up
  need a couple sys files from sp1.cab         


Author: thecascadian
Date: Dec 31, 2006 07:08

Hi, I need some old 1394 driver related files from xp sp1.cab. Any one
still have that around on their drive? I need ohci1394.sys, 1394bus.sys

from c:\windows\driver cache\i386\sp1.cab on a PC that has a pre sp2
install; should be there even if sp2 was added later. I need this in
order to override the XP auto driver replacement so I can put a custom
driver on my 1394 port. Thanks for any help on this!!
1 Comment
  correct "sources" file for debugging?         


Author: Polaris
Date: Dec 22, 2006 10:13

Hi Experts:

I have a short "sources" file below which seems not generating correct debug
info: driver (testva.sys) size of the debug version is only a bit bigger
than fee build and could not set break point in WinDbg. Could you see
anything incorrect here? What is misssing to generate full debug info?

Thanks in Advance!
Polaris

---------- Sources -------------
TARGETNAME=testva
TARGETTYPE=DRIVER
TARGETPATH=obj

MSC_OPTIMIZATION=/Od

TARGETLIBS= $(DDK_LIB_PATH)\ndis.lib

NTDEBUG=ntsd
NTDEBUGTYPE=windbg

C_DEFINES=$(C_DEFINES) -DNDIS_MINIPORT_DRIVER=1
C_DEFINES=$(C_DEFINES) -DNDIS_WDM=1 -DWINNT -DWIN2000 $(DEBFLAGS)
C_DEFINES=$(C_DEFINES) -DNDIS50_MINIPORT=1

INCLUDES=$(DDK_INC_PATH);
Show full article (0.79Kb)
4 Comments
  Re: BSOD BAD_POOL_HEADER         


Author: Doron Holan [MS]
Date: Dec 21, 2006 19:49

absolutely it is. it is one of the things that it makes super easy to
implement.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.

yahoo.com> wrote in message
news:1166664517.003319.307900@t46g2000cwa.googlegroups.com...
>I don't know whether KMDF is friendly for writting bus drivers
>
>
> Gary G. Little wrote:
>> Why not...
Show full article (2.97Kb)
no comments
  NDIS 5.0 in Vista ?         


Author: Polaris
Date: Dec 21, 2006 17:45

Hi Experts:

I have a question on NDIS version usable under Windows Vista:

We have been using an NDIS miniport driver writing using NDIS 5.0. Will this
work under Windows Vista? If not, what should I do to make it work in Vista
with minimum change? For example, should I port the driver code to NDIS 5.1
(which is supported by Vista as I read from the web)?

If I port the code to NDIS 6.0, will the driver still work under older
Windows platforms like Windows 2000 and XP?

Thanks for your advises !
Polaris
2 Comments
  troubleshoot code 10         


Author: confused
Date: Dec 21, 2006 13:31

i.m trying to install a new flash drive wizard is picking it up but wont
install properly, ive keep getting code 10 when using the hardware wizard.
ive tried to update the driver but its up tp date. im running xp, any
sugestions
no comments
  Installation automation         


Author: Friedrich Dominicus
Date: Dec 20, 2006 22:40

I'm not fully sure if this is the right group or a group with
installation in it. I have unidrv based printer and I have an .msi file
for installation which seems to work.

Howerver it does the following on installation. It copies the files in
the DriverStore and from there I can get the files for the full install
while running the add printer wizard.

I know would like to have it install the printe without the need to
start the 'add printer wizard'. I have not idea
1) if one has to write some extra installer for tha task
2) wheter one can add something in the .msi file to force this installation

Unfortunatly I did not found anything about this area in neither a
white-paper nor the WinDDK nor the Platform SDK. I'm sure it must be
documented somewhere but I seem not to be able to find it.

so any hint or suggestion would be very welcome.

Regards
Friedrich
no comments
  BSOD BAD_POOL_HEADER         


Author: vcsrave
Date: Dec 19, 2006 11:12

Hi,

I am writing a usb bus driver (wdm driver) , once I install my driver I
am getting blue screens at very random times, sometime in the middle of
transactions and sometime even after my driver got unloaded. But all
the BSODs shows the same bug check code (0x19). I have installed the
driver in Windows XP sp2.

Any suggestions will be appreciated.

Thanks.

===============================================================

BugCheck 19, {20, fb286cd0, fb286ce0, a0202e0}

Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+2c1 )

Debugging Details:
------------------

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: 81bf3100 Nonpaged pool

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 805360bf to 804e2a52

STACK_TEXT:
aa7bb79c 805360bf 00000003 aa7bbaf8 00000000
nt!RtlpBreakWithStatusInstruction
aa7bb7e8 80536b96 00000003 813c2214 81bf3100
nt!KiBugCheckDebugBreak+0x19
aa7bbbc8 805371aa 00000019 00000020...
Show full article (2.02Kb)
4 Comments
  Re: Help regarding DFU.         


Author: zyx
Date: Dec 19, 2006 00:46

Hi Doron,
Thanks for your reply.Below I have posted the functions that my driver
contains.Please let me know if those are enough or I am missing
anything else.
DriverEntry(x)
{
1.Initialize the config sturcture.
2.Create a KMDF driver object using wdfDriverCreate( ) fn.
}
EvtDeviceAdd(x)
{
1.Setting up callback fns for Pnp and power callbacks
a)EvtDevicePrepareHardware callback
b)EvtDeviceD0Entry callback
c)EvtDeviceD0Exit callback
Register the above fns using WdfDeviceInitSetPnpPowerEventCallbacks
fn.
2.Create a KMDF device object using wdfDeviceCreate( ) fn.
3.Create IO queues for read and write request.
IS THERE ANY OTHER THING THAT NEEDED TO BE DONE HERE,ANY OTHER ...
Show full article (9.66Kb)
no comments
  Re: Help regarding DFU.         


Author: Doron Holan [MS]
Date: Dec 17, 2006 20:02

The WDFDEVICE created in DriverEntry is a KMDF driver object, not the NT
object. you do not want to reset the pipe, you want to reset the entire
device. I think you proably want to use
WdfUsbTargetDeviceCyclePortSynchronously to reset the device.

you probably want to download new firmware in EvtDevicePrepareHardware or
EvtDeviceD0Entry, most likely EvtDevicePrepareHardware though and then
immediately reset the device.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.

"zyx" yahoo.co.in> wrote in message
news:1166272288.627796.222700@16g2000cwy.googlegroups.com...
> Hi,
> I have few more doubts.
> I have found few things to reset the device
> 1.In the...
Show full article (6.41Kb)
no comments
  Re: Help regarding DFU.         


Author: zyx
Date: Dec 16, 2006 01:09

Hi Doron,
I have another doubt regarding driver entry routine.
The input parameter for that routine is driver object and registry
path.
what does the wdfdrivercreate function do.The documentation says that
it creates a driver object for calling the driver.what is the diff
between both the driver object.ie,the input parameter and the one
obtained by wdfdrivercreate method.
I am not able to get it.
Thanks in advance.

zyx wrote:
> Hi Doron,
> I have gone thru the KMDF architecture to an extent.I think so I can
> pick up the remaining things while implementing it.Right now I need to
> get the basic idea of what I should...
Show full article (4.65Kb)
no comments
 
1 2 3 4 5 6 7 8 9