PortTalk Windows NT I/O Port Device Driver 2.2

Download Simple Step Port Devices Driver License
Download Simple Step Port Devices Driver Updater
Download Simple Step Port Devices Driver Download
Download Simple Step Port Devices Drivers

A problem that plagues Windows NT/2000 and Windows XP, is it's strict control over I/O ports. Unlike Windows 95 & 98, Windows NT/2000/XP will cause an exception (Privileged Instruction) if an attempt is made to access a port that you are not privileged to talk too. Actually it's not Windows NT that does this, but any 386 or higher processor running in protected mode.
Accessing I/O Ports in protected mode is governed by two events, The I/O privilege level (IOPL) in the EFLAGS register and the I/O permission bit map of a Task State Segment (TSS). Under Windows NT, there are only two I/O privilege levels used, level 0 & level 3. Usermode programs will run in privilege level 3, while device drivers and the kernel will run in privilege level 0, commonly referred to as ring 0. This allows the trusted operating system and drivers running in kernel mode to access the ports, while preventing less trusted usermode processes from touching the I/O ports and causing conflicts. All usermode programs should talk to a device driver which arbitrates access. The I/O permission bitmap can be used to allow programs not privileged enough (I.e. usermode programs) the ability to access the I/O ports. When an I/O instruction is executed, the processor will first check if the task is privileged enough to access the ports. Should this be the case, the I/O instruction will be executed. However if the task is not allowed to do I/O, the processor will then check the I/O permission bitmap.
The I/O permission bitmap, as the name suggests uses a single bit to represent each I/O address. If the bit corresponding to a port is set, then the instruction will generate an exception however if the bit is clear then the I/O operation will proceed. This gives a means to allow certain processes to access certain ports. There is one I/O permission bitmap per task.
Revision History
6th April 2002 - Version 2.2.
Fixed a debug message typo in the IoExample.
13th January 2002 - Version 2.1, tested on Windows 2000 SP2 and Windows XP RTM.
Added uninstall.exe to deal with older V1.x versions of PortTalk.
12th January 2002 вЂ“ Version 2.0, tested on Windows 2000 SP2 and Windows XP RTM.
Self installs driver for ease of use.
Improved type checking.
Distributed with IoExample code showing use of inportb/outportb() inp/outp() macros and IOCTL calls.
6th September 2001 вЂ“ Version 1.02
Fixed .reg file after previous fix broke Windows 2000 Support. Now supports Windows NT/2000/XP.
26th June 2001 вЂ“ Version 1.01
Fixed .reg file to support both Windows 2000 and Windows NT4.
13th March 1999 вЂ“ Version 1.0 first public release for Windows NT4.
When installing PortTalk V2.x on machines with an older version of V1.x, the existing driver must be un-installed. Simply run the uninstall.exe contained within the PortTalk package with administrator privileges. After the old driver has been removed, running allowio.exe or IoExample.exe will detect the absence of PortTalk and re-install the new driver.
Additionally, the driver can be removed manually. This is only recommended for advanced users. Either
-Replace your old porttalk.sys with the new version and reboot.
-Delete the HKEY_LOCAL_MACHINEsystemcurrentcontrolsetservicesporttalk key and reboot.
-Use the Windows NT Device Driver Installer to stop and remove the PortTalk Driver.
Примечание: Ссылка 'скачать' может вести как непосредственно на файл, так и на сайт производителя, на котором Вы можете найти нужный файл.
Это связано с тем, что некоторые производители не позволяют размещать прямые ссылки на файлы.

Install Sierra Wireless COM Port Device driver for Windows 7 x64, or download DriverPack Solution software for automatic driver installation and update. Download the latest drivers, firmware, and software for your.This is HP’s official website that will help automatically detect and download the correct drivers free of cost for your HP Computing and Printing products for Windows and Mac operating system. If you’re using any Xiaomi device or any Qualcomm powered device and want to flash MIUI ROM or unbrick your dead device, then Qualcomm HS-USB QDLoader 9008 driver will be useful. Any of the Android devices which are running on a Qualcomm processor will be applicable for it. Hello, I am using ThinkPad X301 (2774W14). I had to format and reinstall my windows 7 and I have the following problems: 1. I am missing the PCI Serial Port Driver. Driver: OS Independent: 26.0 Latest: 2/1/2021: Intel® Network Adapter Driver for E810 Series Devices under Linux. This download record includes the ice Linux. Base Driver version 1.3.2 for the E810 series devices. Driver: Linux. 1.3.2 Latest: 2/1/2021.

Рейтинг за сегодня::

-->

Simple I/O plug-ins are extensions to the Windows Driver Test Framework (WDTF) that implement generic device-specific I/O functionality. If a plug-in exists for the type of device being tested, the Device Fundamental tests use the WDTF Simple I/O interfaces to test I/O.

This topic lists the device types that have Simple I/O plug-ins and indicates if there are specific requirements for testing the device. These are the same requirements you need to follow when you use the Windows Hardware Lab Kit (Windows HLK). The topic also offers ideas to troubleshoot and triage test failures.

If your device type is not listed, you can create one, see How to customize I/O for your device using the WDTF Simple I/O Action Plug-in

For a list of Device Fundamental tests that have specific requirements, see Device Fundamental tests that have specific device configuration requirements

Audio

Requirements

The device must have at least one render type endpoint connected (speakers, headphones, or the like).
If the targeted audio device has HDMI video and audio output capability, to perform audio tests, the device must be connected to an HDMI audio capable device such as an HDMI Monitor or an A/V Receiver.

Type of I/O plug-in performs (audio)

Plays a sine tune on render type endpoint. Captures audio on a capture type endpoint.

How to triage test failures

Look at failing HRESULT to perform initial triage.
If test is not responding, use the kernel debugger on the target computer to narrow down the root-cause.
Run traces:
- Start kernel traces:

Start audio traces:

Run tests.
Stop traces:

Merge traces:

View the merged trace file with Xperf (xperfview).

Bluetooth

Bluetooth requirements

No special requirements.

Type of I/O plug-in performs (Bluetooth)

Uses BluetoothFindFirstDevice function to find a Bluetooth device.

CDROM

CDROM requirements

Drive letter is assigned.
Media is present in the device.
Files are present on the media inserted.

Type of I/O plug-in performs (CDROM)

Finds files on the CD-ROM and performs read operation using the Win32 ReadFile API.

How to triage test failures (CDROM)

On the test computer, navigate to the CD/DVD drive in question and confirm you can access the contents of the drives.
The CD-Rom Simple I/O plug-in searches for files on CD/DVD to use to perform reads from. Ensure the CD/DVD has files encoded on disk.
This Simple I/O plug uses the Win32 CreateFile, WriteFile, ReadFile functions. Error returned are most likely Win32 error codes from these APIs.

PortTalk Windows NT I/O Port Device Driver 2.2

Audio

Requirements

Type of I/O plug-in performs (audio)

How to triage test failures

Bluetooth

Bluetooth requirements

Type of I/O plug-in performs (Bluetooth)

CDROM

CDROM requirements

Type of I/O plug-in performs (CDROM)

How to triage test failures (CDROM)

Disk

Disk requirements

Type of I/O plug-in performs (Disk)

Display

Display requirements

Type of I/O plug-in performs (Display)

Download Simple Step Port Devices Driver