Ok...I have a JVC digital video camera (mini dv with the firewire) and
it
does not work either. It worked when we tried uninstallling sp2, but
when
we
reinstalled it no longer worked. I'm am NOT a computer techy person and
really REALLY would like some help! Please help!
Sue (
[email protected])
:
Graham Hughes wrote:
Has you camcorder worked under SP1, but when connected to the
firewire
port
of your upgraded SP2 computer, stopped working?
If so please post your pc specs, inc as much info as possible, inc
hardware
and software, also Make/model/age/PAL-NTSC of the camcorder, and
what,
if
anything, happens when the cam is connected.
Please no discussions of the problem in this post, just info from
people
who
are suffering.
Graham
--
Graham Hughes
MVP Digital Media
www.myvideoproblems.co.uk
www.dvds2treasure.com
www.simplydv.com
Graham, et al:
I am having the same issue with my Sony Z1.
The odd thing is that I can plug in my Panasonic PV-DV910 and Sony
Vegas
comes up in capture mode and captures video just fine. That it works
with another 1394 device would seem eliminate SP1/SP2 problems,
firewall
problems, etc.
I am running Windoze XP Pro, but have elected to not install SP2
because
of reported issues with Photoshop CS and other software I use; I have
installed several hotfixes since SP1 however.
To me, this issue is beginning to look like a problem in recognizing
the
camera. Incidentally, when the Panasonic camera is connected, the
Imaging Device in the Hardware manager reports correctly. When I plug
in
the Sony Z1, Windoze finds new hardware (AVC-Subunit), tries to
install
a driver for it (Sony did not provide any drivers) and then exits with
an error.
I followed advice I have seen in other forums including following the
link to the M$ Knowledge Base, but the Hotfix mentioned in the cited
article is not available except by request. I will try to contact
Microsoft next week and make my request, if i can figure out the
procedure. The website to which M$ refers one makes no mention of who
to
contact to make my request.
One of the articles I found elsewhere mentioned checking in the
%SystemRoot%\inf directory to see if msdv.inf and msdv.PNF had been
renamed to msdv1.inf or some such.
As the msdv.inf file is ASCII, I opened it with a text editor and
found
that it includes the following Sony specific information:
;---------------------------------------------------------------
; 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
In addition, I found similar entries for most manufacturers of 1394
video devices.
I am beginning to wonder if Sony, JVC, and others may not have
properly
followed the 1394 device definition rules referenced elsewhere on the
Microsoft site.
The following entry in msdv.inf is particularly interesting:
%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
Fom the above I conclude that Micro$oft has listed only three Sony
DVCR
devices: VEN_80046&MOD_0&CAMCORDER&DV, Sony&CAMCORDER&DV, and
VEN_80146&MOD_0&CAMCORDER&DV. Interestingly enough, these three
closely
resemble the device names found when attempting to manually install
the
device drivers for a Sony Imaging device.
I suppose it is possible that Sony in the camera firmware:
1. used a different Company_id for it's Prosumer/Professional camera
models.
2. used a different device description for the AVC device other than
the
three shown above.
I have now seen this problem reported in other forums (including Sony)
for both the Sony FX1 and Z1 cameras as well as certain JVC cameras.
Sony points the finger at Microsoft in this case. That other (e.g.
older) 1394 devices seem to work fine makes one wonder if indeed the
camera manufacturer is at fault for not providing an updated version
of
msdv.inf.
Since the msdv.PNF file is binary, I have no way to determine whether
some of the code needs to be changed, but this would have to be done
either by Sony or Micro$oft.
Suggestions and comments are solicited.
Rod Cole
