Resumé:
Jim Serwer
Software Consultant
408-985-6615
Send email

I have worked on three device drivers for Windows, two TDI drivers and one printer driver.

TDI Drivers

The Transport Device Interface (TDI) is a Microsoft protocol by which a TDI client (e.g. WinSock, NetBIOS) talks to network transport device drivers (e.g. TCP/IP).

I have written two TDI Device Drivers, one a VxD for Windows 95/98, and the second a Windows NT Device Driver. These two drivers adhere to very different architectures. But both insert themselves into the TCP/IP stack at the TDI level. These drivers examine all incoming TCP/IP data and copy certain kinds of inputs to a companion application. This is similar to the technology used in personal firewalls and internet filters.

Printer Driver

Gradco Inc. made a printer accelerator card for the PC bus. A Windows 3.1 printer driver translated standard Windows print commands into the protocol of this card. In 1993 I debugged and improved their existing printer driver. This driver subsequently worked on Windows 95 also.

Driver Development Tools

I am a licensed user of NuMega's DriverStudio. This is a suite of seven different driver development tools for Windows 95/98 and Windows NT. From among these tools, I used VTOOLSD, SoftICE, and BoundsChecker Driver Edition while developing the TDI drivers.

Other types of drivers

(With each new contract, I learn new material. Some material is unique to the client's product, and some is of a general nature. It is my firm policy NOT to charge my clients for time I spend learning skills of a general nature.)

Device Drivers include a wide range of different specialties and different device types. I do not charge for my time to learn new devices. If a project requires me to learn about Infrared devices, it may cost me more, but it should not cost you more.