Subject: Little Angel Tutorial 1Aii - How to further customize your system image [Print This Page] Author:
windrv Time: 21-11-2008 15:54 Subject: Little Angel Tutorial 1Aii - How to further customize your system image
After following steps of auto-building a mini system image as described at:
You would perhaps like to further add other system files to make it more useful.
Initially, the automake.cfg file has just an empty automake.txt file.
To add more files to be included into the system image, you could put the filenames into automake.txt or into other .txt or .cfg files as described at #5 in the thread link above.
The automake.cfg file now contains the following entries:
Then you just click on the Make List File button and you are presented with the following dialogue box to input the name of the filelist file to be saved:
Besides saving the base.txt file, LA also does some processing on this filelist file so that you can use for analysis purpose. This will be described later in this thread.
After the Analysis processing is done, you can see the following screen:
The base.txt now contains all the files so far accessed by the system up to the point you click the Make List File button.
If you want to know what files are accessed when you use Internet Explorer to browse the Internet, you can then fire up IE to browse a website such as:
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
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.