VideoHelp Forum




+ Reply to Thread
Results 1 to 13 of 13
  1. Hello all, i have this strange problem and is driving me crazy, i hope we can find a solution!.

    First some info:

    OS: Fully updated Windows XP x64 SP2
    FW Card: D-Link DFW-500 (Windows Recognize it as Texas Instruments OHCI COmplaint IEEE 1394 Host Controller, no additional drivers needed)
    Capture APP: WinDV
    Cable: OK Condition.
    Camera: Sony DCR-PC110

    Problem:

    The problem is really simple: when i connect the camera to windows, you hear the sound of new connection, the autoplay windows shows up asking what i would like to do and immediately disappears, and the sound of device unplugged hears. Of course after that WinDV or any other capture app doesn't see the camera.

    My troubleshooting:

    Old version of windows, lets say Windows XP SP1 32bits, the connection works without a problem (This is not a solution since im keeping x64 sp2 windows).

    If I reboot into Linux (Dual-boot setup). The connection works perfectly and i capture using dvgrab or kino (This is the temporal solution im using), and then edit in Premiere in Windows.

    Now the weird part (Found about this by accident): If i boot into Linux, connect to the camera using Kino/Dvgrab, then reboot into Windows without turning the camera off, Windows recognize the camera! and i can capture using WinDV! or any other program. Even if i turn the camera off/on stills works!. Of course if i turn my computer off, and boot straight into Windows the original problem comes up, windows doesn't see the camera.

    As you can see it seems its not a Camera/Firewire card/Cable issue but a windows issue.

    I'm aware of a solution that involves replacing SP2 1394 Drivers with SP1 ones. The problem is that i cant find SP1 x64 Drivers.

    After searching a lot here and in the net, its seems that microsoft released a hotfix (I Dont remember now the KB Article) for this, but i can't find a x64 version too. And also if i have a fully updated Windows xp sp2 x4 shouldn't this fix be included ? (I update using Windows Update Web Page)

    Well thanks for the time!
    What do you think?
    Quote Quote  
  2. Most probably you need to roll back the FireWire drivers to the SP1 versions:

    http://forum.digital-digest.com/showthread.php?t=42557
    John Miller
    Quote Quote  
  3. Thanks for fast reply!.

    Yes I was aware of that solution, the problem is that i can't find the x64 versions of the files. And the x64 cd i have came with SP2 included
    Quote Quote  
  4. Oh, I was reading too fast and didn't see the x64 bit.

    You could try uninstalling the IEEE-1394 drivers in Device Manager and then reboot to force Windows to reinstall the drivers. Or try turning the camcorder on before you boot (just like you do when you switch over from Linux to Windows).
    Quote Quote  
  5. It's ok!.

    No, that doesn't work , I also tried it before. It only works if i access the camera through kino/dvgrab in Linux and the reboot. It's too weird!.

    Im going to try to find SP1 x64 files on the net. But i tried looking before with no luck! .
    Quote Quote  
  6. I tried searching ALL the IEEE 1394 related x64 hotfixes available, and only came up with this one:

    http://support.microsoft.com/kb/951410
    The problem it fixes is not exactly this one, but also includes all the previous 1394 hotfixes

    Tried installing it, but it doesn't solve the problem.

    I used this website thehotfixshare.net to search the fixes, which has them all nicely organized, i searched for '1394'
    Quote Quote  
  7. What are the dates of the ohci1394.sys and 1394bus.sys that you have?
    John Miller
    Quote Quote  
  8. with 1 gig of ram there's absolutely no reason for you to run xp64. use the 32 bit version you have.
    Quote Quote  
  9. Hi, Sorry the delay.

    1394bus.sys date is: 02/17/2007
    and ohci1394.sys date is: 08/18/2008

    minidv2dvd: Be able to use 4GB+ of RAM isn't the only reason to use a 64-Bit OS.
    Quote Quote  
  10. even the name "xp 64 bit" refers to the memory addressing space of the os. why else use it? for the lack of decent drivers and programs that utilize it? if you can come up with another reason i'm all ears.
    Quote Quote  
  11. It's more responsive and more secure.
    Quote Quote  
  12. Originally Posted by JohnnyMalaria
    It's more responsive and more secure.
    is it more responsive because there are fewer programs running, or are capable of running?

    i've never heard of any 32 bit exploit that didn't also work on 64 bit windows, as also seen in the same security patches for 64 bit as 32 bit.
    Quote Quote  
  13. Well I have it installed since 2 years and NEVER crashed or a single BSOD . Its running as fast as the first day i installed it (Never reinstalled it). Its based in Windows 2003 (NT 5.2 Kernel) , as opposed to Windows XP 32 Bits which is NT 5.1, So its far superior and highly more stable than Xp 32bits. Of course 64 native apps runs faster than their 32 bit counterparts. I have used 32 bits XP before 64Bits for many years, and the difference is highly noticeable in many ways. And i dont have a sinlge problem with drivers. This firewire trouble is the same with 32 bit xp since SP2
    And many other things, but this is not the point of this post! .

    JohnnyMalaria: Could you find anything on the version of my files?
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!