Hi there! I’m having issues with the install of a driver, so I’m doing it manually. Now, I’ve been reading the inf file that came with it, and I’m fairly sure that I did everything I needed to do in order to make it work, but after a restart it still doesn’t work. Would it be safe for me to post up the inf file and get some help translating the directions in it?
What kind of driver? Have you run CHKINF? What do you mean by manually?
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Sunday, May 16, 2010 2:22 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Installing a driver, need some help with inf
Hi there! I’m having issues with the install of a driver, so I’m doing it
manually. Now, I’ve been reading the inf file that came with it, and I’m
fairly sure that I did everything I needed to do in order to make it work,
but after a restart it still doesn’t work. Would it be safe for me to post
up the inf file and get some help translating the directions in it?
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
__________ Information from ESET Smart Security, version of virus signature
database 5118 (20100516) __________
The message was checked by ESET Smart Security.
__________ Information from ESET Smart Security, version of virus signature
database 5118 (20100516) __________
The message was checked by ESET Smart Security.
In additional to run chkinf as Gary suggest you could check setupapi.* files. These files may tell you what is wrong in installation.
Igor Sharovar
Thank you both for your responses. Here’s the answers to your questions, and thanks for taking the time to respond again:
The driver is to enable the use of 5 hardware buttons on the face of my convertible tablet PC.
I just installed PERL in order to run CHkINF, but I can’t seem to figure out where I actually download the tool.
When I say manually, I mean that I attempted to install the driver the way it was supposed to be installed (with the appropriate installer file downloaded from the manufacturer website etc etc), and I’m installing the driver on a windows 7 machine under compatibility mode to windows xp (the driver was made in that era, and was never updated to newer OS’s). After attempted install, there was no noticeable effect of the install. As in, the buttons still had no function except for one, which if held down did the function of “Ctrl + Alt + Del” (It did this before the install too). I decided to go in and try to perform the installation manually by following the commands in the inf file (adding registry keys, putting the .sys file where it needs to go, etc. etc.), and after what I thought was all of the functions that needed to execute, I restarted the computer. Now, not even the ctrlaltdel button works. Hence why I was hoping I could show the inf file and double check that I’m doing everything that it would do automatically.
Where would I fine the setupapi files?
For Windows 7:
C:\Windows\inf\setupapi.app.log
C:\Windows\inf\setupapi.dev.log
And chkinf here:
C:\winddk\7600.16385.1\tools\Chkinf.
Take a look at the NonPnP install at
C:\winddk\7600.16385.1\src\general\ioctl.
But, is this a 32 bit driver you are installing on a 64 bit Win7? If so,
forget about it, it will not work.
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Sunday, May 16, 2010 6:41 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Installing a driver, need some help with inf
Thank you both for your responses. Here’s the answers to your questions,
and thanks for taking the time to respond again:
The driver is to enable the use of 5 hardware buttons on the face of my
convertible tablet PC.
I just installed PERL in order to run CHkINF, but I can’t seem to figure out
where I actually download the tool.
When I say manually, I mean that I attempted to install the driver the way
it was supposed to be installed (with the appropriate installer file
downloaded from the manufacturer website etc etc), and I’m installing the
driver on a windows 7 machine under compatibility mode to windows xp (the
driver was made in that era, and was never updated to newer OS’s). After
attempted install, there was no noticeable effect of the install. As in,
the buttons still had no function except for one, which if held down did the
function of “Ctrl + Alt + Del” (It did this before the install too). I
decided to go in and try to perform the installation manually by following
the commands in the inf file (adding registry keys, putting the .sys file
where it needs to go, etc. etc.), and after what I thought was all of the
functions that needed to execute, I restarted the computer. Now, not even
the ctrlaltdel button works. Hence why I was hoping I could show the inf
file and double check that I’m doing everything that it would do
automatically.
Where would I fine the setupapi files?
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
__________ Information from ESET Smart Security, version of virus signature
database 5119 (20100516) __________
The message was checked by ESET Smart Security.
__________ Information from ESET Smart Security, version of virus signature
database 5119 (20100516) __________
The message was checked by ESET Smart Security.
Thank you for the location, I didn’t realize I would need the WDK in order to use the mentioned tools (I’m just a user, not quite a programmer unfortunately).
0 errors and 0 warnings for chkinf
Directly after running the driver installer for the n-th time, I took a look at the two setupapi files, and they had nothing listed after 9:30pm tonight (it’s 10:15 pm on the system clock right now). Will I need to restart for changes to become evident?
I’m not quite sure what to make of the non pnp driver installation information…I’m sorry for my lack of knowledge in the driver creation field. Like I said earlier, I’m sadly just a user who learns quickly, and is just trying to get these stupid 5 buttons to work.
No, this is definitely Win 7 32-bit, I made sure of that. That and the fact that Pentium M processors probably won’t run 64-bit environments.
Thank you greatly for the help so far, looking forward to more!
PS, would this be an appropriate time to post the inf file in question? It’s not particularly large, I just need some feedback on if I’m interpreting it correctly or not
No, you shouldn’t have to restart to see changes in the log(s).
Yes, please post the INF and the most recent contents of setupapi.log.
Also, where can be this driver be found?
mm
The driver can be found by going to http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=config and putting in AE21J1A903C51001 for the configuration number. The driver in question is the button driver.
Alright then. Here’s an incoming wall of text…this is the inf file:
; fjbtndrv.inf
; Copyright (c) 2003 Fujitsu PC Corporation
[version]
signature=“$WINDOWS NT$”
Provider=%FPC%
ClassGuid={745a17a0-74d3-11d0-b6fe-00a0c90f57da}
Class=HIDClass
DriverVer=06/20/2003,1.000.0620.2003
CatalogFile=fjbtndrv.cat
[ControlFlags]
ExcludeFromSelect=*
[DestinationDirs]
DefaultDestDir =11 ;LDID_SYS
fjbtndrvInst.NTx86.Copy =12 ;LDID_DRIVERS
; Drivers
;----------------------------------------------------------
[Manufacturer]
%FPC%=FPC
[FPC]
%ACPI\FJTabletPCButtons% =fjbtndrvInst,ACPI\FUJ02BF
[fjbtndrvInst.NTx86.HW]
AddReg =fjbtndrvInst.NTx86.AddReg
[fjbtndrvInst.NTx86.AddReg]
HKR,SASButtonID,0x00010001,0x00008000
HKR,CADDelay,0x00010001,0x000002EE
HKR,EnableBtn,0x00010001,0x00000001
HKR,DisableAllBtns,0x00010001,0x00000000
HKLM,System\CurrentControlSet\Services\Fjbtndrv\Parameters,RotationState,0x00010001,0
HKLM,System\CurrentControlSet\Services\Fjbtndrv\Parameters,DockState,0x00010001,0
[fjbtndrvInst.NTx86]
CopyFiles =fjbtndrvInst.NTx86.Copy
[fjbtndrvInst.NTx86.Copy]
FjBtndrv.sys
[fjbtndrvInst.NTx86.Services]
AddService =fjbtndrv,0x00000002,fjbtndrvServiceInst,fjbtndrvEventLogInst
[fjbtndrvEventLogInst]
AddReg =fjbtndrvEventLogAddReg
[fjbtndrvEventLogAddReg]
HKR,EventMessageFile,0x00020000,“%%SystemRoot%%\System32\IoLogMsg.dll;%%SystemRoot%%\System32\drivers\Fjbtndrv.sys”
HKR,TypesSupported,0x00010001,7
; -------------- Tablet PC Buttons Driver install section
[fjbtndrvServiceInst]
DisplayName = %FJbtndrv.SVCDESC%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ;
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %12%\Fjbtndrv.sys
LoadOrderGroup = Extended Base
[SourceDisksNames]
1 = %DiskID%,
[SourceDisksFiles]
fjbtndrv.sys = 1,
; User readable strings
;----------------------------------------------------------
[Strings]
FPC= “Fujitsu PC Corporation”
ACPI\FJTabletPCButtons=“Fujitsu Lifebook T3000 Tablet PC Buttons”
FJbtndrv.SVCDESC=“Fujitsu LIFEBOOK T3000 Button Driver”
DiskID=“Fujitsu LIFEBOOK T3000 Button Driver for Windows XP Tablet PC Setup Disk”
I wish I had the energy right now to go back into my registry and double check that all of the keys created here are located there, but I simply do not. Once I have the time, and if I can be told locations and directions, I will gladly double check the appropriate registry locations. I’m fairly sure though that I was thorough in following the directions listed. My only concern is about the connection to the ACPI (I really don’t know where in the registry I should be making those respective changes.) and the creation of services, seeing as I don’t see the listings in services.msc
I’m rerunning the installer for the driver right now. Current system time is 12:25am, 5/17/2010.
setupapi.app.log:
[Device Install Log]
OS Version = 6.1.7600
Service Pack = 0.0
Suite = 0x0300
ProductType = 1
Architecture = x86
((skipping to the end, last four entires))
>> [DIF_PROPERTYCHANGE - ROOT\SUN_VBOXNETFLTMP\0001]
>> Section start 2010/05/16 23:04:08.301
cmd: C:\Windows\system32\svchost.exe -k netsvcs
<<< Section end 2010/05/16 23:04:08.301
<<< [Exit status: SUCCESS]
>> [DIF_PROPERTYCHANGE - ROOT\SUN_VBOXNETFLTMP\0000]
>> Section start 2010/05/16 23:04:08.301
cmd: C:\Windows\system32\svchost.exe -k netsvcs
<<< Section end 2010/05/16 23:04:08.317
<<< [Exit status: SUCCESS]
>> [DIF_DESTROYPRIVATEDATA]
>> Section start 2010/05/16 23:04:08.317
cmd: C:\Windows\system32\svchost.exe -k netsvcs
<<< Section end 2010/05/16 23:04:08.317
<<< [Exit status: SUCCESS]
>> [DIF_DESTROYPRIVATEDATA]
>> Section start 2010/05/16 23:04:08.317
cmd: C:\Windows\system32\svchost.exe -k netsvcs
<<< Section end 2010/05/16 23:04:08.317
<<< [Exit status: SUCCESS]
Here’s another wall of text, the setupapi.dev.log. Intro, and then a section from the end
[Device Install Log]
OS Version = 6.1.7600
Service Pack = 0.0
Suite = 0x0300
ProductType = 1
Architecture = x86
[BeginLog]
((…))
dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 21:31:08.669
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 21:31:08.670
dvi: No class installer for ‘DsfRoot for DSF’
dvi: CoInstaller 1: Enter 21:31:08.671
dvi: CoInstaller 1: Exit
dvi: Default installer: Enter 21:31:08.672
dvi: Default installer: Exit
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 21:31:08.673
ndv: Device install status=0x00000000
ndv: Performing device install final cleanup…
ndv: {Core Device Install - exit(0x00000000)} 21:31:08.676
dvi: {DIF_DESTROYPRIVATEDATA} 21:31:08.676
dvi: CoInstaller 1: Enter 21:31:08.676
dvi: CoInstaller 1: Exit
dvi: Default installer: Enter 21:31:08.677
dvi: Default installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 21:31:08.678
ump: Server install process exited with code 0x00000000 21:31:08.704
ump: {Plug and Play Service: Device Install exit(00000000)}
dvi: {DIF_DESTROYPRIVATEDATA} 21:31:08.710
dvi: CoInstaller 1: Enter 21:31:08.711
dvi: CoInstaller 1: Exit
dvi: Default installer: Enter 21:31:08.711
dvi: Default installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 21:31:08.712
dvi: {Build Driver List} 21:31:08.712
! dvi: Driver list already built
dvi: {Build Driver List - exit(0x00000000)} 21:31:08.713
dvi: {DIF_SELECTBESTCOMPATDRV} 21:31:08.713
dvi: No class installer for ‘DsfRoot for DSF’
dvi: Using exported function ‘CriticalDeviceCoInstaller’ in module ‘C:\Windows\system32\SysClass.Dll’.
dvi: CoInstaller 1 == SysClass.Dll,CriticalDeviceCoInstaller
dvi: CoInstaller 1: Enter 21:31:08.723
dvi: CoInstaller 1: Exit
dvi: Default installer: Enter 21:31:08.724
dvi: {Select Best Driver}
dvi: Selected driver installs from section [DsfRoot_Device] in ‘c:\program files\dsf\dsfroot.inf’.
dvi: Class GUID of device remains: {4d36e97d-e325-11ce-bfc1-08002be10318}.
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [DsfRoot for DSF]
dvi: InfFile - [c:\program files\dsf\dsfroot.inf]
dvi: Section - [DsfRoot_Device]
dvi: Signer - [Microsoft Windows]
dvi: Rank - [0x00ff0000]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 21:31:08.729
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 21:31:08.730
dvi: No class installer for ‘DsfRoot for DSF’
dvi: CoInstaller 1: Enter 21:31:08.731
dvi: CoInstaller 1: Exit
dvi: Default installer: Enter 21:31:08.732
dvi: Default installer: Exit
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 21:31:08.733
dvi: {DIF_DESTROYPRIVATEDATA} 21:31:08.734
dvi: CoInstaller 1: Enter 21:31:08.735
dvi: CoInstaller 1: Exit
dvi: Default installer: Enter 21:31:08.736
dvi: Default installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 21:31:08.736
<<< Section end 2010/05/16 21:31:08.737
<<< [Exit status: SUCCESS]
Would you like me to post more of either file?
Thanks again for the help!
http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=config and putting in
AE21J1A903C51001 for the configuration number.
You lost me here…
mm
>the driver on a windows 7 machine under compatibility mode to windows xp (the driver was made in
that era, and was never updated to newer OS’s).
This does not work. There is no compatibility mode for drivers.
And, if you have WinXP driver not updated for Win7, then sorry, it is normal that it does not work.
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
@MM Sorry, I pasted in the wrong thing. The link was: http://support.fujitsupc.com/CS/Portal/support.do?msrch=config
@Maxim S. Shatskih: Normally I would believe that nothing could be done, but that’s only because what someone wrote for some ancient technology was never updated. The fact that one of the buttons called Ctrl+Alt+Del at one point, and when my screen dimmed I could press any of the buttons to wake the computer back up, seem to point to the fact that the OS knows how to interact with those buttons. More over, after creating some registry keys (in vain attempt at recreating the steps taken by the installer) all of the buttons ceased reacting, which means that I did accomplish SOMEthing via the registry alone. So I’m sorry if this comes off as offensive, but I know it doesn’t work, but I’m going to make it work. I’m quite persistent when it comes to these things, and I’ve already taken this computer a far away from where it started (effectively in a trash can).
xxxxx@gmail.com wrote:
The driver can be found by going to http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=config and putting in AE21J1A903C51001 for the configuration number. The driver in question is the button driver.
…[FPC]
%ACPI\FJTabletPCButtons% =fjbtndrvInst,ACPI\FUJ02BF
You’re sure that’s the correct hardware ID? Are you pre-installing the
driver package in some way?
Here’s another wall of text, the setupapi.dev.log. Intro, and then a section from the end
But the section you quoted is for a an INF from the DSF (device
simulation framework). It’s not your INF. You need to look through
this file to find the section that corresponds to your device. (For
example, look for your INF name.) If it’s not present, then that
suggests your hardware ID is not actually being exposed.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
No, I’m not preinstalling the drivers. This is my personal tablet pc, I’m just trying to get it working. Nothing particularly fancy.
Thank you Tim, I wasn’t sure what I was looking for in either log file.
From setupapi.app.log, there was no entry in it that contained the “fjbtndrv” keyword anywhere in it.
From setupapi.dev.log, I found this (and this was the only entry). It seems that this corresponds with the date that I installed windows 7 on the machine (I’m 90% sure of that. I can’t quite remember when that was, but I’m fairly sure this was the date, so this may be the automated installer?):
>> [Device Install (Install Windows Update driver) - ACPI\FUJ02BF]
>> Section start 2010/03/24 23:09:18.489
dvi: Set selected driver complete.
dvi: {Build Driver List} 23:09:18.520
dvi: Searching for hardware ID(s):
dvi: acpi\fuj02bf
dvi: *fuj02bf
cpy: Policy is set to make all digital signatures equal.
dvi: Unable to retrieve InfPath - likely no driver installed
dvi: {Build Driver List - exit(0x00000000)} 23:09:18.520
dvi: {Build Driver List} 23:09:18.520
dvi: Searching for hardware ID(s):
dvi: acpi\fuj02bf
dvi: *fuj02bf
cpy: Policy is set to make all digital signatures equal.
dvi: Enumerating INFs from path list ‘c:\windows\softwaredistribution\download\install’
sig: {_VERIFY_FILE_SIGNATURE} 23:09:18.536
sig: Key = fjbtndrv.inf
sig: FilePath = c:\windows\softwaredistribution\download\install\fjbtndrv.inf
sig: Catalog = c:\windows\softwaredistribution\download\install\fjbtndrv.cat
sig: Success: File is signed in catalog.
sig: {_VERIFY_FILE_SIGNATURE exit(0x00000000)} 23:09:18.551
dvi: Created Driver Node:
dvi: HardwareID - ACPI\FUJ02BF
dvi: InfName - c:\windows\softwaredistribution\download\install\fjbtndrv.inf
dvi: DevDesc - Fujitsu Button Device
dvi: DrvDesc - Fujitsu Button Device
dvi: Provider - Fujitsu Computer Systems Corporation
dvi: Mfg - Fujitsu Computer Systems Corporation
dvi: ModelsSec - FPC
dvi: InstallSec - fjbtndrvInst
dvi: ActualSec - fjbtndrvInst.NT
dvi: Rank - 0x00ff0000
dvi: Signer - Microsoft Windows Hardware Compatibility Publisher
dvi: Signer Score - WHQL
dvi: DrvDate - 12/23/2004
dvi: Version - 1.1.1223.2004
inf: Searched 1 INFs in directory: ‘c:\windows\softwaredistribution\download\install’
dvi: {Build Driver List - exit(0x00000000)} 23:09:18.567
dvi: {DIF_SELECTBESTCOMPATDRV} 23:09:18.567
dvi: No class installer for ‘Human Interface Devices’
dvi: No CoInstallers found
dvi: Default installer: Enter 23:09:18.598
dvi: {Select Best Driver}
dvi: Selected driver installs from section [fjbtndrvInst] in ‘c:\windows\softwaredistribution\download\install\fjbtndrv.inf’.
dvi: Class GUID of device changed to: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}.
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [Fujitsu Button Device]
dvi: InfFile - [c:\windows\softwaredistribution\download\install\fjbtndrv.inf]
dvi: Section - [fjbtndrvInst]
dvi: Signer - [Microsoft Windows Hardware Compatibility Publisher]
dvi: Rank - [0x00ff0000]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 23:09:18.614
inf: {SetupCopyOEMInf: c:\windows\softwaredistribution\download\install\fjbtndrv.inf} 23:09:18.614
sto: {Import Driver Package: c:\windows\softwaredistribution\download\install\fjbtndrv.inf} 23:09:18.614
sto: Importing driver package into Driver Store:
sto: Driver Store = C:\Windows\System32\DriverStore (Online | 6.1.7600)
sto: Driver Package = c:\windows\softwaredistribution\download\install\fjbtndrv.inf
sto: Architecture = x86
sto: Locale Name = neutral
sto: Flags = 0x00000008
sto: Copying driver package files to ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}’.
inf: Opened INF: ‘c:\windows\softwaredistribution\download\install\fjbtndrv.inf’ ([strings])
inf: Opened INF: ‘c:\windows\softwaredistribution\download\install\fjbtndrv.inf’ ([strings])
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - ‘c:\windows\softwaredistribution\download\install’
flq: SourceFilename - ‘fjbtndrv.cat’
flq: TargetDirectory- ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}’
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - ‘c:\windows\softwaredistribution\download\install’
flq: SourceFilename - ‘fjbtndrv.inf’
flq: TargetDirectory- ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}’
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - ‘c:\windows\softwaredistribution\download\install’
flq: SourceFilename - ‘FjBtndrv.sys’
flq: TargetDirectory- ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}’
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {_commit_file_queue}
flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=3
flq: {_commit_copy_subqueue}
flq: subqueue count=3
flq: source media:
flq: SourcePath - [c:\windows\softwaredistribution\download\install]
flq: SourceFile - [fjbtndrv.cat]
flq: Flags - 0x00000000
flq: {_commit_copyfile}
flq: CopyFile: ‘c:\windows\softwaredistribution\download\install\fjbtndrv.cat’
flq: to: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\SETC8E3.tmp’
flq: MoveFile: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\SETC8E3.tmp’
flq: to: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\fjbtndrv.cat’
flq: {_commit_copyfile exit OK}
flq: {_commit_copyfile}
flq: CopyFile: ‘c:\windows\softwaredistribution\download\install\fjbtndrv.inf’
flq: to: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\SETC8F4.tmp’
flq: MoveFile: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\SETC8F4.tmp’
flq: to: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\fjbtndrv.inf’
flq: {_commit_copyfile exit OK}
flq: {_commit_copyfile}
flq: CopyFile: ‘c:\windows\softwaredistribution\download\install\FjBtndrv.sys’
flq: to: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\SETC8F5.tmp’
flq: MoveFile: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\SETC8F5.tmp’
flq: to: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\FjBtndrv.sys’
flq: {_commit_copyfile exit OK}
flq: {_commit_copy_subqueue exit OK}
flq: {_commit_file_queue exit OK}
pol: {Driver package policy check} 23:09:18.692
pol: {Driver package policy check - exit(0x00000000)} 23:09:18.692
sto: {Stage Driver Package: C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\fjbtndrv.inf} 23:09:18.692
inf: Opened INF: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\fjbtndrv.inf’ ([strings])
inf: Opened INF: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\fjbtndrv.inf’ ([strings])
sto: Copying driver package files:
sto: Source Path = C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}
sto: Destination Path = C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000010
flq: SourceRootPath - ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}’
flq: SourceFilename - ‘fjbtndrv.cat’
flq: TargetDirectory- ‘C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}’
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000010
flq: SourceRootPath - ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}’
flq: SourceFilename - ‘fjbtndrv.inf’
flq: TargetDirectory- ‘C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}’
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000010
flq: SourceRootPath - ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}’
flq: SourceFilename - ‘FjBtndrv.sys’
flq: TargetDirectory- ‘C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}’
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {_commit_file_queue}
flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=3
flq: {_commit_copy_subqueue}
flq: subqueue count=3
flq: source media:
flq: SourcePath - [C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}]
flq: SourceFile - [fjbtndrv.cat]
flq: Flags - 0x00000000
flq: {_commit_copyfile}
flq: CopyFile: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\fjbtndrv.cat’
flq: to: ‘C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}\SETC958.tmp’
flq: MoveFile: ‘C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}\SETC958.tmp’
flq: to: ‘C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}\fjbtndrv.cat’
flq: {_commit_copyfile exit OK}
flq: {_commit_copyfile}
flq: CopyFile: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\fjbtndrv.inf’
flq: to: ‘C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}\SETC969.tmp’
flq: MoveFile: ‘C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}\SETC969.tmp’
flq: to: ‘C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}\fjbtndrv.inf’
flq: {_commit_copyfile exit OK}
flq: {_commit_copyfile}
flq: CopyFile: ‘C:\Windows\TEMP{0cff78b4-861e-4e49-5fd8-8407cb247e07}\FjBtndrv.sys’
flq: to: ‘C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}\SETC96A.tmp’
flq: MoveFile: ‘C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}\SETC96A.tmp’
flq: to: ‘C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}\FjBtndrv.sys’
flq: {_commit_copyfile exit OK}
flq: {_commit_copy_subqueue exit OK}
flq: {_commit_file_queue exit OK}
sto: {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE} 23:09:18.801
inf: Opened INF: ‘C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}\fjbtndrv.inf’ ([strings])
sig: {_VERIFY_FILE_SIGNATURE} 23:09:18.817
sig: Key = fjbtndrv.inf
sig: FilePath = C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}\fjbtndrv.inf
sig: Catalog = C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}\fjbtndrv.cat
sig: Success: File is signed in catalog.
sig: {_VERIFY_FILE_SIGNATURE exit(0x00000000)} 23:09:18.864
sto: Validating driver package files against catalog ‘fjbtndrv.cat’.
sto: Driver package is valid.
sto: {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE exit(0x00000000)} 23:09:18.864
sto: Verified driver package signature:
sto: Digital Signer Score = 0x0D000005
sto: Digital Signer Name = Microsoft Windows Hardware Compatibility Publisher
sto: {DRIVERSTORE_IMPORT_NOTIFY_BEGIN} 23:09:18.879
ndv: System restore not required for signed driver package.
sto: {DRIVERSTORE_IMPORT_NOTIFY_BEGIN: exit(0x00000000)} 23:09:18.879
sto: Importing driver package files:
sto: Source Path = C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}
sto: Destination Path = C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac
sto: {Copy Directory: C:\Windows\System32\DriverStore\Temp{1b9f9ab4-7607-5e95-779e-be70f41b0c50}} 23:09:18.879
sto: Target Path = C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac
sto: {Copy Directory: exit(0x00000000)} 23:09:18.879
sto: {Index Driver Package: C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf} 23:09:18.879
idb: Registered driver store entry ‘fjbtndrv.inf_x86_neutral_902e0d38a603f7ac’.
idb: Published ‘fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf’ to ‘C:\Windows\INF\oem4.inf’
idb: Published driver store entry ‘fjbtndrv.inf_x86_neutral_902e0d38a603f7ac’.
sto: Published driver package INF ‘oem4.inf’ was changed.
sto: Active published driver package is ‘fjbtndrv.inf_x86_neutral_902e0d38a603f7ac’.
sto: {Index Driver Package: exit(0x00000000)} 23:09:19.254
sto: {DRIVERSTORE_IMPORT_NOTIFY_END} 23:09:19.254
ndv: No system restore point was set earlier.
sto: {DRIVERSTORE_IMPORT_NOTIFY_END: exit(0x00000000)} 23:09:19.270
sto: {Stage Driver Package: exit(0x00000000)} 23:09:19.270
ndv: Doing device matching lookup!
inf: Opened INF: ‘C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf’ ([strings])
inf: Saved PNF: ‘C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.PNF’ (Language = 0409)
ndv: Found device that matches new INF!
sto: Driver package was staged to Driver Store. Time = 672 ms
sto: Imported driver package into Driver Store:
sto: Filename = C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf
sto: Time = 735 ms
sto: {Import Driver Package: exit(0x00000000)} 23:09:19.348
inf: Opened INF: ‘c:\windows\softwaredistribution\download\install\fjbtndrv.inf’ ([strings])
inf: Driver Store location: C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf
inf: Published Inf Path: C:\Windows\INF\oem4.inf
inf: Opened INF: ‘c:\windows\softwaredistribution\download\install\fjbtndrv.inf’ ([strings])
inf: Installing catalog fjbtndrv.cat as: oem4.CAT
inf: OEM source media location: c:\windows\softwaredistribution\download\install\
inf: {SetupCopyOEMInf exit (0x00000000)} 23:09:19.536
dvi: Searching for hardware ID(s):
dvi: acpi\fuj02bf
dvi: *fuj02bf
inf: Opened PNF: ‘C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf’ ([strings])
dvi: Selected driver installs from section [fjbtndrvInst] in ‘c:\windows\system32\driverstore\filerepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf’.
dvi: Class GUID of device changed to: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}.
dvi: Set selected driver complete.
dvi: {Plug and Play Service: Device Install for ACPI\FUJ02BF\4&23C21BFE&0}
ump: Creating Install Process: DrvInst.exe 23:09:19.551
ndv: Infpath=C:\Windows\INF\oem4.inf
ndv: DriverNodeName=fjbtndrv.inf:FPC:fjbtndrvInst:1.1.1223.2004:acpi\fuj02bf
ndv: DriverStorepath=C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf
ndv: Building driver list from driver node strong name…
dvi: Searching for hardware ID(s):
dvi: acpi\fuj02bf
dvi: *fuj02bf
inf: Opened PNF: ‘C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf’ ([strings])
dvi: Selected driver installs from section [fjbtndrvInst] in ‘c:\windows\system32\driverstore\filerepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf’.
dvi: Class GUID of device changed to: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}.
dvi: Set selected driver complete.
ndv: {Core Device Install} 23:09:19.598
inf: Opened INF: ‘C:\Windows\INF\oem4.inf’ ([strings])
inf: Saved PNF: ‘C:\Windows\INF\oem4.PNF’ (Language = 0409)
dvi: {DIF_ALLOW_INSTALL} 23:09:19.661
dvi: No class installer for ‘Fujitsu Button Device’
dvi: No CoInstallers found
dvi: Default installer: Enter 23:09:19.661
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 23:09:19.661
ndv: Installing files…
dvi: {DIF_INSTALLDEVICEFILES} 23:09:19.661
dvi: No class installer for ‘Fujitsu Button Device’
dvi: Default installer: Enter 23:09:19.676
dvi: {Install FILES}
inf: Opened PNF: ‘c:\windows\system32\driverstore\filerepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf’ ([strings])
inf: {Install Inf Section [fjbtndrvInst.NT]}
inf: CopyFiles=fjbtndrvInst.NT.Copy (fjbtndrv.inf line 39)
cpy: Open PnpLockdownPolicy: Err=2. This is OK. Use LockDownPolicyDefault
flq: QueueSingleCopy…
flq: Inf : ‘c:\windows\system32\driverstore\filerepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf’
flq: SourceInf: ‘c:\windows\system32\driverstore\filerepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf’
flq: SourceSection: [sourcedisksfiles]
flq: Source root path based on SourceInf
flq: SourceRootPath: ‘C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac’
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - ‘C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac’
flq: SourceFilename - ‘FjBtndrv.sys’
flq: TargetDirectory- ‘C:\Windows\system32\DRIVERS’
flq: TargetFilename - ‘FjBtndrv.sys’
flq: SourceDesc - ‘Fujitsu Button Driver Setup Disk’
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY exit(0x00000000)}
inf: {Install Inf Section [fjbtndrvInst.NT] exit (0x00000000)}
dvi: Processing co-installer registration section [fjbtndrvInst.NT.CoInstallers].
inf: {Install Inf Section [fjbtndrvInst.NT.CoInstallers]}
inf: {Install Inf Section [fjbtndrvInst.NT.CoInstallers] exit (0x00000000)}
dvi: Co-installers registered.
dvi: {Install INTERFACES}
dvi: Installing section [fjbtndrvInst.NT.Interfaces]
dvi: {Install INTERFACES exit 00000000}
dvi: {Install FILES exit (0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 23:09:19.708
ndv: Pruning file queue…
dvi: {_SCAN_FILE_QUEUE}
flq: ScanQ flags=620
flq: SPQ_SCAN_PRUNE_COPY_QUEUE
flq: SPQ_SCAN_FILE_COMPARISON
flq: SPQ_SCAN_ACTIVATE_DRP
flq: ScanQ number of copy nodes=1
flq: ScanQ action=200 DoPruning=32
flq: ScanQ end Validity flags=620 CopyNodes=1
dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
ndv: Committing file queue…
flq: {_commit_file_queue}
flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=1
flq: {SPFILENOTIFY_STARTQUEUE}
flq: {SPFILENOTIFY_STARTQUEUE - exit(0x00000001)}
flq: {_commit_copy_subqueue}
flq: subqueue count=1
flq: {SPFILENOTIFY_STARTSUBQUEUE}
flq: {SPFILENOTIFY_STARTSUBQUEUE - exit(0x00000001)}
flq: source media:
flq: Description - [Fujitsu Button Driver Setup Disk]
flq: SourcePath - [C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac]
flq: SourceFile - [FjBtndrv.sys]
flq: Flags - 0x00000000
flq: {SPFQNOTIFY_NEEDMEDIA}
flq: {SPFILENOTIFY_NEEDMEDIA}
flq: {SPFILENOTIFY_NEEDMEDIA - exit(0x00000001)}
flq: {SPFQNOTIFY_NEEDMEDIA - returned 0x00000001}
flq: source media: SPFQOPERATION_DOIT
flq: {_commit_copyfile}
flq: {SPFILENOTIFY_STARTCOPY}
ndv: Saving LastKnownGood file C:\Windows\system32\DRIVERS\FjBtndrv.sys (copy)
flq: {SPFILENOTIFY_STARTCOPY - exit(0x00000001)}
flq: CopyFile: ‘C:\Windows\System32\DriverStore\FileRepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\FjBtndrv.sys’
flq: to: ‘C:\Windows\system32\DRIVERS\SETCD21.tmp’
cpy: CopyFile Drp is active
sig: Using catalog ‘C:\Windows\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem4.CAT’.
cpy: Source File ‘C:\Windows\system32\DRIVERS\SETCD21.tmp’ is NOT signed NT5 Crypto.
cpy: DrpGetFileProt Status=2 dwClass=0
flq: MoveFile: ‘C:\Windows\system32\DRIVERS\SETCD21.tmp’
flq: to: ‘C:\Windows\system32\DRIVERS\FjBtndrv.sys’
cpy: DrpSetRegFileProt ‘C:\Windows\system32\DRIVERS\FjBtndrv.sys’ Status=0 Class=OEM Legacy
flq: Caller applied security to file ‘C:\Windows\system32\DRIVERS\FjBtndrv.sys’.
flq: {SPFILENOTIFY_ENDCOPY}
flq: {SPFILENOTIFY_ENDCOPY - exit(0x00000001)}
flq: {_commit_copyfile exit OK}
flq: {SPFILENOTIFY_ENDSUBQUEUE}
flq: {SPFILENOTIFY_ENDSUBQUEUE - exit(0x00000001)}
flq: {_commit_copy_subqueue exit OK}
flq: {SPFILENOTIFY_ENDQUEUE}
flq: {SPFILENOTIFY_ENDQUEUE - exit(0x00000001)}
flq: {_commit_file_queue exit OK}
ndv: Registering CoInstallers…
dvi: {DIF_REGISTER_COINSTALLERS} 23:09:19.848
dvi: No class installer for ‘Fujitsu Button Device’
dvi: Default installer: Enter 23:09:19.848
inf: Opened PNF: ‘c:\windows\system32\driverstore\filerepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf’ ([strings])
inf: {Install Inf Section [fjbtndrvInst.NT.CoInstallers]}
inf: {Install Inf Section [fjbtndrvInst.NT.CoInstallers] exit (0x00000000)}
dvi: Co-installers registered.
dvi: Default installer: Exit
dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 23:09:19.848
ndv: Installing interfaces…
dvi: {DIF_INSTALLINTERFACES} 23:09:19.864
dvi: No class installer for ‘Fujitsu Button Device’
dvi: No CoInstallers found
dvi: Default installer: Enter 23:09:19.864
dvi: {Install INTERFACES}
inf: Opened PNF: ‘c:\windows\system32\driverstore\filerepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf’ ([strings])
dvi: Installing section [fjbtndrvInst.NT.Interfaces]
dvi: {Install INTERFACES exit 00000000}
dvi: Default installer: Exit
dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 23:09:19.864
ndv: Installing device…
dvi: {DIF_INSTALLDEVICE} 23:09:19.864
dvi: No class installer for ‘Fujitsu Button Device’
dvi: Default installer: Enter 23:09:19.864
dvi: {Install DEVICE}
inf: Opened PNF: ‘c:\windows\system32\driverstore\filerepository\fjbtndrv.inf_x86_neutral_902e0d38a603f7ac\fjbtndrv.inf’ ([strings])
dvi: Processing Registry/Property directives…
inf: {Install Inf Section [fjbtndrvInst.NT]}
inf: {Install Inf Section [fjbtndrvInst.NT] exit (0x00000000)}
inf: {Install Inf Section [fjbtndrvInst.NT.Hw]}
inf: AddReg=fjbtndrvInst.NT.AddReg (fjbtndrv.inf line 28)
inf: {Install Inf Section [fjbtndrvInst.NT.Hw] exit (0x00000000)}
dvi: {Writing Device Properties}
dvi: Provider name=Fujitsu Computer Systems Corporation
dvi: DriverDate 12/23/2004
dvi: DriverVersion=1.1.1223.2004
dvi: Class name=HIDClass
dvi: Manufacturer=Fujitsu Computer Systems Corporation
dvi: Matching DeviceID=acpi\fuj02bf
dvi: Strong Name=oem4.inf:FPC:fjbtndrvInst:1.1.1223.2004:acpi\fuj02bf
dvi: {Writing Device Properties - Complete}
inf: {Install Inf Section [fjbtndrvInst.NT.Services]}
inf: AddService=fjbtndrv,0x00000002,fjbtndrvServiceInst,fjbtndrvEventLogInst (fjbtndrv.inf line 45)
inf: ServiceType=1 (fjbtndrv.inf line 57)
inf: StartType=3 (fjbtndrv.inf line 58)
inf: ErrorControl=1 (fjbtndrv.inf line 59)
inf: ServiceBinary=C:\Windows\system32\DRIVERS\Fjbtndrv.sys (fjbtndrv.inf line 60)
inf: DisplayName=“Fujitsu Button Driver” (fjbtndrv.inf line 56)
inf: LoadOrderGroup=“Extended Base” (fjbtndrv.inf line 61)
dvi: Add Service: Created service ‘fjbtndrv’.
inf: AddReg=fjbtndrvEventLogAddReg (fjbtndrv.inf line 48)
inf: {Install Inf Section [fjbtndrvInst.NT.Services] exit(0x00000000)}
dvi: Updated reflected section names for: oem4.inf
dvi: {Install DEVICE exit (0x00000000)}
dvi: Writing common driver property settings.
dvi: DriverDescription=Fujitsu Button Device
dvi: DeviceDisplayName=Fujitsu Button Device
dvi: {Restarting Devices} 23:09:20.973
dvi: Restart: ACPI\FUJ02BF\4&23C21BFE&0
dvi: Restart complete.
dvi: {Restarting Devices exit} 23:09:21.129
dvi: Default installer: Exit
dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 23:09:21.129
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 23:09:21.129
dvi: No class installer for ‘Fujitsu Button Device’
dvi: Default installer: Enter 23:09:21.129
dvi: Default installer: Exit
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 23:09:21.129
ndv: Device install status=0x00000000
ndv: Performing device install final cleanup…
ndv: {Core Device Install - exit(0x00000000)} 23:09:21.145
ump: Server install process exited with code 0x00000000 23:09:21.145
ump: {Plug and Play Service: Device Install exit(00000000)}
dvi: {Build Driver List} 23:09:21.161
! dvi: Driver list already built
dvi: {Build Driver List - exit(0x00000000)} 23:09:21.161
dvi: {DIF_SELECTBESTCOMPATDRV} 23:09:21.161
dvi: No class installer for ‘Fujitsu Button Device’
dvi: No CoInstallers found
dvi: Default installer: Enter 23:09:21.161
dvi: {Select Best Driver}
dvi: Selected driver installs from section [fjbtndrvInst] in ‘c:\windows\softwaredistribution\download\install\fjbtndrv.inf’.
dvi: Class GUID of device remains: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}.
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [Fujitsu Button Device]
dvi: InfFile - [c:\windows\softwaredistribution\download\install\fjbtndrv.inf]
dvi: Section - [fjbtndrvInst]
dvi: Signer - [Microsoft Windows Hardware Compatibility Publisher]
dvi: Rank - [0x00ff0000]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 23:09:21.192
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 23:09:21.192
dvi: No class installer for ‘Fujitsu Button Device’
dvi: Default installer: Enter 23:09:21.192
dvi: Default installer: Exit
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 23:09:21.192
<<< Section end 2010/03/24 23:09:21.223
<<< [Exit status: SUCCESS]
From
Alright, an update. On a new partition, I have done another windows 7 install, perfectly clean, and told it not to update anything when choosing automatic updates. In the device manager, these are the “Other Devices”
Multimedia Audio Controller
O2Micro SmartCardBus_Reader
Other PCI Bridge Device
Unknown Device
–Hardware ID: ACPI\FUJ02B1
–Hardware ID: *FUJ02B1
Unknown Device
–Hardware ID: ACPI\FUJ02BF
–Hardware ID: *FUJ02BF
Unknown Device
–Hardware ID: ACPI\SMCF010
–Hardware ID: *SMCF010
Video Controller
Now, the internet connection on this partition is off, and auto updates are off, so I’m in total control of what drivers get installed. I’m backing up the registry (just doing an export is fine, right?), and creating a backup file. What do you guys think I should do at this point? Or rather, what order of operations?
Correction: I didn’t make a backup file, I created a system restore point. I’m sure there are differences between these two, but I’m not quite sure what.
On this clean partition, I tried running the driver installation as downloaded from the website under system compatibility mode with winxp sp2 and according to the installer, it completed.
setupapi.dev.log does not show any instances of fjbtndrv.inf
Setupapi.dev.log DOES show three instances of “ACPI\Fuj”. Namely, acpi\fuj02b1, acpi\fuj02bf, and acpi\fuj02e5.
fuj02b1 and fuj02bf have a CONFIGFLAG_REINSTALL on a non-started device
fuj02e5 has a CONFIGFLAG_FINISH_INSTALL on started device.
–fuj02e5 has a device description of Wacom Serial Pen Tablet
Searching for changes in the registry:
Searching for “fuj02b1”, I found the following hits. All of these existed both before and after the manual install attempt. In other words, I have no idea what the driver install accomplished.
HKLM\System\ControlSet001\Enum\ACPI\Fuj02b1
HKLM\System\ControlSet002\Enum\ACPI\Fuj02b1
HKLM\System\CurrentControlSet\Enum\ACPI\FUJ02B1
No results for “fjbtn” in the registry
All results for fujitsu were unrelated to the button driver in the registry
In Device Manager, the two unknown devices were unchanged.
No changes in setupapi.dev.log
The registry grew by about 4000 lines, but I’m really not going to look for them. In effect, the manual driver install accomplished nothing. How else should I go about this?
After restoring the system registry, I tried updating the driver manually via the update driver and browse for files on disk.
Fuj02b1 did not find any files appropriate to the device
fuj02bf found:
Fujitsu Lifebook T3000 Tablet PC Buttons.
This is what happened next:
Windows can’t verify the publisher
–install anyway
Finished installing
Now we’re back to square one, where the buttons will wake a computer up (if the screen is dim it’ll brighten up) and pressing and holding one of the tablet buttons calls the task manager.
xxxxx@gmail.com wrote:
After restoring the system registry, I tried updating the driver manually via the update driver and browse for files on disk.
Fuj02b1 did not find any files appropriate to the device
fuj02bf found:
Fujitsu Lifebook T3000 Tablet PC Buttons.This is what happened next:
Windows can’t verify the publisher
–install anyway
Finished installingNow we’re back to square one, where the buttons will wake a computer up (if the screen is dim it’ll brighten up) and pressing and holding one of the tablet buttons calls the task manager.
OK, so what were you trying to accomplish? Are you trying to REPLACE
this driver with one of your own?
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
I have 5 buttons on the face of my tablet pc that don’t work and a seemingly defective manufacturer-provided driver (written in the days of XP, I run win7 32bit). I want to either figure out how and why it’s not working, or end up writing a new driver (I doubt I’d need to go that far, but who knows).
The end goal is to have 5 functional buttons that I will be able to configure at my discretion to do any kinds of key combinations.
Uh, the manufacturer does not have a driver for Win7?
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Wednesday, May 19, 2010 9:05 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Installing a driver, need some help with inf
I have 5 buttons on the face of my tablet pc that don’t work and a seemingly
defective manufacturer-provided driver (written in the days of XP, I run
win7 32bit). I want to either figure out how and why it’s not working, or
end up writing a new driver (I doubt I’d need to go that far, but who
knows).
The end goal is to have 5 functional buttons that I will be able to
configure at my discretion to do any kinds of key combinations.
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
__________ Information from ESET Smart Security, version of virus signature
database 5130 (20100519) __________
The message was checked by ESET Smart Security.
__________ Information from ESET Smart Security, version of virus signature
database 5130 (20100519) __________
The message was checked by ESET Smart Security.
No, they don’t…that was a key point I made, I’m sure of it. If they had a Win 7 32bit driver, I would have been talking exclusively to them to make this work. It’s a Win XP driver, and I want to re-purpose it for my windows 7.
And unless someone can give me some sort of irrefutable evidence that it absolutely can’t be done, I won’t listen on the basis of the fact that the OS recognizes that those buttons are being pressed, and one of them held down causes the ctrl-alt-del action to be performed.