PortTalk will allow 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. This video shows you how to install a Driver from a.SYS file, on Windows 10, Windows 8, Windows 7, Windows XP and other Windows operating systems.DriverGuid. Porttalk is a driver that enables applications to access hardware's I/Os directly, like it was possible in Windows 98. Porttalk consists basically of two files: porttalk.sys: The actual driver. Allowio.exe: Application which takes another application.exe and I/O adresses as parameter and enables it to access them directly. I used porttalk successfully for 2 weeks. I loaded the respective files into the registry, moved the porttalk.sys file into the drivers folder under c: windows system32 drivers. Finally i copied aloowio.exe file into my assembler folder.
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 :
- 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, and a Regedit screenshot after the successful installation) - Reboot the computer (this time with a normal user account).
- 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: 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
- 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 .
Last modified: 2005-11-11 (ISO-date-format, YYYY-MM-DD)
--... ...-- ...-.-
(to run WxPic 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 WxPic 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 the PortTalk 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:
- If the steps shown below sound too complicated for you, run WxPic under Win XP with an administrator account. In that case, WxPic can install, start, and stop the PortTalk service automatically.
- 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 :
- 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).
- Start WxPic (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: No rights to access the SCM - try with admin rights
which means, WxPic 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 WxPic 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 WxPic 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
- 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 .
댓글