From: Numerica Progetti S.r.l. [numprog@tin.it] Sent: Wednesday, June 09, 1999 6:15 AM To: 'jkirby@storagecraft.com'; 'ntdev@atria.com' Subject: RE: [ntdev] NT4 drivers under NT2000 > Hi, > > I can add some more info about porting low level filter drivers (attached > to Port drivers) from NT 4.0 to Win2000 Beta 3. My NT 4.0 filter for > ScsiPorts doesn't work "as is" on Windows 2000 Beta 3 for the following > reasons: > 1) in my DriverEntry() I looked at the Registry > (HKLM\HARDWARE\DEVICEMAP\Scsi) to find which Scsi Ports controlled one or > more CD-ROMs, then attached to such ports to filters every command sent to > a CD-ROM unit. Under Windows 2000, it seems that the initialization of the > registry is non yet complete when my driver is loaded (at Boot, Start=0), > so that I'm able to see the Atapi CD-ROMs but not the Scsi ones (if I look > at the registry when the system is started, all expected entries are > there). > 2) the device tree under Windows 2000 is very different than under NT 4.0 > (this can be easily seen using the OSR DeviceTree utility), so that a > filter attached to a ScsiPort doesn't get called when commands are sent to > a unit controlled by that port. > I've concluded that I have to rework the initialization of my filter, > handling the AddDevice routine (and consequently the PNP and POWER IRPs). > I'm using as a model the DISKPERF sample driver of the Windows 2000 DDK, > but I'm still having problems that I'm investigating. > > Hoping all this may help, and to read any (good) new on the subject > > Carlo Andreoli > ---------------------------------------------------------- > Numerica Progetti Srl > Via Italo Simon, 6 > 56100 Pisa - ITALY > Phone/Fax (039) 050 598487 > e-mail numprog@tin.it > web www.numericaprogetti.com > ---------------------------------------------------------- > > ---------- > From: Jamey Kirby[SMTP:jkirby@storagecraft.com] > Reply To: jkirby@storagecraft.com > Sent: Tuesday, June 08, 1999 10:13 PM > To: Thomas F. Divine; Mike Pittelkow; Ntdev > Subject: RE: [ntdev] NT4 drivers under NT2000 > > Our virtual disk driver and virtual tape driver work just fine under 2000. > We also have a few minitape drivers that are now working. MS made some > changes to the minitape architecture, but we have been able to resolve > most > of them. One of the file system filter drivers that I worked on is also > working fine under 2000 (after we got past driver verifier). > > I have a disk filter driver that needs porting next. I suspect I will be > having a few problems in that arena. I will post any interesting things > that > I find. > > Jamey Kirby > StorageCraft > > > -----Original Message----- > From: owner-ntdev@atria.com [mailto:owner-ntdev@atria.com]On Behalf Of > Thomas F. Divine > Sent: Tuesday, June 08, 1999 8:14 AM > To: Mike Pittelkow; Ntdev > Subject: Re: [ntdev] NT4 drivers under NT2000 > > > Mike, > > The situation isn't totally clear to me yet either. > > In the area of NDIS drivers, I have found that NDIS protocol drivers that > worked under NT4 and NT5 B2 fail under W2K B3. The only obvious problem > that > I found concerns a difference in the implementation of certain NDIS > operations that were defined as MACROS in the NT 4 DDK and are defined as > exported functions in the W2K DDK. > > In particular, the NT4 DDK MACROS are NOT compatible with the W2K B3 > equivalent (but were equivalent on NT5 B2). > > NdisFreePacket and NdisFreeBuffer are two examples. There is a brief note > about this on the NDIS FAQ at > . > The note suggests a workaround to develop a driver that will work on both > NT4 and W2K. HOWEVER, I have recently found that my suggestions in that > note > are IN ERROR. The suggested workaround appears to work on single-processor > hosts, but does not work correctly on MP hosts. > > At this point I think that the idea that "...Windows 2000 continues to > support legacy Windows NT drivers..." is not universally true. > > While this note concerns my experiance with NDIS drivers, I suspect that > similar (or worse) differences exist for other drivers. > > > PCAUSA may be late to the party, but we have decided to build different > drivers for NT4 and W2K. Initially, the ONLY difference will be the DDK > used > to build them... > > Regards, > > Thomas F. Divine > > PCAUSA - Toolkits & Resources For Network Software Developers > NDIS Protocol - TDI Client - Windows 95 Redirector > > > > -----Original Message----- > From: Mike Pittelkow > To: Ntdev > Date: Tuesday, June 08, 1999 10:49 AM > Subject: [ntdev] NT4 drivers under NT2000 > > > > > >I've gotten some clonflicting reports regarding NT4 drivers under NT2k. > > > >According to the Beta 3 DDK, > >Section 2.1 "While , driver support for Plug and Play and power > management > increases the > >potential market for peripheral device(s). " > > > >I take this to mean that NT4 drivers should work, but obviously not be > able > >to take advantage of power management, plug and play, etc. > > > >I've reported several drivers that are on the HCL for NT4 that don't work > >for NT2000, and my only (single) response from MS has been that "Most > >drivers for NT4 will not work under NT2000." > > > >I know for a fact that they worked under Beta 2, they only broke in beta > 3 > >(obviously a lot has changed between the beta's, but I would have > expected > >all the driver related changes to have happened early on). Additionally, > >this seems to totally contradict the DDK. > > > >Anyone have some light to shed on the situtation? > > > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > >[ To unsubscribe, send email to ntdev-request@atria.com with body > >UNSUBSCRIBE (the subject is ignored). ] > > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > [ To unsubscribe, send email to ntdev-request@atria.com with body > UNSUBSCRIBE (the subject is ignored). ] > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > [ To unsubscribe, send email to ntdev-request@atria.com with body > UNSUBSCRIBE (the subject is ignored). ] > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - [ To unsubscribe, send email to ntdev-request@atria.com with body UNSUBSCRIBE (the subject is ignored). ]