Re: Computer turns on and then just dies

s|b <[email protected]> wrote:

> VanguardLH wrote:
> 
>> With a temp monitor with threshold alerts and a history log, I'd set the
>> alert to 60C.  Then, if alerted, check the log to see how often you came
>> close or exceeded that temperature.  60C still has wiggle room.
> 
> In the BIOS? I just installed RealVNC and threw the monitor in another
> room. \-:

No, a temp monitor program that loads on Windows startup, or on Windows
account login (i.e., a startup program).  For VNC to work, you need a
VNC server running on the remote host, and that loads on Windows startup
and Windows account login.  Then you could use a VNC client on the local
host to look at a temp monitor program that also loads on Windows login
on the remote host to use a VNC client on the local host to check the
temp on the remote host.

I doubt you'll be able to see the BIOS settings with VNC.  That requires
a VNC server and temp monitor be running on the remote host that you
monitor, and those need to load on Windows startup on the remote host.
After the POST screen, and you hit a key to go into BIOS, that is before
any OS loads.  You could use VNC client on the local host with a temp
monitor program that loads on the remote host on startup, probably on
login, since VNC client won't work until its VNC server on the remote
host gets loaded which is a startup program, too.

Remote host:
 - Booted into Windows.
 - Logged into a Windows account.
 - VNC server loads on startup (when logging in).
 - Temp monitor loads on startup (when logging in).
 
Local host:
 - Boot into Windows.
 - Log into a Windows account.
 - Use VNC client to look at remote host.
 
Although both local and remote hosts are probably inside your network, I
would configure the VNC server to require password access, or restrict
the IP address of the host connecting to the VNC server.

RealVNC viewer (client) is free.  RealVNC server is not.

https://help.realvnc.com/hc/en-us/articles/360002249677-Licensing-RealVNC-Connect
https://www.realvnc.com/en/connect/pricing/

There is a RealVNC Lite that, I think, is free, but I don't recall if it
includes the server which is needed on the remote host you monitor.  The
above pricing page doesn't show the Lite version in the comparison.

https://www.realvnc.com/en/connect/plan/lite/

I found folks mention the free plan got discontinued, like:

https://www.reddit.com/r/selfhosted/comments/1csq8bm/realvnc_is_sunsetting_their_free_plan_what/

Yet the above RealVNC page still exists for the download.  There are
wholly free alternatives; e.g., TightVNC, TigerVNC (but its server is
unmaintained as of 1.11.0), UltraVNC.  Of course, VNC itself, but with
less glitz.

If your local and remote hosts are not in-network (i.e., you go across
the Internet), TeamViewer (free) is probably a better choice.  Instead
of having someone at the remote host to allow the connect, you can run a
TeamViewer server on the remote host.  With VNC, and with an external
connect coming to the remote host, you would need to punch a hole in
your router's firewall by defining a port forwarding rule.  You'd need
to know the WAN-side IP address of your router/modem to know where to
connect with your local host; however, you can use DDNS (Dynamic DNS)
service to give your remote host an FQDN, so you could use an easily
remembered hostname to the remote host instead of remembering an IP
address (which, if dynamically assigned instead of static, means it
could change).  DDNS has you run a DDNS client on the remote host which
reports the IP address to your DDNS account (which operates the DNS with
a record pointing to your remote host).  I don't think you need to do
any firewall port rules, or bother with DDNS, when using TeamViewer. 

If your local and remote host are both in-network in your home, I don't
much see the point of wasting time setting up VNC server and client.
Just walk over to the other host.