search

albertjan / PipeToCom

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

Installation Guide #10

Closed kaznad closed 5 years ago

kaznad commented 12 years ago

Hi, Please advise how do I install this service? Thanks :)

albertjan commented 12 years ago

After you've installed .net 3, 3.5 and 4. You can run %WINDIR%\Microsoft.NET\Framework\v4.0.30319\InstallUtil -t Path\To\NP2COMS.exe

Use NP2COMV to make a .n2c file drop that in the Path\To\NP2COMS.exe

delete example.n2c

run: c:\>net start NP2COMService

or go to services and start it.

Goodluck

kaznad commented 12 years ago

Hi Albert,

Thank you so much for your help. I am able to install it now.

Now I am not sure how to use the NP2COMV tool.

I would like to install a GPRS Modem. How should I go about doing it?

Lastly I would like to thank you again for taking the time to send me the installation guide.

:)

Regards, Zak

On Tue, Jan 10, 2012 at 4:57 PM, Albert-Jan Nijburg < reply@reply.github.com

wrote:

After you've installed .net 3, 3.5 and 4. You can run %WINDIR%\Microsoft.NET\Framework\v4.0.30319\InstallUtil -t Path\To\NP2COMS.exe

Use NP2COMV to make a .n2c file drop that in the Path\To\NP2COMS.exe

delete example.n2c

run: c:\>net start NP2COMService

or go to services and start it.

Goodluck

Reply to this email directly or view it on GitHub: https://github.com/albertjan/PipeToCom/issues/10#issuecomment-3427015

albertjan commented 12 years ago

Hi, you create a virtual comport on your virtual machine using the settings dialog like so:

settings hyper-v

remember the name you gave the serialport on the virtual machine here

this is what you look for in the combobox on the left in NP2COMV:

NP2COMV

on the rigth in NP2COMV you use the correct SerialPort settings (they're probably correct as default).

Then you press Write config file. This writes a n2c file to the directory of NP2COMV.

Copy this file to Path\To\NP2COMS.exe remember to delete the example file.

kaznad commented 12 years ago

Hi,

I have an error message when I click on test. I followed your example. Named Pipe has been assigned as comport. and the Namedpipe in the NP2COMV is also sert as .\pipe\comport I get an error as below.

[image: Capture.JPG]

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentNullException: Value cannot be null.
Parameter name: input
   at System.Text.RegularExpressions.Regex.Match(String input)
   at NP2COMV.Form1.button1_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
albertjan commented 12 years ago

This exception occurs when the selectedItem of combobox is empty. It's probably a bug on my side, I'll have a look at it. To fix it in the meantime: select the correct namedpipe from the combobox instead of typing it in. I should be in the list if the virtual machine created it.

Remember NP2COM should be run on the host machine. Not on the virtual machine.

kaznad commented 12 years ago

Hi,

Thanks for the advice.

I tried the named pipe from the list which is lsass. I entered it in the hyperv settings as well.

When I tried to use the GPRS modem in the virtual server i did not work.

How do I test if the service is working? In the tool, when I click test, nothing appears below. This is when the NP2com server is stopped. If the service is started and I test, it crashed.

Any way to test this?

On Wed, Jan 11, 2012 at 5:22 PM, Albert-Jan Nijburg < reply@reply.github.com

wrote:

This exception occurs when the selectedItem of combobox is empty. It's probably a bug on my side, I'll have a look at it. To fix it in the meantime: select the correct namedpipe from the combobox instead of typing it in. I should be in the list if the virtual machine created it.

Remember NP2COM should be run on the host machine. Not on the virtual machine.

Reply to this email directly or view it on GitHub: https://github.com/albertjan/PipeToCom/issues/10#issuecomment-3443890

albertjan commented 12 years ago

\\.\pipe\lsass is a system pipe. Do not touch. just name the pipe comport like I showed you in the example. Maybe restart your virtual machine. After you've done that, start NP2COMV now \\.\pipe\comport should then be in the dropdown list. Then try it.

kaznad commented 12 years ago

Hi,

I tried to use the pipename comport in both the vitual server settings and the write the config file pipe name as comport as well. When I tried to click on test on the NP2COMV tool, i get a com1 access denied. Then I tried to stop the NP2COM server and tried again the button change from test to testing but there was no output in the bottom. The modem does not work as well.

Please advise.

On Wed, Jan 11, 2012 at 6:47 PM, Albert-Jan Nijburg < reply@reply.github.com

wrote:

'.\pipe\lsassis a system pipe. Do not touch. just name the pipe comport like I showed you in the example. Maybe restart your virtual machine. After you've done that, start NP2COMV now.\pipe\comport` should then be in the dropdown list. Then try it.

Reply to this email directly or view it on GitHub: https://github.com/albertjan/PipeToCom/issues/10#issuecomment-3444794

kaznad commented 12 years ago

Hi,

It finally works!

It was a stupid mistake on my part. I should have used com port 3 instead.

The only thing now is, it sometimes doesn't work and I have to restart the virtual server. Is there anything I can do to fix this. Once the server is live, it is not practical to restart the server.

On Thu, Jan 12, 2012 at 11:45 AM, Mohd Zakaria kazak21@gmail.com wrote:

Hi,

I tried to use the pipename comport in both the vitual server settings and the write the config file pipe name as comport as well. When I tried to click on test on the NP2COMV tool, i get a com1 access denied. Then I tried to stop the NP2COM server and tried again the button change from test to testing but there was no output in the bottom. The modem does not work as well.

Please advise.

On Wed, Jan 11, 2012 at 6:47 PM, Albert-Jan Nijburg < reply@reply.github.com

wrote:

'.\pipe\lsassis a system pipe. Do not touch. just name the pipe comport like I showed you in the example. Maybe restart your virtual machine. After you've done that, start NP2COMV now.\pipe\comport` should then be in the dropdown list. Then try it.

Reply to this email directly or view it on GitHub: https://github.com/albertjan/PipeToCom/issues/10#issuecomment-3444794

albertjan commented 12 years ago

Hi,

Thats cool.

It's absolutely not practical to restart the vm once it's live.

But I need more information than "it stops working".

Do you have a logfile with such a failure it in? NP2COMS should log some stuff.

Does it happen at random or when you do something special?

RanmaKei commented 11 years ago

I notice it loses communication in a 24 hour period. Currently, I have a task scheduled to restart the service in 24 hours, and then it is able to reestablish communication. Also restarting a VM seems to also break the communication, so I have a shutdown and start-up script on the VM to restart the HOST's NP2COMS service. I'm not sure if this is bad to restart the service when the port is constantly being used, but it seems like the only option to make it reliable.

albertjan commented 11 years ago

@RanmaKei Does the service crash or does just "stop working"? Restarting the vm resets the namedpipe I'll have to look into that, I think I should be able to see when that happens and then reconnect to the pipe. I'd expected to get an exception when the connection is dropped. What do you use as a vm os?

norm8332 commented 11 years ago

Hello, First I'd like to thank you for this program..I have it working but as above while the service continues to run it does stop functioning at one point. I'm still testing to attempt to find out when and why but I believe it is when my host backup of the VMs runs. It suspends/pauses the VMs for a minute. restarting the np2coms service makes it work again without restarting the guest. The guest OS in this case is QNX 4.5 (linux -like) OS. Thanks

albertjan commented 11 years ago

Hi! @norm8332 you're welcome. I have to setup my dev environment for this I think I can check what the state of the pipe is. And then when it goes down restart it asap. I don't think I can asure not to drop any bytes. Most com applications aren't really fault tolerant they don't expect the connection to be down. So I don't know wether or not your guest os and the application there will handle this correctly.

hicham47 commented 10 years ago

Hi !

i have probleme to start the service NP2COMService and access denied with com1

thanks to help me

ps : 2008 R2 server + Hyper-v and VM = 2003 server

albertjan commented 10 years ago

Have you tried running it as administrator? Isn't there another program using the comport.

hicham47 commented 10 years ago

yes local account running service is local administrator and comport is not used

thanks

albertjan commented 10 years ago

the other pipetocom app is also off?

albertjan commented 10 years ago

Windows is almost always right here. You either don't have enough rights or it's used by a different program.

hicham47 commented 10 years ago

I have tested it in my pc running W7 Pro 64 : i have running CMD as administrator and service runs with no problem

i'm trying to unstall and re install to in my 2008 server

thanks

hicham47 commented 10 years ago

np2com

on the 2008 server I still have the same problem although the service is installed as administrator

albertjan commented 10 years ago

Can you post the logs too? Have a look at this tool if you can get some more info. http://technet.microsoft.com/en-us/sysinternals/bb896644.aspx

hicham47 commented 10 years ago

DEBUG 17:13:11,085 NP2COMService OnStart - Loaded (1) connection files DEBUG 17:13:51,023 NP2COMService OnStart - Loaded (1) connection files etc.......

NP2COMV.EXE.CONFIG : <?xml version="1.0"?>

NP2COMS.INSTALLLOG : assemblypath = E:\Support\NamedPipe2COM\NP2COMS.exe Suppression de la source EventLog NP2COMService. Le service NP2COMService est en cours de suppression du système... Le service NP2COMService a été retiré avec succès du système. Installation de l'assembly 'E:\Support\NamedPipe2COM\NP2COMS.exe'. Les paramètres affectés sont : logtoconsole = t = logfile = E:\Support\NamedPipe2COM\NP2COMS.InstallLog assemblypath = E:\Support\NamedPipe2COM\NP2COMS.exe Installation du service NP2COMService en cours... Le service NP2COMService a été installé avec succès. Création d'une source EventLog NP2COMService dans le journal Application... Validation de l'assembly 'E:\Support\NamedPipe2COM\NP2COMS.exe'. Les paramètres affectés sont : logtoconsole = t = logfile = E:\Support\NamedPipe2COM\NP2COMS.InstallLog assemblypath = E:\Support\NamedPipe2COM\NP2COMS.exe

albertjan commented 10 years ago

Or whats the contents of the config file? comport.n2c. And there maybe some information in your windows events. eventvwr

hicham47 commented 10 years ago

N2C file : 

<?xml version="1.0"?>
<Settings xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <MachineName>.</MachineName>
  <NamedPipe>comport</NamedPipe>
  <ComPort>COM1</ComPort>
  <BaudRate>38400</BaudRate>
  <StopBits>One</StopBits>
  <Parity>None</Parity>
  <DataBits>8</DataBits>
</Settings>

in the Windows event viewer
n2p

albertjan commented 10 years ago

Are you sure there is a COM1? and are you absolutely sure nothing else uses the comport?

hicham47 commented 10 years ago

There are COM1 and COM2 and no device connected at time PORTMON says "not connected" and when i select COM2 on the NP2COMV.EXE it says "No response" and crash

albertjan commented 10 years ago

when you start to service you should turn np2comv off. Other than that I can't help you any further.

hicham47 commented 10 years ago

oh it's OK for the service, it start well in fact, the process NP2COMV.EXE was executed while NP2COMV program was closed.

now i going to connect my medical card reader and see if the software on the VM detects the same drive

thank you very much Albertjan

I would return when I'm doing the tests

dcrowson commented 10 years ago

Hello,

I'm trying to get this working on Windows 2012 R2 but I get the following error when I attempt to install the service:

C:>%WINDIR%\Microsoft.NET\Framework\v4.0.30319\InstallUtil -t c:\NP2COM\np2coms .exe Microsoft (R) .NET Framework Installation utility Version 4.0.30319.33440 Copyright (C) Microsoft Corporation. All rights reserved.

Exception occurred while initializing the installation: System.IO.FileLoadException: Could not load file or assembly 'file:///c:\NP2COM\ np2coms.exe' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515).

Note that I also get an error when running the configuration program so I just manually edited the example configuration file.

Unhandled exception... Value cannot be null. Paramter name: input.

Any help would be appreciated!

Dan

albertjan commented 10 years ago

Are you sure none of the files are blocked. Try looking for the streams application and running streams /s /d * in c:\np2com.

Sent from my iPhone

On 17 sep. 2014, at 22:58, "dcrowson" notifications@github.com wrote:

Hello,

I'm trying to get this working on Windows 2012 R2 but I get the following error when I attempt to install the service:

C:>%WINDIR%\Microsoft.NET\Framework\v4.0.30319\InstallUtil -t c:\NP2COM\np2coms .exe Microsoft (R) .NET Framework Installation utility Version 4.0.30319.33440 Copyright (C) Microsoft Corporation. All rights reserved.

Exception occurred while initializing the installation: System.IO.FileLoadException: Could not load file or assembly 'file:///c:\NP2COM\ np2coms.exe' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515).

Note that I also get an error when running the configuration program so I just manually edited the example configuration file.

Unhandled exception... Value cannot be null. Paramter name: input.

Any help would be appreciated!

Dan

— Reply to this email directly or view it on GitHub.

dcrowson commented 10 years ago

Sorry, unblocking fixed the install service issue. When I try to start it, it returns could not be started. When I look in services it is in a 'Starting' state.

The unblocking didn't fix the configuration program but I had just edited the file manually.

Dan

hicham47 commented 10 years ago

Hello ! I just do the tests the drive connected on the server is recognized on COM2 VM Now it has to work over RDP

hicham47 commented 10 years ago

Hello Dan I had the same problem with the service that remains on "start" you must see if in the Task Manager process "N2COMV.EXE" appears, in which case it would kill him. Also see if any other program does not use the COM port selected

albertjan commented 10 years ago

@dcrowson please paste your n2c file here and the logfile from the application directory

dcrowson commented 10 years ago

On a whim, I checked to see if it was working even though it showed "Starting". I found that it was. When I looked again, it showed "Running". I'll keep testing it but as of now it works.

Willing to help test if you want to determine the issue with the NP2COMV.exe program.

Dan

dcrowson commented 10 years ago

Sorry for all of these posts.. I've run into another issue. When I shutdown the VM connected to the com port pipe, the NP2COMService dies. If I have the service set to 'Restart the service' in Recovery, it will stay in a 'Starting' state until I turn the VM back on.

Here are the errors:

Application: np2coms.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.IOException Stack: at System.IO.Pipes.PipeStream.WinIOError(Int32) at System.IO.Pipes.PipeStream.BeginWriteCore(Byte[], Int32, Int32, System.AsyncCallback, System.Object) at System.IO.Pipes.PipeStream.WriteCore(Byte[], Int32, Int32) at NP2COM.Connection.NamedPipeRunner(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart(System.Object)

Faulting application name: np2coms.exe, version: 1.0.0.0, time stamp: 0x4ed61e50 Faulting module name: KERNELBASE.dll, version: 6.3.9600.17278, time stamp: 0x53eebf2e Exception code: 0xe0434352 Fault offset: 0x000000000000606c Faulting process id: 0xd58 Faulting application start time: 0x01cfd354b2f72e65 Faulting application path: C:\Program Files (x86)\NP2COM\np2coms.exe Faulting module path: C:\Windows\system32\KERNELBASE.dll Report Id: 4efb03d7-3f48-11e4-80c3-002590f58cd3 Faulting package full name: Faulting package-relative application ID:

Fault bucket , type 0 Event Name: CLR20r3 Response: Not available Cab Id: 0

Problem signature: P1: np2coms.exe P2: 1.0.0.0 P3: 4ed61e50 P4: System.Core P5: 4.0.30319.33440 P6: 5200436c P7: 130a P8: 15 P9: System.IO.IOException P10:

Attached files:

These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_np2coms.exe_90408ec6f11723638cc0d6af82771731160484a_fa4818ee_082afb0c

Analysis symbol: Rechecking for solution: 0 Report Id: 4efb03d7-3f48-11e4-80c3-002590f58cd3 Report Status: 4100 Hashed bucket:

Fault bucket , type 0 Event Name: CLR20r3 Response: Not available Cab Id: 0

Problem signature: P1: np2coms.exe P2: 1.0.0.0 P3: 4ed61e50 P4: System.Core P5: 4.0.30319.33440 P6: 5200436c P7: 130a P8: 15 P9: System.IO.IOException P10:

Attached files:

These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_np2coms.exe_90408ec6f11723638cc0d6af82771731160484a_fa4818ee_082afb0c

Analysis symbol: Rechecking for solution: 0 Report Id: 4efb03d7-3f48-11e4-80c3-002590f58cd3 Report Status: 0 Hashed bucket:

Dan

albertjan commented 10 years ago

This is a known error. You can just configure the service to restart automatically. :smile: I should fix it but I don't have a lot of time to maintain this tool.

Sent from my iPhone

On 18 sep. 2014, at 17:33, "dcrowson" notifications@github.com wrote:

Sorry for all of these posts.. I've run into another issue. When I shutdown the VM connected to the com port pipe, the NP2COMService dies. Here are the errors:

Application: np2coms.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.IOException Stack: at System.IO.Pipes.PipeStream.WinIOError(Int32) at System.IO.Pipes.PipeStream.BeginWriteCore(Byte[], Int32, Int32, System.AsyncCallback, System.Object) at System.IO.Pipes.PipeStream.WriteCore(Byte[], Int32, Int32) at NP2COM.Connection.NamedPipeRunner(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart(System.Object)

Faulting application name: np2coms.exe, version: 1.0.0.0, time stamp: 0x4ed61e50 Faulting module name: KERNELBASE.dll, version: 6.3.9600.17278, time stamp: 0x53eebf2e Exception code: 0xe0434352 Fault offset: 0x000000000000606c Faulting process id: 0xd58 Faulting application start time: 0x01cfd354b2f72e65 Faulting application path: C:\Program Files (x86)\NP2COM\np2coms.exe Faulting module path: C:\Windows\system32\KERNELBASE.dll Report Id: 4efb03d7-3f48-11e4-80c3-002590f58cd3 Faulting package full name: Faulting package-relative application ID:

Fault bucket , type 0 Event Name: CLR20r3 Response: Not available Cab Id: 0

Problem signature: P1: np2coms.exe P2: 1.0.0.0 P3: 4ed61e50 P4: System.Core P5: 4.0.30319.33440 P6: 5200436c P7: 130a P8: 15 P9: System.IO.IOException P10:

Attached files:

These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_np2coms.exe_90408ec6f11723638cc0d6af82771731160484a_fa4818ee_082afb0c

Analysis symbol: Rechecking for solution: 0 Report Id: 4efb03d7-3f48-11e4-80c3-002590f58cd3 Report Status: 4100 Hashed bucket:

Fault bucket , type 0 Event Name: CLR20r3 Response: Not available Cab Id: 0

Problem signature: P1: np2coms.exe P2: 1.0.0.0 P3: 4ed61e50 P4: System.Core P5: 4.0.30319.33440 P6: 5200436c P7: 130a P8: 15 P9: System.IO.IOException P10:

Attached files:

These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_np2coms.exe_90408ec6f11723638cc0d6af82771731160484a_fa4818ee_082afb0c

Analysis symbol: Rechecking for solution: 0 Report Id: 4efb03d7-3f48-11e4-80c3-002590f58cd3 Report Status: 0 Hashed bucket:

Dan

— Reply to this email directly or view it on GitHub.

hicham47 commented 10 years ago

my card reader works through the RDP from a thin client VM to Hyper-v against only by ADMINISTRATOR for User, the COM port is not detected ...

SunSken commented 10 years ago

Hello.

Thanks for your tool. I'm trying to understand how to use the named pipe created by Hyper V. I notice that your test tool also need admin rights to communicate with the named pipe. Is there some workaround for this? I'm trying to add the pipe name in the Group Policy Editor under "Named pipes that can be accessed anonymously", but with no success so far.

Thanks!

/Daniel

ghost commented 9 years ago

Hello I have a problem. I run this OK: %WINDIR%\Microsoft.NET\Framework\v4.0.30319\InstallUtil -t Path\To\NP2COMS.exe

Then i run NP2COMV to generate new config file. I setup parameters and try to save. I have an error on the screen. bug

I have installed Microsoft .NET Framework 4.5.1 (4.5.50938)

Please help me...

eddelac commented 9 years ago

I've followed the install steps with success, registered the service, created the named pipe, created the config file using the named pipe, saved the config file on the same path, deleted the example config.

But the service stops just after starting it. The virtual machine is on. I'm im missing something?

dcrowson commented 9 years ago

I found this to happen if the device using the com/serial port wasn’t running or connected.

Dan

Dan Crowson

IS Director

CMS Communications, Inc.

722 Goddard Ave

Chesterfield MO 63005

dcrowson@cmsc.com mailto:dcrowson@cmsc.com

www.cmsc.com http://www.cmsc.com/

Expertise you need, the choice you deserve.

From: Edgar de la Cruz [mailto:notifications@github.com] Sent: Wednesday, March 11, 2015 3:49 PM To: albertjan/PipeToCom Cc: dcrowson Subject: Re: [PipeToCom] Installation Guide (#10)

I've followed the install steps with success, registered the service, created the named pipe, created the config file using the named pipe, saved the config file on the same path, deleted the example config.

But the service stops just after starting it. The virtual machine is on. I'm im missing something?

— Reply to this email directly or view it on GitHub https://github.com/albertjan/PipeToCom/issues/10#issuecomment-78368148 . https://github.com/notifications/beacon/AIZ2sWoHMGxP1f5WPwB-0kQtmwE1plUWks5n0KG9gaJpZM4AlvyR.gif

eddelac commented 9 years ago

@PiterEL I had the same problem, it seems to be related with the folder permissions. Try running the program as Administrator.

albertjan commented 9 years ago

@PiterEL It might be due to the fact your running vmware. It creates a namedpipe with a weird name. @eddelac Might be right aswel.

@PiterEL the config files are really easy to edit by hand. have a look at example.n2c you can probably edit that to fit your needs.

albertjan commented 9 years ago

@eddelac did you fix your problem? There is a log file in the directory. If you could open a new issue and post that logfile there. I can have a look and see whats going wrong.

fgmike commented 9 years ago

Hi,

Getting the same error as @PiterEL. The named pipe in the example file, should I change that from com to .\pipe\comport for example?

How else should I edit it, as I cannot see an existing named pipe on my Hyper-V Server 2012 R2 listed when I run np2comv.

Any chance also of fixing the image examples in your setup instructions above? I could not see it to compare.

Trying to get my head around these named pipes is causing some extra grey hairs.

Any help Appreciated.

dayers commented 9 years ago

Just set this up successfully mapping a hyperv vm com port to a physical com port. I followed the steps below in order:

  1. Install tera term on host machine to give you something to test your terminal connection with.
  2. Install driver for usb to serial cable if required.
  3. Insert usb to serial cable.
  4. Launch tera term - select serial - check com usb to serial cable inserted in is port listed. Use device manager com ports or at a command prompt type c:\change port /query.
  5. Install NP2com - You can run %WINDIR%\Microsoft.NET\Framework\v4.0.30319\InstallUtil -t Path\To\NP2COMS.exe.
  6. Create named pipe for vm - launch hyperV manager - highlight VM (vm off at this point) - select settings in lower windows - com1 - enter a name for pipe e.g comportvm. Leave remote computer box inactive.
  7. Start VM (login not reuired at this point).
  8. Run NP2com\NP2comv.exe as an administrator to create a N2C profile; Select pipe name from right named pipe drop down box - comportvm - this is near the bottom of the list Select the settings you want to use -serial port, baud rate, stop bits and parity i.e com4, 9600, 8, none, 1
  9. Select write config file from options on right hand side.
  10. Name and save the file in the NP2COM folder. This is the config file associated with the named pipe from the VM.
  11. Goto services on the host machine and start the NP2COMService. (USB to Serial Cable must be connected at this point).
  12. Logon to vm - install and launch tera term - select com port to use for connection - hit return until output returned.

issues

Named pipe created on VM will net be visible in NP2comv untill vm is started; NP2comservice will not start unless usb to serial cable connected;

vibac commented 9 years ago

albertjan,

I have a questions regarding the install and I am hoping you or someone here can assist me, do we need to complete this installation on both host and guest?

albertjan commented 9 years ago

Do you have .net 3.5 and less installed? ;)

Sent from my iPhone

On 30 jul. 2015, at 19:50, vibac notifications@github.com wrote:

albertjan,

I have a questions regarding the install and I am hoping you or someone here can assist me, do we need to complete this installation on both host and guest?

I also keep getting this error message when trying to register the service; C:\Windows\system32>c:\windows\microsoft.net\framework\v4.0.30319\installutil.ex e C:\NP2COM\NP2COMS.exe Microsoft (R) .NET Framework Installation utility Version 4.0.30319.17929 Copyright (C) Microsoft Corporation. All rights reserved.

Exception occurred while initializing the installation: System.IO.FileLoadException: Could not load file or assembly 'file:///C:\NP2COM\ NP2COMS.exe' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515).

— Reply to this email directly or view it on GitHub.