1394 Sony not recognized

Discussion in 'Amateur Video Production' started by David Carlstrom, Oct 28, 2005.

  1. I have two computers with XP. One recognizes my Sony camcorder. The other
    does not. The issue seems to involve the TI 1394 port that once was on the
    computer. It never worked. XP said the 1394 port could not start. I
    replaced the TI with a generic card with a VIA chip. This card was tested
    in the first computer and works fine with the camcorder. I can't seem to
    get rid of the TI drivers. I've gotten the machine to detect the Sony brand
    name, but even when I point the Wizard at msdv.inf XP says it can't find a
    driver for the camcorder. I've let it search the internet for a driver and
    it says there is none. Does anyone know how to get rid of the last vestige
    of the TI driver? Does anyone know how to get this machine to recognize the
    Sony camcorder. TIA.
     
    David Carlstrom, Oct 28, 2005
    #1
    1. Advertisements

  2. David Carlstrom

    JimK Guest

    This might work
    http://www.golfshow.com/downloads/DV/TI Driver Fix - Windows 98.pdf
     
    JimK, Oct 28, 2005
    #2
    1. Advertisements

  3. David Carlstrom, Oct 28, 2005
    #3
  4. There is no driver for a camcorder as such. msdv.inf contains information
    on how the OS recognizes a camcorder as a camcorder and then associates it
    with the necessary drivers, including msdv.sys.

    The IEEE-1394 driver is ohci1394.sys and is the same for VIA, TI, Sony, NEC,
    National Semiconductor, Fujitsu and any generic OHCI-compliant port.

    The OS looks in 1394.inf and tries to match the unique plug-and-play
    identifier of the port with one of the entries in the last. It then
    populates the registry with a lot of entries which will be there for
    evermore.

    To get an idea of what's still in your registry, you need to search it for
    those entries specific to TI. Each manufacturer has a unique "vendor ID"
    and this is what you need to search for.

    Using regedit or regedt32, search for VEN_104C. You can try to delete them.
    Sometimes, deletion fails and you have to override access attributes
    (regedt32 does that, not regedit). The specific devices to look for are
    (from the 1394.inf):

    %PCI\VEN_104C&DEV_8009.DeviceDesc%=TIOHCI_Install,PCI\VEN_104C&DEV_8009

    %PCI\VEN_104C&DEV_8019.DeviceDesc%=TIOHCI_Install,PCI\VEN_104C&DEV_8019

    %PCI\VEN_104C&CC_0C0010.DeviceDesc%=TIOHCI_Install,PCI\VEN_104C&CC_0C0010

    %PCI\VEN_104C&DEV_8009&SUBSYS_8032104D.DeviceDesc%=TIOHCI_Install,PCI\VEN_10
    4C&DEV_8009&SUBSYS_8032104D

    If you have any other TI hardware, make sure you don't delete those entries!

    Good luck!

    John.

    http://www.golfshow.com/downloads/DV/TI Driver Fix - Windows 98.pd
    f
     
    John F. Miller, Oct 28, 2005
    #4
  5. Thanks, John, I deleted all the VEN_104 stuff as you suggested, but it
    still won't connect the camcorder. When I plug it in, it sees a new device,
    the wizard tries to find a "driver" for it, but fails. Any idea what else
    might prevent XP from connecting the camcorder. All parts work okay on
    another computer.
     
    David Carlstrom, Oct 28, 2005
    #5
  6. You could compare the msdv.inf files on both machines. Perhaps one has a
    more up-to-date one.

    You could also try locating the registry entries for the Sony unit on the PC
    where it works, export them and load them into the registry on the other
    machine.

    (You should be able to work out the Sony vendor ID from the msdv.inf file).

    John.
     
    John F. Miller, Oct 28, 2005
    #6
  7. The msdv.inf files are the same on the two machines.

    I don't know how to export from or load to the registry. Where can I learn
    about that?

    file).
     
    David Carlstrom, Oct 29, 2005
    #7
  8. Start regedit (Start Menu/Run.../regedit <enter>)

    From the Edit menu, choose Find... and look for "avc\ven_80046" (no quotes,
    default dialog settings). regedit will find the first occurence. F3 will
    go to the next one each time you press it. Keep going until the entry that
    is found is in:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D
    0-BEC7-08002BE2092F}\nnnn

    nnnn will be a 4-digit number. Make sure you are looking at the
    CurrentControlSet (not, e.g., ControlSet001). Most likely, the highlighted
    part of the search will be "MatchingDeviceID" in the righthand window pane.

    Now left-click once in the lefthand pane in a whitespace region (i.e., don't
    click on an entry in the list). The highlight will now be one of the
    4-digit numbers listed.

    Right-click on it and choose Export. Choose a name and location for the
    ..reg file and select "Selected branch".

    Close regedit.

    Locate the .reg file and right-click on it once. The context menu will
    included Merge and Edit. Choose Edit - this will open the file in Notepad
    so you can see the contents. You should have something like:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11
    D0-BEC7-08002BE2092F}\0000]
    "OkToHibernate"=hex:01
    "DontSuspendIfStreamsAreRunning"=hex:01
    "HardwareConfig"=hex:01
    "USDClass"="{0527d1d0-88c2-11d2-82c7-00c04f8ec183}"
    "InfPath"="msdv.inf"
    "InfSection"="DVCR.Sony"
    "InfSectionExt"=".NT"
    "ProviderName"="Microsoft"
    "DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
    "DriverDate"="7-1-2001"
    "DriverVersion"="5.1.2600.0"
    "MatchingDeviceId"="avc\\ven_80046&mod_0&camcorder&dv"
    "DriverDesc"="Sony DV Camcorder"
    "SubClass"="StillImage"
    "Vendor"="Sony"
    "FriendlyName"="Sony DV Camcorder"
    "ICMProfiles"="sRGB Color Space Profile.icm"
    "DeviceID"="{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\\0000"
    "Capabilities"=dword:00000031
    "DeviceType"=dword:00000003
    "DeviceSubType"=dword:00000001
    "IsPnP"=dword:00000001
    "CreateFileName"="AUTO"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11
    D0-BEC7-08002BE2092F}\0000\DeviceData]
    "Server"="local"
    "UI DLL"="sti.dll"
    "UI Class ID"="{5d8ef5a3-ac13-11d2-a093-00c04f72dc3c}"
    "DShowDeviceId"="\\\\?\\avc#ven_80046&mod_0&camcorder&dv#f8e260101460008#{65
    e8773d-8f56-11d0-a3b9-00a0c9223196}\\global"
    "ICMProfile"=hex:73,00,52,00,47,00,42,00,20,00,43,00,6f,00,6c,00,6f,00,72,00
    ,\

    20,00,53,00,70,00,61,00,63,00,65,00,20,00,50,00,72,00,6f,00,66,00,69,00,6c,\
    00,65,00,2e,00,69,00,63,00,6d,00,00,00,00,00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11
    D0-BEC7-08002BE2092F}\0000\Events]



    Close Notepad. Copy the .reg file to your other system, right-click on it
    and select Merge.

    "Are you sure you want to add the information in xxxx.reg to the
    registry?" - Answer Yes.

    If successful:

    "Information in xxxx.reg has been successfully entered into the registry." -
    Click OK.

    Now try to connect the device to the system and see if it works.

    If it doesn't, post details of the IEEE-1394 ports in both systems and the
    OS versions (service packs etc etc). Also, what model camcorder do you
    have? I have three different Sony devices, and they all work.

    John.
     
    John F. Miller, Oct 29, 2005
    #8
  9. One other thought - XP SP2 has known issues with IEEE-1394.

    http://support.microsoft.com/default.aspx/kb/885222

    John.
    --
    John Miller
    http://www.enosoft.net/
    high performance tools for music and video

     
    John F. Miller, Oct 29, 2005
    #9
  10. I had found that one and put it in. No help.
     
    David Carlstrom, Oct 30, 2005
    #10
  11. Kjell Andersson, Oct 30, 2005
    #11
  12. Following your instructions did not help. Here are the port details. I
    hope I've grabbed the parts you want to see. I've named computer that works
    "WS" and the one that doesn't "P".

    "WS"

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC1-810F-11
    D0-BEC7-08002BE2092F}]
    "Class"="1394"
    @="IEEE 1394 Bus host controllers"
    "Icon"="-21"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC1-810F-11
    D0-BEC7-08002BE2092F}\0000]
    "InfPath"="1394.inf"
    "InfSection"="VIA_Install"
    "InfSectionExt"=".NT"
    "ProviderName"="Microsoft"
    "DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
    "DriverDate"="7-1-2001"
    "DriverVersion"="5.1.2535.0"
    "MatchingDeviceId"="pci\\ven_1106&dev_3044"
    "DriverDesc"="VIA OHCI Compliant IEEE 1394 Host Controller"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC1-810F-11
    D0-BEC7-08002BE2092F}\0000\Virtual Device List]

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC1-810F-11
    D0-BEC7-08002BE2092F}\0000\Virtual Device List\NIC1394]

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC1-810F-11
    D0-BEC7-08002BE2092F}\0000\Virtual Device List\NIC1394\LOCAL HOST EUI64]
    @=""

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11
    CE-BFC1-08002bE10318}\0009]
    "Characteristics"=dword:00000004
    "BusType"="14"
    "ComponentId"="v1394\\nic1394"
    "InfPath"="net1394.inf"
    "InfSection"="nic1394.ndi"
    "ProviderName"="Microsoft"
    "DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
    "DriverDate"="7-1-2001"
    "DriverVersion"="5.1.2535.0"
    "MatchingDeviceId"="v1394\\nic1394"
    "DriverDesc"="1394 Net Adapter"
    "NetCfgInstanceId"="{F2FA535A-E7B9-498D-AFB9-65E200BC908B}"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11
    CE-BFC1-08002bE10318}\0009\Linkage]
    "RootDevice"=hex(7):7b,00,46,00,32,00,46,00,41,00,35,00,33,00,35,00,41,00,2d
    ,\

    00,45,00,37,00,42,00,39,00,2d,00,34,00,39,00,38,00,44,00,2d,00,41,00,46,00,\

    42,00,39,00,2d,00,36,00,35,00,45,00,32,00,30,00,30,00,42,00,43,00,39,00,30,\
    00,38,00,42,00,7d,00,00,00,00,00
    "UpperBind"=hex(7):54,00,63,00,70,00,69,00,70,00,00,00,00,00
    "Export"=hex(7):5c,00,44,00,65,00,76,00,69,00,63,00,65,00,5c,00,7b,00,46,00,
    32,\

    00,46,00,41,00,35,00,33,00,35,00,41,00,2d,00,45,00,37,00,42,00,39,00,2d,00,\

    34,00,39,00,38,00,44,00,2d,00,41,00,46,00,42,00,39,00,2d,00,36,00,35,00,45,\
    00,32,00,30,00,30,00,42,00,43,00,39,00,30,00,38,00,42,00,7d,00,00,00,00,00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11
    CE-BFC1-08002bE10318}\0009\Ndi]
    "Service"="NIC1394"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11
    CE-BFC1-08002bE10318}\0009\Ndi\Interfaces]
    "UpperRange"="ndis1394"
    "LowerRange"="atm"

    "P"

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11
    CE-BFC1-08002bE10318}\0012]
    "Characteristics"=dword:00000004
    "BusType"="14"
    "ComponentId"="v1394\\nic1394"
    "InfPath"="net1394.inf"
    "InfSection"="nic1394.ndi"
    "ProviderName"="Microsoft"
    "DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
    "DriverDate"="7-1-2001"
    "DriverVersion"="5.1.2535.0"
    "MatchingDeviceId"="v1394\\nic1394"
    "DriverDesc"="1394 Net Adapter"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11
    CE-BFC1-08002bE10318}\0012\Ndi]
    "Service"="NIC1394"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11
    CE-BFC1-08002bE10318}\0012\Ndi\Interfaces]
    "UpperRange"="ndis1394"
    "LowerRange"="atm"

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC1-810F-11
    D0-BEC7-08002BE2092F}\0004]
    "InfPath"="1394.inf"
    "InfSection"="VIA_Install"
    "InfSectionExt"=".NT"
    "ProviderName"="Microsoft"
    "DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
    "DriverDate"="7-1-2001"
    "DriverVersion"="5.1.2535.0"
    "MatchingDeviceId"="pci\\ven_1106&dev_3044"
    "DriverDesc"="VIA OHCI Compliant IEEE 1394 Host Controller"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC1-810F-11
    D0-BEC7-08002BE2092F}\0004\Virtual Device List]

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC1-810F-11
    D0-BEC7-08002BE2092F}\0004\Virtual Device List\NIC1394]

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC1-810F-11
    D0-BEC7-08002BE2092F}\0004\Virtual Device List\NIC1394\LOCAL HOST EUI64]
    @=""
     
    David Carlstrom, Nov 2, 2005
    #12
  13. David Carlstrom

    The DV Show Guest

    Focusing on the registry is only part of your problem.

    Capture routines vary from software to software, computer to computer,
    camcorder to camcorder- which means its not an exact science. This is a
    common question everyone has from PC to Mac and there are many reasons for
    not being able to capture. Because of this, there is no one answer so we can
    start with the common causes blocking your camcorder's communication to your
    computer and offer some simple solutions from there:

    For Sony camcorders it could be a proprietary cable (an exclusively Sony
    cable) not being used. Sony Firewire products often work only with Sony
    I-Link cables.
    1. Your computer's Firewire drive is 400 instead of 800.

    2. Camcorder's menu settings not set up for DV-in/out

    3. Computer resources are low- close all other programs, and run software
    like EndItAll before you start any video work.

    4. You're running a FAT32 system. Convert your filesystem to NTFS - FAT32
    has a 4 GB file size limit. Here's how to do this:
    http://www.mvps.org/marksxp/WindowsXP/fatntfs.php

    5. Connect your camcorder via Firewire to your computer throw the switch to
    playback or VCR mode BEFORE booting up instead of having it in camera mode.

    6. Older Drivers- this is the first place to look if your PC is having
    trouble recognizing your camcorder. Go to your camcorder manufacturer's Web
    site and look in the support section. You should find a page for the latest
    drivers or downloads. Simply download and install the drivers, and your PC
    should be able to work with your camcorder. You might have to reboot your
    computer before the drivers are ready to go, however. Once you've rebooted,
    try connecting your camcorder to the PC again- make sure it's in the
    playback and not camcorder mode.

    7. Older operating system - upgrade! You'll get better results when
    transferring and editing video and burning DVDs than you will with an
    earlier OS. On the Macintosh side, the upgrade to Mac OS 10.3 costs about
    $130. Like its Windows counterpart, the upgrade is well worth the price.
    This version of the Macintosh operating system is faster and more stable
    than earlier versions and comes with iDVD, which is a killer application for
    editing your home videos.

    8. Running SP2 under Windows XP
    http://www.microsoft.com/downloads/details.aspx?FamilyID=a2091337-a0ea-4b34-
    b19f-b6ec04c1f2d2&DisplayLang=en

    9. Firewire card is not enabled or is simply not working. To fix this from
    the main windows screen go Start > Control Panel > System > Hardware >
    Device Manager If when you get to Control Panel you cannot see System,
    either click on classic view at the top left and it will then be one of the
    options or go from Control Panel > Performance and Maintenance> System >
    Device Manager. In Device Manager you should look for the IEEE 1394 Bus host
    controllers entry. If you can expand this you should have something similar
    to OHCI Compliant IEEE 1394 Host Controller. Neither of these entries should
    have a yellow exclamation mark by them. if there is, you have a problem and
    need to fix this. Here's how:

    If you have closed down device manager, then open it back up.

    Right click on OHCI Compliant IEEE 1394 host controller and then left click
    on Update driver. This will open up a box labeled Hardware Update Wizard.
    Click on next and leave it to find the driver. XP should contain all the
    files needed to replace the drivers for your firewire card, so after waiting
    a short while, during which time the box will now say please wait while the
    wizard searches. The box should end up saying the device is installed and
    ready to use. If you check again in device manager the yellow exclamation
    mark should now be gone.

    There may also be a red cross through it, this would mean that the device
    has not been enabled. To re-enable the device all you need to do is right
    click on OHCI Compliant IEEE 1394 host controller and then left click on
    enable and you should be all set.


    10. Conflicts can exist between pci cards due to the way the port has been
    assigned. The main problems are, No IRQ has been assigned, an IRQ has been
    assigned, but it has a software conflict, an IRQ has been assigned, and it
    has a hardware conflict. Simply put the firewire card may be interfering
    with say the sound card, or vice versa.

    11. Installing new software - for example, installing a newer version of QT
    will sometimes update your FireWire extensions during the install.

    Now if these are any of your problems and it still does not work try
    capturing video using a totally seperate utility apart from editing
    software: it's called DVIO for DV in/out it's free and some swear by it
    after exhausting all possible solutions. You could also try WinDV...this
    software is free in our Download Vault:
    http://www.thedvshow.com/downloadvault


    Listen to the new podcast
    for DV creators- The DV Show!
    http://www.thedvshow.com

    --
    Brian Alves
    Executive Producer
    The DV Show
    http://www.thedvshow.com
     
    The DV Show, Nov 3, 2005
    #13
  14. David Carlstrom

    Jaco Guest

    David Carlstrom a écrit :
    Perhaps you need to reload the qdv.dll (for XP)
    by running :
    regsvr32 %windir%\system32\qdv.dll
     
    Jaco, Nov 4, 2005
    #14
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.