Editing 1579: Tech Loops

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 44: Line 44:
 
*Hardware workaround: Sometimes a problem can be solved by hardware changes. Removing TV tuner or telephone modem cards, changing an USB device from one port to another, opening and closing the CD tray, etc. are operations that, in many cases, have led to solving a problem; most of the time with no one knowing exactly why such an operation should or could have any effect in the computer's behavior.
 
*Hardware workaround: Sometimes a problem can be solved by hardware changes. Removing TV tuner or telephone modem cards, changing an USB device from one port to another, opening and closing the CD tray, etc. are operations that, in many cases, have led to solving a problem; most of the time with no one knowing exactly why such an operation should or could have any effect in the computer's behavior.
 
**Has one entry from the most active library (most arrows) and two exits to VM and Awful hack from 2009
 
**Has one entry from the most active library (most arrows) and two exits to VM and Awful hack from 2009
βˆ’
*Awful {{w|Kludge|hack}} from 2009: An example of an awful hack can be found in [[1479: Troubleshooting]]. When an awful hack is necessary, it is often because less awful alternatives do not exist; so awful hacks tend to remain useful for many years. An example can be the 256-character limit in the Windows path for a file, which has been inherited from MS-DOS (way, way before 2009) and is still there up to Windows 10.{{Actual citation needed}}
+
*Awful {{w|Kludge|hack}} from 2009: An example of an awful hack can be found in [[1479: Troubleshooting]]. When an awful hack is necessary, it is often because less awful alternatives do not exist; so awful hacks tend to remain useful for many years. An example can be the 256-character limit in the Windows path for a file, which has been inherited from MS-DOS (way, way before 2009) and is still there up to Windows 10{{Citation needed}}.
 
**This is the most busy box with three entries and three exits. It has an entry from the only box that does not it self have any entries, the bottom right library. Another entry is from the Hardware workaround. It also form a simple entry exit loop with IRC for some reason, that box is not connected to any other boxes. And finally it exits to two libraries. One of these leads to the most active library (most arrows). From this hack all connected boxes can be reached, except the library that only has entry into the hack.
 
**This is the most busy box with three entries and three exits. It has an entry from the only box that does not it self have any entries, the bottom right library. Another entry is from the Hardware workaround. It also form a simple entry exit loop with IRC for some reason, that box is not connected to any other boxes. And finally it exits to two libraries. One of these leads to the most active library (most arrows). From this hack all connected boxes can be reached, except the library that only has entry into the hack.
 
*{{w|Dynamic-link library|DLL}} needed by something: Although "DLL" is a term used by Microsoft Windows, all modern operating systems use dynamic libraries, each with its own name. A dynamic library is a part of a program which is not loaded when the program starts, but rather it's attached "dynamically" to the running process when it is needed. This has the advantage that the dynamic library is not loaded at all if it's not needed, and also several processes which need the same dynamic library can share the same copy in memory.
 
*{{w|Dynamic-link library|DLL}} needed by something: Although "DLL" is a term used by Microsoft Windows, all modern operating systems use dynamic libraries, each with its own name. A dynamic library is a part of a program which is not loaded when the program starts, but rather it's attached "dynamically" to the running process when it is needed. This has the advantage that the dynamic library is not loaded at all if it's not needed, and also several processes which need the same dynamic library can share the same copy in memory.

Please note that all contributions to explain xkcd may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see explain xkcd:Copyrights for details). Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel | Editing help (opens in new window)