Quote:Well, it cant be that hard. Here's what I'm talking about: I just downloaded Wetspot 2 and put it in a directory. I'm quite sure that its not the same directory it was programmed in. Yet, it can open all its files. How do i do this? Is that ASM code what it takes?
Like Cha0s said in his post right after yours, the Wetspot program just opens its files specifying a filename only (no path) which implies accessing them from the "default directory", which needs to be the directory where you put the package. If you created another directory called \WET2 and copied the Wetspot files into it, then changed directory to \WET2, the package would still run even though it's now in a different directory. Get it? This is standard procedure for most software packages.
You said: "I'm quite sure that its not the same directory it was programmed in." The thing is that the files were not programmed or hardcoded into any particular path, just the filenames, which accesses them from the "default directory".
However, lets say that you put the package into a directory called \WETSPOT. Then you change directory to \MAIN, which is now the default directory. Then you run the program by doing \WETSPOT\WETPROG.EXE. It will run the program, but it won't find its files because they are not in the default directory of \MAIN. To run the package correctly, you must do:
cd \WETSPOT ....... (which establishes the default directory.)
WETPROG.EXE
What else can I tell you.
*****