Cannot install driver

On Sun, 20 Nov 2016 19:02:55 +0000, scbs29
wrote:

On Sun, 20 Nov 2016 12:23:04 -0500, burfordTjustice
wrote:

On Sun, 20 Nov 2016 15:09:40 +0000
scbs29 wrote:

On Sun, 20 Nov 2016 10:00:40 -0500, burfordTjustice
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


Call 1 (888) 518-3752 they will help

Since I live in the UK this is not really a viable proposition.
Also, who will this call ?


You can not call the Yanks from your area?
How very odd.

Phone the USA ? You gonna pay my bill :-)
Again, who will this call ? Cos if it is Corel Support (Corel taken
Pinnacle over) they are completely useless. Already tried them and was
told We dont support Studio 15, buy the new version.

Which BTW they tell me does not support DVC100 anyway.

--
remove fred before emailing

snip

Following on, I have just looked at the registry through Regedit.
There were multiple entries for DVC100 of the form


snip

There are several ControlSets. There is CurrentControlSet
which is, well, current.

And another feature to know about is "Last Known Good".
There is some relationship between these control sets
and that feature.

In addition, drivers have a rollback feature, where you
can roll back to the previous driver. The depth of the
rollback is only one level, so there is only the
current driver and the previous driver to rely on.
Before you head out on a "delete at all costs"
mission, consider there is a design to how it works.

*******

Try Device Manager and enable Hidden Devices. And have
a look in there. I think my BT878 drivers were hiding
in there. Drivers that didn't actually do anything.
When I would use DScaler, it seemed to have its own
drivers applied at runtime. There were several potential
drivers - a set belonging to some DVR package (which I'd
installed), the DScaler ones (leave no trace), and the
Hauppauge WinTV drivers (used on some installs and
not others). I don't recollect any huge collisions
because I didn't make a concerted effort to load/run
them all at the same time.

So have a look in Hidden Devices and see what is there.
And don't go deleting everything in there.

http://www.makeuseof.com/tag/how-to-...-from-windows/

cmd.exe (Run as Administrator...)

set devmgr_show_nonpresent_devices=1
devmgmt.msc

(Then, in Device Manager, View : Show hidden devices)

Normally you'd want to use Programs and Features
to clean up stuff. But that's another option.

The last DVC100 driver here, might be a Vista era driver
being used in Windows 7. Too bad they're InstallShield,
as otherwise I would have tried to read the INF files.

http://cdn.pinnaclesys.com/SupportFi...readmeHW10.htm

The OEM22.inf and OEM21.inf referred to in the log,
Windows "anonymizes" INF names at install time. The INF
files have their original file name, recorded at the
top of the text. So if the user installed "dog.inf" for
the audio section of DVC100, and "cat.inf" for
the video section of DVC100, maybe the files become
"oem21.inf" and "oem22.inf". On the assumption that
the system already had oem20.inf before the start
of the install process.

Some hardware, the user is expected to run the installer
CD, before plugging in the hardware. The device may "bind"
to some previous driver if it is plugged in when the driver
CD is used. Even the installer GUI itself, may say something
like "now, plug in the device" so you don't screw it up.

HTH,
Paul

Thanks for the reply and the advice. However,
In addition, drivers have a rollback feature, where you
can roll back to the previous driver. The depth of the
rollback is only one level, so there is only the
current driver and the previous driver to rely on.
Cannot roll back because there are no DVC100 drivers on the system.

Try Device Manager and enable Hidden Devices. And have
a look in there
I did this and there are no hidden drivers or devices.

The last DVC100 driver here, might be a Vista era driver
being used in Windows 7.
This is the one that I am trying to install. The page says that it is
also for Windows 7 64-bit.

Some hardware, the user is expected to run the installer
CD, before plugging in the hardware. The device may "bind"
to some previous driver if it is plugged in when the driver
CD is used. Even the installer GUI itself, may say something
like "now, plug in the device" so you don't screw it up.
True, but the installer does not even get that far, and the DVC100 is
not plugged in.

Could these multiple DVC100 registry entries be a result of multiple
tries to install the drivers after following each advice that I was
given ?
Could it be that the rollback I am told about does not actually
'clean' the registry of the DVC200 entries ?

--
remove fred before emailing

On Tue, 22 Nov 2016 10:29:36 +0000, scbs29
wrote:

snip

Following on, I have just looked at the registry through Regedit.
There were multiple entries for DVC100 of the form


snip

There are several ControlSets. There is CurrentControlSet
which is, well, current.

snip
set devmgr_show_nonpresent_devices=1
devmgmt.msc

(Then, in Device Manager, View : Show hidden devices)

Normally you'd want to use Programs and Features
to clean up stuff. But that's another option.

The last DVC100 driver here, might be a Vista era driver
being used in Windows 7. Too bad they're InstallShield,
as otherwise I would have tried to read the INF files.

http://cdn.pinnaclesys.com/SupportFi...readmeHW10.htm

The OEM22.inf and OEM21.inf referred to in the log,
snip

Could these multiple DVC100 registry entries be a result of multiple
tries to install the drivers after following each advice that I was
given ?
Could it be that the rollback I am told about does not actually
'clean' the registry of the DVC200 entries ?

I could always try backing up the registry files, demoving all dvc100
references from registry and then try installing.
If it fall over I could then restore the registry files from those
backed up.
Can anyone offer an opinion on this ?

--
remove fred before emailing

scbs29 wrote:


I could always try backing up the registry files, demoving all dvc100
references from registry and then try installing.
If it fall over I could then restore the registry files from those
backed up.
Can anyone offer an opinion on this ?

The hackery won't help :-(

I took a look at PCLEUSB2x32.exe using WINE in Linux.

http://cdn.pinnaclesys.com/SupportFi...readmeHW10.htm

It turns out, there is a file

dvcvideo.inf1

It references 2304:021A for a VID and PID. (DVC100,USB\VID_2304&PID_021A&MI_00)
It wants these three files. The files are missing.

emFilter.sys
emScan.sys
emDevice.sys

So what they did, is removed the DVC100 files. Then, they
added the number "1" to the end of ".inf" in effect
commenting out the INF file. The dvcvideo.inf1 file
would not be recognized as offering a driver. I removed
the "1" and popped it into my text editor for a look.

I also see a reference to "VFW" in there, Video For Windows,
which predates WDM and suggests the file might have been
pre-Win2K or something.

You're going to need a different installer.

The web pages warns "and a compatible version of Studio".
So it looks like the driver might have to match the
version of Studio to at least get Studio to work.
The thing should really be standards compliant, once
the driver is finished with it. Either it's a WDM device,
whatever follow WDM, or it's a VFW device (really old).

So the first question then is, what version
of Studio do you have ?

If I use archive.org, the drivers here start at Studio 10.

https://web.archive.org/web/20070702...readmeHW10.htm

Nope. Same problem.

So I tried some EMPIA drivers, the company that
made the USB chip.

( https://web.archive.org/web/20140120.../wp/download-2 )

https://web.archive.org/web/20140120...020412_UAC.rar

The difference between them is, the EMPIA ones
use EMPIA VID & PID. If they aren't edited by
hand (to correct the EMVIDEO.INF file), they
won't install. The Pinnacle design would use
a config prom for the EMPIA chip, in an effort
to change the PNP to 2304:021A.

This shows some of the materials as seen in WINE.

https://s14.postimg.org/4wcl3vclt/newandold.gif

Some capture devices, the manufacturer is clever
and leaves the default EMPIA identifier. In the
case of Pinnacle, they stamp them electronically
with the Pinnacle identifier.

In this case, if I was doing it, I would install
the WDM_Media_D020412_UAC.exe installshield package,
then have a look in C:\Program Files\USB_video_device\Driver\Driver64
and edit the EMPIA.INF file. I would try changing
the PNP identifier, save the file, right-click the
file and select "Install" from the menu.

You can see this is a long shot.

There might still be a full package of software
*somewhere*, that matches multiple EMPIA designs.

What's amazing, is that EMPIA is still in business.
Many companies like this, retreat from their old markets
and try something else, in order to survive.

Take set top boxes. When Digital TV arrived, about
20 companies made product. Within two years, all
but two exited the market, because no one could
sell enough chips to survive.

Even big companies have folded. TI owns NatSemi now,
as an example. And just in the news, QualComm
bought NXP (which was originally Philips).
Pretty weird. And after these kinds of
purchases, sometimes the driver page disappears.
That's the scary part for consumers, is what
happens to their support.

You're going to have to continue shoveling through
Google results, to find just the right package
to work with 2304:021A in Win7.

Paul

On Tue, 22 Nov 2016 11:03:28 -0500, Paul
wrote:

scbs29 wrote:


I could always try backing up the registry files, demoving all dvc100
references from registry and then try installing.
If it fall over I could then restore the registry files from those
backed up.
Can anyone offer an opinion on this ?
snip
as an example. And just in the news, QualComm
bought NXP (which was originally Philips).
Pretty weird. And after these kinds of
purchases, sometimes the driver page disappears.
That's the scary part for consumers, is what
happens to their support.

You're going to have to continue shoveling through
Google results, to find just the right package
to work with 2304:021A in Win7.

Paul

Thanks yet again for your help and advice.
I am going to have to study this and try to sort it out.
What I still do not understand, though, is that when I installed
Pinnacle Studio 15 for the first time (On Windows 7 Pro 64-bit) it
installed, installed dvc100 drivers with no problems, but will not
install them now.


--
remove fred before emailing

On Tue, 22 Nov 2016 17:12:11 +0000, scbs29
wrote:

On Tue, 22 Nov 2016 11:03:28 -0500, Paul
wrote:

scbs29 wrote:


I could always try backing up the registry files, demoving all dvc100
references from registry and then try installing.
If it fall over I could then restore the registry files from those
backed up.
Can anyone offer an opinion on this ?
snip
as an example. And just in the news, QualComm
bought NXP (which was originally Philips).
Pretty weird. And after these kinds of
purchases, sometimes the driver page disappears.
That's the scary part for consumers, is what
happens to their support.

You're going to have to continue shoveling through
Google results, to find just the right package
to work with 2304:021A in Win7.

Paul

Thanks yet again for your help and advice.
I am going to have to study this and try to sort it out.
What I still do not understand, though, is that when I installed
Pinnacle Studio 15 for the first time (On Windows 7 Pro 64-bit) it
installed, installed dvc100 drivers with no problems, but will not
install them now.

Also, the driver installations that I am trying to use are the same
that installed the drivers in the first place (on the Studio 15 CD),
and I have also tried official installers from Pinnacle website. If it
is not the registry entries that are causing the problem, then what is
?
Surely if the installers worked before they it is extremely unlikely
that they can be at fault now ?

--
remove fred before emailing

On Tue, 22 Nov 2016 18:38:23 +0000, scbs29
wrote:

Thanks yet again for your help and advice.
I am going to have to study this and try to sort it out.
What I still do not understand, though, is that when I installed
Pinnacle Studio 15 for the first time (On Windows 7 Pro 64-bit) it
installed, installed dvc100 drivers with no problems, but will not
install them now.

Also, the driver installations that I am trying to use are the same
that installed the drivers in the first place (on the Studio 15 CD),
and I have also tried official installers from Pinnacle website. If it
is not the registry entries that are causing the problem, then what is
?
Surely if the installers worked before they it is extremely unlikely
that they can be at fault now ?

I make absolutely no guarantees at all, but you could try the
following:
1 In Programs and Features, and Device Manager, uninstall
everything related to the issue, that is the software, the
drivers, and the devices.
2 Search the contents of files matching %WinDir%\inf\oem*.*
for strings relating to the hardware, and delete not just any
matching inf(s) but also the corresponding *.pnf file(s),
that is: supposing oem5.inf contains strings relating to the
problem, then delete oem5.inf and oem5.pnf. Note that there
may be more than one pair of such files.
3 Reboot
4 Try the installation again.

--
================================================== ======
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 Tue, 22 Nov 2016 19:23:01 +0000, Java Jive
wrote:

On Tue, 22 Nov 2016 18:38:23 +0000, scbs29
wrote:

Thanks yet again for your help and advice.
I am going to have to study this and try to sort it out.
What I still do not understand, though, is that when I installed
Pinnacle Studio 15 for the first time (On Windows 7 Pro 64-bit) it
installed, installed dvc100 drivers with no problems, but will not
install them now.

Also, the driver installations that I am trying to use are the same
that installed the drivers in the first place (on the Studio 15 CD),
and I have also tried official installers from Pinnacle website. If it
is not the registry entries that are causing the problem, then what is
?
Surely if the installers worked before they it is extremely unlikely
that they can be at fault now ?

I make absolutely no guarantees at all, but you could try the
following:
1 In Programs and Features, and Device Manager, uninstall
everything related to the issue, that is the software, the
drivers, and the devices.
2 Search the contents of files matching %WinDir%\inf\oem*.*
for strings relating to the hardware, and delete not just any
matching inf(s) but also the corresponding *.pnf file(s),
that is: supposing oem5.inf contains strings relating to the
problem, then delete oem5.inf and oem5.pnf. Note that there
may be more than one pair of such files.
3 Reboot
4 Try the installation again.

Thanks for the advice, but there are no .inf files relating to DVC100.

--
remove fred before emailing

scbs29 wrote:
On Tue, 22 Nov 2016 19:23:01 +0000, Java Jive
wrote:

On Tue, 22 Nov 2016 18:38:23 +0000, scbs29
wrote:
Thanks yet again for your help and advice.
I am going to have to study this and try to sort it out.
What I still do not understand, though, is that when I installed
Pinnacle Studio 15 for the first time (On Windows 7 Pro 64-bit) it
installed, installed dvc100 drivers with no problems, but will not
install them now.
Also, the driver installations that I am trying to use are the same
that installed the drivers in the first place (on the Studio 15 CD),
and I have also tried official installers from Pinnacle website. If it
is not the registry entries that are causing the problem, then what is
?
Surely if the installers worked before they it is extremely unlikely
that they can be at fault now ?
I make absolutely no guarantees at all, but you could try the
following:
1 In Programs and Features, and Device Manager, uninstall
everything related to the issue, that is the software, the
drivers, and the devices.
2 Search the contents of files matching %WinDir%\inf\oem*.*
for strings relating to the hardware, and delete not just any
matching inf(s) but also the corresponding *.pnf file(s),
that is: supposing oem5.inf contains strings relating to the
problem, then delete oem5.inf and oem5.pnf. Note that there
may be more than one pair of such files.
3 Reboot
4 Try the installation again.

Thanks for the advice, but there are no .inf files relating to DVC100.


You saw in my postimage, there was the path

C:\program files\usb_video_device\Driver\Driver64

and that appeared to be a staging folder when I was
playing with it.

I don't know if I can get your Studio 15 as a download
or not. But, I would expect the same philosophy, the
usage of a staging folder and an old-fashioned install.
I would expect to find "dvcvideo.inf" and "dvcaudio.inf"
in there, but they don't absolutely need to have those
names. They could call it "dog.inf" and "cat.inf"
if they want. You notice the EMPIA driver uses
"emvideo.inf" for their video install section,
even though it involves the same USB chip.

Using Agent Ransack, you could even do a "text search"
withing the Windows INF folder. That's the one with
oem5.inf, oem6.inf, and so on. Each time a driver is
installed, the INF (and PNF) files are placed in the
central INF folder, and the file name is changed to OEMxx.
And inside one of those files, should be the VID and PID
of the Pinnacle DVC100 (2403:021A).

Once you locate the file, using a text editor, you look
at the top, and it should say that the real name of the
file is "dvcvideo.inf" and so on. You can do some detective
work to determine what the old INF installation was.

Paul

On Tue, 22 Nov 2016 18:18:51 -0500, Paul
wrote:

scbs29 wrote:
On Tue, 22 Nov 2016 19:23:01 +0000, Java Jive
wrote:

On Tue, 22 Nov 2016 18:38:23 +0000, scbs29
wrote:
Thanks yet again for your help and advice.
I am going to have to study this and try to sort it out.
What I still do not understand, though, is that when I installed
Pinnacle Studio 15 for the first time (On Windows 7 Pro 64-bit) it
installed, installed dvc100 drivers with no problems, but will not
install them now.
Also, the driver installations that I am trying to use are the same
that installed the drivers in the first place (on the Studio 15 CD),
and I have also tried official installers from Pinnacle website. If it
is not the registry entries that are causing the problem, then what is
?
Surely if the installers worked before they it is extremely unlikely
that they can be at fault now ?
I make absolutely no guarantees at all, but you could try the
following:
1 In Programs and Features, and Device Manager, uninstall
everything related to the issue, that is the software, the
drivers, and the devices.
2 Search the contents of files matching %WinDir%\inf\oem*.*
for strings relating to the hardware, and delete not just any
matching inf(s) but also the corresponding *.pnf file(s),
that is: supposing oem5.inf contains strings relating to the
problem, then delete oem5.inf and oem5.pnf. Note that there
may be more than one pair of such files.
3 Reboot
4 Try the installation again.

Thanks for the advice, but there are no .inf files relating to DVC100.


You saw in my postimage, there was the path

C:\program files\usb_video_device\Driver\Driver64

and that appeared to be a staging folder when I was
playing with it.

I don't know if I can get your Studio 15 as a download
or not. But, I would expect the same philosophy, the
usage of a staging folder and an old-fashioned install.
I would expect to find "dvcvideo.inf" and "dvcaudio.inf"
in there, but they don't absolutely need to have those
names. They could call it "dog.inf" and "cat.inf"
if they want. You notice the EMPIA driver uses
"emvideo.inf" for their video install section,
even though it involves the same USB chip.

Using Agent Ransack, you could even do a "text search"
withing the Windows INF folder. That's the one with
oem5.inf, oem6.inf, and so on. Each time a driver is
installed, the INF (and PNF) files are placed in the
central INF folder, and the file name is changed to OEMxx.
And inside one of those files, should be the VID and PID
of the Pinnacle DVC100 (2403:021A).

Once you locate the file, using a text editor, you look
at the top, and it should say that the real name of the
file is "dvcvideo.inf" and so on. You can do some detective
work to determine what the old INF installation was.

Paul

Thanks again for your reply.
I had opened each oem*.inf file in notepad looking for dvc100.
I did as you suggested and did a search in .inf. The only mention of
dvc100 is in a fle setupapi.dev.log dated 18 Nov, last modified 22
Nov.
There are 26 mentions of dvc100, of the form
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 11:44:27.046
ndv: Searching Windows Update for drivers... 11:44:27.421
ndv: Acquired WU search serialization mutex. 11:44:27.459
ndv: Received request to cancel Windows Update search.
ndv: About to release WU search serialization mutex. 11:44:39.133
ndv: Windows Update driver search cancelled. 11:44:39.526
ndv: Waiting for previous device install to complete.
11:44:39.701
ndv: {Core Device Install} 11:44:53.824
! ndv: Installing NULL driver!
dvi: Set selected driver complete.
dvi: {DIF_ALLOW_INSTALL} 11:44:53.942
dvi: No class installer for 'DVC100'
dvi: Default installer: Enter 11:44:53.950
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 11:44:53.979
dvi: {DIF_INSTALLDEVICE} 11:44:54.015
dvi: No class installer for 'DVC100'
or
[Device Install (DiShowUpdateDevice) -
USB\VID_2304&PID_021A&MI_00\6&3B750AF&1&0000]
Section start 2016/11/22 19:46:20.651
cmd: "C:\Windows\system32\mmc.exe"
C:\Windows\system32\devmgmt.msc
dvi: {DIF_UPDATEDRIVER_UI} 19:46:20.660
dvi: No class installer for 'DVC100'
dvi: Default installer: Enter 19:46:20.706
dvi: Default installer: Exit
dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 19:46:20.737
ndv: {Update Driver Software Wizard for
USB\VID_2304&PID_021A&MI_00\6&3B750AF&1&0000}
ndv: {Update Driver Software Wizard exit(000004c7)}
Section end 2016/11/22 19:46:39.311
[Exit status: FAILURE(0x000004c7)]

Also, you mentioned trying to download Studio 15. As I said, when I
first installed Studio 15 then the dvc100 drivers wre installed and
the device worked fine. It was only after I uninstalled Studio 15 that
the problems started.


--
remove fred before emailing

scbs29 wrote:


Thanks again for your reply.
I had opened each oem*.inf file in notepad looking for dvc100.
I did as you suggested and did a search in .inf. The only mention of
dvc100 is in a fle setupapi.dev.log dated 18 Nov, last modified 22
Nov.
There are 26 mentions of dvc100, of the form
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 11:44:27.046
ndv: Searching Windows Update for drivers... 11:44:27.421
ndv: Acquired WU search serialization mutex. 11:44:27.459
ndv: Received request to cancel Windows Update search.
ndv: About to release WU search serialization mutex. 11:44:39.133
ndv: Windows Update driver search cancelled. 11:44:39.526
ndv: Waiting for previous device install to complete.
11:44:39.701
ndv: {Core Device Install} 11:44:53.824
! ndv: Installing NULL driver!
dvi: Set selected driver complete.
dvi: {DIF_ALLOW_INSTALL} 11:44:53.942
dvi: No class installer for 'DVC100'
dvi: Default installer: Enter 11:44:53.950
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 11:44:53.979
dvi: {DIF_INSTALLDEVICE} 11:44:54.015
dvi: No class installer for 'DVC100'
or
[Device Install (DiShowUpdateDevice) -
USB\VID_2304&PID_021A&MI_00\6&3B750AF&1&0000]
Section start 2016/11/22 19:46:20.651
cmd: "C:\Windows\system32\mmc.exe"
C:\Windows\system32\devmgmt.msc
dvi: {DIF_UPDATEDRIVER_UI} 19:46:20.660
dvi: No class installer for 'DVC100'
dvi: Default installer: Enter 19:46:20.706
dvi: Default installer: Exit
dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 19:46:20.737
ndv: {Update Driver Software Wizard for
USB\VID_2304&PID_021A&MI_00\6&3B750AF&1&0000}
ndv: {Update Driver Software Wizard exit(000004c7)}
Section end 2016/11/22 19:46:39.311
[Exit status: FAILURE(0x000004c7)]

Also, you mentioned trying to download Studio 15. As I said, when I
first installed Studio 15 then the dvc100 drivers wre installed and
the device worked fine. It was only after I uninstalled Studio 15 that
the problems started.

You need to figure out where that driver came from.

Paul

On Wed, 23 Nov 2016 06:41:16 -0500, Paul
wrote:

scbs29 wrote:


Thanks again for your reply.
I had opened each oem*.inf file in notepad looking for dvc100.
I did as you suggested and did a search in .inf. The only mention of
dvc100 is in a fle setupapi.dev.log dated 18 Nov, last modified 22
Nov.
There are 26 mentions of dvc100, of the form
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 11:44:27.046
ndv: Searching Windows Update for drivers... 11:44:27.421
ndv: Acquired WU search serialization mutex. 11:44:27.459
ndv: Received request to cancel Windows Update search.
ndv: About to release WU search serialization mutex. 11:44:39.133
ndv: Windows Update driver search cancelled. 11:44:39.526
snip
dvi: {DIF_UPDATEDRIVER_UI} 19:46:20.660
dvi: No class installer for 'DVC100'
dvi: Default installer: Enter 19:46:20.706
dvi: Default installer: Exit
dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 19:46:20.737
ndv: {Update Driver Software Wizard for
USB\VID_2304&PID_021A&MI_00\6&3B750AF&1&0000}
ndv: {Update Driver Software Wizard exit(000004c7)}
Section end 2016/11/22 19:46:39.311
[Exit status: FAILURE(0x000004c7)]

Also, you mentioned trying to download Studio 15. As I said, when I
first installed Studio 15 then the dvc100 drivers wre installed and
the device worked fine. It was only after I uninstalled Studio 15 that
the problems started.

You need to figure out where that driver came from.

Paul

I'm sorry, but I don't understand. What driver ? The log file states
that there are no dvc100 drivers. The only dvc100 drivers that have
ever been installed on my pc are those on the Studio 15 installation
disc, and it is those drivers that will not now install due to the
1603 error and rollback.



--
remove fred before emailing

scbs29 wrote:
On Wed, 23 Nov 2016 06:41:16 -0500, Paul
wrote:

scbs29 wrote:

Thanks again for your reply.
I had opened each oem*.inf file in notepad looking for dvc100.
I did as you suggested and did a search in .inf. The only mention of
dvc100 is in a fle setupapi.dev.log dated 18 Nov, last modified 22
Nov.
There are 26 mentions of dvc100, of the form
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 11:44:27.046
ndv: Searching Windows Update for drivers... 11:44:27.421
ndv: Acquired WU search serialization mutex. 11:44:27.459
ndv: Received request to cancel Windows Update search.
ndv: About to release WU search serialization mutex. 11:44:39.133
ndv: Windows Update driver search cancelled. 11:44:39.526
snip
dvi: {DIF_UPDATEDRIVER_UI} 19:46:20.660
dvi: No class installer for 'DVC100'
dvi: Default installer: Enter 19:46:20.706
dvi: Default installer: Exit
dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 19:46:20.737
ndv: {Update Driver Software Wizard for
USB\VID_2304&PID_021A&MI_00\6&3B750AF&1&0000}
ndv: {Update Driver Software Wizard exit(000004c7)}
Section end 2016/11/22 19:46:39.311
[Exit status: FAILURE(0x000004c7)]

Also, you mentioned trying to download Studio 15. As I said, when I
first installed Studio 15 then the dvc100 drivers wre installed and
the device worked fine. It was only after I uninstalled Studio 15 that
the problems started.
You need to figure out where that driver came from.

Paul

I'm sorry, but I don't understand. What driver ? The log file states
that there are no dvc100 drivers. The only dvc100 drivers that have
ever been installed on my pc are those on the Studio 15 installation
disc, and it is those drivers that will not now install due to the
1603 error and rollback.

So you need to extract the driver folder from Studio 15
and see if 2304:021A is in any of the INF files.

I suspect you may have had some other version of Studio
installed at one time, and that's where the drivers came
from. If you extract the driver folder on Studio 15 it's
just going to have "Marvin and friends" drivers for
later hardware. And no DVC100.

And that's what I means when I say "you need to figure out...".
You need a scrupulous mental install log, remembering
all the Pinnacle software you've installed and so on,
if you expect to find the proper driver. My attempts
so far, only find the "smell" of the driver, like
they were teasing me or something. *Somewhere* on your
disk drive, you've got that driver.

Paul

On Wed, 23 Nov 2016 17:13:06 -0500, Paul
wrote:

scbs29 wrote:
On Wed, 23 Nov 2016 06:41:16 -0500, Paul
wrote:

scbs29 wrote:

Thanks again for your reply.
I had opened each oem*.inf file in notepad looking for dvc100.
I did as you suggested and did a search in .inf. The only mention of
dvc100 is in a fle setupapi.dev.log dated 18 Nov, last modified 22
Nov.
There are 26 mentions of dvc100, of the form
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 11:44:27.046
ndv: Searching Windows Update for drivers... 11:44:27.421
snip
1603 error and rollback.

So you need to extract the driver folder from Studio 15
and see if 2304:021A is in any of the INF files.

I suspect you may have had some other version of Studio
installed at one time, and that's where the drivers came
from. If you extract the driver folder on Studio 15 it's
just going to have "Marvin and friends" drivers for
later hardware. And no DVC100.

And that's what I means when I say "you need to figure out...".
You need a scrupulous mental install log, remembering
all the Pinnacle software you've installed and so on,
if you expect to find the proper driver. My attempts
so far, only find the "smell" of the driver, like
they were teasing me or something. *Somewhere* on your
disk drive, you've got that driver.

Paul

Again thanks for the reply.
However, the only Pinnacle software I have ever had is the Studio 15,
which was supplied with the DVC100 device.

On the Studio 15 cd there is a folder called Drivers, which contains
Pinnacle_Video_driver_32bit.exe and
Pinnacle_Video_driver_64bit.exe
which are the same as those downloaded when obtaining drivers from
Pinnacle.
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.

--
remove fred before emailing

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.
--
================================================== ======
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