 |
 |
 |
 |
Some things I agree with
(or not as the case may be)
|
Friday, April 11 Windows error codes, know thy master Those fscking Windows error codes really annoy me sometimes - how am I supposed to remember what 0x00002740 stands for? (It's "Only one usage of each socket address (protocol/network address/port) is normally permitted. WSAEADDRINUSE" aka errorcode 10048, incidentally). If, like me, you don't have a photographic memory (or months to memorise what each code stands for), there's a couple of useful links you should have bookmarked: //infosys.beckhoff.com/index.php?content=content/1031/tcdiagnostics/html/tcdiagnostics_win32_errorcodes.htm //everything2.com/index.pl?node_id=1141825 Armed with those two error code reference points, you should be able to diagnose just about any weird error you come across, from BSODs to arcane or esoteric errors at a DOS prompt. Labels: error codes, kerblam, reference, tech support, windows Dragged out of Christopher's memory and pasted into his blog at 4/11/2008 08:51:00 PM. Roughly. Blog ID: 4138096422993217554· | Permalink |
Mobile/low-bandwidth version |
|
  |
|
