01-30-2017, 12:01 PM
You're full of shit Zi. Here's why:
System32 is a legacy folder in the windows operating system. By this I mean it's been around from the very early days, with only additions; minimal changes (in terms of function). It contains a great deal of core files which enable windows to run, at the very heart. Not long after users discovered this, it quickly became a joke or an excuse, that one had deleted System32. It swiftly progressed from a joke to a prank, in that people promised it was some deep secret hidden by microsoft, or some such entity and deleting it would achieve some positive effect. This was not the case. This prank too wind at least 5 years ago, if not more. With only a select few falling victim to it. With distraught users and technicians alike, Microsoft quickly patched this (at what O/S I don't remember) and later worked a sure fire fix, to stop pranksters in their tracks, into the next O/S. Nowdays, anyone using windows 7/8/10 is prevented from deleting System32 (at first) by windows' advanced permission system. So basically, if you were dumb enough to get tricked into navigating there, and on the road to deleting it, you shouldn't be smart enough to give yourself access to it.
Now although this system is advanced, ultimately you are the user and you decide what you want to keep and what you want to delete. So naturally, there is a work around, but this ensures you actually know what you're doing and do it intentionally. Windows just sets certain permissions of certain directories because it thinks you shouldn't need permission to them unless you want to go ahead and give it to yourself. Now I spent a whole unit in my Cert IV looking at Windows Permissions and Group Policy Editor, I feel like it was a waste, but at least I know for sure it's a lot of fucking around to do something like this, for the first time at least.
Now the lastly, I have reports from several trustworthy witnesses that when you left teamspeak, you "Disconnected" but if you were to have done as you said, you should have "Timed Out". The reason being is any unexpected shutdown doesn't have time to individually closed windows and end processes. They are abruptly ended in that no information is being processed for them anymore, no resources used. So the way Teamspeak works is straight away the program will cease to function, but because it's a network service, it has to deal with timeouts. So in the even that packets stop being transferred by your client (abruptly) they'll continue the connection for a short while (no more than 30sec) to see if you regain connection. If you don't, you time out, if you do you hear people talking again, and all is well. So when an abrupt stop occurs, you will time out. An abrupt stop can be from an O/S crash (Blue screen), a hardware fault, a force shutdown, and sometimes sleep or hibernation (typically from laptops). A correct shudown in windows will send a kill request to teamspeak's profile and it's coded to disconnect you first. This is why when you shut down (properly and usually) with Teamspeak open, it will say disconnected still.
No matter on what scale. I do not appreciate being lied to.
Sell the lie a bit better next time.
System32 is a legacy folder in the windows operating system. By this I mean it's been around from the very early days, with only additions; minimal changes (in terms of function). It contains a great deal of core files which enable windows to run, at the very heart. Not long after users discovered this, it quickly became a joke or an excuse, that one had deleted System32. It swiftly progressed from a joke to a prank, in that people promised it was some deep secret hidden by microsoft, or some such entity and deleting it would achieve some positive effect. This was not the case. This prank too wind at least 5 years ago, if not more. With only a select few falling victim to it. With distraught users and technicians alike, Microsoft quickly patched this (at what O/S I don't remember) and later worked a sure fire fix, to stop pranksters in their tracks, into the next O/S. Nowdays, anyone using windows 7/8/10 is prevented from deleting System32 (at first) by windows' advanced permission system. So basically, if you were dumb enough to get tricked into navigating there, and on the road to deleting it, you shouldn't be smart enough to give yourself access to it.
Now although this system is advanced, ultimately you are the user and you decide what you want to keep and what you want to delete. So naturally, there is a work around, but this ensures you actually know what you're doing and do it intentionally. Windows just sets certain permissions of certain directories because it thinks you shouldn't need permission to them unless you want to go ahead and give it to yourself. Now I spent a whole unit in my Cert IV looking at Windows Permissions and Group Policy Editor, I feel like it was a waste, but at least I know for sure it's a lot of fucking around to do something like this, for the first time at least.
Now the lastly, I have reports from several trustworthy witnesses that when you left teamspeak, you "Disconnected" but if you were to have done as you said, you should have "Timed Out". The reason being is any unexpected shutdown doesn't have time to individually closed windows and end processes. They are abruptly ended in that no information is being processed for them anymore, no resources used. So the way Teamspeak works is straight away the program will cease to function, but because it's a network service, it has to deal with timeouts. So in the even that packets stop being transferred by your client (abruptly) they'll continue the connection for a short while (no more than 30sec) to see if you regain connection. If you don't, you time out, if you do you hear people talking again, and all is well. So when an abrupt stop occurs, you will time out. An abrupt stop can be from an O/S crash (Blue screen), a hardware fault, a force shutdown, and sometimes sleep or hibernation (typically from laptops). A correct shudown in windows will send a kill request to teamspeak's profile and it's coded to disconnect you first. This is why when you shut down (properly and usually) with Teamspeak open, it will say disconnected still.
No matter on what scale. I do not appreciate being lied to.
Sell the lie a bit better next time.
-
x1
-
-
x1
- AlphaNegro
-