Dark underground of INF-files

NTDEV
1

I am trying to install FSD and the FSD recognizer using applied INF-file on Windows 2000 SP 4 and
Windows XP SP1.

I am using the following command line to install:
RUNDLL32.EXE SETUPAPI.DLL, InstallHinfSection DefaultInstall 132 X:\InCDFat\InCDFat.INF
I am using the following command line to uninstall:
RUNDLL32.EXE SETUPAPI.DLL, InstallHinfSection DefaultUninstall 132 G:\InCDFat\InCDFat.INF

I have several problems with the INF-file:

  1. SetupApi.dll can’t install services with ServiceType set to SERVICE_FILE_SYSTEM_RECOGNIZER. It
    is very annoying.
    That is why I am using a workaround inside the AddReg section for the FSD Recognizer.
  2. SetupApi.dll can’t uninstall the FSD Recognizer either with workaround or without it.
    That is why I am using a nasty workaround with DelReg directive inside DefaultUninstall section.

Now the questions:
Where was I wrong?
If I was right, then is this a known problem with the FSD Recognizer installation?
Will it be fixed in next Service Pack of OS?

------------------ Content of INF-file -------------------------------
;
; InCDFat.inf
;
; Copyright 1995-2004 Ahead Software AG and its licensors.
; All Rights Reserved.
;

[Version]
signature = “$Windows NT$”
Provider = %Ahead%
DriverVer = 07/01/2004,4.2.13.0

[DestinationDirs]
DefaultDestDir = 12
InCDFat.Files = 12

[SourceDisksNames]
1 = %Disk1%,

[SourceDisksFiles]
InCDFat.sys = 1
InCDFatRec.sys = 1

[DefaultInstall.nt]
CopyFiles = InCDFat.Files

[DefaultInstall.nt.Services]
AddService = InCDFat,InCDFat.Service
AddService = InCDFatRec,InCDFatRec.Service

[DefaultUninstall.nt]
DelFiles = InCDFat.Files
DelReg = InCDFatRec.DelRegistry

[DefaultUninstall.nt.Services]
DelService = InCDFat

;
; Services Section
;

[InCDFat.Service]
DisplayName = %InCDFatServiceDesc%
ServiceBinary = %12%\InCDFat.sys ;%windir%\system32\drivers\InCDFat.sys
ServiceType = %SERVICE_FILE_SYSTEM_DRIVER%
StartType = %SERVICE_DEMAND_START%
ErrorControl = %SERVICE_ERROR_IGNORE%
AddReg = InCDFat.AddRegistry

[InCDFatRec.Service]
DisplayName = %InCDFatRecServiceDesc%
ServiceBinary = %12%\InCDFatRec.sys
ServiceType = %SERVICE_FILE_SYSTEM_DRIVER%
StartType = %SERVICE_SYSTEM_START%
ErrorControl = %SERVICE_ERROR_IGNORE%
AddReg = InCDFatRec.AddRegistry

[InCDFat.AddRegistry]
HKR,“Group”,%REG_SZ%,“File system”

[InCDFatRec.AddRegistry]
HKR,“Group”,%REG_SZ%,“File system”
HKR,“Type”,%REG_DWORD%,%SERVICE_FILE_SYSTEM_RECOGNIZER%

[InCDFatRec.DelRegistry]
HKLM,“SYSTEM\CurrentControlSet\Services\InCDFatRec”

[InCDFat.Files]
InCDFat.sys,0x00001004
InCDFatRec.sys,0x00001004

[Strings]
Ahead = “Ahead Software AG”
InCDFatServiceDesc = “Ahead InCDFat File System Driver”
InCDFatRecServiceDesc = “Ahead InCDFat FSD Recognizer”
Disk1 = “Ahead InCDFat Source Media”
; Start Type
SERVICE_BOOT_START = 0x0
SERVICE_SYSTEM_START = 0x1
SERVICE_AUTO_START = 0x2
SERVICE_DEMAND_START = 0x3
SERVICE_DISABLED = 0x4
; Service Type
SERVICE_KERNEL_DRIVER = 0x1
SERVICE_FILE_SYSTEM_DRIVER = 0x2
SERVICE_FILE_SYSTEM_RECOGNIZER = 0x8
; Error Control
SERVICE_ERROR_IGNORE = 0x0
SERVICE_ERROR_NORMAL = 0x1
SERVICE_ERROR_SEVERE = 0x2
SERVICE_ERROR_CRITICAL = 0x3
; Registry types
REG_SZ = 0x00000000
REG_MULTI_SZ = 0x00010000
REG_EXPAND_SZ = 0x00020000
REG_DWORD = 0x00010001
; Delete service options
SPSVCINST_STOPSERVICE = 0x00000200

Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail

2

Sorry, I sent the letter to wrong newsgroup.
I redirect it into NTFSD.

Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail

3

Just do this using CreateService.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

----- Original Message -----
From: “Al Shatilo”
To: “Windows System Software Devs Interest List”
Sent: Friday, July 02, 2004 2:47 PM
Subject: [ntdev] Dark underground of INF-files

> I am trying to install FSD and the FSD recognizer using applied INF-file on
Windows 2000 SP 4 and
> Windows XP SP1.
>
> I am using the following command line to install:
> RUNDLL32.EXE SETUPAPI.DLL, InstallHinfSection DefaultInstall 132
X:\InCDFat\InCDFat.INF
> I am using the following command line to uninstall:
> RUNDLL32.EXE SETUPAPI.DLL, InstallHinfSection DefaultUninstall 132
G:\InCDFat\InCDFat.INF
>
> I have several problems with the INF-file:
> 1. SetupApi.dll can’t install services with ServiceType set to
SERVICE_FILE_SYSTEM_RECOGNIZER. It
> is very annoying.
> That is why I am using a workaround inside the AddReg section for the FSD
Recognizer.
> 2. SetupApi.dll can’t uninstall the FSD Recognizer either with workaround or
without it.
> That is why I am using a nasty workaround with DelReg directive inside
DefaultUninstall section.
>
> Now the questions:
> Where was I wrong?
> If I was right, then is this a known problem with the FSD Recognizer
installation?
> Will it be fixed in next Service Pack of OS?
>
>
> ------------------ Content of INF-file -------------------------------
> ;
> ; InCDFat.inf
> ;
> ; Copyright 1995-2004 Ahead Software AG and its licensors.
> ; All Rights Reserved.
> ;
>
> [Version]
> signature = “$Windows NT$”
> Provider = %Ahead%
> DriverVer = 07/01/2004,4.2.13.0
>
> [DestinationDirs]
> DefaultDestDir = 12
> InCDFat.Files = 12
>
> [SourceDisksNames]
> 1 = %Disk1%,
>
> [SourceDisksFiles]
> InCDFat.sys = 1
> InCDFatRec.sys = 1
>
> [DefaultInstall.nt]
> CopyFiles = InCDFat.Files
>
> [DefaultInstall.nt.Services]
> AddService = InCDFat,InCDFat.Service
> AddService = InCDFatRec,InCDFatRec.Service
>
> [DefaultUninstall.nt]
> DelFiles = InCDFat.Files
> DelReg = InCDFatRec.DelRegistry
>
> [DefaultUninstall.nt.Services]
> DelService = InCDFat
>
> ;
> ; Services Section
> ;
>
> [InCDFat.Service]
> DisplayName = %InCDFatServiceDesc%
> ServiceBinary = %12%\InCDFat.sys ;%windir%\system32\drivers\InCDFat.sys
> ServiceType = %SERVICE_FILE_SYSTEM_DRIVER%
> StartType = %SERVICE_DEMAND_START%
> ErrorControl = %SERVICE_ERROR_IGNORE%
> AddReg = InCDFat.AddRegistry
>
> [InCDFatRec.Service]
> DisplayName = %InCDFatRecServiceDesc%
> ServiceBinary = %12%\InCDFatRec.sys
> ServiceType = %SERVICE_FILE_SYSTEM_DRIVER%
> StartType = %SERVICE_SYSTEM_START%
> ErrorControl = %SERVICE_ERROR_IGNORE%
> AddReg = InCDFatRec.AddRegistry
>
> [InCDFat.AddRegistry]
> HKR,“Group”,%REG_SZ%,“File system”
>
> [InCDFatRec.AddRegistry]
> HKR,“Group”,%REG_SZ%,“File system”
> HKR,“Type”,%REG_DWORD%,%SERVICE_FILE_SYSTEM_RECOGNIZER%
>
> [InCDFatRec.DelRegistry]
> HKLM,“SYSTEM\CurrentControlSet\Services\InCDFatRec”
>
> [InCDFat.Files]
> InCDFat.sys,0x00001004
> InCDFatRec.sys,0x00001004
>
> [Strings]
> Ahead = “Ahead Software AG”
> InCDFatServiceDesc = “Ahead InCDFat File System Driver”
> InCDFatRecServiceDesc = “Ahead InCDFat FSD Recognizer”
> Disk1 = “Ahead InCDFat Source Media”
> ; Start Type
> SERVICE_BOOT_START = 0x0
> SERVICE_SYSTEM_START = 0x1
> SERVICE_AUTO_START = 0x2
> SERVICE_DEMAND_START = 0x3
> SERVICE_DISABLED = 0x4
> ; Service Type
> SERVICE_KERNEL_DRIVER = 0x1
> SERVICE_FILE_SYSTEM_DRIVER = 0x2
> SERVICE_FILE_SYSTEM_RECOGNIZER = 0x8
> ; Error Control
> SERVICE_ERROR_IGNORE = 0x0
> SERVICE_ERROR_NORMAL = 0x1
> SERVICE_ERROR_SEVERE = 0x2
> SERVICE_ERROR_CRITICAL = 0x3
> ; Registry types
> REG_SZ = 0x00000000
> REG_MULTI_SZ = 0x00010000
> REG_EXPAND_SZ = 0x00020000
> REG_DWORD = 0x00010001
> ; Delete service options
> SPSVCINST_STOPSERVICE = 0x00000200
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

4

Hello Maxim,

Saturday, July 03, 2004, 12:39:56 AM, you wrote:

Maxim S. Shatskih> Just do this using CreateService.

Maxim S. Shatskih> Maxim Shatskih, Windows DDK MVP
Maxim S. Shatskih> StorageCraft Corporation
Maxim S. Shatskih> xxxxx@storagecraft.com
Maxim S. Shatskih> http://www.storagecraft.com

Thanks, I knew about this method of installation.
My question was about INF-file installation and related to passing
“Windows Logo Program System and Device Requirements, Version 2.2”.

On:

http://www.microsoft.com/whdc/winlogo/downloads.mspx

In “Windows Logo Program System and Device Requirements, Version 2.2” which
is “WLP22-10.doc”, is written as “Driver and Software Requirements”:

"Windows-based driver installation. Driver installation and removal must use
Windows-based methods, as defined in the Windows DDKs. For Windows
XP/Windows Server 2003 family, this means only INF-based installation routines. "

Best regards,
Al

Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail

5

> Thanks, I knew about this method of installation.

My question was about INF-file installation and related to passing
“Windows Logo Program System and Device Requirements, Version 2.2”.

If you use the NT4-style non-WDM non-PnP kernel add-on - then why use INF file
for it? The requirements are used for WHQL signing and signature checks, and
NT4-style binaries are not such anyway.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

6

Hello Maxim,

Monday, July 05, 2004, 9:59:38 PM, you wrote:

> Thanks, I knew about this method of installation.
> My question was about INF-file installation and related to passing
> “Windows Logo Program System and Device Requirements, Version 2.2”.

Maxim S. Shatskih> If you use the NT4-style non-WDM non-PnP kernel add-on - then why use INF file
Maxim S. Shatskih> for it? The requirements are used for WHQL signing and signature checks, and
Maxim S. Shatskih> NT4-style binaries are not such anyway.

Why do you think that INF-file required only for WDM drivers?
Please, proof this statement with links, quotation and etc.!
Anyway FSD drivers for Windows 2000 and above should handle PnP manager IRP`s.
BTW, my original question was about INF-file wrong functionality. Other installation method just
unrelated to the question.
The question was directed mainly to Microsoft people for defect confirmation.

I want to use advantages of Windows Update as well. On
http://www.microsoft.com/whdc/maintain/default.mspx is written:

“Windows Update is the online extension of Windows that helps keep software and drivers up to
date. Winqual services provide mechanisms for managing distribution of drivers through Windows
Update. Drivers that have passed “Designed for Windows” Logo Program testing and have digital
signatures are eligible for distribution through Windows Update.”

Even more on http://www.microsoft.com/whdc/maintain/DrvUpdate.mspx is written:

“How to Deliver Drivers through Windows Update

We strongly recommend that you deliver drivers to end users through Windows Update. Windows Error
Reporting (WER) data shows that distributing drivers through Windows Update significantly reduces
the number of system crashes and hardware failures caused by drivers.

To deliver drivers on Windows Update:

  1. Submit your drivers for the “Designed for Windows” logo.

  2. When you submit a package for logo program testing through the Windows Quality Online Services
    (Winqual), indicate that you want to add your drivers to the Windows Update site and accept the
    Driver Distribution Agreement.

To be eligible for delivery through Windows Update, a driver package must meet the following
criteria:

  • Compress to a file size of 20 MB or less.
  • Pass Windows Hardware Quality Labs (WHQL) testing review for the “Designed for Windows” logo
    program.
  • Use INF-based installation, with:
  • A unique and current DriverVer directive in the information (.inf) files.
  • Installation only on specific hardware ID matches with no known problems.
  • No requirements for system restarts or user input during installation.”

Best regards,
Al

Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail

7

Because you can go into the NT4 registry and MANUALLY add your driver to the
Services key of CurrentControlSet and it will load and its DE function will
be called. You can do the same thing on 2000 or XP for an NT4 legacy driver.
Those of us that have been doing this for as many years as Max and others of
us have KNOW this without having to have documentation approval. Nt4 also
has RegIni which will copy a properly formatted registry fragment into the
registry with the same result.

So yes … experience, which generally is far better than documentation,
states that WDM’s require INF … though if you know what you are doing you
can most likely manually install a WDM driver.

–
Gary G. Little
Seagate Technologies, LLC

“Al Shatilo” wrote in message news:xxxxx@ntdev…
> Hello Maxim,
>
> Monday, July 05, 2004, 9:59:38 PM, you wrote:
>
> >> Thanks, I knew about this method of installation.
> >> My question was about INF-file installation and related to passing
> >> “Windows Logo Program System and Device Requirements, Version 2.2”.
>
> Maxim S. Shatskih> If you use the NT4-style non-WDM non-PnP kernel
add-on - then why use INF file
> Maxim S. Shatskih> for it? The requirements are used for WHQL signing and
signature checks, and
> Maxim S. Shatskih> NT4-style binaries are not such anyway.
>
> Why do you think that INF-file required only for WDM drivers?
> Please, proof this statement with links, quotation and etc.!
> Anyway FSD drivers for Windows 2000 and above should handle PnP manager
IRP`s.
> BTW, my original question was about INF-file wrong functionality. Other
installation method just
> unrelated to the question.
> The question was directed mainly to Microsoft people for defect
confirmation.
>
> I want to use advantages of Windows Update as well. On
> http://www.microsoft.com/whdc/maintain/default.mspx is written:
>
> “Windows Update is the online extension of Windows that helps keep
software and drivers up to
> date. Winqual services provide mechanisms for managing distribution of
drivers through Windows
> Update. Drivers that have passed “Designed for Windows” Logo Program
testing and have digital
> signatures are eligible for distribution through Windows Update.”
>
> Even more on http://www.microsoft.com/whdc/maintain/DrvUpdate.mspx is
written:
>
> “How to Deliver Drivers through Windows Update
>
> We strongly recommend that you deliver drivers to end users through
Windows Update. Windows Error
> Reporting (WER) data shows that distributing drivers through Windows
Update significantly reduces
> the number of system crashes and hardware failures caused by drivers.
>
> To deliver drivers on Windows Update:
>
> 1. Submit your drivers for the “Designed for Windows” logo.
>
> 2. When you submit a package for logo program testing through the Windows
Quality Online Services
> (Winqual), indicate that you want to add your drivers to the Windows
Update site and accept the
> Driver Distribution Agreement.
>
> To be eligible for delivery through Windows Update, a driver package must
meet the following
> criteria:
> - Compress to a file size of 20 MB or less.
> - Pass Windows Hardware Quality Labs (WHQL) testing review for the
“Designed for Windows” logo
> program.
> - Use INF-based installation, with:
> - A unique and current DriverVer directive in the information (.inf)
files.
> - Installation only on specific hardware ID matches with no known
problems.
> - No requirements for system restarts or user input during
installation.”
>
> Best regards,
> Al
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - Send 10MB messages!
> http://promotions.yahoo.com/new_mail
>

8

Hello Gary,

Wednesday, July 07, 2004, 3:17:31 PM, you wrote:

Gary G. Little> Because you can go into the NT4 registry and MANUALLY add your driver to the
Gary G. Little> Services key of CurrentControlSet and it will load and its DE function will
Gary G. Little> be called. You can do the same thing on 2000 or XP for an NT4 legacy driver.
Gary G. Little> Those of us that have been doing this for as many years as Max and others of
Gary G. Little> us have KNOW this without having to have documentation approval. Nt4 also
Gary G. Little> has RegIni which will copy a properly formatted registry fragment into the
Gary G. Little> registry with the same result.

Gary G. Little> So yes … experience, which generally is far better than documentation,
Gary G. Little> states that WDM’s require INF … though if you know what you are doing you
Gary G. Little> can most likely manually install a WDM driver.

What are you trying to proof? Any driver can be added to the system manually.
But how all your statements related to the question?
How can experience to install drivers manually can help if I have to install drivers using
INF-file?
How installation with RegIni can fix defect of Service section for FSD recognizer?

Finally, I asked to not suggest to me other installation methods than using INF-file.

PS. I glad that somebody can do something without having to have documentation approval? But I
should follow documentation approval to use benefits of Windows Update.

Best regards,
Al

Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail

9

Al,

I could be wrong, but I don’t think Microsoft currently has a program for
getting a logo for a filesystem driver and its associated filesystem
recognizer driver. You might however want to ask over on the ntfsd list, as
us hardware driver folks over here are probably going to continue to annoy
you with our hardware-centric view of the world.

=====================
Mark Roddy

-----Original Message-----
From: Al Shatilo [mailto:xxxxx@yahoo.com]
Sent: Wednesday, July 07, 2004 10:09 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Dark underground of INF-files

Hello Gary,

Wednesday, July 07, 2004, 3:17:31 PM, you wrote:

Gary G. Little> Because you can go into the NT4 registry and MANUALLY add
your driver to the
Gary G. Little> Services key of CurrentControlSet and it will load and its
DE function will
Gary G. Little> be called. You can do the same thing on 2000 or XP for an
NT4 legacy driver.
Gary G. Little> Those of us that have been doing this for as many years as
Max and others of
Gary G. Little> us have KNOW this without having to have documentation
approval. Nt4 also
Gary G. Little> has RegIni which will copy a properly formatted registry
fragment into the
Gary G. Little> registry with the same result.

Gary G. Little> So yes … experience, which generally is far better than
documentation,
Gary G. Little> states that WDM’s require INF … though if you know what
you are doing you
Gary G. Little> can most likely manually install a WDM driver.

What are you trying to proof? Any driver can be added to the system
manually.
But how all your statements related to the question?
How can experience to install drivers manually can help if I have to install
drivers using
INF-file?
How installation with RegIni can fix defect of Service section for FSD
recognizer?

Finally, I asked to not suggest to me other installation methods than using
INF-file.

PS. I glad that somebody can do something without having to have
documentation approval? But I
should follow documentation approval to use benefits of Windows Update.

Best regards,
Al

Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

10

There is limited signing of file system filter drivers (for anti-virus
last I checked) and none for file system drivers. There are sample INF
files in the IFS Kit, but they are little more than “add the necessary
keys to the registry via an INF file” because the hardware oriented view
of INF files (“New Hardware Wizard”) does not work - file system drivers
of any ilk are NOT enumerated, do NOT appear in the PnP view of the
world, and in fact are generally marked as “disabled” (to avoid getting
tangled up with PnP apparently) in the registry.

Mark is absolutely right - file system related questions really do
belong on NTFSD, although you won’t get much there either since most of
us do only the bare minimum required. I personally find it is no more
difficult to write a program using the SCM than an INF file, but given
that you’ve constrained the problem to using an INF, look at the trivial
examples in the IFS Kit.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Wednesday, July 07, 2004 10:24 AM
To: ntdev redirect
Subject: RE: [ntdev] Dark underground of INF-files

Al,

I could be wrong, but I don’t think Microsoft currently has a program
for getting a logo for a filesystem driver and its associated filesystem
recognizer driver. You might however want to ask over on the ntfsd list,
as us hardware driver folks over here are probably going to continue to
annoy you with our hardware-centric view of the world.

=====================
Mark Roddy

-----Original Message-----
From: Al Shatilo [mailto:xxxxx@yahoo.com]
Sent: Wednesday, July 07, 2004 10:09 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Dark underground of INF-files

Hello Gary,

Wednesday, July 07, 2004, 3:17:31 PM, you wrote:

Gary G. Little> Because you can go into the NT4 registry and MANUALLY
add your driver to the Gary G. Little> Services key of CurrentControlSet
and it will load and its DE function will Gary G. Little> be called. You
can do the same thing on 2000 or XP for an
NT4 legacy driver.
Gary G. Little> Those of us that have been doing this for as many years
as Max and others of Gary G. Little> us have KNOW this without having to
have documentation approval. Nt4 also Gary G. Little> has RegIni which
will copy a properly formatted registry fragment into the Gary G.
Little> registry with the same result.

Gary G. Little> So yes … experience, which generally is far better
than documentation, Gary G. Little> states that WDM’s require INF …
though if you know what you are doing you Gary G. Little> can most
likely manually install a WDM driver.

What are you trying to proof? Any driver can be added to the system
manually.
But how all your statements related to the question?
How can experience to install drivers manually can help if I have to
install drivers using INF-file?
How installation with RegIni can fix defect of Service section for FSD
recognizer?

Finally, I asked to not suggest to me other installation methods than
using INF-file.

PS. I glad that somebody can do something without having to have
documentation approval? But I should follow documentation approval to
use benefits of Windows Update.

Best regards,
Al

Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@osr.com To unsubscribe
send a blank email to xxxxx@lists.osr.com

11

Hi,

Let me shortly jump in the conversation. :wink:

Microsoft do have a pilot program for getting a ~logo~ on any kind of
driver:

http://www.microsoft.com/whdc/hwtest/search/details.aspx?ID=826

(“WHQL code coverage pilot program to submit hardware-independent drivers
for digital signature”)

Is the service-removal .INF issue raised by Al really only affecting fsd/fsd
rec? No other driver suffers from such issue?

Jump done, leaving the place to experts now.

Best regards,

David Burg

David Burg
Software Development,
InCD Project Leader

Ahead Software AG phone: +49 (0)7248 911 862 (direct line)
Im Stoeckmaedle 18 fax: +49 (0)7248 911 888
76307 Karlsbad email: xxxxx@nero.com
Germany http://www.nero.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Wednesday, July 07, 2004 4:24 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Dark underground of INF-files

Al,

I could be wrong, but I don’t think Microsoft currently has a program for
getting a logo for a filesystem driver and its associated filesystem
recognizer driver. You might however want to ask over on the ntfsd list, as
us hardware driver folks over here are probably going to continue to annoy
you with our hardware-centric view of the world.

=====================
Mark Roddy

-----Original Message-----
From: Al Shatilo [mailto:xxxxx@yahoo.com]
Sent: Wednesday, July 07, 2004 10:09 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Dark underground of INF-files

Hello Gary,

Wednesday, July 07, 2004, 3:17:31 PM, you wrote:

Gary G. Little> Because you can go into the NT4 registry and MANUALLY add
your driver to the
Gary G. Little> Services key of CurrentControlSet and it will load and its
DE function will
Gary G. Little> be called. You can do the same thing on 2000 or XP for an
NT4 legacy driver.
Gary G. Little> Those of us that have been doing this for as many years as
Max and others of
Gary G. Little> us have KNOW this without having to have documentation
approval. Nt4 also
Gary G. Little> has RegIni which will copy a properly formatted registry
fragment into the
Gary G. Little> registry with the same result.

Gary G. Little> So yes … experience, which generally is far better than
documentation,
Gary G. Little> states that WDM’s require INF … though if you know what
you are doing you
Gary G. Little> can most likely manually install a WDM driver.

What are you trying to proof? Any driver can be added to the system
manually.
But how all your statements related to the question?
How can experience to install drivers manually can help if I have to install
drivers using
INF-file?
How installation with RegIni can fix defect of Service section for FSD
recognizer?

Finally, I asked to not suggest to me other installation methods than using
INF-file.

PS. I glad that somebody can do something without having to have
documentation approval? But I
should follow documentation approval to use benefits of Windows Update.

Best regards,
Al

Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@nero.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

12

Note the restrictions on this program:

“WHQL will also issue a ‘Designed for Windows’ logo if your product is a
hardware and kernel-mode driver combination. Note: In this program, WHQL
won’t issue a ‘Software Logo.’”

And:

“The code coverage pilot program is offered through both the WHQL USA
and the WHQL Japan labs and is available only if the following criteria
are met:” … "The driver is not one of the following types: " … “File
system filter driver”

A strict reading of this would imply that if you have a file system
driver that works with a specific hardware device then you can obtain
the appropriate logo. If you had a software only driver (like a network
file system independent of the underlying network hardware, or CD/DVD
recording software independent of underlying hardware) then you could
not obtain such certification. Whether or not WHQL would agree with
that reading is really up to them and ultimately you will need to defer
to them.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David Burg
Sent: Wednesday, July 07, 2004 10:39 AM
To: ntdev redirect
Subject: RE: [ntdev] Dark underground of INF-files

Hi,

Let me shortly jump in the conversation. :wink:

Microsoft do have a pilot program for getting a ~logo~ on any kind of
driver:

http://www.microsoft.com/whdc/hwtest/search/details.aspx?ID=826

(“WHQL code coverage pilot program to submit hardware-independent
drivers for digital signature”)

Is the service-removal .INF issue raised by Al really only affecting
fsd/fsd rec? No other driver suffers from such issue?

Jump done, leaving the place to experts now.

Best regards,

David Burg

David Burg
Software Development,
InCD Project Leader

Ahead Software AG phone: +49 (0)7248 911 862 (direct line)
Im Stoeckmaedle 18 fax: +49 (0)7248 911 888
76307 Karlsbad email: xxxxx@nero.com
Germany http://www.nero.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Wednesday, July 07, 2004 4:24 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Dark underground of INF-files

Al,

I could be wrong, but I don’t think Microsoft currently has a program
for getting a logo for a filesystem driver and its associated filesystem
recognizer driver. You might however want to ask over on the ntfsd list,
as us hardware driver folks over here are probably going to continue to
annoy you with our hardware-centric view of the world.

=====================
Mark Roddy

-----Original Message-----
From: Al Shatilo [mailto:xxxxx@yahoo.com]
Sent: Wednesday, July 07, 2004 10:09 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Dark underground of INF-files

Hello Gary,

Wednesday, July 07, 2004, 3:17:31 PM, you wrote:

Gary G. Little> Because you can go into the NT4 registry and MANUALLY
add your driver to the Gary G. Little> Services key of CurrentControlSet
and it will load and its DE function will Gary G. Little> be called. You
can do the same thing on 2000 or XP for an
NT4 legacy driver.
Gary G. Little> Those of us that have been doing this for as many years
as Max and others of Gary G. Little> us have KNOW this without having to
have documentation approval. Nt4 also Gary G. Little> has RegIni which
will copy a properly formatted registry fragment into the Gary G.
Little> registry with the same result.

Gary G. Little> So yes … experience, which generally is far better
than documentation, Gary G. Little> states that WDM’s require INF …
though if you know what you are doing you Gary G. Little> can most
likely manually install a WDM driver.

What are you trying to proof? Any driver can be added to the system
manually.
But how all your statements related to the question?
How can experience to install drivers manually can help if I have to
install drivers using INF-file?
How installation with RegIni can fix defect of Service section for FSD
recognizer?

Finally, I asked to not suggest to me other installation methods than
using INF-file.

PS. I glad that somebody can do something without having to have
documentation approval? But I should follow documentation approval to
use benefits of Windows Update.

Best regards,
Al

Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@nero.com To unsubscribe
send a blank email to xxxxx@lists.osr.com

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@osr.com To unsubscribe
send a blank email to xxxxx@lists.osr.com

13

Hello Tony,

Indeed a logo in unlikely to be obtained through this pilot program for the
particular case of fsd/fsd filter independent of underlying hardware.
However, the resulting driver signing should open doors for discussion with
the windows update people, and I think we can reasonably assume that a
successful pilot program would encourage Microsoft to pursue with a release
program with logo possibilities for hardware-independent drivers.

Beside, part of this pilot program objective is to learn what difficulties
participants will meet, and well, this .INF file issue is an interesting
case - isn’t it?

Best regards,

David.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Wednesday, July 07, 2004 4:55 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Dark underground of INF-files

Note the restrictions on this program:

“WHQL will also issue a ‘Designed for Windows’ logo if your product is a
hardware and kernel-mode driver combination. Note: In this program, WHQL
won’t issue a ‘Software Logo.’”

And:

“The code coverage pilot program is offered through both the WHQL USA
and the WHQL Japan labs and is available only if the following criteria
are met:” … "The driver is not one of the following types: " … “File
system filter driver”

A strict reading of this would imply that if you have a file system
driver that works with a specific hardware device then you can obtain
the appropriate logo. If you had a software only driver (like a network
file system independent of the underlying network hardware, or CD/DVD
recording software independent of underlying hardware) then you could
not obtain such certification. Whether or not WHQL would agree with
that reading is really up to them and ultimately you will need to defer
to them.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David Burg
Sent: Wednesday, July 07, 2004 10:39 AM
To: ntdev redirect
Subject: RE: [ntdev] Dark underground of INF-files

Hi,

Let me shortly jump in the conversation. :wink:

Microsoft do have a pilot program for getting a ~logo~ on any kind of
driver:

http://www.microsoft.com/whdc/hwtest/search/details.aspx?ID=826

(“WHQL code coverage pilot program to submit hardware-independent
drivers for digital signature”)

Is the service-removal .INF issue raised by Al really only affecting
fsd/fsd rec? No other driver suffers from such issue?

Jump done, leaving the place to experts now.

Best regards,

David Burg

David Burg
Software Development,
InCD Project Leader

Ahead Software AG phone: +49 (0)7248 911 862 (direct line)
Im Stoeckmaedle 18 fax: +49 (0)7248 911 888
76307 Karlsbad email: xxxxx@nero.com
Germany http://www.nero.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Wednesday, July 07, 2004 4:24 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Dark underground of INF-files

Al,

I could be wrong, but I don’t think Microsoft currently has a program
for getting a logo for a filesystem driver and its associated filesystem
recognizer driver. You might however want to ask over on the ntfsd list,
as us hardware driver folks over here are probably going to continue to
annoy you with our hardware-centric view of the world.

=====================
Mark Roddy

-----Original Message-----
From: Al Shatilo [mailto:xxxxx@yahoo.com]
Sent: Wednesday, July 07, 2004 10:09 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Dark underground of INF-files

Hello Gary,

Wednesday, July 07, 2004, 3:17:31 PM, you wrote:

Gary G. Little> Because you can go into the NT4 registry and MANUALLY
add your driver to the Gary G. Little> Services key of CurrentControlSet
and it will load and its DE function will Gary G. Little> be called. You
can do the same thing on 2000 or XP for an
NT4 legacy driver.
Gary G. Little> Those of us that have been doing this for as many years
as Max and others of Gary G. Little> us have KNOW this without having to
have documentation approval. Nt4 also Gary G. Little> has RegIni which
will copy a properly formatted registry fragment into the Gary G.
Little> registry with the same result.

Gary G. Little> So yes … experience, which generally is far better
than documentation, Gary G. Little> states that WDM’s require INF …
though if you know what you are doing you Gary G. Little> can most
likely manually install a WDM driver.

What are you trying to proof? Any driver can be added to the system
manually.
But how all your statements related to the question?
How can experience to install drivers manually can help if I have to
install drivers using INF-file?
How installation with RegIni can fix defect of Service section for FSD
recognizer?

Finally, I asked to not suggest to me other installation methods than
using INF-file.

PS. I glad that somebody can do something without having to have
documentation approval? But I should follow documentation approval to
use benefits of Windows Update.

Best regards,
Al

Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@nero.com To unsubscribe
send a blank email to xxxxx@lists.osr.com

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@osr.com To unsubscribe
send a blank email to xxxxx@lists.osr.com

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@nero.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

14

Hello Tony,

Wednesday, July 07, 2004, 4:34:01 PM, you wrote:

Tony Mason> There is limited signing of file system filter drivers (for anti-virus
Tony Mason> last I checked) and none for file system drivers. There are sample INF
Tony Mason> files in the IFS Kit, but they are little more than “add the necessary
Tony Mason> keys to the registry via an INF file” because the hardware oriented view
Tony Mason> of INF files (“New Hardware Wizard”) does not work - file system drivers
Tony Mason> of any ilk are NOT enumerated, do NOT appear in the PnP view of the
Tony Mason> world, and in fact are generally marked as “disabled” (to avoid getting
Tony Mason> tangled up with PnP apparently) in the registry.

Tony Mason> Mark is absolutely right - file system related questions really do
Tony Mason> belong on NTFSD, although you won’t get much there either since most of
Tony Mason> us do only the bare minimum required.

I already asked the same question in NTFSD. Because of initial Maxim answer, I just follow by the
stream and continue discussion here.

Tony Mason> I personally find it is no more
Tony Mason> difficult to write a program using the SCM than an INF file, but given
Tony Mason> that you’ve constrained the problem to using an INF, look at the trivial
Tony Mason> examples in the IFS Kit.

I found only several samples that somehow related to FSD and all of them install FS filter
drivers.
By the way, I exactly did that you suggest and found problem of FSD recognizer installation.

Tony Mason> Regards,

Tony Mason> Tony

Tony Mason> Tony Mason
Tony Mason> Consulting Partner
Tony Mason> OSR Open Systems Resources, Inc.
Tony Mason> http://www.osr.com

Best regards,
Al

Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo

15

> Why do you think that INF-file required only for WDM drivers?

Please, proof this statement with links, quotation and etc.!

Because NT4-style drivers are well-installed using CreateService.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

16

Hello Maxim,

Ok, but that does not apply to our drivers: our drivers are not NT4-style,
are they?? :-? Maybe something from the INF file of Al made you believe the
drivers are NT4-style? (As you mentioned NT4-style drivers would not fit
WHQL signing and signature checks requirements, which are precisely what we
want to achieve and why we need INF-file installation)

Best regards,

David Burg.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Friday, July 09, 2004 4:01 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Dark underground of INF-files

Why do you think that INF-file required only for WDM drivers?
Please, proof this statement with links, quotation and etc.!

Because NT4-style drivers are well-installed using CreateService.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@nero.com
To unsubscribe send a blank email to xxxxx@lists.osr.com