OK, I just reread the title of this thread and think I may understand your confusion. You say "Using a list.txt" and Jens' code uses an INI file... two separate and very different methodologies.
I strongly advise that you NOT use a TXT file as it is extremely limited, hard to parse, and very difficult to revise. INI files on the other hand, are structured, require a lot less coding, do not need to be parsed line-by-line, and are very easy to revise. All you need to work with INI files are ReadProfileString() and WriteProfileString(). The manual explains their use. INI files do have limitations on file size so it would be helpful to know how many computers and what data will be stored in keys. There is also a possibility of contention with concurrent writes so that should be factored as well. The contention issue is less than with TXT files however.
You can setup INI files in a multitude of ways. You should give careful consideration for future uses of the INI file to prevent needless duplication. If you disect Jens' INI file you will see that the computer names are the section names and that there are specific keys under each section.
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
