Firewire IEEE 1394 Interface

Desktop

Desktop
Desktop computer Forums (Audio, General Hardware, Video)

Firewire IEEE 1394 Interface

This question is not answered

I recently purchased a new Dell XPS 8700 (top-or-the-range model) with Windows 8 (Standard 64-bit). When I ordered the machine I realised that it did not have a Firewire output but mistakenly believed it was just a matter of inserting the appropriate card.

I have spent a couple of days trawling the internet for information. It seems that the relevant legacy drivers have been removed from Windows 8, but may possibly be re-installed from Windows 7 64-bit. However, I am confused about whether there is a suitable PCI slot for a card and, if so, what card I should obtain. If no spare slot is provided, can I remove the audio card and replace it with an IE1394 card?

This issue is important to me because I use a £1,000 Nikon 4000ED slide scanner (Firewire output only) so that I can utilise a huge library of film-based 35mm images. However, a scan of the forums reveals that countless other people are also frustrated by the decision to drop support for Firewire.

Please can anyone help me find a solution to this?

All Replies
  • Hi Traveller417,

    There are 2 PCIe x1, 1 PCIe x4 and 1 mini PCIe slot in the system. You may use any of these slots to install an IEEE 1394 card for firewire. As far as driver for the card is concerned it should either be provided by the manufacturer with the card in a disk or you may install it directly from card manufacturer’s website.

    You may check the following link for the options: http://bit.ly/18tB8qy. For Owner’s Manual, you may refer to the link: http://bit.ly/12kXKAS.

    Please feel free to reply for any further questions. I will be glad to assist you. 

    Thanks & Regards
    Amogh G
    #iworkfordell
    To know more about Dell Product Support, Drivers & Downloads, Order & Dispatch status -> choose your region USAIndia. For helpful Dell Support Videos, you may click Here

  • Syba makes one that works.  SD PEX30009  TI Chipset

    Best Buy SKU: 1306938523

    Directx June 2010 would need to be added back to windows vista/7/8

    www.microsoft.com/.../details.aspx

    PCI\VEN_104C&DEV_8025 = Texas Instruments 1394 OHCI Compliant Host Controller

    www.sybausa.com/productInfo.php

    Syba Low Profile PCI-Express 1394b/1394a (2B1A) Card, TI Chipset, Extra Regular Bracket SD-PEX30009

    DRIVER For Windows XP, Server 2003, Vista, Server 2008 & Windows 7

    www.sybausa.com/.../SD-PEX30009.zip

       Ports:

           2x 1394B firewire ports

           1x 1394A firewire port

           1x 1394A firewire internal header (Shared Port)

       1-Lane (x1) PCI-Express with transfer rate 2.5Gbps Full Duplex channel

       Compliant with PCI-Express Revision 1.0a

       Support provisions of IEEE Standard P1394b-2002

       Compliant with 1394 Open Host Controller Interface (OHCI) specification Revision 1.1 and 1.2 draft

       Support 800 / 400 / 200 / 100Mbps transfer rate

       Fully Plug & Play and Hot Plug supported

       Fully backward compatible to 1394a specification

       Compliant with IEEE 1394a-2000 and 1394-1995 standard for a High-Performance Serial Bus

       Fully interoperable with Firewire™, iLink™ and SB1394™ implementation of IEEE 1394 standard

       Equipped with Bidirectional  IEEE Standard 1394b-2002 ports for 800Mbps data transfer

    ;    o1394b.inf --

    ;

    ;    This file contains installation information for

    ;    OrangeWare 1394b boards.

    ;

    ;    Copyright (c) 2003 - 2005 OrangeWare Corporation

    [Version]

    LayoutFile=Layout.inf, Layout1.inf, Layout2.inf

    signature="$CHICAGO$"

    Class=1394

    ClassGUID={6BDD1FC1-810F-11D0-BEC7-08002BE2092F}

    Provider=%OWC%

    DriverVer=2/15/2005,1.02.0000.2

    [Manufacturer]

    %OWC%=OWC

    %ORANGEMFG%=ORANGE

    %BELKINMFG%=BELKIN

    %SPEEDDRAGONMFG%=SPEEDDRAGON

    [OWC]

    %PCI\VEN_104C&DEV_8025&SUBSYS_702A14DB.DeviceDesc%=OW1394B,PCI\VEN_104C&DEV_8025&SUBSYS_702A14DB

    %PCI\VEN_104C&DEV_8025&SUBSYS_131418AB.DeviceDesc%=OW1394B,PCI\VEN_104C&DEV_8025&SUBSYS_131418AB

    %PCI\VEN_104C&DEV_8025&SUBSYS_38840EE4.DeviceDesc%=OW1394B,PCI\VEN_104C&DEV_8025&SUBSYS_38840EE4

    %PCI\VEN_104C&DEV_8025&SUBSYS_31101409.DeviceDesc%=OW1394B,PCI\VEN_104C&DEV_8025&SUBSYS_31101409

    [ORANGE]

    %PCI\VEN_104C&DEV_8025&SUBSYS_804012EE.DeviceDesc%=OW1394B,PCI\VEN_104C&DEV_8025&SUBSYS_804012EE

    [BELKIN]

    %PCI\VEN_104C&DEV_8025&SUBSYS_06231799.DeviceDesc%=OW1394B,PCI\VEN_104C&DEV_8025&SUBSYS_06231799

    [SPEEDDRAGON]

    %PCI\VEN_104C&DEV_8025&SUBSYS_00051592.DeviceDesc%=OW1394B,PCI\VEN_104C&DEV_8025&SUBSYS_00051592

    %PCI\VEN_104C&DEV_8025&SUBSYS_00061592.DeviceDesc%=OW1394B,PCI\VEN_104C&DEV_8025&SUBSYS_00061592

    [OW1394B]

    CopyFiles=  OW1394B.CopyFiles

    Include=    1394.inf

    Needs=      OHCI.Device

    [OW1394B.NT]

    CopyFiles=  OW1394B.CopyFiles.NT

    Include=    1394.inf

    Needs=      ClassInstall32,GENERIC_Install

    ;;----------------------------------------

    ;;

    [OW1394B.Addreg]

    HKR,,"UpperFilters",0x00010000,"o1394b.sys" ;| 8 = REG_MULTI_SZ value // also, append to existing list, if any

    [OW1394B.HW]

    AddReg=OW1394B.Addreg

    [OW1394B.CopyFiles]

    o1394b.sys

    ;;----------------------------------------

    ;;----------------------------------------

    ;; 2k and XP

    [OW1394B.HW.AddReg]

    HKR,,"UpperFilters",0x00010000,"o1394b" ;| 8 = REG_MULTI_SZ value // also, append to existing list, if any

    [OW1394B.NT.HW]

    AddReg = OW1394B.HW.AddReg

    [OW1394B.NT.Services]

    AddService= O1394B,0,OW1394B.AddService

    Include=    1394.inf

    Needs=      GENERIC_Install.NT.Services

    [OW1394B.AddService]

    DisplayName    = %O1394bBF.SvcDesc%

    ServiceType    = 1              ;SERVICE_KERNEL_DRIVER

    StartType      = 0                    ;SERVICE_AUTO_START;SERVICE_DEMAND_START

    ErrorControl   = 1              ;SERVICE_ERROR_NORMAL

    ServiceBinary  = %12%\o1394b.sys

    ;LoadOrderGroup = PnP Filter

    [OW1394B.CopyFiles.NT]

    o1394b.sys

    ;;----------------------------------------

    [DestinationDirs]

    OW1394B.CopyFiles = 10,SYSTEM32\DRIVERS

    OW1394B.CopyFiles.NT = 12

    OW1394B.DelFiles.Ext = 10,SYSTEM32\DRIVERS

    [Strings]

    OWC="OrangeWare Corporation"

    ORANGEMFG = "Orange Micro, Inc."

    BELKINMFG = "Belkin"

    SPEEDDRAGONMFG = "Speed Dragon Multimedia Ltd."

    PCI\VEN_104C&DEV_8025&SUBSYS_131418AB.DeviceDesc="OHCI IEEE 1394b Host Controller"

    PCI\VEN_104C&DEV_8025&SUBSYS_804012EE.DeviceDesc="Orange Micro OrangeLink OHCI IEEE 1394b Host Controller"

    PCI\VEN_104C&DEV_8025&SUBSYS_702A14DB.DeviceDesc="OHCI IEEE 1394b Host Controller"

    PCI\VEN_104C&DEV_8025&SUBSYS_38840EE4.DeviceDesc="OHCI IEEE 1394b Host Controller"

    PCI\VEN_104C&DEV_8025&SUBSYS_31101409.DeviceDesc="1394B Host Controller"

    PCI\VEN_104C&DEV_8025&SUBSYS_06231799.DeviceDesc="FireWire 800 PCI Card"

    PCI\VEN_104C&DEV_8025&SUBSYS_00051592.DeviceDesc="1394b 32-Bit PCI Host Controller Card"

    PCI\VEN_104C&DEV_8025&SUBSYS_00061592.DeviceDesc="1394b 64-Bit PCI Host Controller Card"

    PCI\CC_0C0010.DeviceDesc="Generic OHCI 1394 Host Controller with 1394b Driver Support"

    O1394bBF.SvcDesc = "OW 1394b Bus Filter Service"

    Report Unresolved Customer Service Issues here:

    Dell - Unresolved Customer Service Issues

    I do not work for Dell. I too am a user.

    The forum is primarily user to user, with Dell employees moderating.

  • Many thanks for your reply - which is very helpful. Incidentally, I have the D00X8714 model rather than the Special Edition - I hope the PCI slots are the same as you described. That seems to be confirmed within the Owner's Manual. Thanks for the links.

    Looking at the list of PCI-E cards, only two actually state that they are compatible with Windows 8, although I guess others may also be compatible. Both those that mention Windows 8 use the Ti chipset. How does one choose the right product? Is it a matter of a suitable mechanical fit? I note the 4 PCI slots in the XPS 8700 seem to have various size connectors.

  • Thank yo for both the previous posts. I appreciate all the assistance. I have spoken with Syba and they confirm that the SD PEX30009  TI Chipset does work with Windows 8. The drivers are also provided.

    My question is why do I need to reload DirectX?

  • Directx 9 and 10 are removed from Vista / 7 / 8 and older software uses this interface.

    You download the patch and extract into a folder then run the DXSETUP.EXE file.

    If your software is not Directshow 11 compatible it will not work for video editing.

    The max Directx driver for XP is Directx 9.0c  The June 2010 patch puts back the drivers that were removed including the DX9 and DX10 directshow filters.

    Compatibility mode wont work if the underlying drivers are not there.

    DirectX versionVersion numberOperating systemDate released
    DirectX 1.0 4.02.0095 September 30, 1995
    DirectX 2.0 Was shipped only with a few 3rd party applications 1996
    DirectX 2.0a 4.03.00.1096 Windows 95 OSR2 and NT 4.0 June 5, 1996
    DirectX 3.0 4.04.00.0068   September 15, 1996
    4.04.00.0069 Later package of DirectX 3.0 included Direct3D 4.04.00.0069 1996
    DirectX 3.0a 4.04.00.0070 Windows NT 4.0 SP3 (and above)
    last supported version of DirectX for Windows NT 4.0
    December 1996
    DirectX 3.0b 4.04.00.0070 This was a very minor update to 3.0a that fixed a cosmetic problem with the Japanese version of Windows 95 December 1996
    DirectX 4.0 Never launched
    DirectX 5.0 4.05.00.0155 (RC55) Available as a beta for Windows 2000 that would install on Windows NT 4.0 August 4, 1997
    DirectX 5.2 4.05.01.1600 (RC00) DirectX 5.2 release for Windows 95 May 5, 1998
    4.05.01.1998 (RC0) Windows 98 exclusive June 25, 1998
    DirectX 6.0 4.06.00.0318 (RC3) Windows CE as implemented on Dreamcast August 7, 1998
    DirectX 6.1 4.06.02.0436 (RC0) February 3, 1999
    DirectX 6.1a 4.06.03.0518 (RC0) Windows 98 SE exclusive May 5, 1999
    DirectX 7.0 4.07.00.0700 (RC1) September 22, 1999
    4.07.00.0700 Windows 2000 February 17, 2000
    DirectX 7.0a 4.07.00.0716 (RC0) March 8, 2000
    4.07.00.0716 (RC1) 2000
    DirectX 7.1 4.07.01.3000 (RC1) Windows Me exclusive September 14, 2000
    DirectX 8.0 4.08.00.0400 (RC10) November 12, 2000
    DirectX 8.0a 4.08.00.0400 (RC14) Last supported version for Windows 95 February 5, 2001
    DirectX 8.1 4.08.01.0810 Windows XP, Windows XP SP1, Windows Server 2003 and Xbox exclusive October 25, 2001
    4.08.01.0881 (RC7) This version is for the down level operating systems
    (Windows 98, Windows Me and Windows 2000)
    November 8, 2001
    DirectX 8.1a 4.08.01.0901 (RC?) This release includes an update to Direct3D (D3d8.dll) 2002
    DirectX 8.1b 4.08.01.0901 (RC7) This update includes a fix to DirectShow on Windows 2000 (Quartz.dll) June 25, 2002
    DirectX 8.2 4.08.02.0134 (RC0) Same as the DirectX 8.1b but includes DirectPlay 8.2 2002
    DirectX 9.0 4.09.00.0900 (RC4) December 19, 2002
    DirectX 9.0a 4.09.00.0901 (RC6) March 26, 2003
    DirectX 9.0b 4.09.00.0902 (RC2) August 13, 2003
    DirectX 9.0c 4.09.00.0903 Windows XP SP2 exclusive
    4.09.00.0904 (RC0) August 4, 2004
    4.09.00.0904 Windows XP SP2, SP3*, Windows Server 2003 SP1 and Windows Server 2003 R2 August 6, 2004 / April 21, 2008*
    DirectX - bimonthly updates 4.09.00.0904 (RC0 for DX 9.0c) The February 9, 2005 release is the first 64-bit capable build.[12] The last build for Windows 98SE/Me is the redistributable from December 13, 2006.[13] The last build for Windows 2000 is the redistributable from February 5, 2010.[14] April 2006 is the first official support to Windows Vista[15] and August 2009 is the first official support to Windows 7 and DX11 update[16] Released bimonthly from October 2004 to August 2007, and quarterly thereafter; Latest version: June 2010[17]
    DirectX 10 6.00.6000.16386 Windows Vista exclusive November 30, 2006
    DirectX 10.1 6.00.6001.18000 Windows Vista SP1, Windows Server 2008
    includes Direct3D 10.1
    February 4, 2008
    DirectX 10.1 6.00.6002.18005 Windows Vista SP2, Windows Server 2008 SP2
    includes Direct3D 10.1
    April 28, 2009
    DirectX 11 6.01.7600.16385 Windows 7, Windows Server 2008 R2 October 22, 2009
    6.00.6002.18107 Windows Vista SP2 and Windows Server 2008 SP2, through the Platform Update for Windows Vista and Windows Server 2008[18] October 27, 2009
    6.01.7601.17514 Windows 7 SP1, Windows Server 2008 R2 SP1 February 16, 2011
    DirectX 11.1 6.02.9200.16384 Windows 8, Windows RT, Windows Server 2012 August 1, 2012
    DirectX 11.2 Windows 8.1, Windows RT, Windows Server 2012 R2


    Report Unresolved Customer Service Issues here:

    Dell - Unresolved Customer Service Issues

    I do not work for Dell. I too am a user.

    The forum is primarily user to user, with Dell employees moderating.

  • I thought it worth posting the solution I have achieved - although thanks to the support of several other people!

    I bought a Syba SD-PEX30009 as suggested above (although it turned out to be faulty and had to be replaced) and installed it in my new Windows 8 PC. Everything worked straight away. No need to install a driver - Windows 8 did this automatically, and no need to load DirectX.

    Having installed Vuescan in place of the standard (and now incompatible with Windows 8) Nikon software, my Nikon Coolscan 4000ED works normally.

    Hopefully this solution may be of use to someone in the future - thank you for all the replies.

  • I just found this and I must also try it: 

    raveller417

    I recently purchased a new Dell XPS 8700 (top-or-the-range model) with Windows 8 (Standard 64-bit). When I ordered the machine I realised that it did not have a Firewire output but mistakenly believed it was just a matter of inserting the appropriate card.

    I have spent a couple of days trawling the internet for information. It seems that the relevant legacy drivers have been removed from Windows 8, but may possibly be re-installed from Windows 7 64-bit. However, I am confused about whether there is a suitable PCI slot for a card and, if so, what card I should obtain. If no spare slot is provided, can I remove the audio card and replace it with an IE1394 card?

    This issue is important to me because I use a £1,000 Nikon 4000ED slide scanner (Firewire output only) so that I can utilise a huge library of film-based 35mm images. However, a scan of the forums reveals that countless other people are also frustrated by the decision to drop support for Firewire.

    Please can anyone help me find a solution to this?

    Home > Articles Menu > Fixing Slow Firewire Transfers

    Fixing Firewire Problems in Windows 7

    After installing Windows 7 on both 64 bit and 32 bit systems, we ran into a problem using Adobe Premiere, we couldn’t import video into the computer via the Firewire port anymore. 


    At first we thought this was a compatibility problem between Windows 7 and Adobe, but we quickly ruled that out when another program also had problems using the Firewire port.

    The problem was with the new Windows 7 Firewire driver (a.k.a. the 1394 Driver) and the fix was a simple one. Replace the new 1394 driver with the Legacy driver that comes with Windows 7.

    Below is the step by step instructions on how to install the Legacy driver so you won‘t have any problems either: 

    Click Start

    Then click on Control Panel

    Click on Device Manager

    Note: If you don’t see Device Manager listed, click on View By: Category on the top right side of the
        Control Panel Window.
        Then Click on Large Icons
        You should now have a list of items in the Control Panel and click on Device Manager.

    Under the Device Manager, look down the list for IEEE 1394 Bus Host Controllers and Double Click on it.

    It should display something like - 1394 OHCI Compliant Host Controller

       Note: If it has the word (Legacy) behind it, you are already setup and you can just exit out.

    Next, double click on the 1394 OHCI Compliant Host Controller

    A window will popup saying 1394 OHCI Compliant Host Controller Properties

    Click on the Driver Tab

    Then look down in the widow and click on Update Driver

    Then select - Browse my computer for driver software

    Next select - Let me pick from a list of device drivers on my computer

    It will bring up a list of drivers.

    Click on 1394 OHCI Compliant Host Controller (Legacy)

        NOTE: It is important that you select the one with (Legacy) after it, just like shown above.

    Then click Next

    Once it installs the 1394 OHCI Compliant Host Controller (Legacy),
    it will say Windows has successfully updated your driver software.

    Click on the Close button and exit out of all of the other windows.

    Then Reboot your computer.

    You will now be able to import video via the Firewire port on your computer.

    If you are still having a problem importing video after you have switched the Firewire driver to Legacy, then the problem may be with the Firewire port.  This is a common problem.  The Firewire port will work with an external driver, but it won't let you import video from your video camera.  Most people report this problem with Dell computer, but it does happen with other brands, even brand new computers.  This problem is usually with the Firewire port that is built into the motherboard.

    The fix is simple:
    1.  Install a Firewire card into one of the open slots in the computer
    2.  Using the instructions above, set the drive to Legacy.
    3.  Reboot the computer.
    4.  Then connect the Firewire cable from the video camera, into the new Firewire port that you just added.

    This fixes the problem 99% of the time.  Firewire cards are not the expensive, they run from $10 and up, depending on any extra features the card may have.

    NOTE:  We have noticed that when Microsoft has issued certain updates, it can cause Windows 7 to switch back to use the original 1394 OHCI Compliant Host Controller driver.  If you notice the Firewire device is transferring slowly again just repeat the above steps and reinstall the Legacy driver."

  • Thank you for the information.

    Just purchased a XPS special edition (windows 7) and need a firewire for my canon HV20. Which slot did you use to install the firewire?  Thanks again!

  • Hi,

    My XPS had three PCI-E slots - two small (narrow) connectors and one wider one. My IEEE1394 card fitted the narrower slots but one of these was physically obstructed by heat sinks etc - on the graphics card (I think). There was therefore only one slot I could use and everything worked fine.

    Incidentally, I was advised by the manufacturer of the firewire card to ignore all the advice about installing legacy drivers etc - although I am using Windows 8. The OS found the correct driver without any problem and the card worked as soon as it was installed.