3 things which Microsoft can never Explain
11/26/2010 11:18:00 PM
Explanations:
Magic 1.
An Indian found that nobody can create a FOLDER anywhere on the Computer which can be named as "CON". This is something funny and inexplicable… At Microsoft the whole Team, couldn't answer why this happened!
TRY IT NOW, IT WILL NOT CREATE A "CON" FOLDER.
Not only Con you cannot create a folder with following names also... NUL,COM1,COM2.... to COM9 and LPT1 ,LPT2....to LPT9
The Reason is CON is the device for CONsole.
COM1 is Communication Port 1 and similarly
LPT1 stands for first Serial Port available
In Windows all devices are stored as files (like Linux). In linux we can see the file location,may be because its Opensource. But in Windows we can't locate these device files.
So its a system device file (or /and) folder. So we can't use the same name again. Windows already have a policy for hiding these locked folders/files from user .this is because on booting all these devices needs to be checked and verified.
There are Several workarounds available......
One which i tried and succeeded is.
C:\Users\>d:
D:\>md\\.\\c:\\con.
Magic2.
For those of you using Windows, do the following:
1.) Open an empty notepad file
2.) Type "Bush hid the facts" (without the quotes)
3.) Save it as whatever you want.
4.) Close it, and re-open it.
Noticed the weird bug? No one can explain!
'Bush hid the facts' is the common name for a bug present in the function IsTextUnicode of Windows NT 3.5 and its successors, including Windows XP. This causes a file of text encoded in Windows-1252 or similar encoding to be interpreted by applications that use it (such as Notepad) as if it were UTF-16LE, resulting in mojibake.
A Mojibake is often caused when a character encoding is not correctly tagged in a document, or when a document is moved to a system with a different default encoding. Such incorrect display occurs when writing systems or character encodings are mistagged or "foreign" to the user's computer system: if a computer does not have the software required to process a foreign language's characters, it will attempt to process them in its default language encoding, usually resulting in gibberish.
The bug appeared for the first time in Windows NT 3.5 but was not discovered until early 2004.
Solution:
Because of this bug in IsTextUnicode, Notepad misinterprets the encoding of the file when it is reopened. If the file is originally saved as "UTF-8" rather than "ANSI" the text displays correctly - this is because Notepad prepends the UTF-8 byte order mark, which is a different pattern that does not trigger this bug. The bug is also avoided by saving as "Unicode", which really saves as UTF-16.
Older versions of Notepad such as those that came with Windows 95, 98, ME, and NT 3.1 do not include Unicode support so the bug does not occur.
Magic3.
Try it out yourself…
Open Microsoft Word and type
=rand (200, 99)
And then press ENTER
And see the magic…..!
Rand(a,b) is basically a VB function where a is the seed and b is the limit. Digging about its funny behaviour in MS word I found that it produce ‘The quick brown fox jumps over the lazy dog’ in msword 2003 and below.in word 2007 it produces some random paragraphs. One of the theories is this helped Microsoft testers in testing the font in initial versions of MS word (so it was intentional)..and was left as junk code in after versions. Note that ‘The quick brown fox jumps over the lazy dog’ contains all the letters in alphabet.
0 comments