microsoft.public.development.device.drivers Google Group

Re: Linksys WRTP54G-VR

2010-03-11T00:04:40Z

The install hangs on the last step, displaying 99% complete, but never
finishes (even after an hour).
It did this before too.

Re: Linksys WRTP54G-VR

2010-03-10T22:32:29Z

Can you set up the router without installing any drivers using Telnet or web interface?

Linksys WRTP54G-VR

2010-03-10T21:16:53Z

I have a Linksys WRTP54G-VR
Wireless Broadband G router.
hooked up to a Motorola SB4200 via the LAN cable to Comcast.
It is connected to a HP Pavillion a1632x with a NVidea nForce Network
Controller card running Vista64 sp2 . It worked fine under XP64
until my machine got a virus.
1)
Is this device fully supported and tested under Vista64 sp2? Has

RE: Filter driver on boot device

2010-03-10T19:24:33Z

You are changing the semantics of the device model by making the disk
requests sequential that is why it crashes. Even if it does work, your
performance will stink, so this is a bad desing.
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: [link]
Blog: [link]

Filter driver on boot device

2010-03-10T19:19:01Z

I am writing a KMDF filter driver attached to the boot drive, so it loads
with start_type = 0. I only want one read/write request in flight at a time.

When I set the following in addDevice, I get a crash with "Inaccessible Boot
Device:"
WDF_IO_QUEUE_CONFIG_INIT_DEFAU LT_QUEUE
(&ioQueueConfig,WdfIoQueueDisp atchSequential);

Re: C2220 & 32bit app on 64 bit driver

2010-03-10T15:44:49Z

This conradicts what you said above about the structure size "matching fine". It does not.
If you want to simplify the driver - then replace all pointers in the structures with ULONGLONGs (8byte on all platforms), and, in 32bit apps, cast (ULONGLONG)(ULONG)Ptr.
In the 32bit version of the driver, you will need to cast down.

Re: C2220 & 32bit app on 64 bit driver

2010-03-10T13:20:38Z

ULONG_PTR is always defined for a driver so I don't see what your logic is
doing. Also, PtrToUlong should only be used to convert a pointer to an
integer, using it to take create a pointer is a bug.
Finally, your whole interface is broken. You should avoid at all costs
having a pointer in an IOCTL structure. Not only can you not make this

Re: C2220 & 32bit app on 64 bit driver

2010-03-10T11:44:01Z

Hi,
Thanks for your inputs.
I have used the "PtrToUlong" function for coverting the void * pointer to my
datatype ULONG_PTR, it avoided the C2220 error and working fine.
I am using the below typedef to replace void pointer in my IOCTL structures
and replaced the ULONG to ULONG32 in my structures.
All os my IOCTL structures variables are void * or ULONG32 size variables.

Re: WMI in drivers

2010-03-10T10:10:20Z

I would duplicate all functions in both interfaces, and write the app to use IOCTLs only.
Such a separation is just extra unnecessary complexity for the app, and has no logical meaning or positive value.
IOCTLs and WMI are both just access methods, nothing else - IOCTLs more suitable for high performance and C/C++, WMI - for scripting languages.

Re: WMI in drivers

2010-03-10T09:58:53Z

Hello and thank you for answer.
Probably I have described by wish correctly. I want to link WMI class
instance and device symbolic name that is used for CreateFile function call.
Our device will have WMI interface to retrieve device states (such as supply
voltage) and regular IOCTL interface to peroform read/write operations. And

Re: Windows7 send wrong USB data payload after wake from sleep mod

2010-03-09T20:39:01Z

I've made test as you recommend. It's G45/ICH10 chipset, and in device
manager are two EHCI and couple of UHCIs. All USB devices was disconnected,
then all controllers disabled and reenabled. Failure still occur.
This was great idea, but what can i do next? Test of another motherboard
show same error, therefore this should not to be problem of piece of hw. I

RE: Hub and Tracker the problem- use a USBtracer

2010-03-09T20:18:04Z

Obiously tracker is connected before hub, but capture was made also after hub
with the same results. I think, it's not Ellisys missrecording or HUB
problem. Also this error exact explain of the device behavior - device
receive wrong command, therefore readed device status (interrupt transfer)
never reach requested value.

Re: Our disk's driver run properly compiled for 32bit and not for

2010-03-09T19:19:01Z

So, I was testing driver for last week :-)
To your questions - this driver is filter driver (system sends request to
this driver and this driver send I/O request to low level drivers - ntfs/fat).
I install it now by myself (start/stop), but in full version it will be
install by inf file and running all time (start when user log in and stop

DevCon to remove ghost devices "remove failed"

2010-03-09T18:15:02Z

Hello,
I just pulled a Virtual Tape Library out of my backup environment and
am now having some stability issues with the remaining devices. In
working with the vendor, they suggested I check for ghost tape drives
that could cause issues. Sure enough they are there. When using
devcon, I run:
devcon findall =tapedrive

Re: WdfIoTargetOpen fails in opening the remote I/O

2010-03-09T16:22:17Z

Just to make sure, did you correctly set the TMF file before attempting to
view the log? The extension is !wdftmffile.