Microsoft 1394 Driver

Posted on  by



  1. Microsoft 1394 Driver Windows 7
  2. Wireless Comfort Desktop 5000 | Device Downloads | Microsoft ..
  3. See Full List On Docs.microsoft.com
Microsoft-->

Overview of the IEEE 1394 bus technology.

To develop IEEE 1394 bus, you need these headers:

For the programming guide, see IEEE 1394 bus.

Microsoft 1394 Driver Windows 7

  1. Expand IEEE 1394 Bus host controllers, and then locate the host controller. Right-click the host controller, and then click Update Driver Software. The screen shot of the host controller and the Update Driver Software is listed in the following example: Click Browse my computer for driver software.
  2. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the 'Applies to' section. More Information. For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base.
  3. Microsoft 1394 Drivers Download. In our share libs contains the list of Microsoft 1394 drivers available for download. To download the proper driver by vender name. If not found in our garage driver you need, please contact us, we will help you in time, and updates to our website.
Microsoft 1394 Driver

IOCTLs

TitleDescription
IOCTL_1394_CLASSAn IEEE 1394 driver uses the IRP_MJ_INTERNAL_DEVICE_CONTROL IRP, with IoControlCode IOCTL_1394_CLASS, to communicate with the bus driver. The driver has access to all operations provided by the IEEE 1394 bus and its host controller through this request.
IOCTL_61883_CLASSAn IEC-61883 client driver uses the IRP_MJ_INTERNAL_DEVICE_CONTROL IRP with IoControlCode IOCTL_61883_CLASS to communicate with 1394 driver stack using the IEC-61883 protocol.

Now download the Microsoft Firewire 1394 OHCI Legacy Driver Installer and remember where you downloaded the file to. Then once you have downloaded the installer, follow the instructions below. Microsoft Firewire 1394 OHCI Legacy Driver. Find where you downloaded the file to. It will have the filename 1394OHCILegacyDriver.msi as shown above.

SCS.4DJ - there are 1 drivers found for the selected device, which you can download from our website for free. Select the driver needed and press download. Free download - eMPIA USB 2.0 Video Devices EM28xx Drivers v.5.2009.1202.0 for Windows XP, Windows Vista, Windows 7 32-bit (x86), 64-bit (x64). Download FTDI FTD2XX USB Drivers - latest version for Windows. FTDI FTD2XX USB Drivers installs the necessary files in your Windows directory. After installation, Windows will detect the USB. Application software can access the USB device through a series of. This software is provided by Future Technology Devices International Limited ``as is. Drivers SCS USB devices.

Enumerations

Wireless Comfort Desktop 5000 | Device Downloads | Microsoft ..

TitleDescription
CMP_CONNECT_TYPEThis enumeration specifies a connection type.
CMP_PLUG_LOCATIONThis enumeration specifies the location of a plug.
CMP_PLUG_TYPEThis enumeration specifies the type of a plug.

Functions

TitleDescription
PBUS_RESET_ROUTINEThis is a caller-supplied function to be called by the protocol driver when the 1394 bus is reset.
PCMP_MONITOR_ROUTINEThis routine is called for plug monitoring.
PCMP_NOTIFY_ROUTINEThis routine is called for plug notification.

Structures

TitleDescription
ADDRESS_FIFOThe ADDRESS_FIFO structure is an entry in a singly-linked list of MDLs used by the REQUEST_ALLOCATE_ADDRESS_RANGE IEEE 1394 bus request.
ADDRESS_OFFSETThe ADDRESS_OFFSET structure specifies the 48-bit address within a device's IEEE 1394 address space.
ADDRESS_RANGEThe ADDRESS_RANGE structure describes a range in a IEEE 1394 device's address space.
AV_61883_REQUESTThe AV_61883_REQUEST structure is used to pass requests to the IEC-61883 protocol driver.
AV_PCRThe AV_PCR structure specifies settings for an input or output plug.
BUS_GENERATION_NODEThe BUS_GENERATION_NODE structure is used in conjunction with the Av61883_GetUnitInfo request to retrieve bus characteristics.
BUS_RESET_DATAThe BUS_RESET_DATA structure specifies the context for the extended bus reset notification routine.
BUS_RESET_NOTIFYThis structure is used to register or deregister the PBUS_RESET_ROUTINE callback.
CIP_ATTACH_FRAMEThis structure is used in an attach frame request.
CIP_CANCEL_FRAMEThe request cancels an attached frame buffer. A frame can be canceled while the stream is running.
CIP_DATA_FORMAT_VER2This structure is a CIP data format which is used by CMP_CONNECT_VER2.
CIP_DATA_FORMAT_VER3This structure is used by CipDataFormat.
CIP_FRAMEThe CIP_FRAME structure describes a frame to be attached to an input or output plug.
CIP_LISTENThis structure is used for a listen request. The request begins isochronous reception on the specified connection.
CIP_NOTIFY_INFOThe CIP_NOTIFY_INFO structure contains information about the frame.
CIP_STOPThis structure is used to stop transmission or reception.
CIP_TALKThis structure is used to begin transmission.
CIP_VALIDATE_INFOThe CIP_VALIDATE_INFO structure contains information about the frame.
CMP_CONNECT_VER2This structure contains information for a connection request. The request attempts to make a connection to a plug control register on the local host.
CMP_CONNECT_VER3This structure contains information for a connection request.
CMP_CREATE_PLUGThis structure is used to create a plug.
CMP_DELETE_PLUGThis structure is used to delete a plug.Av61883_CreatePlug.
CMP_DISCONNECTThis structure is used to break a connection.
CMP_GET_PLUG_HANDLEThis structure is used in getting the handle of a plug.
CMP_GET_PLUG_STATEThis structure is used in getting the state of a plug.
CMP_MONITOR_INFOThe CMP_MONITOR_INFO structure is used in conjunction with the Av61883_MonitorPlugs request to allow a driver to monitor access to local oPCR and iPCR plugs.
CMP_MONITOR_PLUGSThis structure is used to monitor plug access. The request allows a driver to monitor all access to local oPCR and iPCR plugs.
CMP_NOTIFY_INFOThis structure is used by the PCMP_NOTIFY_ROUTINE callback.
CMP_SET_PLUGThis structure is used to assign settings to a plug.
CONFIG_ROMThe CONFIG_ROM structure is used to contain the first 24 bytes of an IEEE 1394 device's configuration ROM.
CYCLE_TIMEThe CYCLE_TIME structure contains the IEEE 1394 isochronous cycle time.
FCP_FRAMEThe FCP_FRAME structure describes a function control protocol (FCP) request.
FCP_GET_REQUESTThis structure is used for a get request.
FCP_REQUESTThis structure is used for a send request.
FCP_RESPONSEThe structure is used in a request yjsy retrieves the next FCP response from the queue of requests maintained by the IEC-61883 protocol driver.
FCP_SEND_RESPONSEThis structure is used for a send response.
GET_LOCAL_HOST_INFO1The GET_LOCAL_HOST_INFO1 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request using u.GetLocalHostInformation.nLevel GET_HOST_UNIQUE_ID.
GET_LOCAL_HOST_INFO2The GET_LOCAL_HOST_INFO2 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request using u.GetLocalHostInformation.nLevel GET_HOST_CAPABILITIES.
GET_LOCAL_HOST_INFO3The GET_LOCAL_HOST_INFO3 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request using u.GetLocalHostInformation.nLevel = GET_POWER_SUPPLIED.
GET_LOCAL_HOST_INFO4The GET_LOCAL_HOST_INFO4 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request using u.GetLocalHostInformation.nLevel = GET_PHYS_ADDR_ROUTINE.
GET_LOCAL_HOST_INFO5The GET_LOCAL_HOST_INFO5 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request using u.GetLocalHostInformation.nLevel = GET_HOST_CONFIG_ROM.
GET_LOCAL_HOST_INFO6The GET_LOCAL_HOST_INFO6 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request using u.GetLocalHostInformation.nLevel = GET_HOST_CSR_CONTENTS.
GET_LOCAL_HOST_INFO7_W2KThe GET_LOCAL_HOST_INFO7 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request with u.GetLocalHostInformation.nLevel set to GET_HOST_DMA_CAPABILITIES.
GET_LOCAL_HOST_INFO7_WXPThe GET_LOCAL_HOST_INFO7 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request with u.GetLocalHostInformation.nLevel set to GET_HOST_DMA_CAPABILITIES.
GET_LOCAL_HOST_INFO8The GET_LOCAL_HOST_INFO8 structure contains the data returned by a REQUEST_GET_LOCAL_HOST_INFO request with u.GetLocalHostInformation.nLevel set to GET_HOST_DDI_VERSION.
GET_UNIT_CAPABILITIESThe GET_UNIT_CAPABILITIES structure is used in conjunction with the Av61883_GetUnitInfo request to retrieve unit information about a device's capabilities.
GET_UNIT_IDSThe GET_UNIT_CAPABILITIES structure is used in conjunction with the Av61883_GetUnitInfo request to retrieve device identifiers.
GET_UNIT_INFOThis structure is used to get unit information.
IO_ADDRESSThe IO_ADDRESS structure specifies the 1394 64-bit destination address for read, write and lock operations.
IPCRThe IPCR structure contains initialization values for an input plug.
IRBDrivers use this structure to pass most requests to IEEE 1394 bus driver.
IRB_REQ_ALLOCATE_ADDRESS_RANGEThis structure contains the fields necessary for the 1394 stack to carry out a request to allocate an address range.
IRB_REQ_ASYNC_LOCKThis structure contains the fields necessary for the 1394 stack to carry out an asychronous lock request.
IRB_REQ_ASYNC_READThis structure contains the fields necessary for the 1394 stack to carry out an asynchronous read request.
IRB_REQ_ASYNC_STREAMThis structure contains the fields necessary for the 1394 bus driver to carry out an asynchronous write request.
IRB_REQ_ASYNC_WRITEThis structure contains the fields necessary for the 1394 stack to carry out an asynchronous write request.
IRB_REQ_BUS_RESETThis structure contains the fields necessary for the 1394 bus driver to create a bus reset request.
IRB_REQ_BUS_RESET_NOTIFICATIONThis structure contains the fields necessary for the 1394 bus driver to carry out a bus reset notification request.
IRB_REQ_CONTROLThis structure contains the fields necessary for the 1394 bus driver to carry out a control request.
IRB_REQ_FREE_ADDRESS_RANGEThis structure contains the fields necessary for the 1394 stack to carry out a free address range reqeust.
IRB_REQ_GET_1394_ADDRESS_FROM_DEVICE_OBJECTThis structure contains the fields necessary to carry out a Get1394AddressFromDeviceObject request.
IRB_REQ_GET_CONFIG_ROMThis structure contains the fields necessary for the bus driver to carry out a GetConfigRom request.
IRB_REQ_GET_CONFIGURATION_INFORMATIONThis structure contains the fields necessary for the 1394 bus driver to carry out a GetConfigurationInformation request.
IRB_REQ_GET_GENERATION_COUNTThis structure contains the fields necessary for the 1394 bus driver to carry out a GetGenerationCount request.
IRB_REQ_GET_LOCAL_HOST_INFORMATIONThis structure contains the fields necessary for the 1394 bus driver to carry out a GetLocalHostInformation request.
IRB_REQ_GET_MAX_SPEED_BETWEEN_DEVICESThis structure contains the fields necessary in order for the Bus driver to carry out a GetMaxSpeedBetweenDevices request.
IRB_REQ_GET_SPEED_TOPOLOGY_MAPSThis structure contains the fields necessary for the 1394 bus driver to carry out a GetSpeedTopologyMaps request.
IRB_REQ_ISOCH_ALLOCATE_BANDWIDTHThis structure contains the fields necessary in order for the Bus driver to carry out an IsochAllocateBandwidth request.
IRB_REQ_ISOCH_ALLOCATE_CHANNELThis structure contains the fields necessary in order for the 1394 bus driver to carry out an IsochAllocateChannel request.
IRB_REQ_ISOCH_ALLOCATE_RESOURCES_W2KThis structure contains the fields necessary for the 1394 bus driver to carry out a IsochAllocateResources request.
IRB_REQ_ISOCH_ALLOCATE_RESOURCES_WXPThis structure contains the fields necessary for the 1394 bus driver to carry out a IsochAllocateResources request.
IRB_REQ_ISOCH_ATTACH_BUFFERSThis structure contains the fields required for the 1394 bus driver to carry out a IsochAttachBuffers request.
IRB_REQ_ISOCH_DETACH_BUFFERSThis structure contains the fields required to carry out a IsochDetachBuffers request.
IRB_REQ_ISOCH_FREE_BANDWIDTHThis structure contains the fields necessary in order for the Bus driver to carry out an IsochFreeBandwidth request.
IRB_REQ_ISOCH_FREE_CHANNELThis structure contains the fields required to carry out a IsochFreeChannel request.
IRB_REQ_ISOCH_FREE_RESOURCESThis structure contains the fields necessary to carry out a IsochFreeResources request.
IRB_REQ_ISOCH_LISTENThis structure contains the fields necessary to carry out a ReqIsochListen request.
IRB_REQ_ISOCH_MODIFY_STREAM_PROPERTIESThis structure contains the fields necessary for the Bus driver to carry out an IsochModifyStreamProperties request.
IRB_REQ_ISOCH_QUERY_CURRENT_CYCLE_TIMEThis structure contains the fields necessary for the Bus driver to carry out an IsochQueryCurrentCycleTime request.
IRB_REQ_ISOCH_QUERY_RESOURCESThis structure contains the fields necessary to carry out a IsochQueryResources request.
IRB_REQ_ISOCH_SET_CHANNEL_BANDWIDTHThis structure contains the fields necessary for the Bus driver to carry out an IsochSetChannelBandwidth request.
IRB_REQ_ISOCH_STOPThis structure contains the field necessary to carry out a IsochStop request.
IRB_REQ_ISOCH_TALKThis structure contains the field necessary to carry out a IsochTalk request.
IRB_REQ_RECEIVE_PHY_PACKETSThis structure contains the fields necessary to carry out a ReceivePhyPackets request.
IRB_REQ_SEND_PHY_CONFIGURATION_PACKETThis structure contains the fields necessary to carry out a SendPhyConfigurationPacket request.
IRB_REQ_SEND_PHY_PACKETThis structure contains the fields necessary to carry out a SendPhyPacket request.
IRB_REQ_SET_DEVICE_XMIT_PROPERTIESThis structure contains the fields necessary to carry out a SetDeviceXmitProperties request.
IRB_REQ_SET_LOCAL_HOST_PROPERTIESThis structure contains the fields required to carry out a SetLocalHostProperties request.
ISOCH_DESCRIPTORThe ISOCH_DESCRIPTOR structure describes a buffer to be attached or detailed from a resource handle, using the REQUEST_ISOCH_ATTACH_BUFFERS and REQUEST_ISOCH_DETACH_BUFFERS requests.
NODE_ADDRESSThe NODE_ADDRESS structure specifies the 10-bit bus number and 6-bit node number that serve as the node address for a 1394 node.
NOTIFICATION_INFO_W2KThe bus driver passes NOTIFICATION_INFO to pass information to the driver-provided notification routine for a driver-allocated address range in the computer's IEEE 1394 address space.
NOTIFICATION_INFO_WXPThe bus driver passes NOTIFICATION_INFO to pass information to the driver-provided notification routine for a driver-allocated address range in the computer's IEEE 1394 address space.
OPCRThe OPCR structure contains initialization values for an output plug.
PHY_CONFIGURATION_PACKETThe PHY_CONFIGURATION_PACKET structure contains a raw PHY configuration packet.
SELF_IDThe SELF_ID structure contains a raw packet zero self-ID packet. See the IEEE 1394 Trade Association specification website for details.
SELF_ID_MOREThe SELF_ID_MORE structure contains a raw packet one, two, or three self-ID packet. See the IEEE 1394 specification for details.
SET_CMP_ADDRESS_TYPEThe SET_CMP_ADDRESS_TYPE structure is used in conjunction with the Av61883_SetUnitInfo request to set the parameters that the IEC-61883 protocol driver should use when capturing and transmitting isochronous packets.
SET_FCP_NOTIFYThis structure is used for FCP notification.
SET_LOCAL_HOST_PROPS2SET_LOCAL_HOST_PROPS2 sets a lower bound on the value the bus will use for its gap count.
SET_LOCAL_HOST_PROPS3SET_LOCAL_HOST_PROPS3 contains the data necessary for defining or identifying one or more unit directories in the Configuration ROM of a 1394 Host Controller.
SET_UNIT_DIRECTORYThis structure is used to assign settings for a unit directory.
SET_UNIT_INFOThis structure is used to set unit information.
SPEED_MAPThe SPEED_MAP structure is stores a IEEE 1394 bus speed map.
TEXTUAL_LEAFThe TEXTUAL_LEAF structure describes the device description that can be stored in the Configuration ROM of devices that satisfy the PC 98 or PC 99 specifications.
TOPOLOGY_MAPThe TOPOLOGY_MAP structure is used to store an IEEE 1394 bus topology map. The relations between devices are found in the port members of the entries in TOP_Self_ID_Array.
UNIT_DDI_VERSIONThe UNIT_DDI_VERSION structure is used in conjunction with the Av61883_GetUnitInfo request to retrieve the current 61883 DDI version.
UNIT_DIAG_LEVELThe UNIT_DDI_VERSION structure is used in conjunction with the Av61883_GetUnitInfo request to retrieve the current diag level
UNIT_ISOCH_PARAMSThe UNIT_ISOCH_PARAMS structure is used to get or set the parameters that the IEC-61883 protocol driver uses when capturing or transmitting isochronous packets.

See Full List On Docs.microsoft.com

Overview

Is Firewire IEEE 1394 still supported by Windows 10 ..1394

ubCore™, is the first and only driver suite that fully supports the 1394b standard. It is highly recommended by Texas Instruments as the ideal software companion for their 1394b chipset.

ubCore™ is a set of low-level drivers with a top-down layered structure that provides the physical interface to various 1394 devices and includes the following advantageous features:

  • Full 1394b support at 800Mbps.
  • Support for future standard speeds (S1600 and S3200).
  • Full 1394b CAT5 (100/400 Mbps) and POF (200 Mbps) support.
  • Full 1394b GOF support at 800 Mbps speeds.
  • Complete 1394a and 1394b SBP2 disk support.
  • Complete support of 1394a and 1394b IIDC compliant cameras.
  • Comprehensive set of tools and applications.
  • Full Plug & Play support for Windows 2000/XP/2003-8 Server/Vista/7/8/10.
  • Support for 64 bit Windows Operating Systems (AMD64 and Intel EM64t CPUs).
  • Microsoft signed drivers for Windows Vista/7/8 32 bit and 64 bit.
  • User friendly installation wizard.

ubCore™ combined with FireAPI™ (Unibrain’s 1394 Development Toolkit), provides to the software developer a powerful set of functions and tools that enables him to integrate 1394 technology into his product.

Features

ubCore™ drivers come into 2 “flavors” (versions): ‘ubCore’ and ‘ubCore Pro‘.
ubCore™ is oriented for end users who want to utilize the full Firewire-800 speed of their 1394b devices (webcams, firewire hard drives, networking) and it is available as a free download, while ubCore Pro™ is oriented for professional users and FireAPI™ SDK customers.
ubCore Pro™ is not free; a FireAPI license is required for it’s full features and applications to be activated.
The same license is also required so that applications developed with FireAPI SDK, will execute in runtime systems.

Versions

IIDC firewire cameras support

Qualcomm atheros usb devices driver download for windows 10 64. Yes (up to VGA only)

SBP2 driver support

Yes

64 bit OS support

Yes

Fire-i™ application

No

Firewire Bus topology viewer

No

Firewire command-line control tool

No

IIDC Explorer camera control tool

No

1394 driver auto-switch utility

Yes

A/V devices and DV cameras support

No

ubCore™ 1394a – 1394b Windows drivers Product History

November 2012 – Version 6.00
  • Added: support for DAP Technology S1600 chipset, adapters and Sony S1600 cameras.
  • Added: support for Windows 8, WHQL signed drivers for Windows 8.
  • Added: support for the new Fire-i 550, Fire-i 850 1394a CMOS camera models.
  • Added: option to save the frame buffer to a raw file (Fire-i Application).
  • Added: Fire-i NET SDK library is now merged into ubCore installation.
  • Fixed: SBP2 driver power management issues on Win8 (sbp2.sys).
  • Fixed: Saving frames in Tiff16 format, the info was truncated to 8-bit (Fire-iApplication).
  • Fixed: Changing packet size in Format7, is not updated on the camera (Fire-iX, Fire-i.NET).
  • Fixed: Hardware license may not be recognized on some FireBoardBlue_e adapters (ubohci.sys).
  • Fixed: Rare crash when using many small isochronous requests on fast systems (ubohci.sys).
  • Firenet networking driver removed from ubCore runtime, not supported anymore.

September 2011 – Version 5.80

  • Added support for choosing jpeg quality level when saving frames (Fire-i application).
  • Added trigger parameter set box, in the trigger dialog (Fire-i application).
  • Fixed: Rare crash of miniport OHCI driver in multicore or multripocessor systems.
  • Fixed: Rare crash on IIDC camera driver when booting system with cameras connected.

January 2011 – Version 5.72

  • Added: support for absolute camera registers in DLL interface (UB1394.DLL).
  • Added: software absolute support for Unibrain cameras in the DLL interface (UB1394.DLL).

December 2010 – Version 5.71

  • Added jumbo packet support for Fire-i 780 cameras (UB1394.DLL)
  • Fixed: Unintended frame skip when using Snapshot button (Fire-i app)
  • Fixed: Firenet driver installation glitches in modified setup.
  • Fixed: Camera license tool x64 cannot license WoW apps in Win x64 OS.
  • Added: Some features in Fire-i X SDK, details here.

April 2010 – Version 5.70

  • Added support for Licensed version of Fireboard800 Pro Dual adapter.
  • Added video capture functionality in ub1394.dll (Fire-i DLL API)
  • Fixed: some ubCore upgrade issues when an older verion is already installed.
  • Added support for RAW formats in 64 bit version of Fire-i IIDC app.
  • Added software absolute shutter support for Unibrain Fire-i board Pro and industrial cameras.

October 2009 – Version 5.63

  • WHQL Signed Windows 7/Vista/XP drivers.
  • Fixed: ubohci driver crash when receiving jumbo-packet frames from a high resolution camera.
  • Fixed: Problem saving frames from Little-Endian cameras (IIDC driver).
  • Added support for Unibrain Fire-i 980 5 Mpixel 1394b camera (IIDC driver).

April 2009 – Version 5.62 Download the imaging source europe cameras wireless.

  • Added support for Windows 7 beta (build 7000 or later).
  • Fixed: Multiple sleep/resume cycles with SBP2 devices connected may lead to system crash.
  • Fixed: Fire-i application should remember last FPS selected.
  • Fixed: Fidcam.sys IIDC driver must first stop the camera before detaching isochronous descriptors.
  • Firenet driver is not installed by default anymore.

December 2008 – Version 5.60

  • Added support for VersaPHY.
  • Added support for latest LSI 1394b PCI express chipset (FW643-e).
  • Fixed: ExpressCard or PCMCIA adapter removal my cause system crash.
  • Fixed: Restore settings after new install does not work correctly.
  • Fixed: SCSI pass through fails from 32-bit process on x64 OS (SBP2 driver).
  • Fixed: SBM should NOT optimize gap_count when only 1394b nodes are on the bus.

August 2008 – Version 5.52

  • Added: Fire-i X ActiveX control/SDK library in ubCore Pro runtimes.
  • Fixed: SBP2 driver crash in volumes larger than 4 TB.
  • Fixed: SBP2 driver fails to recognize multiple external hard drives at boot.
  • Fixed: NMI system crash on certain Xeon systems during isochronous transmit.
  • Fixed: SBM produces gap_count 63 when the zero ping bug is in effect.

June 2008 – Version 5.51

  • Added: Support for RAID external hard drive enclosures.
  • Added: Fire-i Ms stack (fidcam.sys) added in ubCore Pro setup.
  • Added: Add capability in CFiCamera to select the video format with a GUI.
  • Fixed: Image streaming freezing periodically at 60 fps (or more) in Firei application.
  • Many improvements and various minor fixes in FireViewer, ubSwitch, FireIIDC utilities.

February 2008 – Version 5.50

  • Added: DMA channel multiplexing at the driver level, completely transparent to user mode.
  • Added: NDIS 6.0 support for Firenet driver in Windows Vista 32/64 bit for improved performance.
  • Added: Maximum 64 adapters supported by all drivers in ubCore.
  • Added: RAW-8 mode support in Fire-i WDM driver and Firei.dll.
  • Added: RAW mode support and Format-7 color codings in Firei.dll. (ubCore Pro only)
  • Added: Advanced features support in new Sony, PointGrey and AVT 1394b cameras. (ubCore Pro only)
  • Added: Many new features/commands in FireViewer, FireCommander and Fire-i IIDC applications (ubCore Pro only)
October 2007 – Version 5.21
  • Fixed: Significant improvement in system stability on Windows Vista when sleeping/resuming with FireNet installed.
  • Fixed: Fatal NMI error during setup on specific computer hardware with 1394b PCI adapters.
  • Fixed: Incorrect isochronous timeout handling causes OS resource leaks on x86/x64 systems.
  • Fixed: Serial Bus Manager driver now supports more than 4 firewire adapters.
  • Fixed: IIDC camera driver (UBDCAM.SYS) sets initial max packet size for Format 7 correctly.
  • Added: DMA limit for iso operations based on operating system and hardware.
  • Added: IIDC camera driver (UBDCAM.SYS) automatically breaks image iso requests according to DMA limit.

June 2007 – Version 5.20

  • Added support for LSI (Agere) FW643 1394b to PCI express chipset.
  • Added ISO command in FireCommander for performing isochronous operations.
  • Fixed: system crash when doing multiple concurrent isochronous receives.
  • Fixed: Firei.exe crashes sometimes when copying video file after capture. (ubCore Pro only)

May 2007 – Version 5.13

  • Singed drivers for Windows Vista 32 and 64 bit editions.
  • Added: x86 FireAPI applications can run on x64 systems.
  • Added: 64-bit Fire-i application on x64 systems. (ubCore Pro only)
  • Dual x86/x64 DirectShow Filter support on x64 systems. (ubCore Pro only)
  • NEW!: FireIIDC™ camera control application, based on firei.dll (ubCore Pro only)

January 2007 – Version 5.12

  • Added: Complete and improved redesign of the installation engine.
  • Fixed: Improved support for Windows Vista (RTM)
  • Fixed: IIDC drivers fail to operate with cameras that fail read/write requests with resp_conflict.
  • Fixed: Improved support for AVT Pike 1394b cameras.
  • Fixed: High resolution image streams cause IIDC driver video to halt.

December 2006 – Version 5.11

  • Added: Windows Vista (32 bit) support.
  • Added: Multiple new commands in FireCommander & ubTweak utilities (ubCore Pro only)
  • Fixed: Maxtor One-Touch™ external 1394b hard drives incompatibility
  • Fixed: Multiple Firenet network driver power management issues
  • Fixed: Minor issues with specific IIDC cameras which respond with delay in very fast computers (ubCore Pro only)

October 2006 – Version 5.10

  • Added: Custom Configuration ROM contents (virtual devices).
  • New improved SDK license/activation utility.
    (ubCorePro only)
  • Added: Ability to change the maximum address range size.
  • Added: Multiple freeing of Map Registers by ubohci.sys.
  • Fixed various issues in the isochronous engine.
  • New enhanced versions of ubTweak, FireCommander and ubSwitch utilities. (ubCore Pro only)
  • Various bug fixes in IIDC and Firenet drivers

June 2006 – Version 5.0

  • Important bug fixes and driver performance improvements.
  • Added ubTweak™, driver configuration/tuning utility
    (ubCorePro only).
  • Added support for Oxford 922 RAID external hard drives (SBP2 driver).
  • The drivers are now compliant with 1394 Trade Association Base 1394 test.
  • Added ability to disable Plug & Play for certain devices.

February 2006 – Version 4.0

  • Full Windows Plug & Play support. Easy switch between Unibrain and Microsoft driver via a single click (“ubswitch” application).
  • Added support for Windows Power Management.
  • Added support for Windows 2003 Server Operating System.
  • Added support for Windows XP 64 bit (AMD Athlon 64 and Intel EM64t).
  • Added IIDC 1394 cameras DirectShow WDM compliant driver and control application.
  • Added support for 1394b (Firewire-800) IIDC cameras.
  • Added support for S1600/S3200.

July 2003 – Version 3.0

  • Added support for 1394b (Firewire-800).
  • Added support for SBP2 interface.
  • Added FireShare application.
  • Added support for FireBoard Blue™.
  • Added support for FireBoard 800™.
  • Added support for PCMCIA OHCI cards.
  • Added support for optical cables and repeaters.

April 2002 – Version 2.1

  • Added support for Windows XP.
  • Added support for 3rd party OHCI cards.

September 2001 – Version 2.0

  • Added support for FireBoard 400-OHCI card.
  • Added support for Windows ME.

July 2000 – Version 1.6

  • Added support for Windows 2000.

June 1999 – Version 1.5

  • Added support for IIDC cameras.
  • Added support for Windows 98SE.

June 1998 – Version 1.0

  • Support FireBoard-400 Lynx-2 PCI adapter.
  • Supports Windows NT 4.0.
  • Supports Kernel mode for driver development.
  • Support User mode for application development.
  • Support for FireWire Networking (Firenet driver).
  • Added Fireviewer and FireCommander tools.

Download Versions