Re: XP exec background process
- From: "Jim Carlock" <anonymous@xxxxxxxxx>
- Date: Fri, 03 Mar 2006 04:52:03 GMT
"Shailesh Humbad" <humbads@xxxxxxxxxxxxxxx> 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.
.
- Follow-Ups:
- Re: XP exec background process
- From: Shailesh Humbad
- Re: XP exec background process
- References:
- XP exec background process
- From: Shailesh Humbad
- Re: XP exec background process
- From: Drakazz
- Re: XP exec background process
- From: Shailesh Humbad
- XP exec background process
- Prev by Date: Re: imagejpeg generating string not image even with header("Content-type:image/jpeg")
- Next by Date: Re: Reccomendations for a good file manager script.
- Previous by thread: Re: XP exec background process
- Next by thread: Re: XP exec background process
- Index(es):
Relevant Pages
|
