OK - let's look this over...

You see that KGen adds this line to the beginning of your script:
 Code:
;; KixGenerated: 2013/12/09 16:08:52 / Kix32 Version 4.62
This is just a reference of when the code was generated and which version of Kixtart was used. This becomes important if you tokenize your code.. KGen leaves a .GEN file in your folder that is not tokenized, so you never have to worry about losing your script source code.

The next section is the output from KGen. There are never "errors" from KGen, just "Warnings". Due to Kixtart's free-form layout, it's difficult to detect strings and commands that spread across multiple lines.

The KGen output reports finding 229 UDFs in your library and local folder in 139 separate files. (some files are libraries and contain many functions!) It also says that none are needed for the generation of your script. (you manually included the required functions.)

After KGen assembles your script, it makes 5 passes through your code using the Sanity UDF. This identifies and warns about several common issues:
Pass 1 locates and indexes all of the variables
Pass 2 reports on variables that were not declared, or declared but not used
Pass 3 indexes the paired objects
Pass 4 reports on mismatched paired objects
Pass 5 generates the reports

The warning shows that on line 81, you used a variable ($) that was not Dim'd or otherwise declared, and reminds you that it will be treated as a GLOBAL var. Review line 81
 Code:
$ = SetOption('Explicit', 'On')
and decide to either use a different, previously declared variable or define the variable that was used. The function is "Main" - your main code, but would show a function name if the warning occurred inside a function.

Sometimes, it will not be possible to eliminate all warnings. I usually investigate and confirm that it is not an issue. One of the most common is "Variable inside string", which is not recommended, but often occurs in an Execute statement. The coding workaround to avoid KGen errors usually isn't worth the effort for Execute statements. \:\)

In this case, the issue is minor and will not affect the script, but adding a
 Code:
Dim $         ; temp var
to your variable declaration section will eliminate that warning message completely. It's really up to you to

If you take the Memory and WMIQuery UDFs out of your inventory.txt file, KGen should put them back into the completed script. This makes your source file smaller and appear less complex. KGen should then report using 2 UDFs from the library.

Good work getting this organized!

Glenn
_________________________
Actually I am a Rocket Scientist! \:D