24.12.2020

Porttalk Driver

Porttalk Driver Rating: 5,0/5 9201 votes
  1. View Manuals, Download Software, Watch Videos and Find Answers for Any MagTek Product: MagTek.
  2. Download PortTalk - Connect to any TCP/IP server, send it some commands and see how server responds. Free Trial Driver Booster 6 PRO (60% OFF when you buy) PortTalk. 1,436 downloads Updated.
  3. To install the PortTalk driver: Boot your PC with administrator privileges Copy the PORTTALK.SYS to your /system32/drivers directory. Click on the PORTTALK.REG file to load the required registry keys. (for reference, the contents of PORTTALK.REG are listed in the appendix) Reboot the computer (this time with a normal user account).
  1. Porttalk Driver Windows 10
  2. Porttalk Driver Windows 7

But to install the PortTalk driver, you need a administrator rights. The driver only needs to be installed once (with an admin account), but it can be used later with a user account. More up-to-date information about PortTalk can be found on the PortTalk website (look for the chapter 'Starting and installing the driver').

Clarinet vst free download. How to install the PortTalk driverpermanently
(to run WinPic under Win XP with a user account)

This document describes how to install Craig Peacock's PortTalk driver underWindows XP.

Under Windows XP (etc), you may want run WinPic with a user account later.But to install the PortTalk driver, you need a administrator rights.The driver only needs to be installed once (with an admin account),but it can be used later with a user account.

More up-to-date information about PortTalk can be found on thePortTalk website (look for the chapter 'Startingand installing the driver'). The following text describes how I (the authorof WinPic) installed the PortTalk driver under Windows XP in November 2005.

Notes:

  • Port Talk is not required under Win 95/98/ME. So ignore this document if you run WinPic under one of those systems - use the option 'I/O port access already granted before start'.
    Furthermore, if the steps shown below sound too complicated for you, run WinPic under Win XP with an administrator account. In that case, WinPic can install, start, and stop the PortTalk service automatically.
  • Why use PortTalk for the PIC Programmer ? See FAQ, 'how to make WinPic faster'.
  • Why run your PC without admin rights ? Because it's safer, especially if you frequently surf the net. With admin rights, a malicious software (or visitor) can do all sorts of things to your system, which you certainly don't want.

To install the PortTalk driver :

  1. Boot your PC with administrator privileges
  2. Copy the PORTTALK.SYS to your /system32/drivers directory.
  3. Click on the PORTTALK.REG file to load the required registry keys.
    (for reference, the contents of PORTTALK.REG are listed in the appendix, and a Regedit screenshot after the successful installation)
  4. Reboot the computer (this time with a normal user account).
  5. Start WinPic (with 'I/O Port Access Driver' set to 'use Port Talk').

If the PortTalk installation was successfull, WinPic can access your PICprogrammer on the serial or parallel port now. If not, you will get an errormessages like the following:

Porttalk Driver Windows 10

  • PortTalk: No rights to access the SCM - try with admin rights
    which means, WinPic could not talk to the PortTalk driver, and tried to install that service itself through the Service Control Manager, which failed because you are not logged in with administrator rights. Try again to install PortTalk manually (as explained above) and check the registry entries this time.
  • PortTalk: You do not have rights to the PortTalk service database
  • PortTalk: The specified service name is invalid
  • PortTalk: Driver does not exist. Installing driver.
    These three messages indicate that WinPic could communicate with the SCM, but the SCM could not open the PortTalk service for various reasons. Most likely, you didn't copy PORTTALK.SYS into the windows system directory.

If everything failed, don't despair .. use WinPic with admin rights. Thisis better than not being able to program PICs at all ;-)

Contents of PORTTALK.REG

PORTTALK.REG can be downloaded from thePortTalk website. It is basically a textfile, which can be processed by the Windows Registry editor to add a fewentries to the registry. It looked like this (in November 2005):

After double-clicking PORTTALK.REG, you can check if the contents are reallycopied into the windows registry (it will fail if you have no administratorrights). To check, open regedit, and look into
HKEY_LOCAL_MACHINE .. SYSTEM .. CurrentControlSet .. Services .

You should see at least the four subkey values which were added by PORTTALK.REG.

Links

Porttalk Driver Windows 7

  • http://www.beyondlogic.org/porttalk/porttalk.htm is the PortTalk website, where you can download the PortTalk driver, its documentation, and the registry file PORTTALK.REG .
Author: Wolfgang Buescher (DL4YHF)
Last modified: 2005-11-11 (ISO-date-format, YYYY-MM-DD)

--.. ..-- ..-.-

11,577 downloads·Added on: August 29, 2006·Manufacturer: Others
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.

It is highly recommended to always use the most recent driver version available.
Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

COMPATIBLE WITH:
Windows NT
file size:
67 KB
filename:
porttalk22.zip
CATEGORY:
Other Drivers & Tools