Pwede din i-consider na system limitation or functional gap...Originally Posted by mantoy
![]()
Pwede din i-consider na system limitation or functional gap...Originally Posted by mantoy
![]()
All operating systems have its own rules. Example, you cannot use "Toyota/Honda" as a directory name whether in Windows or in Linux, because of the "/" character. Also, web browsers do not accept a blank space as part of the URL. It may sound strange and simple, but that's the rule. Every software has usage rules.Originally Posted by fuego4x2
No, it's not! It's hard to explain, but there are certain reserved words in DOS that can't be used as filenames. Con is one of them.Originally Posted by fuego4x2
On the contrary, it's the OS that specifically restricts you from using those names, it's not that it can't tell a file from a device driver.![]()
yes pero parang illogical yung naming restriction nila since device handlers yung isa and directory naman yung isa. teka lang... pag naibalik ko ang dual boot ko dito try ko gawan ng mga directory na ganyan ang names sa root directory ng windows partition ko through linux then ire-reboot ako sa windows.
kung meron dyan nakadual boot na... try nyo naman.
mag-conflict kaya sa devices? hahahahaha!
Let me illustrate why it is a bug:
Open a DOS window and then type "mkdir \\.\C:\CON" without the quotes.
You can replace C:\ with any drive or directory that you like.
Trust me, the MS developers did a poor job! Ergo, it is a BUG.
strictly speaking its not really a bug; its a restriction. pero sa tingin ko bug yan na natuklasan ng MS developers na hindi na nila ginawan ng paraan kaya ginawa na lang nilang official yung restriction.
![]()
THAT is a bug, and is completely different from you not being able to make a file/dir named "con" (which is NOT a bug).Originally Posted by fuego4x2
Being able to make a dir named "CON": Bug.
NOT being able to make a dir named "CON": not a bug.
I believe this filename restriction is just a legacy thing and shouldn't be in Windows NT at all, it's just there to provide backwards compatibility so that old DOS apps wouldn't get confused if you run them.
the rule is....you are not allowed to create a folder named CON:
but with what you did... that makes it a bug. why? you were able to go around the rule and were able to create a folder named CON.Originally Posted by fuego4x2
Parang usapang religion na rin ito ah, tulad nung sa isang thread. Hehe.
I think the point being emphasized in this discussion now is whether Microsoft is stupid company or what.
Malamang mauwi rin itong discussion na ito sa Windows versus Linux na naman.
Halatang mga windows boys kayo ah. If you guys started using PCs back in the DOS era - you'll recall kung pano gumawa ng batch files (such as autoexec.bat) using "copy con <filename.bat>" command.
Obviously, it was a reserved word. Much like forward or backward slash - meron silang "function".
Edit: Mods should change the thread title to "Amazing how people think that DOS commands are Windows bugs!"
Last edited by airshaq20; October 11th, 2005 at 11:10 PM.
Actually, this CON issue is no big deal to me. My concern is the claim that "the whole Microsoft Team, including Bill Gates" doesn't know about it. This is the portion of the story which made this thread "supposed to be" a big deal.Originally Posted by airshaq20
Originally Posted by IPSG_SlimShady
So where did you read about this "claim"? Are you telling us that eversince DOS era, that this "bug" hasn't been discovered?
Might want to read this site so you'll have an idea about basic DOS file naming and what-nots.
http://www.cknow.com/tutorcom/dos04_names.htm
Errr... I read it from the first post in this thread?Originally Posted by airshaq20
![]()
Originally Posted by IPSG_SlimShady
Are you saying you believe everything people post on forums? Is that your basis for facts?