gsense.co.uk
gSense Page 2.
http://gsense.co.uk/index_2.html
kernelmode.blogspot.com
Kernel Mode: Debugging Story One - First Pass
http://kernelmode.blogspot.com/2006/01/debugging-story-one-first-pass.html
Saturday, January 28, 2006. Debugging Story One - First Pass. Our previous posting covered the symptoms of this problem]. So, the usual stuff:. 1 Get the hardware from the client (in this case just a bare circuit board from inside the machine). 2 Make sure we can see the same problem as they can. 3 Clone a nice clean VMWare XPSP2 machine for testing with. 4 Hook-up Windbg to VMWare as a kernel mode debugger, via a named pipe. 5 Get their drivers installed on the VMWare machine. Snapshot it. Owning Proces...
kernelmode.blogspot.com
Kernel Mode: Debugging Story One - Initial Bug Report
http://kernelmode.blogspot.com/2006/01/debugging-story-one-initial-bug-report.html
Saturday, January 28, 2006. Debugging Story One - Initial Bug Report. I spent a chunk of the last week tracking down a couple of Windows driver bugs. I rather like reading debugging war stories, and I wondered if there might be any interest in this one. The client's product is a big piece of machinery, with a USB interface for connection to a Windows PC. Their device is configured so that it appears to be three USB peripherals:. An imaging device, which loads the Windows USBSCAN.SYS driver. CARDSYS - In ...
kernelmode.blogspot.com
Kernel Mode: Our connection with CY4601
http://kernelmode.blogspot.com/2006/01/our-connection-with-cy4601.html
Saturday, January 28, 2006. Our connection with CY4601. The Cypress Semiconductor CY4601 reference design is a 'USB to serial converter' solution. There are a number of such products around - some, like the FTDI solution, are based on an ASIC and don't have a microcontroller at the perpheral end at all. Others, like the Cypress version, use a general-purpose USB peripheral microcontroller with appropriate firmware. Prior to last week, we thought the current driver was pretty much there.
kernelmode.blogspot.com
Kernel Mode: January 2006
http://kernelmode.blogspot.com/2006_01_01_archive.html
Saturday, January 28, 2006. Debugging Story One - First Pass. Our previous posting covered the symptoms of this problem]. So, the usual stuff:. 1 Get the hardware from the client (in this case just a bare circuit board from inside the machine). 2 Make sure we can see the same problem as they can. 3 Clone a nice clean VMWare XPSP2 machine for testing with. 4 Hook-up Windbg to VMWare as a kernel mode debugger, via a named pipe. 5 Get their drivers installed on the VMWare machine. Snapshot it. Owning Proces...
kernelmode.blogspot.com
Kernel Mode: February 2006
http://kernelmode.blogspot.com/2006_02_01_archive.html
Saturday, February 11, 2006. The smartcard driver which appears in the previous posts raises an interesting point about WHQL signing. The supplied smartcard driver was WHQL signed - it was signed back in 2001, despite having the serious IRP completion bug. Of course, the patched, working driver is no longer WHQL signed. So which is the higher quality driver? Wednesday, February 01, 2006. Debugging Story One - Second Pass. See previous posts for earlier details about this problem]. Dead strange this - cle...
kernelmode.blogspot.com
Kernel Mode: WHQL and patching
http://kernelmode.blogspot.com/2006/02/whql-and-patching.html
Saturday, February 11, 2006. The smartcard driver which appears in the previous posts raises an interesting point about WHQL signing. The supplied smartcard driver was WHQL signed - it was signed back in 2001, despite having the serious IRP completion bug. Of course, the patched, working driver is no longer WHQL signed. So which is the higher quality driver? Subscribe to: Post Comments (Atom). Debugging Story One - Second Pass. View my complete profile.
kernelmode.blogspot.com
Kernel Mode: Debugging Story One - Second Pass
http://kernelmode.blogspot.com/2006/02/debugging-story-one-second-pass.html
Wednesday, February 01, 2006. Debugging Story One - Second Pass. See previous posts for earlier details about this problem]. Ok, so we fixed the problem with the WaitCommEvent IRP not being failed on a SURPRISE REMOVAL. I'd always prefer the bugs to be found in someone else's code, but really I'm just happy when they're fixed. Whenever I ran this on a machine where I had good visibility, the driver stack would unload properly and, as you'd expect, this didn't leave anything around to remember that it was...