Quote:
Originally Posted by DragonRider
If you were a 100% about what you are saying you would know that the problem this user posted about is caused by cold booting but with the wake by lan still turned on  |
Just had to quote that so people could actually believe how little sense your post made.
First, the user did not say whether he was cold booting or warm booting. Therefore it is impossible to make the statement "the problem this user posted about is caused by cold booting." And what "but with the wake by lan still turned on" must be some bizarre output by Google Translate. There is no way short of a clandestine spyware you installed in his system that you could know what his wake on lan status is. (LAN means local area network) This kind of problem happens all the time in computers that are not connected to a LAN and which have wake on LAN disabled in what used to be called a BIOS.
And again, making fun of my distinction between cold booting and warm booting reveals a troubling lack of knowledege from someone claiming authoritative knowledge.
Cold boot vs warm boot from the Microsoft website. This is a bit dated but contains the important information that with a warm boot not all settings are reinitialized. If your error is there, a warm boot will not fix the problem. This article is not the source of my knowledge in this matter, nor does it contain the entirety of my knowledge in the matter, but it does provide a basis for further research by those interested in understanding on their own.