Cannot install driver

On Thu, 24 Nov 2016 10:56:25 +0000, Java Jive
wrote:

On Thu, 24 Nov 2016 09:31:55 +0000, scbs29
wrote:

I have used TextCrawler to search every .inf file on my pc and none of
them contain any reference to dvc100.
The only one that contains any reference to Pinnacle contains the line
Pinnacle Systems - BDA Hybrid TV Capture Driver
Which is not the dvc100. I did try right click and Install and was
told TheINF file you selected does not support this method of
installation.

If that was an oem*.inf file, then rename that oem*.inf to something
like oem*.inf.not, delete the corresponding *.pnf, reboot, and try the
installation from scratch again.

Thanks for the reply
The file is
c:\windows\inf\ph3xibc1inf
and
c:\windows\inf\ph6xib64c1.inf

There is also
%HPMC.PIN.DeviceDesc% = HPMC_Inst,
SCSI\ChangerPINNACLEALTA____________
and
HPMC.PIN.DeviceDesc = "Pinnacle Micro Alta Optical Library"
in
c:\windows\inf\mchgr.inf

Does your advice apply to any of these ?

--
remove fred before emailing

On Thu, 24 Nov 2016 11:54:48 +0000, scbs29
wrote:

Thanks for the reply
The file is
c:\windows\inf\ph3xibc1inf
and
c:\windows\inf\ph6xib64c1.inf

There is also
%HPMC.PIN.DeviceDesc% = HPMC_Inst,
SCSI\ChangerPINNACLEALTA____________
and
HPMC.PIN.DeviceDesc = "Pinnacle Micro Alta Optical Library"
in
c:\windows\inf\mchgr.inf

Does your advice apply to any of these ?

I've got all of those on my Dell Inspiron, and haven't got your
specific device, or any similar driver or software installations from
it, so I doubt it.

The only other things that occur to me a

:-? Following on your discussions with Paul, the message you got
trying to install the inf suggests that it is part of a wider
installation, and to get everything to work, you must run the wider
installation correctly. I've just repaired my old Dell Latitude 610
laptop by replacing the mobo, and the replacement supports Bluetooth
whereas the original did not. I found I could not install the
Bluetooth device just by rt-clicking it in Device Manager and
choosing to install the drivers. I had to find which among
potentially 10s or 100s were the correct Dell R*.exe files to download
and run, and in which order. I managed it eventually, and got
Bluetooth working, but it was a right-royal PITA to do.

:-? Rather as Paul has suggested, since originally installing the
hardware, drivers, and software, have you installed any other related
or similar device, drivers, or software that could have queered the
pitch?

Apart from the above, I'll keep out of this from now on, because it
doesn't look like I can help.
--
================================================== ======
Please always reply to ng as the email in this post's
header does not exist. Or use a contact address at:
http://www.macfh.co.uk/JavaJive/JavaJive.html
http://www.macfh.co.uk/Macfarlane/Macfarlane.html

On Thu, 24 Nov 2016 12:37:11 +0000, Java Jive
wrote:

On Thu, 24 Nov 2016 11:54:48 +0000, scbs29
wrote:

Thanks for the reply
The file is
c:\windows\inf\ph3xibc1inf
and
c:\windows\inf\ph6xib64c1.inf

There is also
%HPMC.PIN.DeviceDesc% = HPMC_Inst,
SCSI\ChangerPINNACLEALTA____________
and
HPMC.PIN.DeviceDesc = "Pinnacle Micro Alta Optical Library"
in
c:\windows\inf\mchgr.inf

Does your advice apply to any of these ?

I've got all of those on my Dell Inspiron, and haven't got your
specific device, or any similar driver or software installations from
it, so I doubt it.

The only other things that occur to me a

:-? Following on your discussions with Paul, the message you got
trying to install the inf suggests that it is part of a wider
installation, and to get everything to work, you must run the wider
installation correctly. I've just repaired my old Dell Latitude 610
laptop by replacing the mobo, and the replacement supports Bluetooth
whereas the original did not. I found I could not install the
Bluetooth device just by rt-clicking it in Device Manager and
choosing to install the drivers. I had to find which among
potentially 10s or 100s were the correct Dell R*.exe files to download
and run, and in which order. I managed it eventually, and got
Bluetooth working, but it was a right-royal PITA to do.

:-? Rather as Paul has suggested, since originally installing the
hardware, drivers, and software, have you installed any other related
or similar device, drivers, or software that could have queered the
pitch?

Apart from the above, I'll keep out of this from now on, because it
doesn't look like I can help.

No nothing that would have any bearing on the dvc100. As I said, it
was working perfectly until I uninstalled Studio, it was only Studio
that I was having problems with. It was when I tried to install the
drivers or reinstall Studio that the problem arose.
Thanks any way for your help and advice.


--
remove fred before emailing

scbs29 wrote:
On Thu, 24 Nov 2016 12:37:11 +0000, Java Jive
wrote:

On Thu, 24 Nov 2016 11:54:48 +0000, scbs29
wrote:
Thanks for the reply
The file is
c:\windows\inf\ph3xibc1inf
and
c:\windows\inf\ph6xib64c1.inf

There is also
%HPMC.PIN.DeviceDesc% = HPMC_Inst,
SCSI\ChangerPINNACLEALTA____________
and
HPMC.PIN.DeviceDesc = "Pinnacle Micro Alta Optical Library"
in
c:\windows\inf\mchgr.inf

Does your advice apply to any of these ?
I've got all of those on my Dell Inspiron, and haven't got your
specific device, or any similar driver or software installations from
it, so I doubt it.

The only other things that occur to me a

:-? Following on your discussions with Paul, the message you got
trying to install the inf suggests that it is part of a wider
installation, and to get everything to work, you must run the wider
installation correctly. I've just repaired my old Dell Latitude 610
laptop by replacing the mobo, and the replacement supports Bluetooth
whereas the original did not. I found I could not install the
Bluetooth device just by rt-clicking it in Device Manager and
choosing to install the drivers. I had to find which among
potentially 10s or 100s were the correct Dell R*.exe files to download
and run, and in which order. I managed it eventually, and got
Bluetooth working, but it was a right-royal PITA to do.

:-? Rather as Paul has suggested, since originally installing the
hardware, drivers, and software, have you installed any other related
or similar device, drivers, or software that could have queered the
pitch?

Apart from the above, I'll keep out of this from now on, because it
doesn't look like I can help.

No nothing that would have any bearing on the dvc100. As I said, it
was working perfectly until I uninstalled Studio, it was only Studio
that I was having problems with. It was when I tried to install the
drivers or reinstall Studio that the problem arose.
Thanks any way for your help and advice.



I had a chance to run this one.

Pinnacle_Video_Driver_64bit.exe 11,878,776 bytes File Version 14.0.0.166

I loaded that into a 64 bit Windows VM (instead of WINE).
Double-clicked. Then using File Explorer, looked in %temp%.
In there, I could see Pinnacle_Video_Driver_64bit.msi sitting
there. Using 7ZIP, I could look inside. Te key file is
dvcvideo64.inf. The actual files to install are in dvc64.cab,
and they look similar to an EMPIA file set.

https://s13.postimg.org/mrlm561zb/64bitversion.gif

So that installer, at least on the surface, does look
suitable to install a driver for it. The dvcvideo64.inf
has 2304:021A for the hardware identifier.

And being an MSI, I would expect it to create an entry
in Programs and Features control panel.

Paul

On Thu, 24 Nov 2016 17:44:13 -0500, Paul
wrote:

scbs29 wrote:
On Thu, 24 Nov 2016 12:37:11 +0000, Java Jive
wrote:

On Thu, 24 Nov 2016 11:54:48 +0000, scbs29
wrote:
snip
I had a chance to run this one.

Pinnacle_Video_Driver_64bit.exe 11,878,776 bytes File Version 14.0.0.166

I loaded that into a 64 bit Windows VM (instead of WINE).
Double-clicked. Then using File Explorer, looked in %temp%.
In there, I could see Pinnacle_Video_Driver_64bit.msi sitting
there. Using 7ZIP, I could look inside. Te key file is
dvcvideo64.inf. The actual files to install are in dvc64.cab,
and they look similar to an EMPIA file set.

https://s13.postimg.org/mrlm561zb/64bitversion.gif

So that installer, at least on the surface, does look
suitable to install a driver for it. The dvcvideo64.inf
has 2304:021A for the hardware identifier.

And being an MSI, I would expect it to create an entry
in Programs and Features control panel.

Paul

I did get as far as extracting the files from the msi. I assume you
mean to install by right click on dvcvideo64.inf and select Install.
When I do this I get the message
The INF file you selected does not support this method of
installation. BTW I get the same message from any of the inf files.
Please let me know if I have got it wrong.

--
remove fred before emailing

scbs29 wrote:
On Thu, 24 Nov 2016 17:44:13 -0500, Paul
wrote:

scbs29 wrote:
On Thu, 24 Nov 2016 12:37:11 +0000, Java Jive
wrote:

On Thu, 24 Nov 2016 11:54:48 +0000, scbs29
wrote:
snip
I had a chance to run this one.

Pinnacle_Video_Driver_64bit.exe 11,878,776 bytes File Version 14.0.0.166

I loaded that into a 64 bit Windows VM (instead of WINE).
Double-clicked. Then using File Explorer, looked in %temp%.
In there, I could see Pinnacle_Video_Driver_64bit.msi sitting
there. Using 7ZIP, I could look inside. Te key file is
dvcvideo64.inf. The actual files to install are in dvc64.cab,
and they look similar to an EMPIA file set.

https://s13.postimg.org/mrlm561zb/64bitversion.gif

So that installer, at least on the surface, does look
suitable to install a driver for it. The dvcvideo64.inf
has 2304:021A for the hardware identifier.

And being an MSI, I would expect it to create an entry
in Programs and Features control panel.

Paul

I did get as far as extracting the files from the msi. I assume you
mean to install by right click on dvcvideo64.inf and select Install.
When I do this I get the message
The INF file you selected does not support this method of
installation. BTW I get the same message from any of the inf files.
Please let me know if I have got it wrong.


Are you looking for 32-bit or 64-bit drivers ?
As the Pinnacle_Video_Driver_64bit.exe is intended for
DVC100, while the 32-bit one doesn't have DVC100 (2304:021A).

You should be able to use the MSI from the 64-bit one.

Paul

On Fri, 25 Nov 2016 14:28:32 -0500, Paul
wrote:

scbs29 wrote:
On Thu, 24 Nov 2016 17:44:13 -0500, Paul
wrote:

scbs29 wrote:
On Thu, 24 Nov 2016 12:37:11 +0000, Java Jive
wrote:

On Thu, 24 Nov 2016 11:54:48 +0000, scbs29
wrote:
snip
I had a chance to run this one.

Pinnacle_Video_Driver_64bit.exe 11,878,776 bytes File Version 14.0.0.166

I loaded that into a 64 bit Windows VM (instead of WINE).
Double-clicked. Then using File Explorer, looked in %temp%.
In there, I could see Pinnacle_Video_Driver_64bit.msi sitting
there. Using 7ZIP, I could look inside. Te key file is
dvcvideo64.inf. The actual files to install are in dvc64.cab,
and they look similar to an EMPIA file set.

https://s13.postimg.org/mrlm561zb/64bitversion.gif

So that installer, at least on the surface, does look
suitable to install a driver for it. The dvcvideo64.inf
has 2304:021A for the hardware identifier.

And being an MSI, I would expect it to create an entry
in Programs and Features control panel.

Paul

I did get as far as extracting the files from the msi. I assume you
mean to install by right click on dvcvideo64.inf and select Install.
When I do this I get the message
The INF file you selected does not support this method of
installation. BTW I get the same message from any of the inf files.
Please let me know if I have got it wrong.


Are you looking for 32-bit or 64-bit drivers ?
As the Pinnacle_Video_Driver_64bit.exe is intended for
DVC100, while the 32-bit one doesn't have DVC100 (2304:021A).

You should be able to use the MSI from the 64-bit one.

Paul

It is the 64-bit ones that I want.
I have used the MSI from the 64-bit one with excatly the same result,
rollback.
Problem is that I cannot remember how I got the log file from an
earlier try. That is where I got the 1603 error from.
In the error.txt file produced by MSI Analyzer from the MSI file is an
entry
1603 The file [2][3] is being held in use{ by the following
process: Name: [4], ID: [5], Window Title: [6]}. Close that
application and retry. This may not be related to the error in the
64-bit log file though.

I am trying to get some output from the failed installation by
msiexec /... MSI file
but as yet all I get is the help message, no matter what arguments I
use. Still looking at this though.

Actual message in log file regarding this error is
DIFXAPP: INFO: RETURN: DriverPackageInstallW (0x3EE)
DIFXAPP: ERROR encountered while installing driver package C:\Program
Files (x86)\Common
Files\Pinnacle\Driver\Video\MarvinAVS\MarvinAVS64. inf
DIFXAPP: InstallDriverPackages failed with error 0x3EE
DIFXAPP: RETURN: InstallDriverPackages() 1006 (0x3EE)
CustomAction MsiInstallDrivers returned actual error code 1603 (note
this may not be 100% accurate if translation happened inside sandbox)

I must admit that I am starting to get rather disheartened, but am not
ready to give up yet.

--
remove fred before emailing

scbs29 wrote:
On Fri, 25 Nov 2016 14:28:32 -0500, Paul
wrote:

scbs29 wrote:
On Thu, 24 Nov 2016 17:44:13 -0500, Paul
wrote:

scbs29 wrote:
On Thu, 24 Nov 2016 12:37:11 +0000, Java Jive
wrote:

On Thu, 24 Nov 2016 11:54:48 +0000, scbs29
wrote:
snip
I had a chance to run this one.

Pinnacle_Video_Driver_64bit.exe 11,878,776 bytes File Version 14.0.0.166

I loaded that into a 64 bit Windows VM (instead of WINE).
Double-clicked. Then using File Explorer, looked in %temp%.
In there, I could see Pinnacle_Video_Driver_64bit.msi sitting
there. Using 7ZIP, I could look inside. Te key file is
dvcvideo64.inf. The actual files to install are in dvc64.cab,
and they look similar to an EMPIA file set.

https://s13.postimg.org/mrlm561zb/64bitversion.gif

So that installer, at least on the surface, does look
suitable to install a driver for it. The dvcvideo64.inf
has 2304:021A for the hardware identifier.

And being an MSI, I would expect it to create an entry
in Programs and Features control panel.

Paul
I did get as far as extracting the files from the msi. I assume you
mean to install by right click on dvcvideo64.inf and select Install.
When I do this I get the message
The INF file you selected does not support this method of
installation. BTW I get the same message from any of the inf files.
Please let me know if I have got it wrong.

Are you looking for 32-bit or 64-bit drivers ?
As the Pinnacle_Video_Driver_64bit.exe is intended for
DVC100, while the 32-bit one doesn't have DVC100 (2304:021A).

You should be able to use the MSI from the 64-bit one.

Paul

It is the 64-bit ones that I want.
I have used the MSI from the 64-bit one with excatly the same result,
rollback.
Problem is that I cannot remember how I got the log file from an
earlier try. That is where I got the 1603 error from.
In the error.txt file produced by MSI Analyzer from the MSI file is an
entry
1603 The file [2][3] is being held in use{ by the following
process: Name: [4], ID: [5], Window Title: [6]}. Close that
application and retry. This may not be related to the error in the
64-bit log file though.

I am trying to get some output from the failed installation by
msiexec /... MSI file
but as yet all I get is the help message, no matter what arguments I
use. Still looking at this though.

Actual message in log file regarding this error is
DIFXAPP: INFO: RETURN: DriverPackageInstallW (0x3EE)
DIFXAPP: ERROR encountered while installing driver package C:\Program
Files (x86)\Common
Files\Pinnacle\Driver\Video\MarvinAVS\MarvinAVS64. inf
DIFXAPP: InstallDriverPackages failed with error 0x3EE
DIFXAPP: RETURN: InstallDriverPackages() 1006 (0x3EE)
CustomAction MsiInstallDrivers returned actual error code 1603 (note
this may not be 100% accurate if translation happened inside sandbox)

I must admit that I am starting to get rather disheartened, but am not
ready to give up yet.


I don't have much to add.

The Corel page seems to think the MSI does it all.

https://support.corel.com/hc/en-us/a...ns-with-Studio

The MSI file probably uses msiexec. And it has
command line parameters.

http://stackoverflow.com/questions/7...n-msi-log-file

It should have both install and uninstall options.

Certain MSI errors are "place-holders" that are
used when the real error code cannot "percolate"
up the chain. As a result, they're a kind of
"something happened" error code, and are useless
for diagnosis.

You can sometimes look at the INF file and see
what it's up to. What services it sets up and so on.
In WinXP, you could use the setupapi.* stuff to
get some info. The files on later OSes still
exist, but may not have the same details shown.

Paul

On Sat, 19 Nov 2016 13:55:53 +0000, scbs29
wrote:

Hello all
I am trying to install a Pinnacle video driver for use wih my Dazzle
DVC100 capture 'gadget'.
I did use Pinnacle Studio 15 for this, but had problems so switched to
AVS Video Recorder which was more successful.
Since I did not want to use Studio 15 any more I uninstalled it.
Unfortunately it also uninstalled the drivers. I downloaded the driver
installation from Pinnacle and tried that. The installation proceeded
partway and then I was greeted with a message
The wizard was interrupted before Pinnacle Video Driver could be
compleely installed.
You system has not been modified. To complete installation at another
time, please run setup again.
I have rerun this 6 or 7 times, rebooting, different compatibility, as
administrator but it makes no difference.
I then decided to reinstall Studio 15, which installed ok but again
the video driver was not installed, but with no error message.
It seems that I just cannot install these video drivers.
I have found one or two suggestions but they make no difference.
Can anyone help ?
Packard Bell iXtreme X6620 UK
Intel Core 2 Quad Q8300 @ 2.5GHz
6 GBytes DDR2 RAM
NVIDIA GeForce GTX 750 Ti, 2Gb RAM
Windows 7 Pro, 64-bit
MoBo Packard Bell EG43M
Direct X 11

Just in case it helps for anyone to come to a conclusion as to what is
going wrong, I attach a zip of the log file produced with

msiexec /i pvd64.msi /L*v dazzle.log

pvd64.msi - copy of the msi file renamed with a shorter name


--
remove fred before emailing

On Sat, 26 Nov 2016 15:07:20 +0000, scbs29
wrote:

On Sat, 19 Nov 2016 13:55:53 +0000, scbs29
wrote:

Hello all
I am trying to install a Pinnacle video driver for use wih my Dazzle
DVC100 capture 'gadget'.
I did use Pinnacle Studio 15 for this, but had problems so switched to
AVS Video Recorder which was more successful.
Since I did not want to use Studio 15 any more I uninstalled it.
Unfortunately it also uninstalled the drivers. I downloaded the driver
installation from Pinnacle and tried that. The installation proceeded
partway and then I was greeted with a message
The wizard was interrupted before Pinnacle Video Driver could be
compleely installed.
You system has not been modified. To complete installation at another
time, please run setup again.
I have rerun this 6 or 7 times, rebooting, different compatibility, as
administrator but it makes no difference.
I then decided to reinstall Studio 15, which installed ok but again
the video driver was not installed, but with no error message.
It seems that I just cannot install these video drivers.
I have found one or two suggestions but they make no difference.
Can anyone help ?
Packard Bell iXtreme X6620 UK
Intel Core 2 Quad Q8300 @ 2.5GHz
6 GBytes DDR2 RAM
NVIDIA GeForce GTX 750 Ti, 2Gb RAM
Windows 7 Pro, 64-bit
MoBo Packard Bell EG43M
Direct X 11

Just in case it helps for anyone to come to a conclusion as to what is
going wrong, I attach a zip of the log file produced with

msiexec /i pvd64.msi /L*v dazzle.log

pvd64.msi - copy of the msi file renamed with a shorter name

Forgot maybe problems with attachments. I have put file dazzle.zip on
https://www.dropbox.com/s/541ujx0wu4...azzle.zip?dl=0
Please try that and let me know if there are any problems.

--
remove fred before emailing

scbs29 wrote:
On Sat, 26 Nov 2016 15:07:20 +0000, scbs29
wrote:

On Sat, 19 Nov 2016 13:55:53 +0000, scbs29
wrote:

Hello all
I am trying to install a Pinnacle video driver for use wih my Dazzle
DVC100 capture 'gadget'.
I did use Pinnacle Studio 15 for this, but had problems so switched to
AVS Video Recorder which was more successful.
Since I did not want to use Studio 15 any more I uninstalled it.
Unfortunately it also uninstalled the drivers. I downloaded the driver
installation from Pinnacle and tried that. The installation proceeded
partway and then I was greeted with a message
The wizard was interrupted before Pinnacle Video Driver could be
compleely installed.
You system has not been modified. To complete installation at another
time, please run setup again.
I have rerun this 6 or 7 times, rebooting, different compatibility, as
administrator but it makes no difference.
I then decided to reinstall Studio 15, which installed ok but again
the video driver was not installed, but with no error message.
It seems that I just cannot install these video drivers.
I have found one or two suggestions but they make no difference.
Can anyone help ?
Packard Bell iXtreme X6620 UK
Intel Core 2 Quad Q8300 @ 2.5GHz
6 GBytes DDR2 RAM
NVIDIA GeForce GTX 750 Ti, 2Gb RAM
Windows 7 Pro, 64-bit
MoBo Packard Bell EG43M
Direct X 11
Just in case it helps for anyone to come to a conclusion as to what is
going wrong, I attach a zip of the log file produced with

msiexec /i pvd64.msi /L*v dazzle.log

pvd64.msi - copy of the msi file renamed with a shorter name

Forgot maybe problems with attachments. I have put file dazzle.zip on
https://www.dropbox.com/s/541ujx0wu4...azzle.zip?dl=0
Please try that and let me know if there are any problems.


DIFXAPP: ENTER: InstallDriverPackages()
DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.1.
DIFXAPP: 'CustomActionData' property 'UI Level' is 5.
DIFXAPP: 'CustomActionData' property 'componentId' is {8AC3B98F-F706-465C-9583-AF3E21C9E77E}.
DIFXAPP: 'CustomActionData' property 'componentPath' is
C:\Program Files (x86)\Common Files\Pinnacle\Driver\Video\MarvinAVS\.
DIFXAPP: 'CustomActionData' property 'flags' is 0xE.
DIFXAPP: 'CustomActionData' property 'installState' is 2.
DIFXAPP: 'CustomActionData' property 'ProductName' is Pinnacle Video Driver.
DIFXAPP: 'CustomActionData' property 'ManufacturerName' is Pinnacle Systems.
DIFXAPP: INFO: opening HKEY_USERS 'S-1-5-21-339526536-3042199886-1387627938-1000
\Software\Microsoft\Windows\CurrentVersion\DIFxApp
\Components\{8AC3B98F-F706-465C-9583-AF3E21C9E77E}'
(User's SID: 'S-1-5-21-339526536-3042199886-1387627938-1000') ...
DIFXAPP: INFO: ENTER: DriverPackageInstallW
DIFXAPP: WARNINGRIVER_PACKAGE_LEGACY_MODE flag set but not supported
on Plug and Play driver on VISTA. Flag will be ignored.
DIFXAPP: INFO: Installing INF file
'C:\Program Files (x86)\Common Files\Pinnacle\Driver\Video\MarvinAVS\MarvinAVS64. inf' (Plug and Play).
DIFXAPP: INFO: Could not open file
C:\Windows\System32\DriverStore\FileRepository\mar vinavs64.inf_amd64_neutral_233b261c4fe7c577\marvin avs64.inf. (Error code 0x3: The system cannot find the path specified.)
DIFXAPP: ERROR: PnP Install failed. (Error code 0x3EE: The volume for a file has been externally altered so that the opened file is no longer valid.)

So the error is not 1603, it's 1006 (0x3EE).

Do you have an AV running ?

The log is not specific, that it actually created
that amd64_neutral file. I was thinking maybe it had
spotted an old one. But maybe that's not the case.

If I was there, I would:

1) Temporarily disable AV. Some have a setting where they
will be disabled for 10-15 minutes while you work.
2) Use sysinternals.com Process Monitor, don't set any
filters, just let it log.
3) Run the install.
4) Go to the File menu in Process Monitor, and untick the
capture tick mark. That stops the trace. Look for
access to MarvinAVS64.inf, see if there was a
CreateFile request for marvinavs64.inf_amd64_neutral_233b261c4fe7c577
folder and so on. To verify the installer really is
writing a new copy there for some reason. Because
when the rollback happens, all sorts of stuff could
be removed before you can look at it.

When msiexec runs, it should auto-elevate and have
a UAC prompt, to give permission to run as Administrator.
I don't expect "Run as Administrator" would really help.

HTH,
Paul

On Sat, 26 Nov 2016 18:33:53 -0500, Paul
wrote:

scbs29 wrote:
On Sat, 26 Nov 2016 15:07:20 +0000, scbs29
wrote:

On Sat, 19 Nov 2016 13:55:53 +0000, scbs29
wrote:

Hello all
I am trying to install a Pinnacle video driver for use wih my Dazzle
DVC100 capture 'gadget'.
I did use Pinnacle Studio 15 for this, but had problems so switched to
AVS Video Recorder which was more successful.
Since I did not want to use Studio 15 any more I uninstalled it.
Unfortunately it also uninstalled the drivers. I downloaded the driver
installation from Pinnacle and tried that. The installation proceeded
partway and then I was greeted with a message
The wizard was interrupted before Pinnacle Video Driver could be
compleely installed.
You system has not been modified. To complete installation at another
time, please run setup again.
I have rerun this 6 or 7 times, rebooting, different compatibility, as
administrator but it makes no difference.
I then decided to reinstall Studio 15, which installed ok but again
the video driver was not installed, but with no error message.
It seems that I just cannot install these video drivers.
I have found one or two suggestions but they make no difference.
Can anyone help ?
Packard Bell iXtreme X6620 UK
Intel Core 2 Quad Q8300 @ 2.5GHz
6 GBytes DDR2 RAM
NVIDIA GeForce GTX 750 Ti, 2Gb RAM
Windows 7 Pro, 64-bit
MoBo Packard Bell EG43M
Direct X 11
Just in case it helps for anyone to come to a conclusion as to what is
going wrong, I attach a zip of the log file produced with

msiexec /i pvd64.msi /L*v dazzle.log

pvd64.msi - copy of the msi file renamed with a shorter name

Forgot maybe problems with attachments. I have put file dazzle.zip on
https://www.dropbox.com/s/541ujx0wu4...azzle.zip?dl=0
Please try that and let me know if there are any problems.


DIFXAPP: ENTER: InstallDriverPackages()
DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.1.
DIFXAPP: 'CustomActionData' property 'UI Level' is 5.
DIFXAPP: 'CustomActionData' property 'componentId' is {8AC3B98F-F706-465C-9583-AF3E21C9E77E}.
DIFXAPP: 'CustomActionData' property 'componentPath' is
C:\Program Files (x86)\Common Files\Pinnacle\Driver\Video\MarvinAVS\.
DIFXAPP: 'CustomActionData' property 'flags' is 0xE.
DIFXAPP: 'CustomActionData' property 'installState' is 2.
DIFXAPP: 'CustomActionData' property 'ProductName' is Pinnacle Video Driver.
DIFXAPP: 'CustomActionData' property 'ManufacturerName' is Pinnacle Systems.
DIFXAPP: INFO: opening HKEY_USERS 'S-1-5-21-339526536-3042199886-1387627938-1000
\Software\Microsoft\Windows\CurrentVersion\DIFxApp
\Components\{8AC3B98F-F706-465C-9583-AF3E21C9E77E}'
(User's SID: 'S-1-5-21-339526536-3042199886-1387627938-1000') ...
DIFXAPP: INFO: ENTER: DriverPackageInstallW
DIFXAPP: WARNINGRIVER_PACKAGE_LEGACY_MODE flag set but not supported
on Plug and Play driver on VISTA. Flag will be ignored.
DIFXAPP: INFO: Installing INF file
'C:\Program Files (x86)\Common Files\Pinnacle\Driver\Video\MarvinAVS\MarvinAVS64. inf' (Plug and Play).
DIFXAPP: INFO: Could not open file
C:\Windows\System32\DriverStore\FileRepository\mar vinavs64.inf_amd64_neutral_233b261c4fe7c577\marvin avs64.inf. (Error code 0x3: The system cannot find the path specified.)
DIFXAPP: ERROR: PnP Install failed. (Error code 0x3EE: The volume for a file has been externally altered so that the opened file is no longer valid.)

So the error is not 1603, it's 1006 (0x3EE).

Do you have an AV running ?

The log is not specific, that it actually created
that amd64_neutral file. I was thinking maybe it had
spotted an old one. But maybe that's not the case.

If I was there, I would:

1) Temporarily disable AV. Some have a setting where they
will be disabled for 10-15 minutes while you work.
2) Use sysinternals.com Process Monitor, don't set any
filters, just let it log.
3) Run the install.
4) Go to the File menu in Process Monitor, and untick the
capture tick mark. That stops the trace. Look for
access to MarvinAVS64.inf, see if there was a
CreateFile request for marvinavs64.inf_amd64_neutral_233b261c4fe7c577
folder and so on. To verify the installer really is
writing a new copy there for some reason. Because
when the rollback happens, all sorts of stuff could
be removed before you can look at it.

When msiexec runs, it should auto-elevate and have
a UAC prompt, to give permission to run as Administrator.
I don't expect "Run as Administrator" would really help.

HTH,
Paul

Thanks for the reply.
I did an install under Process Monitor for both the full Pinnacle
install and just the drivers.
There were plentry of entries of the sort
"18:49:29.9781161","msiexec.exe","6812","CreateFil e",
"C:\Program Files (x86)\Common
Files\Pinnacle\Driver\Video\Bender64\PCLEBend64.in f","PATH NOT
FOUND","Desired Access: Read Attributes, Disposition: Open, Options:
Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete,
AllocationSize: n/a, Impersonating: stuart-PC\stuart"

For whatever reason the full Pinnacle install did not create
C:\Program Files (x86)\Common Files\Pinnacle and thus none of the
folders the install was expecting.

I have put a file pinnacle.zip on
https://www.dropbox.com/s/lptp0vscet...nacle.zip?dl=0
which contains csv files of the Process Monitor output for the full
Pinnacle install and the install ofonly the drivers filtered for path
containing Pinnacle and result not SUCCESS.
I don't know if it will help or even if it is readable.


--
remove fred before emailing

scbs29 wrote:
On Sat, 26 Nov 2016 18:33:53 -0500, Paul
wrote:

scbs29 wrote:
On Sat, 26 Nov 2016 15:07:20 +0000, scbs29
wrote:

On Sat, 19 Nov 2016 13:55:53 +0000, scbs29
wrote:

Hello all
I am trying to install a Pinnacle video driver for use wih my Dazzle
DVC100 capture 'gadget'.
I did use Pinnacle Studio 15 for this, but had problems so switched to
AVS Video Recorder which was more successful.
Since I did not want to use Studio 15 any more I uninstalled it.
Unfortunately it also uninstalled the drivers. I downloaded the driver
installation from Pinnacle and tried that. The installation proceeded
partway and then I was greeted with a message
The wizard was interrupted before Pinnacle Video Driver could be
compleely installed.
You system has not been modified. To complete installation at another
time, please run setup again.
I have rerun this 6 or 7 times, rebooting, different compatibility, as
administrator but it makes no difference.
I then decided to reinstall Studio 15, which installed ok but again
the video driver was not installed, but with no error message.
It seems that I just cannot install these video drivers.
I have found one or two suggestions but they make no difference.
Can anyone help ?
Packard Bell iXtreme X6620 UK
Intel Core 2 Quad Q8300 @ 2.5GHz
6 GBytes DDR2 RAM
NVIDIA GeForce GTX 750 Ti, 2Gb RAM
Windows 7 Pro, 64-bit
MoBo Packard Bell EG43M
Direct X 11
Just in case it helps for anyone to come to a conclusion as to what is
going wrong, I attach a zip of the log file produced with

msiexec /i pvd64.msi /L*v dazzle.log

pvd64.msi - copy of the msi file renamed with a shorter name
Forgot maybe problems with attachments. I have put file dazzle.zip on
https://www.dropbox.com/s/541ujx0wu4...azzle.zip?dl=0
Please try that and let me know if there are any problems.

DIFXAPP: ENTER: InstallDriverPackages()
DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.1.
DIFXAPP: 'CustomActionData' property 'UI Level' is 5.
DIFXAPP: 'CustomActionData' property 'componentId' is {8AC3B98F-F706-465C-9583-AF3E21C9E77E}.
DIFXAPP: 'CustomActionData' property 'componentPath' is
C:\Program Files (x86)\Common Files\Pinnacle\Driver\Video\MarvinAVS\.
DIFXAPP: 'CustomActionData' property 'flags' is 0xE.
DIFXAPP: 'CustomActionData' property 'installState' is 2.
DIFXAPP: 'CustomActionData' property 'ProductName' is Pinnacle Video Driver.
DIFXAPP: 'CustomActionData' property 'ManufacturerName' is Pinnacle Systems.
DIFXAPP: INFO: opening HKEY_USERS 'S-1-5-21-339526536-3042199886-1387627938-1000
\Software\Microsoft\Windows\CurrentVersion\DIFxApp
\Components\{8AC3B98F-F706-465C-9583-AF3E21C9E77E}'
(User's SID: 'S-1-5-21-339526536-3042199886-1387627938-1000') ...
DIFXAPP: INFO: ENTER: DriverPackageInstallW
DIFXAPP: WARNINGRIVER_PACKAGE_LEGACY_MODE flag set but not supported
on Plug and Play driver on VISTA. Flag will be ignored.
DIFXAPP: INFO: Installing INF file
'C:\Program Files (x86)\Common Files\Pinnacle\Driver\Video\MarvinAVS\MarvinAVS64. inf' (Plug and Play).
DIFXAPP: INFO: Could not open file
C:\Windows\System32\DriverStore\FileRepository\mar vinavs64.inf_amd64_neutral_233b261c4fe7c577\marvin avs64.inf. (Error code 0x3: The system cannot find the path specified.)
DIFXAPP: ERROR: PnP Install failed. (Error code 0x3EE: The volume for a file has been externally altered so that the opened file is no longer valid.)

So the error is not 1603, it's 1006 (0x3EE).

Do you have an AV running ?

The log is not specific, that it actually created
that amd64_neutral file. I was thinking maybe it had
spotted an old one. But maybe that's not the case.

If I was there, I would:

1) Temporarily disable AV. Some have a setting where they
will be disabled for 10-15 minutes while you work.
2) Use sysinternals.com Process Monitor, don't set any
filters, just let it log.
3) Run the install.
4) Go to the File menu in Process Monitor, and untick the
capture tick mark. That stops the trace. Look for
access to MarvinAVS64.inf, see if there was a
CreateFile request for marvinavs64.inf_amd64_neutral_233b261c4fe7c577
folder and so on. To verify the installer really is
writing a new copy there for some reason. Because
when the rollback happens, all sorts of stuff could
be removed before you can look at it.

When msiexec runs, it should auto-elevate and have
a UAC prompt, to give permission to run as Administrator.
I don't expect "Run as Administrator" would really help.

HTH,
Paul

Thanks for the reply.
I did an install under Process Monitor for both the full Pinnacle
install and just the drivers.
There were plentry of entries of the sort
"18:49:29.9781161","msiexec.exe","6812","CreateFil e",
"C:\Program Files (x86)\Common
Files\Pinnacle\Driver\Video\Bender64\PCLEBend64.in f","PATH NOT
FOUND","Desired Access: Read Attributes, Disposition: Open, Options:
Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete,
AllocationSize: n/a, Impersonating: stuart-PC\stuart"

For whatever reason the full Pinnacle install did not create
C:\Program Files (x86)\Common Files\Pinnacle and thus none of the
folders the install was expecting.

I have put a file pinnacle.zip on
https://www.dropbox.com/s/lptp0vscet...nacle.zip?dl=0
which contains csv files of the Process Monitor output for the full
Pinnacle install and the install ofonly the drivers filtered for path
containing Pinnacle and result not SUCCESS.
I don't know if it will help or even if it is readable.



The best leverage comes when you work on it
at your end, because you can see interesting
stuff faster than I can.

The MSIEXEC should be using the TrustedInstaller
token when installing. TrustedInstaller is not
a full account - id does not have a home directory.
But it is an item in SID-world. And TrustedInstaller
"owns" C:\Program Files. The whole process should
have no problem putting files there if it wants.

When you see attempts to access stuff like that,
it could be "for real" or could be "bogus". Say a
developer is lazy, and leaves some old info in the
MSI manifest. MSI manifests are very complicated.
It's likely easy to screw them up. Maybe the behavior
seen is crucial to making it work. Or the behavior
is bogus, and if you could "get past" the error, it
would have worked.

Unfortunately, you already tried using the INF
directly, and it told you you cannot install it
that way. And I don't understand why that is, well
enough to hand-craft a hack for it.

I'll look at your ZIP, but it's unlikely I'll
be able to see a "theme" as to why it is fouling up.
I'm not aware of a "secret decoder ring" for MSI stuff.

MSIexec is great when it works. And not so great
when it doesn't.

Paul

scbs29 wrote:


Thanks for the reply.
I did an install under Process Monitor for both the full Pinnacle
install and just the drivers.
There were plentry of entries of the sort
"18:49:29.9781161","msiexec.exe","6812","CreateFil e",
"C:\Program Files (x86)\Common
Files\Pinnacle\Driver\Video\Bender64\PCLEBend64.in f","PATH NOT
FOUND","Desired Access: Read Attributes, Disposition: Open, Options:
Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete,
AllocationSize: n/a, Impersonating: stuart-PC\stuart"

For whatever reason the full Pinnacle install did not create
C:\Program Files (x86)\Common Files\Pinnacle and thus none of the
folders the install was expecting.

I have put a file pinnacle.zip on
https://www.dropbox.com/s/lptp0vscet...nacle.zip?dl=0
which contains csv files of the Process Monitor output for the full
Pinnacle install and the install ofonly the drivers filtered for path
containing Pinnacle and result not SUCCESS.
I don't know if it will help or even if it is readable.

After looking at the files, I don't see
anything that smacks of "success". The drivers
log looks like a giant "fail whale".

Does the area on the disk in question now exist ?

Or is there no evidence that anything worked ?

If I knew of a way to run msiexec in a compatibility
mode, I'd have suggested that by now...

Paul

On Mon, 28 Nov 2016 23:59:38 -0500, Paul
wrote:

scbs29 wrote:


Thanks for the reply.
I did an install under Process Monitor for both the full Pinnacle
install and just the drivers.
There were plentry of entries of the sort
"18:49:29.9781161","msiexec.exe","6812","CreateFil e",
"C:\Program Files (x86)\Common
Files\Pinnacle\Driver\Video\Bender64\PCLEBend64.in f","PATH NOT
FOUND","Desired Access: Read Attributes, Disposition: Open, Options:
Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete,
AllocationSize: n/a, Impersonating: stuart-PC\stuart"

For whatever reason the full Pinnacle install did not create
C:\Program Files (x86)\Common Files\Pinnacle and thus none of the
folders the install was expecting.

I have put a file pinnacle.zip on
https://www.dropbox.com/s/lptp0vscet...nacle.zip?dl=0
which contains csv files of the Process Monitor output for the full
Pinnacle install and the install ofonly the drivers filtered for path
containing Pinnacle and result not SUCCESS.
I don't know if it will help or even if it is readable.

After looking at the files, I don't see
anything that smacks of "success". The drivers
log looks like a giant "fail whale".

Does the area on the disk in question now exist ?

Or is there no evidence that anything worked ?

If I knew of a way to run msiexec in a compatibility
mode, I'd have suggested that by now...

Paul

Many thanks for all of the help and advice, but I am going to give up
on this and get a different device. I think that I have been messing
about for too long.

--
remove fred before emailing