^ Never outline precisely how you lost your precious Star-Chan in a public forum.

Just a note, this is inadmissible evidence in some places if you don't inform the other party/parties they are being recorded. :)

---

New one:

Never drink more than 10 shots of southern comfort(or any hard liquor really) in under an hour or two...especially while standing up.

(Did that when a young adult of around 22 and regretted it when I hurled all over my nice clean clothes and half the floor)

Just Skip
This is just an explanation or some additional info on the naming of "con", a short for Console, to file in Windows.

Any file (jpg, pdf, docx, txt, etc.) when you actually name it as "con" the operating system
would not allow it. A notice through a pop-up would say, "the specified device name is invalid".

Why? --> Because its a reserved file name
And yes it has something to do with the ms-dos and the msx-dos of microsoft back then as "con" is actually a device
file name for a code that has something to do on how your programs access or communicate to a connected hardware
with your computer (e.g. printer, keyboard).

Why does something like ms-dos or msx-dos feature years ago have something to do with the now latest windows 10?
- Well, it is simply because of how the now latest windows 10 has some parts that are simply built on upon the
old ones. Think of it as the old Disk Operating System, being upgraded or built upon over the years until the
it finally reached OS you have now with all the GUI and stuffs.

For more additional info:
This video explains the thing in an informative way.
https://www.youtube.com/watch?v=bC6tngl0PTI&t=358s

From what I remember:
* On sufficiently recent versions of Windows Explorer, you get a helpful message that mentions that "con" and a bunch of other names are reserved.
* On older versions (I think as late as at least Vista), you get some rather unhelpful error. This also happens if you somehow have a file with that name (perhaps you used cygwin to create it?) and try to do anything with it.

(Windows can handle those file names, but the API used by most (but not all) user-land programs will treat them as reserved.)

^ Never get so off topic that you forget to post in keeping with its subject matter. (posting the word "never" one time followed by something not to do would have been sufficient.

>.<

Never mention the two cities Sodom and Gomorrah in a game forum, it will crack some heads...

Never expect dtgreene to follow the rules / wishes of the thread creator.

Seriously:

When you are drilling in a wall, NEVER expect that concealed cables are laid in 90 degree angles.

Popular:

NEVER be responsible, you can always find someone who made you do what you have done!

so you mean that you should always try to drill with care if your drilling a hole in a 30 cm wide area with the socket as center and the height taken from the socket to the top of the wall?

This.

Never, when doing electrical work in someone else's house, forget to label circuits, wires, etc, and when you do, never label them merely with abbreviations!
(the wire labeled SWFL goes, straightforwardly enough, to the SouthWestFloodLight, but nowhere was this labeled.

Never feed a cat a pill without two layers of gloves.

Never allow your girlfriend to take her cat with her in a purse to a loud dance club.

Never expect solutions for problems from the people who created them.

NEVER sit in front of your monitor, cat on your lap, browsing cat pictures and/or videos on the Internet! It may cost you a monitor or two if you aren't quick enough to hold your cat back!

Never, assume that anyone would allow their cat inside their home.