Hi,
In this state I checked and yes CPVNM was running, I have right clicked to restart it and it has hung on "stopping".
Ok so the service is not crashed, it's just unable to see the ethernet port. At this time you have two CopperLan networks: the first inside this computer, and the second composed of all other interconnected machines. When the ethernet interface is up again, both networks are merging to make one.
And there is a problem on service stopping. Send me an email at
pca@copperlan.org then I'll give you a download link to an intermediate build fixing the service stop issue.
BTW I didnt actually disable touchosc so maybe this and skype and network activity monitor dont clash with CL. I'm going to re-enable them all at startup.
I don't think so. CopperLan is not IP based and goes along other protocols like those used by Skype and OSC without interfering.
Yes this time copperlan sees the card and is working as it should.
Good to read!
1) Have I perhaps barked up the wrong tree with this service delay time thing? Although it appears to have got good results I'm just skeptical with all things computers these days.
No you had a very good idea actually!
It is possible that the CPVNM service meets some weird issue if the ethernet driver is not yet stable when it's starting. We'll check this to reinforce the VNM about it.
2) Are there any other services from copperlan that are relevant?
No
3) The delay time minimum is 1minute and I'm inpatient when I have an idea in my head. Do you think just setting CPNVM to restart on failure will work?
Yes it should be with the new version I'll give you. Your current version of the VNM has a problem during stopping, this is a reported issue that has been fixed in the forthcoming release.
I forgot to ask if you can address my query on snapshots being effective.
Actually, the snapshot issue is due to the Ethernet port issue... if the problematic PC is disconnected from the network it's just snapshooting itself and the other computers grab information for all machines but the problematic PC... And if the CPVNM service is down for any reason the related software & MIDI ports are not available along the network, so they can't be snapshot.
This is why I started by asking you the CPVNM status when the issue occurs
It's also worth noting that when it drops my ethernet controller any patching to that pc has lost its location data and is shown as a long string of numbers and the assignment isnt working.
This is because the location is not lost actually! The port is not able to locate the destination on the network because it's located on another computer which is not reachable at the moment, but you'll get back the connection as soon the target machine is up on the network again!
...it was able to go off the network name of the pc rather than the mac id of the ethernet card. I could be way out here though. And also a way to export a snapshot to our own folder.
Actually the snapshot is using CopperLan IDs, independent from the machine it's running on. But when you recall a snapshot it's first seeking on the network to check that the target applications are available. It's not the case when your problematic computer is not connected to the rest of the CopperLan network.
But again, you don't have to worry and to re-create your setup each time. The snapshot will be totally recalled as soon the Ethernet port is up and the win8 machine is on the global CopperLan network. Connections are not lost, they just can be unavailable at some time if the target machine is not accessible. But these unavailable connections are automatically reactivated as soon the target is there again.