Installation Problems

Bill_Olson · November 15, 2010, 10:09pm

I think I last talked about this on the Windbg list. I’ve been having a
lot of problems getting the tools to work. Things work on one machine,
but not on another. I was able to get windbg to connect to one machine
with only one OS installed, but not on a dual boot machine. The single
OS system would not show messages with DbgMon.

Despite the handicaps, I got the driver working on the single OS
computer, but now have problems on the dual boot computer.

Since switching back to the dual boot computer (on the XP side) I have
run into a number of strange things. DbgMon seems to work on this
machine, but the only messages I’ve seen are system messages. The
majority from Detectdr. I’ve also seen a watchdog timer message.

I have been unable to get the driver to work if you aren’t logged in as
Admin and I’ve been trying to tweak the INF to deal with that. I
installed the driver through the Add New Hardware wizard using the INF.
I then rebooted and switched to a non-Admin account, When I tried to
run, I got errors from my app. When I tried to read from hardware using
the driver, I got an ERROR_GEN_FAILURE which is for when a device
attached has failed. When I tried to write to the driver, I got
ERROR_ACCESS_DENIED.

I did some online research and found some information on setting up
security access permissions. There were already some in the INF
template I used, which was from the portio example in the DDK.

The original was:

[MyDeviceClassReg]
HKR,0,%ClassName%
HKR,Icon,-5
HKR,DeviceCharacteristics,0x10001,0x100 ;Use same security checks
on relative opens
HKR,Security,“D:P(A;;GA;;;SY)(A;;GA;;;BA)” ;Allow generic all access
to system and built-in Admin.

I added:

[MyDeviceClassReg.Security]
“D:P(A;;GR;;;WD)(A;;GA;;;SY)(A;;GA;;;BA)”

When I still couldn’t use the driver in non-Admin mode, I tried changing
it to:

“D:P(A;;GA;;;WD)(A;;GA;;;SY)(A;;GA;;;BA)”

Which I know is not recommended, but I was experimenting.

I was also getting problems installing the driver with the Security
section. It was coming up with file not found errors in the Add
Hardware Wizard. I commented out the security key settings and the
driver now installs OK.

The biggest problem is that now even the Administrator can’t use the
driver. When I try to read or write to it in Admin mode, I get Access
Denied errors. I think something got messed up in the security
settings, but I can’t figure out how to fix them. I know Windows hides
security settings in the registry so you can’t even find them in there.

Am I going to have to erase this installation of Windows and start over?

Bill

Pavel_A1 · November 16, 2010, 6:42am

Your share of beginners woes seems to be heavier than average…

Try the Sysinternals Debug View to see the messages.

Yes, it is a good idea to restore the machine to clean state.
By the same occasion, you can put each system on its own disk
and avoid dual boot situations altogether.
By the same occasion, make the OS partition small, so it takes less time and
space to back up.

Good luck,
– pa

“Bill Olson” wrote in message news:xxxxx@ntdev…
> I think I last talked about this on the Windbg list. I’ve been having a
> lot of problems getting the tools to work. Things work on one machine,
> but not on another. I was able to get windbg to connect to one machine
> with only one OS installed, but not on a dual boot machine. The single OS
> system would not show messages with DbgMon.
>
> Despite the handicaps, I got the driver working on the single OS computer,
> but now have problems on the dual boot computer.
>
> Since switching back to the dual boot computer (on the XP side) I have run
> into a number of strange things. DbgMon seems to work on this machine,
> but the only messages I’ve seen are system messages. The majority from
> Detectdr. I’ve also seen a watchdog timer message.
>
> I have been unable to get the driver to work if you aren’t logged in as
> Admin and I’ve been trying to tweak the INF to deal with that. I
> installed the driver through the Add New Hardware wizard using the INF. I
> then rebooted and switched to a non-Admin account, When I tried to run, I
> got errors from my app. When I tried to read from hardware using the
> driver, I got an ERROR_GEN_FAILURE which is for when a device attached has
> failed. When I tried to write to the driver, I got ERROR_ACCESS_DENIED.
>
> I did some online research and found some information on setting up
> security access permissions. There were already some in the INF template
> I used, which was from the portio example in the DDK.
>
> The original was:
>
>
> [MyDeviceClassReg]
> HKR,0,%ClassName%
> HKR,Icon,-5
> HKR,DeviceCharacteristics,0x10001,0x100 ;Use same security checks on
> relative opens
> HKR,Security,“D:P(A;;GA;;;SY)(A;;GA;;;BA)” ;Allow generic all access to
> system and built-in Admin.
>
> I added:
>
> [MyDeviceClassReg.Security]
> “D:P(A;;GR;;;WD)(A;;GA;;;SY)(A;;GA;;;BA)”
>
> When I still couldn’t use the driver in non-Admin mode, I tried changing
> it to:
>
> “D:P(A;;GA;;;WD)(A;;GA;;;SY)(A;;GA;;;BA)”
>
> Which I know is not recommended, but I was experimenting.
>
> I was also getting problems installing the driver with the Security
> section. It was coming up with file not found errors in the Add Hardware
> Wizard. I commented out the security key settings and the driver now
> installs OK.
>
> The biggest problem is that now even the Administrator can’t use the
> driver. When I try to read or write to it in Admin mode, I get Access
> Denied errors. I think something got messed up in the security settings,
> but I can’t figure out how to fix them. I know Windows hides security
> settings in the registry so you can’t even find them in there.
>
> Am I going to have to erase this installation of Windows and start over?
>
> Bill
>

Bill_Olson · November 16, 2010, 7:07pm

On 11/16/10 3:34 AM, Pavel A. wrote:

Your share of beginners woes seems to be heavier than average…

I have had my frustrations. Ironically the drivers work fine when I can
get them to work. It’s getting them installed right that’s the biggest
headache.

Try the Sysinternals Debug View to see the messages.

I’ll try it.

Yes, it is a good idea to restore the machine to clean state.
By the same occasion, you can put each system on its own disk
and avoid dual boot situations altogether.
By the same occasion, make the OS partition small, so it takes less time
and space to back up.

I do have to deliver the machine dual boot, but I can do that as my last
step. My customer is going to use this machine as his demo machine and
he wants to have both OSs installed.

I think the registry corruption is getting worse. I’m now not able to
install the driver at all on XP. It’s also taking 7-8 minutes in the
Add Hardware Wizard to come up with the entire list of drivers. Looking
at the install log, it’s bombing out registering the service with a file
not found error. This is after successfully copying the driver to
System32\drivers. The name of the driver in the registration step is
correct, so I don’t know what file it can’t find.

The 7-8 minute lag is new in the last 24 hours. It was taking about 30
seconds to come up with the list before. The install log looks like it
is generating the list multiple times for some reason.

Anyway, next step is to blow away the XP partition and start over.
Hopefully that will solve some of these problems…

Bill

Good luck,
– pa

“Bill Olson” wrote in message news:xxxxx@ntdev…
>> I think I last talked about this on the Windbg list. I’ve been having
>> a lot of problems getting the tools to work. Things work on one
>> machine, but not on another. I was able to get windbg to connect to
>> one machine with only one OS installed, but not on a dual boot
>> machine. The single OS system would not show messages with DbgMon.
>>
>> Despite the handicaps, I got the driver working on the single OS
>> computer, but now have problems on the dual boot computer.
>>
>> Since switching back to the dual boot computer (on the XP side) I have
>> run into a number of strange things. DbgMon seems to work on this
>> machine, but the only messages I’ve seen are system messages. The
>> majority from Detectdr. I’ve also seen a watchdog timer message.
>>
>> I have been unable to get the driver to work if you aren’t logged in
>> as Admin and I’ve been trying to tweak the INF to deal with that. I
>> installed the driver through the Add New Hardware wizard using the
>> INF. I then rebooted and switched to a non-Admin account, When I tried
>> to run, I got errors from my app. When I tried to read from hardware
>> using the driver, I got an ERROR_GEN_FAILURE which is for when a
>> device attached has failed. When I tried to write to the driver, I got
>> ERROR_ACCESS_DENIED.
>>
>> I did some online research and found some information on setting up
>> security access permissions. There were already some in the INF
>> template I used, which was from the portio example in the DDK.
>>
>> The original was:
>>
>>
>> [MyDeviceClassReg]
>> HKR,0,%ClassName%
>> HKR,Icon,-5
>> HKR,DeviceCharacteristics,0x10001,0x100 ;Use same security checks on
>> relative opens
>> HKR,Security,“D:P(A;;GA;;;SY)(A;;GA;;;BA)” ;Allow generic all access
>> to system and built-in Admin.
>>
>> I added:
>>
>> [MyDeviceClassReg.Security]
>> “D:P(A;;GR;;;WD)(A;;GA;;;SY)(A;;GA;;;BA)”
>>
>> When I still couldn’t use the driver in non-Admin mode, I tried
>> changing it to:
>>
>> “D:P(A;;GA;;;WD)(A;;GA;;;SY)(A;;GA;;;BA)”
>>
>> Which I know is not recommended, but I was experimenting.
>>
>> I was also getting problems installing the driver with the Security
>> section. It was coming up with file not found errors in the Add
>> Hardware Wizard. I commented out the security key settings and the
>> driver now installs OK.
>>
>> The biggest problem is that now even the Administrator can’t use the
>> driver. When I try to read or write to it in Admin mode, I get Access
>> Denied errors. I think something got messed up in the security
>> settings, but I can’t figure out how to fix them. I know Windows hides
>> security settings in the registry so you can’t even find them in there.
>>
>> Am I going to have to erase this installation of Windows and start over?
>>
>> Bill
>>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

OSR_Community_User · November 16, 2010, 7:26pm

>>
I think the registry corruption is getting worse. I’m now not able to install the driver at all on XP. It’s also taking 7-8 minutes in the Add Hardware Wizard to come up with the entire list of drivers. Looking at the install log, it’s bombing out registering the service with a file not found error. This is after successfully copying the driver to System32\drivers. The name of the driver in the registration step is correct, so I don’t know what file it can’t find.

The 7-8 minute lag is new in the last 24 hours. It was taking about 30 seconds to come up with the list before. The install log looks like it is generating the list multiple times for some reason.
<<

My take on what you’re reporting (and without harder evidence, it is not ironclad- just based on a lot of woeful experience):

It isn’t the registry, and it isn’t corrupted- you’re making assumptions that probably don’t fit the circumstances (not that this doesn’t happen a lot with device installation, and yes, I’m sort of doing that now, as well, but…). It sounds to me like your installation attempts are now successful enough to copy the INF to %windir%\inf, and you’ve done that enough times that reading the same file (basically) over and over dozens and dozens of time to eventually get the same basic info [duplicates get suppressed here, IIRC] is beginning to take a lot of time.

It also could mean that any of those earlier INFs may be as good (or worse yet, better for some reason) a match as the INF you think you’re working with, so you’re just repeating the same old mistake (from some previous attempt) over and over and over.

Do a text search on your hardware ID in that directory, and delete all the oem*.?nf files that contain it. Then see how fast your installs are- and if your latest INF is as good as you think it is.

This is one of the reasons a clean OS is suggested so often (and the above is not a panacea- I opt for the clean install case very time- it may take longer to do the install, but I spend a lot less time chasing my tail over things like this).

Bill_Olson · November 16, 2010, 11:33pm

Good stuff to know. I’m learning a lot more about the installation
process with each problem. My first attempts at an INF did have some
mistakes in them and if those INFs are still there and being rehashed,
that could cause some problems.

I’ve done a clean install and I’m making an image of the system disk
right now. I also took Pavel’s advice and made it as small as was
feasible to save time making copies.

I’m probably making a number of newbie mistakes because while I have
done drivers for DOS and embedded OSs, this is my first experience in
the Windows kernel world. I tried to get into an OSR class, but they
canceled the last one here in Portland, and the other ones on the West
Coast have been bad timing for me.

Bill

On 11/16/10 4:25 PM, Bob Kjelgaard wrote:

>>
I think the registry corruption is getting worse. I’m now not able
to install the driver at all on XP. It’s also taking 7-8 minutes in
the Add Hardware Wizard to come up with the entire list of drivers.
Looking at the install log, it’s bombing out registering the service
with a file not found error. This is after successfully copying the
driver to System32\drivers. The name of the driver in the
registration step is correct, so I don’t know what file it can’t
find.

The 7-8 minute lag is new in the last 24 hours. It was taking about
30 seconds to come up with the list before. The install log looks
like it is generating the list multiple times for some reason. <<

My take on what you’re reporting (and without harder evidence, it is
not ironclad- just based on a lot of woeful experience):

It isn’t the registry, and it isn’t corrupted- you’re making
assumptions that probably don’t fit the circumstances (not that this
doesn’t happen a lot with device installation, and yes, I’m sort of
doing that now, as well, but…). It sounds to me like your
installation attempts are now successful enough to copy the INF to
%windir%\inf, and you’ve done that enough times that reading the same
file (basically) over and over dozens and dozens of time to
eventually get the same basic info [duplicates get suppressed here,
IIRC] is beginning to take a lot of time.

It also could mean that any of those earlier INFs may be as good (or
worse yet, better for some reason) a match as the INF you think
you’re working with, so you’re just repeating the same old mistake
(from some previous attempt) over and over and over.

Do a text search on your hardware ID in that directory, and delete
all the oem*.?nf files that contain it. Then see how fast your
installs are- and if your latest INF is as good as you think it is.

This is one of the reasons a clean OS is suggested so often (and the
above is not a panacea- I opt for the clean install case very time-
it may take longer to do the install, but I spend a lot less time
chasing my tail over things like this).

— NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Bill_Olson · November 17, 2010, 2:54am

OK, I reinstalled XP and am working with the driver on a fresh install
of Windows. The long delay searching for all hardware options still
happens.

When I try to use the driver, I get the following errors:
On write to driver = error 31 GEN_FAILURE
On read from driver = error 5 ACCESS_DENIED

When I look at the driver in Device Manager, it says the driver is
installed OK, but for the resources, it says:

The device isn’t using any resources because it has a problem.

It is supposed to reserve I/O addresses 0x300-0x302

I put a section in the INF to set these addresses

[MTIsaDrv_Inst.NT]
CopyFiles=MTIsaDrv.CopyFiles
LogConfig=MTIsaDrv.NT.FactDef

[MTIsaDrv.CopyFiles]
MTIsaDrv.sys

[MTIsaDrv_Inst.NT.Services]
AddService=MTIsaDrv,0x00000002,MTIsaDrv_Service

[MTIsaDrv.NT.FactDef]
ConfigPriority=HARDRECONFIG
IOConfig=300-302(3ff: ; 10 bit decode ranging from 300 - 302

It doesn’t appear to be working though. When I try to set the resources
manually, the computer wants to reboot afterward and it still has the
same message with no resources set when I go back into Device Manager.

I suspect the error 31 might be due to resource allocation, but I still
have the error 5 to deal with. At this point I’m logged in as
administrator and the permissions are set here:

[IODeviceClassReg]
HKR,0,%ClassName%
HKR,Icon,-5
HKR,DeviceCharacteristics,0x10001,0x100 ;Use same security checks
on relative opens
HKR,Security,“D:P(A;;GA;;;SY)(A;;GA;;;BA)” ;Allow generic all access
to system and built-in Admin.

This should allow administrator access.

I also found the Instance ID ends up set to ROOT\UNKNOWN\0000. This is
a legacy device, so there is no PnP information available. How do I set
this in the driver or the setup to something else?

Bill

On 11/16/10 8:31 PM, Bill Olson wrote:

Good stuff to know. I’m learning a lot more about the installation
process with each problem. My first attempts at an INF did have some
mistakes in them and if those INFs are still there and being rehashed,
that could cause some problems.

I’ve done a clean install and I’m making an image of the system disk
right now. I also took Pavel’s advice and made it as small as was
feasible to save time making copies.

I’m probably making a number of newbie mistakes because while I have
done drivers for DOS and embedded OSs, this is my first experience in
the Windows kernel world. I tried to get into an OSR class, but they
canceled the last one here in Portland, and the other ones on the West
Coast have been bad timing for me.

Bill

On 11/16/10 4:25 PM, Bob Kjelgaard wrote:
>>>
> I think the registry corruption is getting worse. I’m now not able
> to install the driver at all on XP. It’s also taking 7-8 minutes in
> the Add Hardware Wizard to come up with the entire list of drivers.
> Looking at the install log, it’s bombing out registering the service
> with a file not found error. This is after successfully copying the
> driver to System32\drivers. The name of the driver in the
> registration step is correct, so I don’t know what file it can’t
> find.
>
> The 7-8 minute lag is new in the last 24 hours. It was taking about
> 30 seconds to come up with the list before. The install log looks
> like it is generating the list multiple times for some reason. <<
>
> My take on what you’re reporting (and without harder evidence, it is
> not ironclad- just based on a lot of woeful experience):
>
> It isn’t the registry, and it isn’t corrupted- you’re making
> assumptions that probably don’t fit the circumstances (not that this
> doesn’t happen a lot with device installation, and yes, I’m sort of
> doing that now, as well, but…). It sounds to me like your
> installation attempts are now successful enough to copy the INF to
> %windir%\inf, and you’ve done that enough times that reading the same
> file (basically) over and over dozens and dozens of time to
> eventually get the same basic info [duplicates get suppressed here,
> IIRC] is beginning to take a lot of time.
>
> It also could mean that any of those earlier INFs may be as good (or
> worse yet, better for some reason) a match as the INF you think
> you’re working with, so you’re just repeating the same old mistake
> (from some previous attempt) over and over and over.
>
> Do a text search on your hardware ID in that directory, and delete
> all the oem*.?nf files that contain it. Then see how fast your
> installs are- and if your latest INF is as good as you think it is.
>
> This is one of the reasons a clean OS is suggested so often (and the
> above is not a panacea- I opt for the clean install case very time-
> it may take longer to do the install, but I spend a lot less time
> chasing my tail over things like this).
>
>
> — NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

OSR_Community_User · November 17, 2010, 3:18am

On 11/17/2010 1:25 AM, Bob Kjelgaard wrote:

This is one of the reasons a clean OS is suggested so often […] it
may take longer to do the install, but I spend a lot less time
chasing my tail over things like this).

If you can use it with your driver, Virtual Machine images are great to
cut down on the “takes longer” penalty for a fresh install.

Copy the VM disk image of a clean installation, then install your driver
in the copy. If anything goes bad, you can simply throw it away.

This helped me a lot chasing down my own INF problems. It also helps for
cross-OS-version installation testing.

(Of course you can’t use this for any performance testing.)

OSR_Community_User · November 17, 2010, 3:23am

On 11/17/2010 8:52 AM, Bill Olson wrote:

OK, I reinstalled XP and am working with the driver on a fresh install
of Windows. The long delay searching for all hardware options still
happens.

Do the setupapi logs state anything about the installation?

Bill_Olson · November 17, 2010, 4:07am

The first install on the newly installed OS I had copied some stuff to dynamically find the I/O addresses, but that didn’t work, so I uninstalled and reinstalled with the INF code posted earlier. The first install was with:

[MTIsaDrv_Inst.NT]
CopyFiles=MTIsaDrv.CopyFiles
LogConfig=MTIsaDrv.LC0, MTIsaDrv.LC1

[MTIsaDrv.LC0]
ConfigPriority=DESIRED
IOConfig=300-302(3ff: ; 10 bit decode ranging from 300 - 302

[MTIsaDrv.LC1]
ConfigPriority=NORMAL
IOConfig=3@300-3ff(3ff: ; 3 ports starting anywhere between 300 and 3fc

The second install set the Device Instance Id to ROOT\IODEVICE\0000, so it is some minor progress, but doesn’t solve the bigger problem of the I/O addresses and the error messages.

setupapi.log squawks about the signature, but that’s to be expected. I created my own cat file with inf2cat. There was an error during uninstall:
cfgMgr32 returned: 0x17: CR_REMOVE_VETOED, though the device was removed.

Here is the section of the setupapi.log with the two installs and uninstall:

[2010/11/16 21:00:48 1704.500 Driver Install]
#-124 Doing copy-only install of “ROOT\UNKNOWN\0000”.
#-198 Command line processed: “F:\WINDOWS\system32\rundll32.exe” F:\WINDOWS\system32\shell32.dll,Control_RunDLL “F:\WINDOWS\system32\hdwwiz.cpl”,Add Hardware
#E360 An unsigned or incorrectly signed file “f:\program files\rti\multitracenew\driver\mtisadrv.cat” for driver “MTIsaDrv Driver” will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject.
#W187 Install failed, attempting to restore original files.
#E360 An unsigned or incorrectly signed file “f:\program files\rti\multitracenew\driver\mtisadrv.cat” for driver “MTIsaDrv Driver” will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject.
#-024 Copying file “f:\program files\rti\multitracenew\driver\MTIsaDrv.sys” to “F:\WINDOWS\system32\DRIVERS\MTIsaDrv.sys”.
#E360 An unsigned or incorrectly signed file “f:\program files\rti\multitracenew\driver\MTIsaDrv.sys” for driver “MTIsaDrv Driver” will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [MTIsaDrv_Inst.NT.Interfaces] from “f:\program files\rti\multitracenew\driver\mtisadrv.inf”.
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of “ROOT\UNKNOWN\0000”.
#E360 An unsigned or incorrectly signed file “f:\program files\rti\multitracenew\driver\MTIsaDrv.cat” for driver “MTIsaDrv Driver” will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject.
#I121 Device install of “ROOT\UNKNOWN\0000” finished successfully.
[2010/11/16 21:14:22 1984.196]
#-198 Command line processed: “F:\WINDOWS\system32\mmc.exe” F:\WINDOWS\system32\devmgmt.msc /s
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of “ROOT\UNKNOWN\0000”.
#W003 Query-removal during property change of ROOT\UNKNOWN\0000 was vetoed by ROOT\UNKNOWN\0000 (veto type 1: PNP_VetoLegacyDevice)
#W110 Device “ROOT\UNKNOWN\0000” required reboot: Query remove vetoed (property change).
#I304 DICS_PROPCHANGE: Device could not be restarted.
[2010/11/16 21:30:12 1672.1115]
#-198 Command line processed: “F:\WINDOWS\system32\mmc.exe” F:\WINDOWS\system32\devmgmt.msc /s
#-166 Device install function: DIF_REMOVE.
#I289 Removing device “ROOT\UNKNOWN\0000”.
#W001 Query-removal during uninstall of ROOT\UNKNOWN\0000 was vetoed by Root\UNKNOWN\0000 (veto type 1: PNP_VetoLegacyDevice)
#W105 Device “ROOT\UNKNOWN\0000” required reboot: Query remove failed (uninstall) CfgMgr32 returned: 0x17: CR_REMOVE_VETOED.
#I048 Device removed.
[2010/11/16 23:13:03 324.495 Driver Install]
#-124 Doing copy-only install of “ROOT\IODEVICE\0000”.
#-198 Command line processed: “F:\WINDOWS\system32\rundll32.exe” F:\WINDOWS\system32\shell32.dll,Control_RunDLL “F:\WINDOWS\system32\hdwwiz.cpl”,Add Hardware
#E360 An unsigned or incorrectly signed file “f:\program files\rti\multitracenew\driver\mtisadrv.cat” for driver “MTIsaDrv Driver” will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject.
#W187 Install failed, attempting to restore original files.
#E360 An unsigned or incorrectly signed file “f:\program files\rti\multitracenew\driver\mtisadrv.cat” for driver “MTIsaDrv Driver” will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject.
#-024 Copying file “f:\program files\rti\multitracenew\driver\MTIsaDrv.sys” to “F:\WINDOWS\system32\DRIVERS\MTIsaDrv.sys”.
#E360 An unsigned or incorrectly signed file “f:\program files\rti\multitracenew\driver\MTIsaDrv.sys” for driver “MTIsaDrv Driver” will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [MTIsaDrv_Inst.NT.Interfaces] from “f:\program files\rti\multitracenew\driver\mtisadrv.inf”.
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of “ROOT\IODEVICE\0000”.
#E360 An unsigned or incorrectly signed file “f:\program files\rti\multitracenew\driver\MTIsaDrv.cat” for driver “MTIsaDrv Driver” will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject.
#I121 Device install of “ROOT\IODEVICE\0000” finished successfully.

Bill_Olson · November 17, 2010, 4:27am

I just discovered that DbgMon will work now after the reinstall. I captured messages from the driver and found that the error 5 and error 31 were due to a typo in my CTL_CODE definitions for this driver.

It works in admin mode. Now to see if I can get it to work in non-admin mode.

Thanks for the help thus far…

Bill