China 1394 net adapter manufacturer, customize 1394 net adapters sale--Chijiu Battery

E-mail:
sales@batteryy.com

Established in 1995, Chijiu Battery Co., Ltd. are a high-tech China 1394 net adapter manufacturer and wholesaler engaged in the design, manufacturing and marketing of battery, charger, adapter and solar panels etc. Our custom 1394 net adapters are extensively used in telecommunications, electronics, solar energy systems, electric vehicles, UPS, security systems, emergency lighting, power tools, mobile phone, digital camera & camcorder, MP3, laptop, portable DVD, blue-tooth, PDA and intelligent charger solution. To keep the GB/T7112-1998, IEC60086-2 standards. We implement the certificate system ISO9002 since 1998. In 2001 we passed the audit of ISO9001:2000 quality management system and ISO14001:1996 environment management system conducted by the world-renowned Det Norske Veritas (DNV) and had the certificates issued.

1394-LAPTOP-PCMCIA-ACC
Accessory pack for laptops that do not have a FireWire port. The pack contains an OHCI compliant PCMCIA cardbus card 1394 adapter, a "dongle" for the card, a universal power supply and a 4-pin to 6-pin 2 meter FireWire cable.
Interface Type : FireWire Laptop Use : Yes
Card Type : PCMCIA Cardbus Card
External Power : Included - 100-240V AC Adapter
Includes Cables : Yes - 2 meter FireWire Cable
To understand Windows 1394 asynchronous transfer operation, one must understand the different types of addressing modes that the Windows 1394 bus driver uses. Addressing modes determine how the bus driver interprets destination address information that is passed along with asynchronous transfer requests. For Windows 2000 and earlier platforms, there were two modes of addressing when using asynchronous transfers normal-mode and raw-mode. What these modes are and how they work is explained later. For XP and later platforms, there is a new addressing mode called virtual-mode addressing. Virtual-mode addressing is used for 1394 virtual devices. The virtual device mechanism for 1394 was introduced with the Windows XP 1394 bus driver stack. In order to fully understand 1394 asynchronous communication on Windows platforms, it is helpful to understand what 1394 virtual devices are and how they are used. In a moment, I will take a step to the side and cover virtual devices in some detail. As for asynchronous transfer addressing modes, none of these were documented in the Windows Device Driver Development Kit (DDK) help until about a year ago.

ADP-1394-4M6F:ADAPTER IEEE 1394 4P Male TO 6P Female
Host controllers always enumerate with the 1394\Microsoft&1394_PC ID. This ID might appear to be a fine solution to load a set of drivers for a host controller-to-host controller transfer, and indeed this setup does work. However, using 1394\Microsoft&1394_PC in one's INF file is not a practical solution. Multiple drivers might wish to use this same ID, yet only one driver is loaded per host controller. Despite such a powerful peer-to-peer potential, the 1394 bus is severely hobbled on 2000 and earlier Windows platforms. Fortunately, someone at Microsoft realized the limitations being forced on the 1394 bus. The Windows XP and later versions of the 1394 bus driver allow a user to enumerate devices through the 1394 bus using custom device IDs. These devices do not have to correlate to any real hardware. They are called 1394 virtual devices.
The host controller does not have to be connected to another host controller or to any other hardware in order to enumerate a virtual device. In addition to solving the host controller peer-to-peer problem, virtual devices allow even greater flexibility than was ever possible on 2000 and earlier Windows platforms. Virtual devices have full access to the 1394 bus through the 1394 bus driver. Virtual device can perform asynchronous transfers to other nodes, isochronous transfers, and they can allocate address ranges in the host controller's memory space. Figure 2 shows how the setup from Figure 1 changes using virtual devices