Page 1 of 1

Windows 10 on IPC2

Posted: Thu Sep 17, 2015 8:47 am
by bjorn_latronix
Hi. I want to install Win10-pro-64bit on an IPC2. Did you try it? Should I expect any trouble?

Re: Windows 10 on IPC2

Posted: Fri Sep 18, 2015 3:38 pm
by irads
Win10 should install with no major issues on IPC2. Please be advised that Compulab does not support it officially yet and we did not run rigorous tests on Windows 10, so we cannot offer support in case you encounter problems. That said, the likelihood of major problems is low.

Re: Windows 10 on IPC2

Posted: Fri Jan 29, 2016 8:36 am
by bjorn_latronix
I installed Win10 Pro on IPC2 with no issues late 2015. During pilot tests the IPC2 intermittently lost contact with one of the ethernet ports. The port had be disabled / reenabled or the PC had to be restarted to regain contact. I had no luck solving it with Driver updates from Intel. I had to drop the project for a while but in a few weeks I will restart the tests.

This may have absolutely nothing to do with the IPC2 but I would like to hear if anyone else has seen the problem or perhaps solved it.

Re: Windows 10 on IPC2

Posted: Wed Feb 03, 2016 10:48 am
by mbirger
Please let us know what drivers have you been using?
I will forward it to our Windows expert.

Re: Windows 10 on IPC2

Posted: Mon Feb 15, 2016 2:30 pm
by Leonid
Hello,

1. Please, provide us the SN and PN of your IPC2.

2. What Ethernet controller lose connection? i211 or i218?

3. When connection is lost, do you see the Ethernet controller in the Device Manager?

Re: Windows 10 on IPC2

Posted: Fri Dec 16, 2016 7:21 am
by bjorn_latronix
Hi,

Sorry about this late reply. The issue is still there on the 12 unmanned Win10-1511-IPC2s that I have sent out. These systems are extremely stable and the problem is manageable. The issue is shurely caused by Microsoft/Intel/Firewall rather than Compulab hardware.

The issue arises in the Intel-218 on Win10-startup. The Ethernet port is still apparently up but I loose connection to some UDP-ports in the range 6000:6208. I can fix it by taking down the Ethernet-switch or disable+enable the Ethernet port in Windows. On each startup I run this Powershell script that takes down and up the port automatically before starting the program.

#Take the network down and up to avoid weird network trouble (some ip/ports will not work)
Get-NetAdapter -name camnet | Disable-NetAdapter -Confirm:$false
Get-NetAdapter -name camnet | Enable-NetAdapter -Confirm:$false
sleep 4

Answers:
1. Example:
SN: 1160114-05035
PN: IPC2-C4600-WACB-FMUSB3-ACF

2. i218

3. I think it was visible in the Device Manager. I should have noticed if it was gone. I will check it but it may be a while.

4. I use the 12.15.22.6. This is the most recent driver that Intel released Powershell management for. I am aware that a driver update may solve this issue but I really need the management.