I managed a bunch of desktops (2,000+) where we wanted to place applications in specific locations as you want to do including multiple monitors. I used AutoIt for a lot of this. Also used Windows Scripting Host but found AutoIt easier to use when you needed/wanted a windowed interface. Last used it on Windows XP but the app will also run on Windows 7 and Windows 8 (desktop mode only).
@zeeglen: ...am curious as to what percentage of computer users power down every night vs those who unplug only when thunderstorms are in the forecast?
I used to both power down and unplug everything in my office every evening, but it got to br a pain crawling around under the desk, and then I purchased a monster uninterruptable power supply that is supposed to offer protection against lightning.
So now I just power everything down each evening. Apart from anything else, I have a vauge hope that this clears anything out of the memory that didn't get cleared up as it should.
Not to hijack this discussion, but as a side note am curious as to what percentage of computer users power down every night vs those who unplug only when thunderstorms are in the forecast?
Maybe because I come from a vacuum tube era where power-cycle thermal stresses were huge I usually do not turn my PC off, so as to avoid thermal stress on ball-grid-array devices with no mechanical flex to them. My PC before this current one had to have the CPU heated with a hair dryer before it would finally boot; this expanded the broken solder balls(s) to make contact to the PCB. Once started, it remained hot enough to keep the cracked balls in contact.
Have seen several BGA problems related to thermally affected cracked solder ball joints.
Any reader opinions/experiences on reliability affected by 'leave it on' vs 'turn it off'?
@Max I used to be able to lock the desktop in Windows 3.11 by putting one line in the WIN.INI file. Now everything is in the registry and even if you know exactly what to put in and where (and few people seem to) it's still a pain to change things.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.