DV AV/C subunit driver will not install and now the VX-1000 is lost

Problem I posted in this NG Fri, 05 Jan 2001 02:30:31 GMT was resolved
by Microsoft within a few weeks or months. The problem then (and now)
- the IEEE1394 drivers for the AVC/C Subunit do not install leaving a
Yellow Question mark on the Device Manager report. The higher level
stuff appears OK.

Microsoft told me then that it wasn't a problem if you installed with a
Complete Install CD. They also told me that there was a way to get the
same effect with the update CD. I did what they said. Initially that
didn't fix the problem. Further work, in my case, possibly because I
had some Ulead software in the other room, was necessary. That work
did the trick.

Unfortunately I do not recall the details except vaguely. Microsoft
had me change something in a couple text files. Perhaps I should put it
a little differently - they had me change some characters in one or two
files. Reboot a few times. Then it worked. I thought no more about it
until recently the audio pooped out on that good old winME system
(another story) and winME Movie Maker will not run.

I was making another system anyway, also winME, for some Vegas video
stuff. I just finished putting the D-Link DFB-A5 USB 2.0/FireWire
Combo in the new unit. I Installed winME OS and all on a clean
harddrive. The Firewire works fine on my external WDC harddrive. But
Device Manager reports, just like in 2001, the AV/C Subunit "Device
status: The drivers for this device are not installed ( code 28. )."

YIKES!
Anyone know what those files must be? I think the reasoning behind the
problem is something at driver install time communicates with the
camcorder device, queries it. The camcorder is supposed to send a
string in response that is checked by the driver install program. If
that string does not match (something in an INF file? / whatever) the
install fails.

Does this ring a bell with somebody? Jeff LeBlanc are you there?

Thanks.

some of the details from the 2001 post:

3 AVC Device
3.1 General tab:
Device Type: AVC Device Class;
Manufacturer: Microsoft;
Hardware Version: not available.
Status: This device is working properly.
3.2 Driver tab:
Driver Provider: Microsoft;
Driver Date 6/8/2000;
Digital Signer: Microsoft Consumer Windows Publisher;
click Driver File Details button:
avc.sys 4.90.3000.1;
VMM32.VXD;


4 Other Devices
4.1 AV/C Subunit
click Properties button.
4.1.1 General tab:
Device Type: Other Devices;
Manufacturer: None specified;
Hardware Version: Not available;
Device status: The drivers for this device are not installed ( code
28. ).
To reinstall the drivers for this device click Reinstall Driver
[button] . .
..

 

Here are some more of how this was made to work previously as I have
found some of the old stuff from the winME fix to get Movie Maker to
run with Sony VX-1000:
Some of the DM entries involved may have names changed. For example,
underneath the AVC Device Class:
On VX-1000 not compatible with Movie Maker system:
Under Imaging Device I have "Sony AV Device".
I never saw mention of an Imaging Device.

On VX-1000 works with Movie Maker system:
AVC Device Class has subordinate entry named "AVC Device". I think
prior to changes it said "AV Device/Sub".
Under Imaging Device there is a subordinate entry "Sony AV Device".

One of the files altered might have been MSDV.inf.

As for the registry, a reg file was used:
This might have needed "a minor change" before it was final (furnished
by MS).
There was also an INF file laying around here somewhere I HOPE.
Contents of Sony reg file:


REGEDIT4

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Image\0000]
"FriendlyName"="Sony DV Camcorder"
"CreateFileName"="AUTO"
"Vendor"="Sony"
"DeviceType"=dword:00000003
"DeviceSubType"=dword:00000001
"Capabilities"=dword:00000031
"DevLoader"="*ntkern"
"NTMPDriver"="msdv.sys"
"OkToHibernate"=hex:01
"HardwareConfig"=hex:01
"USDClass"="{0527d1d0-88c2-11d2-82c7-00c04f8ec183}"
"InfPath"="MSDV.INF"
"InfSection"="DVCR.Sony"
"ProviderName"="Microsoft"
"DriverDate"="06/08/2000"
"DriverDesc"="Sony DV Camcorder"
"ICMProfiles"="sRGB Color Space Profile.icm"
"MatchingDeviceId"="AVC\\VEN_80046&CAMCORDER"
"SignedBy"="Microsoft Consumer Windows Publisher"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Image\0000\DeviceData]
"Server"="local"
"UI DLL"="sti.dll"
"UI Class ID"="{5d8ef5a3-ac13-11d2-a093-00c04f72dc3c}"
"ICMProfile"=hex:73,52,47,42,20,43,6f,6c,6f,72,20,53,70,61,63,65,20,50,72,6f,\
66,69,6c,65,2e,69,63,6d,00,00
"DShowDeviceId"="\\\\.\\0000000000000015#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\\global"


[HKEY_LOCAL_MACHINE\Enum\AVC]

[HKEY_LOCAL_MACHINE\Enum\AVC\VEN_80046&MOD_0&CAMCORDER]

[HKEY_LOCAL_MACHINE\Enum\AVC\VEN_80046&MOD_0&CAMCORDER\C7C58E0201460008]
"Capabilities"=hex:b4,00,00,00
"HardwareID"="AVC\\VEN_80046&MOD_0&CAMCORDER"
"CompatibleIDs"="AVC\\VEN_80046&CAMCORDER,AVC\\CAMCORDER"
"DeviceDesc"="Sony DV Camcorder"
"ClassGUID"="{6bdd1fc6-810f-11d0-bec7-08002be2092f}"
"Class"="Image"
"Serial"=hex:15,00,00,00,00,00,00,00
"SubClass"="StillImage"
"Driver"="Image\\0000"
"Mfg"="Sony"
"ConfigFlags"=hex:00,00,00,00



Thanks,

 

Pardon my scrambled syntax. Beginning about the middle of my first
paragraph of my 2nd post. It should say:

On system-when-VX1000-not-compatible-with-Movie-Maker:
A. 1394 Bus Controller\PCI OHCI Compliant IEEE 1394 Host Controller
B. 61883 Device Class\61883 Class Bus Device,
C. AVC Device Class\AVC device,
D. Other devices\AV/C Subunit, PCI Universal Serial Bus
E. Storage Device\IEEE1394 Disk.


On system-when-VX1000-is-compatible-with-Movie-Maker:
A. 1394 Bus Controller\NEC Firewarden OHCI Compliant,
B. 61883 Device Class\61883 Class Bus Device,
C. AVC Device Class\AVC device,
D. Imaging Device\Sony AV Device,
E. Storage Device\IEEE1394 Disk.

Sorry,

 

Hmmm. I know every body is busy even when it isn't Christmas... But
maybe this will help some of you keep that $5000 VX1000 going a bit
longer. Maybe the changes needed to get it to run on XP are similar?

It seems to me the driver installation is mainly controlled by INF
files. I think** the INF file that I used in 2001-2002 was the
MSDV.inf version/dated DriverVer=06/08/2000. Looking at the
FileCompare results I see that one code used to identify a Sony DV
Camcorder was changed from VEN_80046 to VEN_80146. Perhaps VEN_80046
is the code the VX1000 returns when the driver install process queries
it over the ieee1394 cable. Anybody know of a monitor such as
Netmonitor that can watch ieee1394 packets?

All the differences between the MSDV.inf that almost certainly** went
with the system-when-VX1000-is-compatible-with-Movie-Maker and the one
that didn't might be these:
Comparing files MSDVbadSonyID.INF and other\microsoftMSDV.inf
****** MSDVbadSonyID.INF
294: [Sony]
295: %AVC\VEN_80046.DeviceDesc%=DVCR.Sony,AVC\VEN_80046

296: %AVC\VEN_80046&TYP_4.DeviceDesc%=DVCR.Sony,AVC\VEN_80046&TYP_4

297:
%AVC\VEN_80046&CAMCORDER.DeviceDesc%=DVCR.Sony,AVC\VEN_80046&CAMCORDER

298:
%AVC\VEN_80046&CAMCORDER.DeviceDesc%=DVCR.Sony,AVC\VEN_80146&CAMCORDER

299: [DVCR.Sony]
****** other\microsoftMSDV.inf
294: [Sony]
295: %AVC\VEN_80146.DeviceDesc%=DVCR.Sony,AVC\VEN_80146

296: %AVC\VEN_80146&TYP_4.DeviceDesc%=DVCR.Sony,AVC\VEN_80146&TYP_4

297:
%AVC\VEN_80146&CAMCORDER.DeviceDesc%=DVCR.Sony,AVC\VEN_80146&CAMCORDER

298:
%AVC\VEN_80146&CAMCORDER.DeviceDesc%=DVCR.Sony,AVC\VEN_80146&CAMCORDER

299: [DVCR.Sony]
******

****** MSDVbadSonyID.INF
446: AVC\VEN_8001F&CAMCORDER.DeviceDesc="Sharp DV Camcorder"
447: AVC\VEN_80046.DeviceDesc="Sony AV Device"
448: AVC\VEN_80046&TYP_4.DeviceDesc="Sony DV Tape Recorder/Player"
449: AVC\VEN_80046&CAMCORDER.DeviceDesc="Sony DV Camcorder"
450: PlugIn_IAMExtDevice="WDM Streaming IAMExtDevice Interface
Handler"
****** other\microsoftMSDV.inf
446: AVC\VEN_8001F&CAMCORDER.DeviceDesc="Sharp DV Camcorder"
447: AVC\VEN_80146.DeviceDesc="Sony AV Device"
448: AVC\VEN_80146&TYP_4.DeviceDesc="Sony DV Tape Recorder/Player"
449: AVC\VEN_80146&CAMCORDER.DeviceDesc="Sony DV Camcorder"
450: PlugIn_IAMExtDevice="WDM Streaming IAMExtDevice Interface
Handler"
******
Thank you all for your time and ideas.

Robert

**I have to quibble because what is there now is not msdv.sys but a
link to it on a drive that has been "recycled". The copy I'm comparing
with is from a backup of that cannibalized that drive.

 

Hi Bob

Hows it feel to have started such a hot topic? Only a little pause
while folks got prepared for the Texas v USC Rosebowl? They'l be back
once everyone has calmed down and payed off there bookie.

I found confirmation of an MSDV.inf issue at
http://forums.afterdawn.com/thread_view.cfm/3/142580. If I read them
correctly, they confirm that not all VX-1000 / vx1000 camcorders use
the same vendor id. Some require 80046. Some 80146.

So now what? Are their other issues? How do I check this? I guess I
will copy over the forums.afterdawn.com msdv.inf into the winME\ INF
directory, right click it and select INSTALL.

The pertinent MSDV.inf section follows (plus a few others that might
be useful in the future when or if the forums vanish.:
;---------------------------------------------------------------
; S o n y
;
; 1 3 9 4 D V C R
;---------------------------------------------------------------
[Sony]
%AVC\VEN_80046.DeviceDesc%=DVCR.Sony,AVC\VEN_80046&MOD_0 ; Sony AV
Device; Failed AVC Subunit Cmd
%AVC\VEN_80046.DeviceDesc%=DVCR.Sony,AVC\Sony&MOD_0 ; Sony AV Device;
Failed AVC Subunit Cmd

%AVC\VEN_80046&TYP_4.DeviceDesc%=DVCR.Sony,AVC\VEN_80046&MOD_0&TYP_4&DV
; Sony DV Tape Recorder/Player
%AVC\VEN_80046&TYP_4.DeviceDesc%=DVCR.Sony,AVC\Sony&TYP_4&DV ; Sony DV
Tape Recorder/Player with vendor text

%AVC\VEN_80046&CAMCORDER.DeviceDesc%=DVCR.Sony,AVC\VEN_80046&MOD_0&CAMCORDER&DV
; Sony DV camcorder
%AVC\VEN_80046&CAMCORDER.DeviceDesc%=DVCR.Sony,AVC\Sony&CAMCORDER&DV ;
Sony DV camcorder with vendor text
%AVC\VEN_80046&CAMCORDER.DeviceDesc%=DVCR.Sony,AVC\VEN_80146&MOD_0&CAMCORDER&DV
; For Sony's device that use 80146 as its Company_id

[DVCR.Sony]
Include= ks.inf, kscaptur.inf
Needs= KS.Registration,KSCAPTUR.Registration
AddReg=
DVCR.AddReg.Win9x,DVCR.AddReg,DVCR.PinNames,DVCR.PlugIns,DVCR.WIA.AddReg

DelFiles= DVCR.DelDrivers
CopyFiles= DVCR.CopyDrivers

SubClass= StillImage
DeviceType= 3
DeviceSubType=0x1
Capabilities= 0x00000031
DeviceData= DVCR.DeviceData
ICMProfiles= "sRGB Color Space Profile.icm"

[DVCR.Sony.NT]
Include= ks.inf, kscaptur.inf
Needs= KS.Registration,KSCAPTUR.Registration.NT
AddReg= DVCR.AddReg,DVCR.PinNames,DVCR.PlugIns,DVCR.WIA.AddReg
CopyFiles= DVCR.CopyDrivers

SubClass= StillImage
DeviceType= 3
DeviceSubType=0x1
Capabilities= 0x00000031
DeviceData= DVCR.DeviceData
ICMProfiles= "sRGB Color Space Profile.icm"

[DVCR.Sony.Interfaces]
AddInterface=%KSCATEGORY_VIDEO%,GLOBAL, DVCR.Sony.Interface
AddInterface=%KSCATEGORY_CAPTURE%,GLOBAL, DVCR.Sony.Interface
AddInterface=%KSCATEGORY_RENDER%,GLOBAL, DVCR.Sony.Interface
AddInterface=%KSCATEGORY_RENDER_EXT%,GLOBAL,DVCR.Sony.Interface

[DVCR.Sony.NT.Interfaces]
AddInterface=%KSCATEGORY_VIDEO%,GLOBAL, DVCR.Sony.Interface
AddInterface=%KSCATEGORY_CAPTURE%,GLOBAL, DVCR.Sony.Interface
AddInterface=%KSCATEGORY_RENDER%,GLOBAL, DVCR.Sony.Interface
AddInterface=%KSCATEGORY_RENDER_EXT%,GLOBAL,DVCR.Sony.Interface

[DVCR.Sony.Interface]
AddReg=DVCR.Sony.Intf.AddReg

[DVCR.Sony.Intf.AddReg]
HKR,,CLSID,,%ProxyVCap.CLSID%
HKR,,FriendlyName,,%DVCR.Capture%
HKR,,Description,, %DVCR.Sony.Capture%

[DVCR.Sony.NT.Services]
AddService = MSDV,0x00000002,DVCR.ServiceInstall