Whats wrong with these modified Passthru inf files?

OSR_Community_User · October 19, 2006, 7:11am

My Driver’s PtBindAdapter is not being called when i use these modified inf
files. Pls let me know if you can figure out some problem with these inf
files.

/******************************************************************************************/
/* Protocol Inf
**************************************************************************/

/******************************************************************************************/

[Version]
Signature = “$Windows NT$”
Class = NetService
ClassGUID = {4D36E974-E325-11CE-BFC1-08002BE10318}
Provider = %Startup%
DriverVer = 10/19/2006,1.1.1.1

[Manufacturer]
%Startup% = STARTUP,NTx86

[ControlFlags]

; For Win2K
[Startup]
%IMROHC_Desc% = IMROHC.ndi, ms_passthru

[STARTUP.NTx86]
%IMROHC_Desc% = IMROHC.ndi, ms_passthru

[IMROHC.ndi]
AddReg = IMROHC.ndi.AddReg, IMROHC.AddReg
Characteristics = 0x4410 ; NCF_FILTER | NCF_NDIS_PROTOCOL !–Filter
Specific–!!
CopyFiles = IMROHC.Files.Sys
CopyInf = IMROHC_M.inf

[IMROHC.ndi.Remove]
DelFiles = IMROHC.Files.Sys

[IMROHC.ndi.Services]
AddService = IMROHC, IMROHC.AddService

[IMROHC.AddService]
DisplayName = %IMROHCService_Desc%
ServiceType = 1 ;SERVICE_KERNEL_DRIVER
StartType = 3 ;SERVICE_DEMAND_START
ErrorControl = 1 ;SERVICE_ERROR_NORMAL
ServiceBinary = %12%\IMROHC.sys
LoadOrderGroup = PNP_TDI
AddReg = IMROHC.AddService.AddReg

[IMROHC.AddService.AddReg]

[SourceDisksNames]
1=%DiskDescription%,“”,

[SourceDisksFiles]
IMROHC.sys=1

[DestinationDirs]
DefaultDestDir = 12
IMROHC.Files.Sys = 12 ; %windir%\System32\drivers

[IMROHC.Files.Sys]
IMROHC.sys,2

[IMROHC.ndi.AddReg]
HKR, Ndi, HelpText, , %IMROHC_HELP%
HKR, Ndi, FilterClass, , failover
HKR, Ndi, FilterDeviceInfId, , ms_passthrump
HKR, Ndi, Service, , IMROHC
HKR, Ndi\Interfaces, UpperRange, , noupper
HKR, Ndi\Interfaces, LowerRange, , nolower
HKR, Ndi\Interfaces, FilterMediaTypes, , “ethernet”

[IMROHC.AddReg]
HKR, Parameters, Param1, 0, 4

[Strings]
Startup = “Startup”
DiskDescription = “ROHC Installation Disk for Windows”
IMROHC_Desc = “ROHC Driver for Windows”
IMROHC_HELP = “ROHC Driver for Windows”
IMROHCService_Desc = “ROHC Service”
/******************************************************************************************/
/* Miniport Inf
**************************************************************************/

/******************************************************************************************/

[Version]
signature = “$Windows NT$”
Class = Net
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
Provider = %Startup%
DriverVer = 10/19/2006,1.1.1.1

[ControlFlags]
ExcludeFromSelect = ms_passthrump

[DestinationDirs]
DefaultDestDir=12
; No files to copy

[Manufacturer]
%Startup% = STARTUP,NTx86

; For Win2K
[Startup]
%IMROHCMP_Desc% = IMROHCMP.ndi, ms_passthrump

; For XP and later
[STARTUP.NTx86]
%IMROHCMP_Desc% = IMROHCMP.ndi, ms_passthrump

[IMROHCMP.ndi]
Characteristics = 0x29 ;NCF_NOT_USER_REMOVABLE | NCF_VIRTUAL | NCF_HIDDEN
CopyFiles =

[IMROHCMP.ndi.Services]
AddService = IMROHC,0x2, IMROHCMP.AddService

[IMROHCMP.AddService]
ServiceType = 1 ;SERVICE_KERNEL_DRIVER
StartType = 3 ;SERVICE_DEMAND_START
ErrorControl = 1 ;SERVICE_ERROR_NORMAL
ServiceBinary = %12%\IMROHC.sys

[IMROHCMP.AddService.AddReg]

[Strings]
Startup = “Startup”
IMROHCMP_Desc = “IMROHC Miniport”

[SourceDisksNames]
;None

[SourceDisksFiles]
;None

TIA,

Giri.

David_R_Cattley · October 19, 2006, 8:03am

First: You should have changed the PnP names of the NetService and Net
(Adapter} device objects and *not* used the ms_passthru and ms_passthrump
names. Pick something else. Since you undoutbly have installed the Passhru
sample on your system, you probably have at least one set (if not more) of
INFs in %windir%\inf named OEMnnn.inf that already specify how to install
the ms_passthrump device(s).

Second: Is your driver even being loaded? I don’t mean if you do a “NET
START IMROHC” I mean is it being loaded automatically by PnP. I am going to
guess ‘no’.

As with adapting any sample, it is best to ‘search and replace’ just about
every substring that has the sample name in it. In this case, the
‘passthru’ in ms_pasthru and ms_passthrump are pretty important. These are
the ‘assumed’ PnP IDs for the two components being installed. Unless you
change them, PnP is going to potentially make the wrong decision when faced
with installing a driver for a ms_passthrump device, which, is the device ID
of the virtual miniport created by the Passthru driver (and your driver so
says your INF).

I reccomend that you go to the WHDC site (www.microsoft.com/whdc) and find
the whitepaper on debugging PnP install “Troubleshooting Device Installation
with the SetupAPI Log File”. It will explain how to use
%windir%\setupapi.log to see what PnP has decided to do while installing
your driver. I suspect you will find it has decided to pick the
ms_passthrump driver from the Passthru sample and not yours.

Good Luck,
Dave Cattley
Consulting Engineer
Systems Software Development

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of giri
Sent: Thursday, October 19, 2006 7:11 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Whats wrong with these modified Passthru inf files?

My Driver’s PtBindAdapter is not being called when i use these modified inf
files. Pls let me know if you can figure out some problem with these inf
files.

/***************************************************************************
***************/
/* Protocol Inf
**************************************************************************/
/***************************************************************************
***************/

[Version]
Signature = “$Windows NT$”
Class = NetService
ClassGUID = {4D36E974-E325-11CE-BFC1-08002BE10318}
Provider = %Startup%
DriverVer = 10/19/2006,1.1.1.1 http:

[Manufacturer]
%Startup% = STARTUP,NTx86

[ControlFlags]

; For Win2K
[Startup]
%IMROHC_Desc% = IMROHC.ndi, ms_passthru

[STARTUP.NTx86]
%IMROHC_Desc% = IMROHC.ndi, ms_passthru

[IMROHC.ndi]
AddReg = IMROHC.ndi.AddReg, IMROHC.AddReg
Characteristics = 0x4410 ; NCF_FILTER | NCF_NDIS_PROTOCOL !–Filter
Specific–!!
CopyFiles = IMROHC.Files.Sys
CopyInf = IMROHC_M.inf

[IMROHC.ndi.Remove]
DelFiles = IMROHC.Files.Sys

[IMROHC.ndi.Services]
AddService = IMROHC, IMROHC.AddService

[IMROHC.AddService]
DisplayName = %IMROHCService_Desc%
ServiceType = 1 ;SERVICE_KERNEL_DRIVER
StartType = 3 ;SERVICE_DEMAND_START
ErrorControl = 1 ;SERVICE_ERROR_NORMAL
ServiceBinary = %12%\IMROHC.sys
LoadOrderGroup = PNP_TDI
AddReg = IMROHC.AddService.AddReg

[IMROHC.AddService.AddReg]

[SourceDisksNames]
1=%DiskDescription%,“”,

[SourceDisksFiles]
IMROHC.sys=1

[DestinationDirs]
DefaultDestDir = 12
IMROHC.Files.Sys = 12 ; %windir%\System32\drivers

[IMROHC.Files.Sys]
IMROHC.sys,2

[IMROHC.ndi.AddReg]
HKR, Ndi, HelpText, , %IMROHC_HELP%
HKR, Ndi, FilterClass, , failover
HKR, Ndi, FilterDeviceInfId, , ms_passthrump
HKR, Ndi, Service, , IMROHC
HKR, Ndi\Interfaces, UpperRange, , noupper
HKR, Ndi\Interfaces, LowerRange, , nolower
HKR, Ndi\Interfaces, FilterMediaTypes, , “ethernet”

[IMROHC.AddReg]
HKR, Parameters, Param1, 0, 4

[Strings]
Startup = “Startup”
DiskDescription = “ROHC Installation Disk for Windows”
IMROHC_Desc = “ROHC Driver for Windows”
IMROHC_HELP = “ROHC Driver for Windows”
IMROHCService_Desc = “ROHC Service”

/ **********************************************************
/
/ Miniport Inf
/
/
*************** /

[Version]
signature = “$Windows NT$”
Class = Net
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
Provider = %Startup%
DriverVer = 10/19/2006,1.1.1.1

[ControlFlags]
ExcludeFromSelect = ms_passthrump

[DestinationDirs]
DefaultDestDir=12
; No files to copy

[Manufacturer]
%Startup% = STARTUP,NTx86

; For Win2K
[Startup]
%IMROHCMP_Desc% = IMROHCMP.ndi, ms_passthrump

; For XP and later
[STARTUP.NTx86]
%IMROHCMP_Desc% = IMROHCMP.ndi, ms_passthrump

[IMROHCMP.ndi]
Characteristics = 0x29 ;NCF_NOT_USER_REMOVABLE | NCF_VIRTUAL | NCF_HIDDEN
CopyFiles =

[IMROHCMP.ndi.Services]
AddService = IMROHC,0x2, IMROHCMP.AddService

[IMROHCMP.AddService]
ServiceType = 1 ;SERVICE_KERNEL_DRIVER
StartType = 3 ;SERVICE_DEMAND_START
ErrorControl = 1 ;SERVICE_ERROR_NORMAL
ServiceBinary = %12%\IMROHC.sys

[IMROHCMP.AddService.AddReg]

[Strings]
Startup = “Startup”
IMROHCMP_Desc = “IMROHC Miniport”

[SourceDisksNames]
;None

[SourceDisksFiles]
;None

TIA,

Giri.

— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the List
Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer</http:>

OSR_Community_User · October 19, 2006, 8:46am

Hi David,

I dont do “net start IMROHC” but use the passthru installation procedure
of Adding Service and showing the path to the directory where inf files and
sys file are present
I succesfully installed passthru.sys and when I uninstalled it, i made
sure i deleted oemXX.inf for the two inf files
I have modified all the strings initially in both the inf files,
including ms_passthru and ms_passthruMP but I was facing the same problem.
So I did the text by text replacement in an iterative manner, each time
performing install and uninstall sucessfully. I started facing problem when
I replaced passthru.ndi etc with IMROHC.ndi corrsponding .AddReg section
names etc…
I have been observing c:\windows\setupapi.log to find how different it is
installing passthru.sys and imrohc.sys. I found only one difference in that
for passthru installation, the setup is able to find ms_passthrump in
oem18.inf but for IMROHC installation, its first updating INFCACHE1.dat and
then finding ms_passthru.mp in oemxx.inf.
My driver is getting loaded but not getting called at PtBindAdapter. Its
getting - PtPnpHandler for Adapter 0x00000000 for event 6, PtPnpHandler for
Adapter 0x00000000 for event 4, PtPnpHandler for Adapter 0x00000000 for
event 6 and Reconfigure for Adapter 0x0000000. And there after the LAN
connection stops functioning .
Finally after installing and uninstalling passthru.sys, I checked the
registry and couldnt find any occurances of ms_passthrump. Also I replaced
ms_passthru and ms_passthrump with new texts and the result is same.

Also I deleted OEMXX.inf’s corresponding to passthru and IMROHC
installations and then deleted INFCACHE.1 and observed that INFCACHE.1 is
rebuilt when i tried fresh install of IMROHC. But the same problem was
observed.

Finally I didnt understand what this is:

[Passthru.AddReg]
; The following key is Required
; The following key is Passthru specific
HKR, Parameters, Param1, 0, 4

Can we use that registry entry as it is? What is that entry for?

Thanks,
Giri.

On 10/19/06, David R. Cattley wrote:
>
> First: You should have changed the PnP names of the NetService and Net
> (Adapter} device objects and not used the ms_passthru and ms_passthrump
> names. Pick something else. Since you undoutbly have installed the Passhru
> sample on your system, you probably have at least one set (if not more) of
> INFs in %windir%\inf named OEMnnn.inf that already specify how to install
> the ms_passthrump device(s).
>
> Second: Is your driver even being loaded? I don’t mean if you do a “NET
> START IMROHC” I mean is it being loaded automatically by PnP. I am going to
> guess ‘no’.
>
> As with adapting any sample, it is best to ‘search and replace’ just about
> every substring that has the sample name in it. In this case, the
> ‘passthru’ in ms_pasthru and ms_passthrump are pretty important. These are
> the ‘assumed’ PnP IDs for the two components being installed. Unless you
> change them, PnP is going to potentially make the wrong decision when faced
> with installing a driver for a ms_passthrump device, which, is the device ID
> of the virtual miniport created by the Passthru driver (and your driver so
> says your INF).
>
> I reccomend that you go to the WHDC site (www.microsoft.com/whdc) and find
> the whitepaper on debugging PnP install “Troubleshooting Device Installation
> with the SetupAPI Log File”. It will explain how to use
> %windir%\setupapi.log to see what PnP has decided to do while installing
> your driver. I suspect you will find it has decided to pick the
> ms_passthrump driver from the Passthru sample and not yours.
>
> Good Luck,
> Dave Cattley
> Consulting Engineer
> Systems Software Development
>
> ------------------------------
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] On Behalf Of giri
> Sent: Thursday, October 19, 2006 7:11 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Whats wrong with these modified Passthru inf files?
>
>
> My Driver’s PtBindAdapter is not being called when i use these modified
> inf files. Pls let me know if you can figure out some problem with these inf
> files.
>
>
> / /
> / Protocol Inf
> /
>
> //
>
> [Version]
> Signature = “$Windows NT$”
> Class = NetService
> ClassGUID = {4D36E974-E325-11CE-BFC1-08002BE10318}
> Provider = %Startup%
> DriverVer = 10/19/2006,1.1.1.1
>
>
> [Manufacturer]
> %Startup% = STARTUP,NTx86
>
> [ControlFlags]
>
> ; For Win2K
> [Startup]
> %IMROHC_Desc% = IMROHC.ndi, ms_passthru
>
> [STARTUP.NTx86]
> %IMROHC_Desc% = IMROHC.ndi, ms_passthru
>
> [IMROHC.ndi]
> AddReg = IMROHC.ndi.AddReg, IMROHC.AddReg
> Characteristics = 0x4410 ; NCF_FILTER | NCF_NDIS_PROTOCOL !–Filter
> Specific–!!
> CopyFiles = IMROHC.Files.Sys
> CopyInf = IMROHC_M.inf
>
> [IMROHC.ndi.Remove]
> DelFiles = IMROHC.Files.Sys
>
> [IMROHC.ndi.Services]
> AddService = IMROHC, IMROHC.AddService
>
> [IMROHC.AddService]
> DisplayName = %IMROHCService_Desc%
> ServiceType = 1 ;SERVICE_KERNEL_DRIVER
> StartType = 3 ;SERVICE_DEMAND_START
> ErrorControl = 1 ;SERVICE_ERROR_NORMAL
> ServiceBinary = %12%\IMROHC.sys
> LoadOrderGroup = PNP_TDI
> AddReg = IMROHC.AddService.AddReg
>
>
> [IMROHC.AddService.AddReg]
>
> [SourceDisksNames]
> 1=%DiskDescription%,“”,
>
> [SourceDisksFiles]
> IMROHC.sys=1
>
> [DestinationDirs]
> DefaultDestDir = 12
> IMROHC.Files.Sys = 12 ; %windir%\System32\drivers
>
> [IMROHC.Files.Sys]
> IMROHC.sys,2
>
> [IMROHC.ndi.AddReg]
> HKR, Ndi, HelpText, , %IMROHC_HELP%
> HKR, Ndi, FilterClass, , failover
> HKR, Ndi, FilterDeviceInfId, , ms_passthrump
> HKR, Ndi, Service, , IMROHC
> HKR, Ndi\Interfaces, UpperRange, , noupper
> HKR, Ndi\Interfaces, LowerRange, , nolower
> HKR, Ndi\Interfaces, FilterMediaTypes, , “ethernet”
>
> [IMROHC.AddReg]
> HKR, Parameters, Param1, 0, 4
>
> [Strings]
> Startup = “Startup”
> DiskDescription = “ROHC Installation Disk for Windows”
> IMROHC_Desc = “ROHC Driver for Windows”
> IMROHC_HELP = “ROHC Driver for Windows”
> IMROHCService_Desc = “ROHC Service”
>
> //
> / Miniport Inf
> /
>
> / /
>
> [Version]
> signature = “$Windows NT$”
> Class = Net
> ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
> Provider = %Startup%
> DriverVer = 10/19/2006,1.1.1.1
>
> [ControlFlags]
> ExcludeFromSelect = ms_passthrump
>
> [DestinationDirs]
> DefaultDestDir=12
> ; No files to copy
>
> [Manufacturer]
> %Startup% = STARTUP,NTx86
>
> ; For Win2K
> [Startup]
> %IMROHCMP_Desc% = IMROHCMP.ndi, ms_passthrump
>
> ; For XP and later
> [STARTUP.NTx86]
> %IMROHCMP_Desc% = IMROHCMP.ndi, ms_passthrump
>
> [IMROHCMP.ndi]
> Characteristics = 0x29 ;NCF_NOT_USER_REMOVABLE | NCF_VIRTUAL | NCF_HIDDEN
> CopyFiles =
>
> [IMROHCMP.ndi.Services]
> AddService = IMROHC,0x2, IMROHCMP.AddService
>
>
> [IMROHCMP.AddService]
> ServiceType = 1 ;SERVICE_KERNEL_DRIVER
> StartType = 3 ;SERVICE_DEMAND_START
> ErrorControl = 1 ;SERVICE_ERROR_NORMAL
> ServiceBinary = %12%\IMROHC.sys
>
>
> [IMROHCMP.AddService.AddReg]
>
> [Strings]
> Startup = “Startup”
> IMROHCMP_Desc = “IMROHC Miniport”
>
> [SourceDisksNames]
> ;None
>
> [SourceDisksFiles]
> ;None
>
> TIA,
>
> Giri.
> — Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the List
> Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

David_R_Cattley · October 19, 2006, 9:07am

Ok, from you reply I will assume that your driver is being loaded because
PnP has enumerated a devnode for *your* virtual miniport. Now the question
is whether or not NDIS can figure out that your protocol should be bound to
anything.

Did you change the name of the ‘protocol’ when registring the protocol
characteristics in DriverEntry so that it matches the name of the protocol
that is known to NDI and the binding engine?

> Finally I didnt understand what this is:

It is just a sample parameter definition in the INF file showing where/how
to define a driver specific parameter. It is not for anything in particular
other than to demonstrate where/how to set a parameter in the INF. I don’t
recall if the sample actually reads the value.

Good Luck,
Dave Cattley
Consulting Engineer
Systems Software Development

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of giri
Sent: Thursday, October 19, 2006 8:46 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Whats wrong with these modified Passthru inf files?

Hi David,

I dont do “net start IMROHC” but use the passthru installation procedure
of Adding Service and showing the path to the directory where inf files and
sys file are present
I succesfully installed passthru.sys and when I uninstalled it, i made
sure i deleted oemXX.inf for the two inf files
I have modified all the strings initially in both the inf files,
including ms_passthru and ms_passthruMP but I was facing the same problem.
So I did the text by text replacement in an iterative manner, each time
performing install and uninstall sucessfully. I started facing problem when
I replaced passthru.ndi etc with IMROHC.ndi corrsponding .AddReg section
names etc…
I have been observing c:\windows\setupapi.log to find how different it is
installing passthru.sys and imrohc.sys. I found only one difference in that
for passthru installation, the setup is able to find ms_passthrump in
oem18.inf but for IMROHC installation, its first updating INFCACHE1.dat and
then finding ms_passthru.mp in oemxx.inf.
My driver is getting loaded but not getting called at PtBindAdapter. Its
getting - PtPnpHandler for Adapter 0x00000000 for event 6, PtPnpHandler for
Adapter 0x00000000 for event 4, PtPnpHandler for Adapter 0x00000000 for
event 6 and Reconfigure for Adapter 0x0000000. And there after the LAN
connection stops functioning .
Finally after installing and uninstalling passthru.sys, I checked the
registry and couldnt find any occurances of ms_passthrump. Also I replaced
ms_passthru and ms_passthrump with new texts and the result is same.

Also I deleted OEMXX.inf’s corresponding to passthru and IMROHC
installations and then deleted INFCACHE.1 and observed that INFCACHE.1 is
rebuilt when i tried fresh install of IMROHC. But the same problem was
observed.

Finally I didnt understand what this is:

[Passthru.AddReg]
; The following key is Required
; The following key is Passthru specific
HKR, Parameters, Param1, 0, 4

Can we use that registry entry as it is? What is that entry for?

Thanks,
Giri.

OSR_Community_User · October 19, 2006, 1:06pm

>>Did you change the name of the ‘protocol’
Thanks! That was the problem.

>It is just a sample parameter definition in the INF file
The comment part “; The following key is Required” in there is misleading.

-Giri.

On 10/19/06, David R. Cattley wrote:
>
> Ok, from you reply I will assume that your driver is being loaded because
> PnP has enumerated a devnode for your virtual miniport. Now the question
> is whether or not NDIS can figure out that your protocol should be bound to
> anything.
>
> Did you change the name of the ‘protocol’ when registring the protocol
> characteristics in DriverEntry so that it matches the name of the protocol
> that is known to NDI and the binding engine?
>
>
> >> Finally I didnt understand what this is:
>
> It is just a sample parameter definition in the INF file showing where/how
> to define a driver specific parameter. It is not for anything in particular
> other than to demonstrate where/how to set a parameter in the INF. I don’t
> recall if the sample actually reads the value.
>
> Good Luck,
> Dave Cattley
> Consulting Engineer
> Systems Software Development
>
>
> ------------------------------
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *giri
> Sent: Thursday, October 19, 2006 8:46 AM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Whats wrong with these modified Passthru inf files?
>
>
> Hi David,
> 1) I dont do “net start IMROHC” but use the passthru installation
> procedure of Adding Service and showing the path to the directory where inf
> files and sys file are present
> 2) I succesfully installed passthru.sys and when I uninstalled it, i made
> sure i deleted oemXX.inf for the two inf files
> 3) I have modified all the strings initially in both the inf files,
> including ms_passthru and ms_passthruMP but I was facing the same problem.
> So I did the text by text replacement in an iterative manner, each time
> performing install and uninstall sucessfully. I started facing problem when
> I replaced passthru.ndi etc with IMROHC.ndi corrsponding .AddReg section
> names etc…
> 4) I have been observing c:\windows\setupapi.log to find how different it
> is installing passthru.sys and imrohc.sys. I found only one difference in
> that for passthru installation, the setup is able to find ms_passthrump in
> oem18.inf but for IMROHC installation, its first updating INFCACHE1.datand then finding ms_passthru.mp in
> oemxx.inf.
> 5) My driver is getting loaded but not getting called at PtBindAdapter.
> Its getting - PtPnpHandler for Adapter 0x00000000 for event 6, PtPnpHandler
> for Adapter 0x00000000 for event 4, PtPnpHandler for Adapter 0x00000000 for
> event 6 and Reconfigure for Adapter 0x0000000. And there after the LAN
> connection stops functioning .
> 6) Finally after installing and uninstalling passthru.sys, I checked the
> registry and couldnt find any occurances of ms_passthrump. Also I replaced
> ms_passthru and ms_passthrump with new texts and the result is same.
>
> Also I deleted OEMXX.inf’s corresponding to passthru and IMROHC
> installations and then deleted INFCACHE.1 and observed that INFCACHE.1 is
> rebuilt when i tried fresh install of IMROHC. But the same problem was
> observed.
>
> Finally I didnt understand what this is:
>
> [Passthru.AddReg]
> ; The following key is Required
> ; The following key is Passthru specific
> HKR, Parameters, Param1, 0, 4
>
> Can we use that registry entry as it is? What is that entry for?
>
> Thanks,
> Giri.
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>