Common Option Panel contain the parameters that are to be used by LiveImaging Functions, StillImaging Functions, Help Button & Make List File Button.
1. Target is where the system image is to be placed when doing LiveImaging or StillImaging.
Target can be an .dsk image file or a drive letter.
LiveImaging takes the system drive as the source.
StillImaging requires you to specify a source as well.
If you use Image File as the Target, you will be prompted to specify an image file to be used later when doing LiveImaging or StillImaging.
2. Image Size (MB) is the size of the image file you expect to make.
If it is blank, the Image Size will be estimated for you, reminding you that sufficient space should be there for making the image. Using drive letter as the Target is the same.
3. Max File Size is the size in MB of the file to be handled.
The Default size is 20. This means that file of size greater than 20MB will not be copied or imaged. Normally you don't need to change this value except that you want to include files of size larger than 20MB in the image.
4. User Option File is an option file that helps to further customize the processing.
If a User Option File is absolutely needed, you will be prompted to provide it. Otherwise, Little Angel will ignore it or will do a default action for it if it is left blank. This will be explained later when coming to each function button.
5. Add System is a default selection for doing LiveImaging or StillImaging.
This means that by default, Little Angel will add the system files so far used since system boot-up to the image you are going to make. If it is not needed, you can de-select it.
6. Full System is an option that you can select if you want to make the image into a Full System image.
This will include the full system filelist when doing imaging.
For xp system, selecting this option will include fullexp.txt for processing. For 2k3 system, fulle2k3.txt will be used.
These two filelists included in the package are scanned from the full system made under VirtualBox.
You can provide your own filelists and replace them if desirable.
7. Make List File
This button when pressed will help you to make different kinds of filelists.
Make List File examines User Option File to see what action it is going to take.
If User Option File is left blank, it will prompt you to give it a filelist filename and then it will make a default filelist for you.
This default filelist is a list of files that have been accessed since the system boots up.
You can however specify a User Option File, ending in .lst, for it to use.
Currently, the package includes the following .lst files to be used:
for comparing 2 filelists
for comparing a list to a drive specified as source
for scanning a file folder to a list
for scanning the source drive into a list. scan2list.lst is a more generic option, you can use it to scan any drive as well.
for translating an input filelist so that an output filelist is produced containing only files found in the Source, using the Source path.
For example, if in the input filelist, there is a file:
but the file is found in the Source as:
This file entry will be listed in the output filelist file as C:\drivers\123.dad
This button helps you to do some handy tasks.
When pressed, it also examines the User Option File to see what action is to take.
Currently, the package includes the following option files, ending in .cfg, to be used:
This helps clear Little Angel's monitoring buffer. Upon system boot-up, if Little Angel Monitor is activated, Little Angel Monitor will keep a log of files accessed in a memory buffer. This buffer is used for making the default filelist as explained above when you press Make List File with blank User Option File.
This installs the Little Angel Monitor if you want to use it in case it is not setup or uninstalled. It will only take effect upon the next system boot-up.
At any time you want to place a Mark, signalling the beginning or the end of a certain system activity such as opening or ending a certain application, you can use this .cfg file and press the Help button. A Mark with the description you provide will be placed in the Little Angel Monitor buffer.
This pauses the Little Angel Montior for the time being.
This resumes Little Angel Monitoring.
This uninstalls the Little Angel Monitor if you don't want to use it anymore. It will only take effect upon the next system boot-up.
LiveCopy used in Little Angel depends on certain system services which may not be started. It helps to start these services, including:
These services can be started only if the corresponding system files are installed. The vshadow component included in the package helps you to add such files to your system image when you use the Add Component function. This is to be explained later.
This helps you to mount up .dsk image file created by Little Angel so that the .dsk image file appears as a drive to be used. To unmount it, you can use imdisk to do it easily.
This helps you to refresh the drive list as detected by the system inside Little Angel.
This helps you to subst a file folder into a drive for use inside Little Angel.
This helps you to unsubst the drive you make above in i.
This helps to you specify the number of minutes to wait between each cycle of copying when you use the Online LiveCopy function. Online LiveCopy will help you to copy the files you use online time and again into a drive so that you can examine continuously what files have been and being accessed. This will be explained later when discussing LiveImaging.
The above are such helpful tasks that are currently provided by Little Angel when you press the Help button.
Other .cfg files are not used by the Help button.
There are 2 .cfg files included that are not supposed to be used and will be ignored.
These 2 are wdlst.cfg & wdlst_no_cache.cfg
wdlst.cfg is a special .cfg file used by Little Angel for generating the minixp system.
wdlst_no_cache.cfg is just a sample filelist like wdlst.cfg but excluding system cache files. If you want to build a minixp and exclude system cache files inside, you can rename it into wdlst.cfg for use. But normally, even not using this file, system cache files are normally not accessed by you when using the system.
*.cfg files can also be designed by you, but are intended for doing imaging than used by the Help button.
*.cfg files designed by user can contain filenames ending in .cfg or .txt
so *.cfg files are containers for .cfg and .txt files.
.txt is the filelist file that is used by Imaging functions for copying files into images. *.txt file is therefore a text file containing filenames of files to be copied into images.