Every process on a Windows system has a working directory
associated with it when the process starts. Simply put, when an
application has to work with pathnames, it assumes that any bare
filenames or partial paths are relative to the working
directory.   The reasons for this setup are pretty easy to
demonstrate. Suppose you're in the Cmd.exe console shell and
you're navigating through your home directory structure looking
at files and folders. To get a listing of the files in that
folder beginning with the letter a, you type   <span
style="color: black; text-decoration: none; text-underline:
none">dir a*</h3>   at the command prompt. Because Cmd.exe
always starts out in the home directory, it sees this as a
partial name and assumes you want to see names starting with the
letter a in the working directory. This assumption saves a lot
of repetitive typing. It also makes it much easier to write
scripts or use applications that deal with special subsets of
files in particular locations.   You can change your work