Parallel Port Communication Problem
-
Hi! Guys, I am working with VB.NET 2002 on Windows XP. I have a problem while working with parallel port. I have downloaded the dlls needed to communicate with parallel port on Windows XP. But, the program doesn't seems to be working. Isn't there any way to communicate with Parallel Port in Visual Studio.NET 2002 itself? I am really feeling help-less while hardware interfacing comes in my way while working with VS.NET. If you guys know anything please let me know. I am open for comments and suggestions. Thanking you, Ritesh.
-
Hi! Guys, I am working with VB.NET 2002 on Windows XP. I have a problem while working with parallel port. I have downloaded the dlls needed to communicate with parallel port on Windows XP. But, the program doesn't seems to be working. Isn't there any way to communicate with Parallel Port in Visual Studio.NET 2002 itself? I am really feeling help-less while hardware interfacing comes in my way while working with VS.NET. If you guys know anything please let me know. I am open for comments and suggestions. Thanking you, Ritesh.
There is nothing native to .NET. This is because all hardware, including the par/ser ports, is abstracted by the operating system and the processor running in protected mode. You absolutely must have those helper .DLL's to give you the ability to control the port directly. You might want to look at these: http://www.codeproject.com/csharp/csppleds.asp[^] http://www.logix4u.net/[^] RageInTheMachine9532
-
Hi! Guys, I am working with VB.NET 2002 on Windows XP. I have a problem while working with parallel port. I have downloaded the dlls needed to communicate with parallel port on Windows XP. But, the program doesn't seems to be working. Isn't there any way to communicate with Parallel Port in Visual Studio.NET 2002 itself? I am really feeling help-less while hardware interfacing comes in my way while working with VS.NET. If you guys know anything please let me know. I am open for comments and suggestions. Thanking you, Ritesh.
u hv the full admin right to ur NT system? if u dont hv the full admin right although u get all the DLL in sys directory, it's still helpless. u must hv the full admin right to ur NT system, otherwise u need to find a crack program to crack it. But it's quite hard to find such one
-
u hv the full admin right to ur NT system? if u dont hv the full admin right although u get all the DLL in sys directory, it's still helpless. u must hv the full admin right to ur NT system, otherwise u need to find a crack program to crack it. But it's quite hard to find such one
Actually, the User's rights have nothing to do with the problem. You can be a normal (member of) User and have no issues with it at all. The problem is the the INP and OUT instructions can only run in processor Ring0 (Kernel mode). Users programs are restricted to running in Ring3 (User mode). This means that if you try and execute and INP or OUT I/O port instruction, you'll get the infamous Application Exception Error saying something about executing a Priviledged Instruction. The user's rights to the system have nothing to do with this. To get around the problem, you need a kernel mode (Ring0) device driver that can talk to the parallel port, and read and write data to it, and exposes some form of API that a user mode (Ring3) application can talk to. The kernel mode driver contains the INP and OUT instructions that are allowed to run in Ring0, but not Ring3. Now, for a good example of how this is accomplished, see this site: http://www.logix4u.net/[^] RageInTheMachine9532
-
Actually, the User's rights have nothing to do with the problem. You can be a normal (member of) User and have no issues with it at all. The problem is the the INP and OUT instructions can only run in processor Ring0 (Kernel mode). Users programs are restricted to running in Ring3 (User mode). This means that if you try and execute and INP or OUT I/O port instruction, you'll get the infamous Application Exception Error saying something about executing a Priviledged Instruction. The user's rights to the system have nothing to do with this. To get around the problem, you need a kernel mode (Ring0) device driver that can talk to the parallel port, and read and write data to it, and exposes some form of API that a user mode (Ring3) application can talk to. The kernel mode driver contains the INP and OUT instructions that are allowed to run in Ring0, but not Ring3. Now, for a good example of how this is accomplished, see this site: http://www.logix4u.net/[^] RageInTheMachine9532
Hi! Folks,:) Below are the few queries that have arised in my mind after looking at the code in file "inpout32drv.cpp". These are few of the hardcoded paths, that I have found, 1. C:\kernel_mode_driver_source\i386\hwinterface.pdb 2. nsf.\i386\hwinterface.sys 3. In CreateService function call you are using the hardcoded path "System32\\Drivers\\hwinterface.sys", but I have the "hwinterface.sys" file in the application directory only. Also, I have no such file in my "system32\drivers" directory. First of all I don't know these paths stands for what? Second thing is, Any of the above specified paths are not valid on my system. Can these be a reason, that program is not working on my system? I am sending the same at your e-mail box. Thanking You, Regards, Ritesh.