How to avoid potential problems

How to avoid potential problems

EVALUATION USERS OF INF-Tool Lite, PLEASE NOTE:
If your Evaluation version of INF-Tool does not work as expected or behaves "mysterious", this might have to do with a virus infection. Please also note that just the licensed (registered) version contains all the routines you need to enable the full features of the program, there is absolutely no way to "activate" them in the Evaluation version.

Potential traps when using INF-based installations

·	It's not possible to run standard INF setups from "Long File Name" directories. This limitation is not caused by INF-Tool, but by Microsoft's implementation of the INF functionality. To prevent the potential occurence of this problem at your customer's computers, please suggest them to install only from "standard" directories like "C:\test" or add the line "AdvancedINF=2.0" to the [Version] section of the INF script (Advpack.dll is required to use this line). The registered version of INF-Tool will add this line automatically for you. This is NO problem if you are using the self-extracting EXE distribution method!
·	Problems can arise when you want to install to locked directories. E.g, it could even be a problem to install to the Windows directory of Windows NT if your customer's (or your) rights are restricted in a way. Please verify this carefully before you distribute your installation packages (or mail me that your scripts don't work ;-).

How to avoid potential problems:

·	Since WindowsNT handles .INF setup files a bit different from Windows95/98, there could occur problems under special circumstances, if you run scripts created with INF-Tool Lite under Windows NT. Anyway, INF-Tool Professional creates the files in a way to work under both versions properly.

·	prevent creation of your distribution directory in System areas as the Windows desktop etc., use INF-Tool's preconfigured settings instead (which should point to a subdirectory of INF-Tool's own setup directory for each single project you created - like C:\inf-tool\project1.dst, C:\inf-tool\project2.dst etc.)

·	Please note that hard-coded destination directories with long names (like "C:\Program files") can just be created with INF-Tool Professional (the registered version of the program) since a certain add-on library which is just part of this version is required for that.

Registered users can find an really HUGE list of Tips & Tricks for INF-Tool as well as fixes and workarounds for common problems in the Tips & Tricks Helpfile - to get the topmost out of INF-Tool!

Table of contents | INF-Tool Home page