You now want to compare the two filelist files just made:

base.txt

and

base_ie.txt

base_ie.txt should have the filenames of the files accessed by IE into to base.txt after the system is settled down.

To make the comparison, you press the selection button to the right of the User Option File on the LA screen and select the file:

complist2list.lst

as follows:

Then you press the Make List File button again:

It asks for the first file for comparison, so you click OK and then select:

base.txt

After clicking the Open button, you are asked to select the second file for comparison:

After clicking OK, you select:

base_ie.txt

as follows:

After clicking Open, you wait for sometime and the following screen comes out telling you comparison is finished:

Then you use My Computer to browse to your LA program folder as follows:

After you click the Date Modified Header, you can sort the filenames appearing in My Computer according to Date Modified.

If you do not see the screen as listed above, you can press the Date Modified Header again.

Clicking the Date Modified Header will list the filenames either in date ascending or discending order.

So you can see from the above screen that you have the following groups of filenames below the base.txt and base_ie.txt as below:

Group 1:

list1.txt
list2.txt
listlistin1.txt
listlistin2.txt
listlistbothin12.txt
listlistmerge12.txt

Group 2:

list3.txt
list4.txt
listlistin3.txt
listlistin4.txt
listlistbothin34.txt
listlistmerge34.txt

Group 3:

list5.txt
list6.txt
listlistin5.txt
listlistin6.txt
listlistbothin56.txt
listlistmerge56.txt

Group 4:

list5short.txt
list6short.txt
listlistin5short.txt
listlistin6short.txt
listlistbothin56short.txt
listlistmerge56short.txt

First of all, when making the filelist comparison, it copies the first file selected, base.txt as list1.txt, and the second file selected, base_ie.txt as list2.txt.

It then makes analysis for you and creates other files as follows:

listlistin1.txt -- the filenames only found in list1.txt

listlistin2.txt -- the filenames only found in list2.txt

listlistbothin12.txt -- the filenames found both in list1.txt and list2.txt

listlistmerge12.txt -- the filenames merged from list1.txt and list2.txt

1 & 2 become 3 & 4 in Group 2.

3 & 4 become 5 & 6 in Group 3.

5 & 6 in Group 3 become 5short & 6short in Group 4.

The filenames in list1.txt and list2.txt are translated to taking a driver letter of the system drive to become list3.txt and list4.txt.

So if the system drive is c:; all files having drive letters besides c: are turned to start with c:

Filenames in list3.txt and list3.txt are translated and put inside list5.txt and list6.txt.

Only filenames having the folder location name of:

system32 folder
windows folder
program files folder

are translated; others are left as they are.

For example:

C:\WINDOWS\system32   --> %sysdir%
C:\WINDOWS                 --> %windir%
C:\Program Files              --> %programfiles%

This translation into relative path is for making it convenient to be used in system that may have system drive letter other than C: and the system file folders other than the standard folders.

List5short.txt and List6short.txt are shortlists for List5.txt and List6.txt.

Filenames inside List5.txt and List6.txt but not from the folders of:

%sysdir%
%windir%
%programfiles%

are excluded in List5short.txt and List6short.txt.

So you could easily examine what system files are accessed by an application that you used.

Take our Internet Explorer example again, you could look inside:

listlistin6short.txt

to see a shortlist of the system files resolved into relative paths that are accessed since you use Internet Explorer to browse the Internet and download files.

This is also how roughly the .txt and .cfg files inside the automake.cfg are derived.

You could of course add or delete the entries inside listlistin6short.txt for making better the component filelist for Internet Explorer when you have more technical information from other sources.

You could put filenames of such component filelist files inside automake.cfg so that LA would use them for making all auto-build system images, including:

Full System
Optimal System
and
Mini System

If you want to use such component filelist files only for making, for example, Mini System, then you could put the filenames of such component filelist files into:

miniexp.cfg

Full System and Optimal System will not use the above .cfg file for making the system image.

So the above is a simple and short but useful sequence of steps for you to make component filelist files to be used by LA for making system images for you.