search

albertjan / PipeToCom

Couple your Hyper-V namedpipe comport to a real one.
55 stars 21 forks source link

NP2COMService blocks the com port #19

Closed ghost closed 11 years ago

ghost commented 11 years ago

Dear Albert-Jan,

I am trying to use your neat little service to accomplish something very strange indeed. Sysinternals PortMon supports only 32-bit Windows, but I have 64-bit. So what I did, was to get the "Windows XP Mode" virtual machine for my Windows 7, which runs 32-bit. Sure enough, PortMon works there.

So I tried to access the COM port via a pipe. I managed to create one using your handy Service, but as a bad news to me, it still blocks the COM port. As non-blocking access (simply listening) to the serial port is my goal, I wondered whether your service could be modified easily to accomplish just that.

Other than that, I am happy to hear any off-topic solutions to my problem.

Better Vibes, Leroy Jenkem

albertjan commented 11 years ago

Sorry can't be done from c#

http://social.msdn.microsoft.com/Forums/en-US/csharpgeneral/thread/3607b601-9a36-4d27-a816-a51b2ff589e7/

you could run your program that uses the comport in the virtual machine along with the portmon that'll probably work

ghost commented 11 years ago

Thanks for your suggestion, it solved my problem. The "Windows XP mode" does not support binding host COM ports with a high number. As unlogical as it may seem, to make a COM port available to the VM, set its number to 1 or 2 from the host Device Manager.

Albert-Jan Nijburg notifications@github.com schrieb:

Closed #19.

Reply to this email directly or view it on GitHub: https://github.com/albertjan/PipeToCom/issues/19