Inpout32 Dll Serial Port Example
Thanks veena,but i would like to tell u that first i will have to copy this file intoC:windowssystem32 and then i will have to register.i wont work without system registration.i had first done the same thing what u have told to me.n then i tried this thing later.but still i isn't work.thanks again for the ur guidance.regards,pulkitVeenaMG via visualbasic-l wrote:Hi,Just copy it to folder:Windowssystem32It may work without registering explicitly.RegardsVeena.
Hi Phil,First of all THANK YOU for this incredibly useful update to InpOut32. I am attempting to use QB64 (v 1.00) on a Window 7 machine with an on-board COM port (i.e. Hardware port, not a USB adapter) to talk to a voltmeter via serial port. I am having trouble opening the port.I have installed the 32 bit inpout32.dll from the 1501.zip package using InstallDriver.exe.
I have confirmed that c:windowssystem32driversinpoutx64.sys was installed. I am using the code described on the QB64 wiki here: qb64 dot net /wiki/index.php/PortAccessLibraries to open the COM port by sending bit-level commands to the UART ports as shown in the code immediataly under 'COM Ports' halfway down the page.And, everything works, BUT ONLY after I have loaded the free serial port test program here: microridge dot com /comtestserial.htm With that test program I can send characters to the COM port and change it's state manually. If I run my QB64 program concurrently, I can do the same. As soon as I shut down the test program, I can no longer do anything with the COM port from Basic.I also wrote the code attached below to continuously query the UART registers of COM1. It seems to work fine, returning the values of the bytes associated with the COM port, but again, only when the serial test port program is running. Once I stop that test program, the values returned by my QB64 program are all 255, i.e.
It doesn't seem to be able to read the port.SO, do you have any suggestions as to what is going on and how to fix it? I'm brand new to the forum.
Inpout32 Dll Serial Port Example Key
I've been using inpout32 for several years with a dot net visual basic application on a xp machine. I'm now trying to get the same application working on a new windows 7 machine with a usb - parallel port adapter cable. I haven't found a download link that specifically refers to 32 bit windows 7, so I just copied my old inpout32.dll from the xp machine to the w7 machine.
I see that my app uses hard coded port 56448 (&HDC80) when itlzg the parallel port i/o. It's not working - software exception when trying to write to the port:'(WrtPort) error: Unable to load DLL 'inpout32.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)'(I had put the old inputout32.dll in the same folder as my application executable in the windows 7 system).I've completely forgotten how I got all this working on the XP system.Is there an 'installation' process to incorporate the dll?Thanksftbrady. PhilThanks for the info, but I'm sorry to say there's a little confusion remaining.You wrote:If you use the latest version of Inputx64 on my website, it should work with both x86 (inpout32.dll) and x64 (inpoutx64.dll). The 32but DLL contains drivers for both x86 and x64 editions of Windows and there is an Installer (install.exe) which forces elevated access (UAC) which is required the first time InpOut32 is run to ensure you have the privileges to install the driver.I was unable to find 'the latest version of Inputx64'Is that a typo? What name, exactly, should I be looking for in the downloads?So sorry I get easily confused.Thanks for all you do.ftbrady.
Danube wrote:Hi Phil,Thanks for the reply. Are you saying I should include inpoutx64.dll instead of inpout32.dll in my QB64 code?Under Win 7, I see that QB64 runs as a 32 bit app, so installed the input32.dll. Should I use the x64 version instead?DanNo, if qb64 runs as a 32bit app, you should use inpout32.dll from my website, which will install a 64bit driver on Win 7 x64 or 32bit driver on Win 7 x86. You have to run elevated to install the driver (ie.
The first time you use the DLL). There is an installdriver.exe to achieve that, or you can run QB64 as administrator too.EDIT: I see there is some confusion here because ftbrady hijacked your thread. Don't you hate it when that happens! My reply was to him rather than you. To be honest, I have no idea why you have that problem were it only works when the port is open in another program.
I have in the past hit the serial port registers directly using InpOut32 (and that's why I ported it in the first place) but it was many years ago and I dont actually use InpOut32 myself anymore. So unfortunately, i dont know if I can help you. Thanks Phil,Yeah, it's a weird problem. I think your drivers are installed fine. The.sys and.dll are in the right places. And it works, but of course, only with that third party app running.
If I have time, I'll try to find a 4th party app. And see if it too works.But an interesting thing happened today. My computer reboot on me (it does that every once in a while), and when it came back up, some COM port bits must have been stuck because for a while my QB program worked fine WITHOUT the 3rd party com app.! I then did another reboot, and the problem returned.I just wish I knew more about how the serial port works under Win7 (well, enough to figure this out, and no more!).
Clearly there are some people doing it, but not in BASIC usually. I will try to see if I can get the COM port to work in VBA.Dan. No worries about hijacking my thread. We're working towards the same goal more or less.I really don't think my problem is with inpout32.dll, nor its installation, but rather my implementation of windows.Wait a minute.
Inpout32 Dll Serial Port Example Free
Tell me more about the serial port you are using. Is it on USB? The big difference between my work machine and my home machine is that at home I have to use a USB-serial adapter.
But at work, I've got some annoying company Anti-virus, and I need to ask if that has any control over the serial ports.If I can get input32.dll working at home, it will go a long way towards convincing me the problem is my machine at work, and not win 7.Dan.