Path: news.mitre.org!blanket.mitre.org!agate!newsgate.duke.edu!nntprelay.mathworks.com!howland.erols.net!usc!newshub.cts.com!newsfeed.cts.com!cmkrnl!jeh
From: jeh@cmkrnl.com (Jamie Hanrahan)
Newsgroups: comp.os.ms-windows.programmer.nt.kernel-mode
Subject: Re: resonable time to develop driver
Message-ID: <1997Dec8.173414.8354@cmkrnl>
Date: 8 Dec 97 17:34:14 PST
References: <66hge6$1vl@news1.zippo.com>
Organization: Kernel Mode Systems, San Diego, CA
Lines: 28

In article <66hge6$1vl@news1.zippo.com>, barskir@thorin.atsc.allied.com (Renata) writes:
> Trying to get a feel for what is a reasonable amount of time for an individual 
> who has never done an NT driver, to develop a Port I/O (like Genport) Driver 
> (supporting multiple boards of the same kind) and the Win32 interface to that 
> driver.

If you just wanted to extend genport to multiple boards, AND if you
get some training (like one of our (shameless plug alert!) seminars),
I'd say to allow a week to a month after the seminar - the variation
depends on how much it is REALLY like the genport driver and on good
you are about dotting i's and crossing t's.  Getting the basic code
lined out should take no more than a couple of days (for genport it
would only be changes to its DriverEntry and Unload routines) but
getting it all EXACTLY right might take a while. 

In my NT driver seminars I do use GenPort as one of our first examples
for code walk-throughs, so this would probably be time well-spent.  
See http://www.solsem.com for details.

On the other hand you could use WinRT (www.bluewatersystems.com) and
not have to write a driver at all. 

	--- Jamie Hanrahan, Kernel Mode Systems, San Diego CA
        Internet: jeh@cmkrnl.com (JH645)  CompuServe: 74140,2055  
drivers, internals, networks, applications, and training for VMS and Windows NT
NT driver FAQ, links, and other information:  http://www.cmkrnl.com/

If you post a reply in news, please don't e-mail it too.