This article describes an issue that occurs when you use a FireWire port-based device in Windows 8.1 or Windows 8. Additional steps of configuration is required to enable this update after the installation.
- The IOCTLUSBGETNODECONNECTIONINFORMATIONEX request retrieves information about a USB port and the device that is attached to the port, if there is one.Client drivers must send this IOCTL at an IRQL of PASSIVELEVEL.IOCTLUSBGETNODECONNECTIONINFORMATIONEX is a user-mode I/O control request.
- Sound card drivers and multimedia device drivers are available to be downloaded for free for the Soft32 site. Visit the site today to take advantage!
Right-click on your PC Start button and open Device Manager Double click LPT and COM ports then locate the Prolific USB to Serial Driver and right-click it so you can select Update Driver For driver software click My computer From My computer select 'Let me pick from a list of drivers available'.
Symptoms
Assume that you have a computer that equips with an IEEE 1394 FireWire controller card. After you upgrade the computer from Windows 7 to Windows 8.1 or Windows 8, devices that connect to the computer by using a FireWire port do not work.
Cause
This issue occurs because the legacy 1394 bus drivers (1394bus.sys and Ochi1394.sys) are removed in Windows 8.1 or Windows 8.
Resolution
Update information
How to obtain this update
Microsoft Download Center
The following files are available for download from the Microsoft Download Center:
Operating system | Update |
---|---|
All supported x86-based versions of Windows 8.1 or of Windows 8 | |
All supported x64-based versions of Windows 8.1 or of Windows 8 |
Data Card Port Devices Drivers
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Additional steps of configuration requirement
After you install the 1394 OHCI Legacy Driver.msi file, follow these steps:
Right-click the Legacy1394.inf file under one of the following paths based on the computer's architecture:
C:Program Files1394 OHCI Compliant Host Controller (Legacy)x86_driver
C:Program Files1394 OHCI Compliant Host Controller (Legacy)x64_driver
Click Install.
Open Device Manager in Control Panel.
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.
Click Let me pick from a list of device drivers on my computer.
Click Generic1394 OHCI compliant host controller (Legacy), and then click the Next button.
Click the Close button.
Prerequisites
There are no prerequisites for installing this update.
Registry information
To apply this update, you do not have to make any changes to the registry.
Data Card Port Devices Driver
Restart requirement
You have to restart the computer after you apply this update.
Update replacement information
This update does not replace a previously released update.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 8.1 and Windows 8 file information notesThe MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are not listed
For all supported x86-based versions of Windows 8.1 or of Windows 8
File name | File version | File size | Date | Time | Platform |
---|---|---|---|---|---|
1394_ohci_legacydriver.msi | Not Applicable | 208,896 | 15-Aug-2014 | 20:48 | Not Applicable |
For all supported x86-based versions of Windows 8.1 or of Windows 8
File name | File version | File size | Date | Time | Platform |
---|---|---|---|---|---|
1394_ohci_legacydriver.msi | Not Applicable | 208,896 | 15-Aug-2014 | 20:48 | Not Applicable |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the 'Applies to' section.
More Information
Steps of uninstalling the 1394 OHCI Legacy Driver.msi file
Open Control Panel in the Category view.
Click Uninstall a program in Control Panel.
Right-click 1394 OHCI Compliant Host Controller (Legacy), and then click Uninstall.
The screen shot of uninstalling the 1394 OHCI Compliant Host Controller (Legacy) is listed in the following example:
Additional package information
Data Card Port Devices Driver List
This driver is only intended to work with legacy 1394 host controllers. Therefore, you may experience lower transfer data rates than the 1394b driver.
The driver is intended to resolve compatibility issues for 1394 peripherals on 1394b systems. If you are not experiencing these issues, you should continue to use inbox drivers that are provided in Windows 8.1 or Windows 8.
You have to reinstall this stand-alone driver package if you upgrade to a newer operating system version in the future.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
PANPAD® provides a simple, secure, semi-integrated payments solution. The PANPAD solution includes the PANPAD terminal application, which runs on PCI-certified Ingenico terminal devices (pre-provisioned and provided by CardConnect). Payment card data is encrypted at the point of entry by CardSecure, potentially reducing your scope of PCI DSS compliance, since sensitive data is never exposed to the point-of-sale (POS) application.
Unlike Bolt terminals, which communicate with the POS system using a network connection (Ethernet or WiFi), PANPAD terminals communicate over a serial connection, using USB.
PANPAD is ideal for businesses that do not require a feature-rich POS solution. Complex POS systems require terminals with equally complex applications and significant integration requirements. PANPAD offers simple and secure card-present and card-not-present payments, and is integrated with the CardPointe platform to provide robust reporting capabilities.
How it Works
- When the merchant swipes or manually enters the card data at the PANPAD terminal, the card data is sent directly and securely to CardConnect where it is encrypted and tokenized using CardSecure.
- The mathematically irreversible token is then returned to the terminal for use by the POS application to make an authorization request to the CardPointe Gateway.
- CardSecure securely decrypts and transmits payment card information to the processor via Secure Sockets Layer (SSL).
Requirements
Before you begin to integrate PANPAD with your solution, ensure that you meet the following requirements:
- A distributed application architecture
- A Windows application server and clients running .NET 3.5 or 4.0
- A Windows workstation for developing and testing your application
- PANPAD terminals, pre-provisioned and provided by CardConnect. Currently, the following terminals are supported:
- Ingenico iPP320 and iPP350
- Ingenico iSC250 and iSC Touch 250
- The PANPAD dynamic link library (DLL), used by your application to connect to your terminals.
- The Ingenico USB drivers, required to connect the PANPAD terminal to your workstation.
- A CardConnect merchant account and CardPointe Gateway API credentials
The PanPad solution includes a Windows Dynamic Link Library (DLL), which allows your application to communicate with the PanPad terminal over the serial communication layer, using a USB. The DLL includes a number of functions, including calls to CardSecure to tokenize payment card data.
See the PanPad Integration Guide for detailed information for integrating the PanPad DLL with your application.
PanPad DLL Integration Kit
The PanPad DLL integration kit includes the following resources to help you get started:
- CardConnect Desktop Tokenizer vR51 – The Desktop Tokenizer is a sample .NET payment card tokenization application. You can connect your terminals to a workstation running the Desktop Tokenizer client application to tokenize payment cards and troubleshoot device issues.
- TokenDemo – A sample PanPad client application VisualStudio project.
- TokenDemoRun – A precompiled Windows command line-executable build of the TokenDemo program. TokenDemoRun provides basic PanPad functionality using the DLL.
Click below to download the PanPad DLL integration kit:
Installing the Ingenico USB Drivers
To connect the PanPad terminal to your workstation, you must install the required USB drivers.
Click below to download the Ingenico USB drivers:
After you have downloaded the drivers, do the following to install them on your workstation:
- Browse to and double-click the file to launch the Installation Wizard.
- On the Welcome page, click Next to begin the installation process.
- Accept the default install location or select a custom location, then click Next.
- On the Usb Driver parameters page, click Next without making any changes.
- On the Advanced parameters page, optionally select the Uninstall Microsoft Usbser driver(s) check box if you want to uninstall an old version of the Microsoft USB Driver; otherwise, ignore this option and click Next to finish the installation.
Once the driver installation completes, you can connect the PanPad terminal to your workstation.
Connecting the PanPad Terminal
The following procedure provides information for getting started with your PanPad terminal:
- Unbox the terminal and do the following:
- Connect the power supply to the USB adapter.
- Plug the power supply into an available power outlet.
- Attach the USB cable to the device by inserting the HDMI end (opposite the USB end) into the jack located under the device.
- Connect the USB cable to an available USB port on your workstation. Do not connect the device to a USB hub.
- On your workstation, do the following to verify the port that the terminal is connected to:
- On the Start menu, type Device Manager and select it from the search results, or browse to the Device Manager from the Control Panel.
- On the Device Manager, expand the Ports heading to display a list of connected devices.
The connected terminal should be labeled Sagem Telium Comm Port including the port that the terminal is connected to (for example COM7).
If the port number is not displayed, right-click the Sagem Telium Comm Port device and select Properties. On the Properties dialog box, select the Port Settings tab and click Advanced. The COM Port Number field at the bottom of the Advanced Settings page displays the port number.