DPINST CA
Hi Guys,
Please help my frustration and I have read plenty of posts on DPINST.
Usually I use wisescript to execute the dpinst command and works great...
DPInst is used to install Citizen drivers to Win7 32bit box. (silently).
But now through various change....receiving 1721 and 1722 errors in the verbose log.
I can use dpinst manually through the cmd line successfully.
I am without it and using INSTED and trying to execute the CA.
Now this could be an excercise of me using CustomActionData - I am not an expert of this...
I saw an article where dpinst can be inserted into the Binary table.
And simply add the CA with :
Executable File DPINST.exe
Commandline arguments /S /LM /PATH "[INSTALLDIR]
The type is set to 3074.
Also have the dpinst in the path of c:\program files\citizen\cts2000 with the inf files as well.
Using CA Type 3106 - I have:
CA:
GetDIR 51 InstallDriver [CTS2000_Driver]
InstallDriver 3106 CTS2000_Driver dpinst.exe /Q /LM /PATH "c:\program files\citizen\CTS2000 Driver 1.0.0.1"
Property set:
InstallDriver [CTS2000_Driver]
The InstallDriver /PATH=... is so the last backslash is ommited.
The GetDIR and InstallDriver are sequenced....GetDIR after InstallInitiate....and InstallDriver just before InstallFinalise with NOT(REMOVE~="ALL") as the condition.
The MSI Log shows:
MSI (s) (64:6C) [14:32:50:748]: Executing op: ActionStart(Name=InstallDriver,,)
MSI (s) (64:6C) [14:32:50:748]: Executing op: CustomActionSchedule(Action=InstallDriver,ActionType=3106,Source=C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1\,Target=dpinst.exe /Q /LM /PATH "c:\program files\citizen\CTS2000 Driver 1.0.0.1",CustomActionData=C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1\)
MSI (s) (64:6C) [14:32:50:748]: Note: 1: 1721 2: InstallDriver 3: C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1\ 4: dpinst.exe /Q /LM /PATH "c:\program files\citizen\CTS2000 Driver 1.0.0.1"
MSI (s) (64:6C) [14:32:50:748]: Product: CTS2000 Driver -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: InstallDriver, location: C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1\, command: dpinst.exe /Q /LM /PATH "c:\program files\citizen\CTS2000 Driver 1.0.0.1"
Is the problem due to the backslash in: location: C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1\
Please help my frustration and I have read plenty of posts on DPINST.
Usually I use wisescript to execute the dpinst command and works great...
DPInst is used to install Citizen drivers to Win7 32bit box. (silently).
But now through various change....receiving 1721 and 1722 errors in the verbose log.
I can use dpinst manually through the cmd line successfully.
I am without it and using INSTED and trying to execute the CA.
Now this could be an excercise of me using CustomActionData - I am not an expert of this...
I saw an article where dpinst can be inserted into the Binary table.
And simply add the CA with :
Executable File DPINST.exe
Commandline arguments /S /LM /PATH "[INSTALLDIR]
The type is set to 3074.
Also have the dpinst in the path of c:\program files\citizen\cts2000 with the inf files as well.
Using CA Type 3106 - I have:
CA:
GetDIR 51 InstallDriver [CTS2000_Driver]
InstallDriver 3106 CTS2000_Driver dpinst.exe /Q /LM /PATH "c:\program files\citizen\CTS2000 Driver 1.0.0.1"
Property set:
InstallDriver [CTS2000_Driver]
The InstallDriver /PATH=... is so the last backslash is ommited.
The GetDIR and InstallDriver are sequenced....GetDIR after InstallInitiate....and InstallDriver just before InstallFinalise with NOT(REMOVE~="ALL") as the condition.
The MSI Log shows:
MSI (s) (64:6C) [14:32:50:748]: Executing op: ActionStart(Name=InstallDriver,,)
MSI (s) (64:6C) [14:32:50:748]: Executing op: CustomActionSchedule(Action=InstallDriver,ActionType=3106,Source=C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1\,Target=dpinst.exe /Q /LM /PATH "c:\program files\citizen\CTS2000 Driver 1.0.0.1",CustomActionData=C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1\)
MSI (s) (64:6C) [14:32:50:748]: Note: 1: 1721 2: InstallDriver 3: C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1\ 4: dpinst.exe /Q /LM /PATH "c:\program files\citizen\CTS2000 Driver 1.0.0.1"
MSI (s) (64:6C) [14:32:50:748]: Product: CTS2000 Driver -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: InstallDriver, location: C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1\, command: dpinst.exe /Q /LM /PATH "c:\program files\citizen\CTS2000 Driver 1.0.0.1"
Is the problem due to the backslash in: location: C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1\
0 Comments
[ + ] Show comments
Answers (12)
Please log in to answer
Posted by:
tron2ole
13 years ago
I had made a change which switched to the 1722 error:
reference to the file table dpinst.exe
CA:
GetDIR 51 InstallDriver [CTS2000_Driver]DpInst,exe
InstallDriver 3090 dpinst.exe /Q /LM
Property set: InstallDriver Value= [CTS2000_Driver]dpinst.exe
Any suggestions?
reference to the file table dpinst.exe
CA:
GetDIR 51 InstallDriver [CTS2000_Driver]DpInst,exe
InstallDriver 3090 dpinst.exe /Q /LM
Property set: InstallDriver Value= [CTS2000_Driver]dpinst.exe
Any suggestions?
Posted by:
tron2ole
13 years ago
The Dpinst log in windir looks for the inf file but because the msi is not installing...the files are not resident...
Any ideas?
Any ideas?
INFO: ****************************************
INFO: 06/20/2011 15:25:06
INFO: Windows Codename Longhorn
INFO: Product Version 2.0.0.0.
INFO: Architecture: X86.
INFO: Command Line: '"C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1\DPInst.exe" /Q /LM'
INFO: ****************************************
INFO: Current working directory: 'C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1'
INFO: Running on path 'C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1'
INFO: No valid 'dpinst.xml' file provided.
WARNING:Running on Windows Codename Longhorn, 'Add/Remove Programs' is not supported and has been disabled.
INFO: Install option set: Running in quiet mode. Suppressing Wizard and OS popups.
INFO: Install option set: legacy mode on.
INFO: Install option set: Suppress Add or Remove Programs entries.
INFO: Found driver package: 'C:\Program Files\Citizen\CTS2000 Driver 1.0.0.1\cts2000e.inf'.
INFO: ENTER: DriverPackagePreinstallW
INFO: Running on Windows codenamed Longhorn.
WARNING:DRIVER_PACKAGE_LEGACY_MODE flag set but not supported on Longhorn. Flag will be ignored.
SUCCESS:c:\program files\citizen\cts2000 driver 1.0.0.1\cts2000e.inf is preinstalled.
INFO: RETURN: DriverPackagePreinstallW (0x0)
INFO: ENTER: DriverPackageGetPathW
ERROR: DriverPackageGetPath is not yet supported for PnP drivers on LH.
INFO: RETURN: DriverPackageGetPathW (0xA)
INFO: ENTER: DriverPackageInstallW
INFO: Running on Windows codenamed Longhorn.
INFO: Installing INF file "c:\program files\citizen\cts2000 driver 1.0.0.1\cts2000e.inf" (Plug and Play).
INFO: Looking for Model Section [CSJ]...
INFO: No matching devices found in INF "c:\program files\citizen\cts2000 driver 1.0.0.1\cts2000e.inf" on the Machine.
INFO: No drivers installed. No devices found that match driver(s) contained in 'c:\program files\citizen\cts2000 driver 1.0.0.1\cts2000e.inf'.
INFO: RETURN: DriverPackageInstallW (0xE000020B)
INFO: No matching device was found for 'c:\program files\citizen\cts2000 driver 1.0.0.1\cts2000e.inf'. Driver will be installed when plugged in.
INFO: Not creating any Add or Remove Programs entry because not supported on Longhorn yet.
INFO: Returning with code 0x100
INFO: 06/20/2011 15:25:06
Posted by:
tron2ole
13 years ago
Dont make me use a VBScript as a CA.....I should be able to execute DPINST natively within the Windows Installer! [sm=rolleyes.gif]
Posted by:
SandeepPanat
13 years ago
Have you tried using elevated command prompt with Run as Administrator option to execute the MSI?
I assume, you have looked into the CA references for Execute from installation and Execute from destination.
Does the Wisescript standalone wrapper works fine?
I assume, you have looked into the CA references for Execute from installation and Execute from destination.
Does the Wisescript standalone wrapper works fine?
Posted by:
tron2ole
13 years ago
Hi SandeepPanat.
Thanks for your reply...
Yeah originally I tried CA Type 3106 is execute from installation and execute from destination - that is type 34 .
With that...I always use execute deferred and no impresonate....that gives another 1024 and 2048 = 3106.
I have tried execute from Binary table - not what I preferred....as i could have added a vbscript but done anyway....
But this did not work even though I provided the /PATH switch.
Tried to link the CA to the File Table Key and also the working directory as you had suggested....
Dont know where I am going wrong....!
I have used wisescript before....like vbscript....very easy to do....but for this exercise....I want to be proven wrong that it cant be done within the installer itself....
Thanks for your reply...
Yeah originally I tried CA Type 3106 is execute from installation and execute from destination - that is type 34 .
With that...I always use execute deferred and no impresonate....that gives another 1024 and 2048 = 3106.
I have tried execute from Binary table - not what I preferred....as i could have added a vbscript but done anyway....
But this did not work even though I provided the /PATH switch.
Tried to link the CA to the File Table Key and also the working directory as you had suggested....
Dont know where I am going wrong....!
I have used wisescript before....like vbscript....very easy to do....but for this exercise....I want to be proven wrong that it cant be done within the installer itself....
Posted by:
tron2ole
13 years ago
I tried the CA:
Action Type Source Target
InstallDriver 3170 CTS2000_Driver DPInst.exe" /LM /Q
WPS translated to:
Execute Program From Destination
Custom Action Name = InstallDriver
Working Directory = CTS2000_Driver
EXE and Command Line = DPInst.exe" /LM /Q
Action Type Source Target
InstallDriver 3170 CTS2000_Driver DPInst.exe" /LM /Q
WPS translated to:
Execute Program From Destination
Custom Action Name = InstallDriver
Working Directory = CTS2000_Driver
EXE and Command Line = DPInst.exe" /LM /Q
Posted by:
anonymous_9363
13 years ago
If you're using Wise, get the DfxApp merge module and use that. It's a real no-brainer.
Posted by:
sunny07
13 years ago
A quick confirmation did you copy the dpinst.exe to the same folder where the sys file for drivers exist.
if not add dpinst in msi to the folder where the drivers are and use the CA execute program from destination wiht /LM /Q option
if not add dpinst in msi to the folder where the drivers are and use the CA execute program from destination wiht /LM /Q option
Posted by:
pjgeutjens
13 years ago
If you're using Wise, get the DfxApp merge module and use that
And if you're using InstallShield the Device Driver Wizard will help you get the same result.
Like Ian said, you REALLY wanna try to use DfxApp
PJ
Posted by:
tron2ole
13 years ago
Hey thanks for the replies guys....my apology for the non reply - oz time.
VBScab - I am using INSTED....we have Wise for Windows Installer not WPS.
But correct you are saying to use DiffXApp Merge Module.
I just wanted to know what I am doing wrong as a learning excercise.....in case and in the future I have multiple INF files....then DiffXApp will be painful...
I am sure that you mentioned in one of your posts to use dpinst in case that there are plenty of INF files?
Sunny07 - DPINST is with the INF file....with all the files which I had to create a new Catalog file using INF2CAT and signtool etc....worked great.
And if I execute DPINST manually...works fine......I am using CA execute program from destination with the /LM /Q option - I receive 1721 error.
As mentioned: All the driver files (including dpinst) are in c:\program files\citizen\cts2000 1.0.0.1\
Execute Program From Destination
Custom Action Name = InstallDriver
Working Directory = CTS2000_Driver
EXE and Command Line = DPInst.exe" /LM /Q
Is this correct?
VBScab - I am using INSTED....we have Wise for Windows Installer not WPS.
But correct you are saying to use DiffXApp Merge Module.
I just wanted to know what I am doing wrong as a learning excercise.....in case and in the future I have multiple INF files....then DiffXApp will be painful...
I am sure that you mentioned in one of your posts to use dpinst in case that there are plenty of INF files?
Sunny07 - DPINST is with the INF file....with all the files which I had to create a new Catalog file using INF2CAT and signtool etc....worked great.
And if I execute DPINST manually...works fine......I am using CA execute program from destination with the /LM /Q option - I receive 1721 error.
As mentioned: All the driver files (including dpinst) are in c:\program files\citizen\cts2000 1.0.0.1\
Execute Program From Destination
Custom Action Name = InstallDriver
Working Directory = CTS2000_Driver
EXE and Command Line = DPInst.exe" /LM /Q
Is this correct?
Posted by:
tron2ole
13 years ago
Fixed!! Thanks for your patience guys....
DPINST was fine.....
I executed the CA process assynchronisely (128).... Type 3234
And changed the condition of the CA to execute from NOT(REMOVE~="ALL") to NOT Installed.
I know that NOT(REMOVE~="ALL") should have worked....and would check ok.....
But I guess there is no use for a repair action for dpinst...either do it on install or nothing I guess.
DPINST was fine.....
I executed the CA process assynchronisely (128).... Type 3234
And changed the condition of the CA to execute from NOT(REMOVE~="ALL") to NOT Installed.
I know that NOT(REMOVE~="ALL") should have worked....and would check ok.....
But I guess there is no use for a repair action for dpinst...either do it on install or nothing I guess.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.