Preventing Reboots in Windows 10 for Long-Term Tests

[JohnJoyceFlusso]

Ah, I should have been clearer about the USB-to-serial thing (though it's not the main thrust of the problem anyway); it isn't a 'real' serial port. It's actually an inhouse USB-I2C adapter using an 'ItsyBitsy' that happens to look like a serial port to the PC. However it's not just straightforward USB-I2C; the code provides a wrapper around multiple I2C transactions, and does some maths. It was developed as part of our eval kit for our sensor product, so it was the 'obvious' thing to use.

Seems like there are multiple ways the whole setup could be re-engineered, with varying degrees of time and cost. I'll see how we get on with the current setup for 1000hrs (~6 weeks) before getting too far into other options!

[wiebe@CARYA]

I've used TCP\IP2Serial, mostly because they (also) work great on cRIOs.

As long as the drivers don't use Bytes At Port and such evil, VISA can switch between serial and TCP\IP (converted to serial) by simply changing the resource string.

The configuration is a hassle though, a replacement part needs to be configured correctly. The configuration should be treated as a resource (SCC and documentation), or you'll loose time when you need to replace (or duplicate) the system. 

EDIT: That crossed...

[wiebe@CARYA]

---

@JohnJoyceFlusso wrote:

Seems like there are multiple ways the whole setup could be re-engineered, with varying degrees of time and cost. I'll see how we get on with the current setup for 1000hrs (~6 weeks) before getting too far into other options!

---

Also, don't forget to inform the cleaning crew!

[JohnJoyceFlusso]

I've marked this one as an answer / solution as it seems to have done the job for us. 45 days running so far without an enforced reboot (have I just cursed it?).

It was quite a faff with the security settings / ownership for those fiiles to get to a position where I could do the rename. What security holes that has produced I don't know! And yet on other machines I could do the rename with little effort. Possibly that was related to what sort of login the machine has - local user, or whatever you call a login with an email address that's connected to Office365.