Io.dll 2002

該網站首頁: http://geekhideout.com/iodll.shtml Allows programs written in Visual Basic/Delphi/C/C , and more, to access any I/O port (including the parallel port) under Windows 95/98/ME/NT/2000/XP. File name: Io.dll 2002 File homepage: Product homepage Order page: Order information Language: C, C , C Builder, C .NET, Delphi 2-3-4-5-6, Pascal, Visual Basic 3-4-5-6, Visual C Platform: Windows 2000-95-98-ME-NT-XP Release Date: 1/1/1996 File type: Freeware Size: 30 KBytes Price/fee (US$): 0.00$ 下載: http://geekhideout.com/downloads/io.zip 以下是他的說明: IO.DLL Your Attention Please! A bug was found in IO.DLL that caused the error "Unable to start the IO.SYS service" to occur on Windows 2000/XP machines. This bug has been found and was fixed on 08/06/02. If you are using an older version of io.dll, you will want to upgrade now! Synopsis IO.DLL allows seamless port I/O operations for Windows 95/98/NT/2000/XP using the same library. Introduction In the pre-Windows days, it was a relatively simple matter to access I/O ports on a typical PC. Indeed, nearly every language sported a special command for doing so. As Windows emerged and gradually evolved, this flapping in the wind behaviour could no longer be tolerated because of operating system's ability to virtualize hardware. Virtualizing hardware means that an application (typically a DOS box in Windows) believes it is talking directly to a physical device, but in reality it is talking to a driver that emulates the hardware, passing data back and forth as appropriate. This is how you are able to open dozens of DOS boxes in your Windows session, each one with the strange notion that it has exclusive access to peripherals such as the video adapter, keyboard, sound card and printer. If one were to rudely bang out data to an I/O port that Windows thought it was in full control of, the "official bad thing" could occur, the severity of which depending upon the exact hardware that was being accessed. Actually, with the virtualization just mentioned, it is quite improbable that Windows would permit anything too nasty from occuring. Windows 95/98 actually does allow I/O operations be executed at the application level, although you'd be hard pressed to find a language that supports this directly. Typically the programmer will have to resort to assembly language for this kind of low-level control. If you know what you are doing, this can be a quick and easy way to access I/O ports. Of course, not everyone knows, or desires to learn 80x86 assembly programming just because they want to turn on a lamp from their computer. However, the unwillingness to learn assembly language becomes rather trivial when faced with 9x's big brother. Windows NT/2000/XP, being the secure operating system that it is, does not permit port I/O operations at the application level at all. Period. A program with inline IN and OUT assembly instructions that runs perfectly on Windows 95/98 will fail horribly when it comes to Windows NT/2000/XP. Windows NT/2000/XP does, however, allow I/O instructions in its kernel mode drivers. A kernel mode driver runs at the most priviledged level of the processor and can do whatever it pleases, including screwing up the system beyond repair, thus writing a kernel mode driver is not for the feint of heart. If you were to take it upon yourself to wade through the documentation of the Windows NT/2000/XP ddk and piece together a driver that was callable by your application to do the I/O instructions on behalf of your application, you'd probably notice something not too pleasant--this sort of access is painfully slow. The call from application level to system level typically takes about one millisecond. Compare this to the one microsecond that a normal I/O access takes. To further the insult, you are at the whim of the operating system. If it has tasks which it believes are of higher priority than your lowly call to your driver, it will perform them, making precise timing nearly impossible. Obviously, writing a driver that does acts a proxy for the I/O calls isn't the most ideal solution. There is, however, a solution for NT/2000/XP that allows the same convienience of inline assembly language that 95/98 does. As mentioned, a kernel mode driver can do whatever it wants. The implication here is that if another kernel mode driver shut off application access to the I/O ports, it should be possible for another kernel mode driver to turn it back on. This is where IO.DLL enters the picture. Licensing IO.DLL is completely free! However, you may not: Charge others for it in any way. For example, you cannot sell it as a stand alone product. Claim that it is your property. Also, the author (that's me) cannot be held liable due to io.dll's failure to perform. As with most free stuff, you are on your own. Source Code and Special Modifications The source code is available for $1,000 US. I'm willing to work with people should they require a special modification to IO.DLL. For example, you might have a strict timing requirement of some sort that can only be done in kernel mode. For a fee, I will modify IO.DLL and/or the embedded kernel mode driver for the task at hand. Description of IO.DLL IO.DLL provides a useful set of commands for reading and writing to the I/O ports. These commands are consistent between 95/98 and NT/2000/XP. Furthermore, there is no need for the programmer to learn assembly language or muck with kernel mode drivers. Simply link to the DLL and call the functions. It's that easy. Windows NT/2000/XP is accomodated through the use of a small kernel mode driver that releases the ports as needed to the application. This driver is embedded in the DLL and is installed if Windows NT/2000/XP is determined to be the underlying operating system. Due to the very minor overhead involved in dynamically linking to IO.DLL, and the optimized functions contained within, access to I/O ports is nearly as fast as if it was written in raw assembler and inlined in your application. This holds true for both Windows 95/98 and Windows NT/2000/XP. Before moving on, it is probably prudent to mention that the technique employed in IO.DLL for releasing the ports to the application level isn't, strictly speaking, the proper way to do things. The proper way is to have a virtual device driver for Windows 95/98 and a kernel mode driver for Windows NT/2000/XP. This isn't very practical for many people though, nor is it really necessary. There are several successful commercial products on the market that do exactly what IO.DLL does. Let it be noted though that some of them are shady with their explanation of how their product works, meanwhile charging $500 or more for it. Download io.dll 49k io.zip 31k (includes text version of this documentation) C Prototypes void PortOut(short int Port, char Data); void PortWordOut(short int Port, short int Data); void PortDWordOut(short int Port, int Data); char PortIn(short int Port); short int PortWordIn(short int Port); int PortDWordIn(short int Port); void SetPortBit(short int Port, char Bit); void ClrPortBit(short int Port, char Bit); void NotPortBit(short int Port, char Bit); short int GetPortBit(short int Port, char Bit); short int RightPortShift(short int Port, short int Val); short int LeftPortShift(short int Port, short int Val); short int IsDriverInstalled(); Delphi Prototypes procedure PortOut(Port : Word; Data : Byte); procedure PortWordOut(Port : Word; Data : Word); procedure PortDWordOut(Port : Word; Data : DWord); function PortIn(Port : Word) : Byte; function PortWordIn(Port : Word) : Word; function PortDWordIn(Port : Word) : DWord; procedure SetPortBit(Port : Word; Bit : Byte); procedure ClrPortBit(Port : Word; Bit : Byte); procedure NotPortBit(Port : Word; Bit : Byte); function GetPortBit(Port : Word; Bit : Byte) : WordBool; function RightPortShift(Port : Word; Val : WordBool) : WordBool; function LeftPortShift(Port : Word; Val : WordBool) : WordBool; function IsDriverInstalled : Boolean; Visual Basic Prototypes Private Declare Sub PortOut Lib "IO.DLL" (ByVal Port As Integer, ByVal Data As Byte) Private Declare Sub PortWordOut Lib "IO.DLL" (ByVal Port As Integer, ByVal Data As Integer) Private Declare Sub PortDWordOut Lib "IO.DLL" (ByVal Port As Integer, ByVal Data As Long) Private Declare Function PortIn Lib "IO.DLL" (ByVal Port As Integer) As Byte Private Declare Function PortWordIn Lib "IO.DLL" (ByVal Port As Integer) As Integer Private Declare Function PortDWordIn Lib "IO.DLL" (ByVal Port As Integer) As Long Private Declare Sub SetPortBit Lib "IO.DLL" (ByVal Port As Integer, ByVal Bit As Byte) Private Declare Sub ClrPortBit Lib "IO.DLL" (ByVal Port As Integer, ByVal Bit As Byte) Private Declare Sub NotPortBit Lib "IO.DLL" (ByVal Port As Integer, ByVal Bit As Byte) Private Declare Function GetPortBit Lib "IO.DLL" (ByVal Port As Integer, ByVal Bit As Byte) As Boolean Private Declare Function RightPortShift Lib "IO.DLL" (ByVal Port As Integer, ByVal Val As Boolean) As Boolean Private Declare Function LeftPortShift Lib "IO.DLL" (ByVal Port As Integer, ByVal Val As Boolean) As Boolean Private Declare Function IsDriverInstalled Lib "IO.DLL" As Boolean Function Descriptions Please refer to the prototype for the particular language you are using. PortOut Outputs a byte to the specified port. PortWordOut Outputs a word (16-bits) to the specified port. PortDWordOut Outputs a double word (32-bits) to the specified port. PortIn Reads a byte from the specified port. PortWordIn Reads a word (16-bits) from the specified port. PortDWordIn Reads a double word (32-bits) from the specified port. SetPortBit Sets the bit of the specified port. ClrPortBit Clears the bit of the specified port. NotPortBit Nots (inverts) the bit of the specified port. GetPortBit Returns the state of the specified bit. RightPortShift Shifts the specified port to the right. The LSB is returned, and the value passed becomes the MSB. LeftPortShift Shifts the specified port to the left. The MSB is returned, and the value passed becomes the LSB. IsDriverInstalled Returns non-zero if io.dll is installed and functioning. The primary purpose of this function is to ensure that the kernel mode driver for NT/2000/XP has been installed and is accessible. Notes When installing a new io.dll, it may be necessary to first shut off the existing io.sys kernel mode driver for NT/2000/XP. To do this, open up a Command Prompt and enter the command "net stop io.sys". 如果有朋友須要監測Printer Port這裡有個Tools可以幫一些忙!

Parallel Port Monitor

Your Attention Please! A bug was found in Parallel Port Monitor that caused the error "Unable to start the IO.SYS service" to occur on Windows 2000/XP machines. This bug has been found and was fixed on 08/06/02. If you are using an older version of the software, you will want to upgrade now! The Parallel Port Monitor is a utility for viewing and manipulating the state of a parallel port on a Windows 95/98/ME/NT/2000 computer. Download http://geekhideout.com/downloads/parmon.zip (209k ) 網路志工聯盟----Visita網站http://www.vista.org.tw ---[ 發問前請先找找舊文章 ]--- 發表人 - axsoft 於 2002/11/27 17:18:02

我試了一下網頁上的方法來對I/O作存取的動作 但是出來的值不合理.. 我用使用asm.寫成的inportb,outportb function所讀出來的值 跟使用matlab所讀出來的值很接近(研華的PCL833) 但是使用網站的方法讀出來的值就差很多.. 讀到的數值理論上應該都是正數,網站的dll讀出來的值會出現負數.. 不曉得有沒有大大成功使用過網站的方法?

我用BCB5 WinXP 不能RUN喔!!?? ~ 勿在浮沙上面築高塔 ~

------
~ 勿在浮沙上面築高塔 ~

Parallel Port Monitor 真是個好用的軟體 小弟日前遇到的 Case 需以 Printer Port 控燈, 即以此軟體監控並 Debug,才得以順利完成.