what happens depends on what the people making the setup script/program programmed it to do.
That's all anyone can say, as it could do anything.
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337
People write specific dlls that are specific to their applications and there dlls are required to be registered with Windows registry so that the calling application knows where the library can be found. Suppose you are using Oracle as a db server then your application requires oci.dll file to connect to the oracle db and you simply use the windows data sources utility to locate the dll and create a data source. This dll here acts as an interface between your application and the oracle db server. It knows how to connect to the oracle and you just pass some parameters to it. Similarly, you can write your own dll. COM programming can give you a better understanding. Suppose in COM you are writing a server and a client. Then on the client side, the server specific parameters needs to be registered with the windows registry. Remember you will again be writing an interface that will be registered with the client and knows how to connect to the server.
lookof2day
Junior Poster in Training
83 posts since Aug 2007
Reputation Points: 16
Solved Threads: 11