Posted by Shailesh Humbad on 11/18/84 11:41

Jim Carlock wrote:
> "Shailesh Humbad" <humbads@nowhere.invalid> posted:
>> BTW, Windows does not care about capitalization on the command line.
>
> On DOS and Windows systems...
>
> When working with paths and filenames, such items are case-insensitive.
> DOS used to save all paths and filenames as 100% uppercase. However,
> Windows will save the files in mixed case, even though the "file system"
> treats it as case insensitive (providing only the visual benefits of upper
> and lower case).
>
> Passing switches/parameters on the command-line for different commands
> may or may not be case-sensitive.
>
> Some compilers are case-sensitive. Some tools are case-sensitive.
>
> ntsd.exe command line parameters...
> -g ignores initial breakpoint in debuggee
> -G ignores final breakpoint at process termination
>
> ml.exe assembler...
> /Fr[file] Generate limited browser info
> /FR[file] Generate full browser info
>
> As far as the file system goes, you can type ml.exe any way you like.
>
> As far as the switches go, the application processes the switches, and
> you just don't know unless you know.
>
> Hope this helps.
>
> Jim Carlock
> +"North Carolina Swimming Pools"+http://aquaticcreationcnc.com
> Post replies to the group.
>
>

I meant references to Windows file names and options for Windows
built-in commands (unless you can point out a counter-example).

I summarized the methods here:
http://www.somacon.com/p395.php

[Back to original message]