then

After that you are informed that the registry backup is restored and copied and the .dsk image file is closed.

After pressing OK, you are returned to the Little Angel main screen and you can then click close to exit Little Angel:

4. Run bootimage.exe inside the g4dimdiskerunt.zip package to specify the .dsk image file just made for booting

After pressing select disk image, you will be allowed to browse the .dsk image you want to add to the grub4dos menu for booting. And after selecting the .dsk image by pressing open, then the bootimage.exe will put the appropriate mbr and bootsector code to the selected .dsk image file and add its titles for booting in menu.lst, the grub4dos menu file. bootimage.exe will then exit afterwards.

Then you can reboot and go to the grub4dos menu and select the .dsk image file for booting.

4 titles are added into the grub4dos menu.

2 titles use map --mem command to boot it, one hide the system partition the other not.

2 titles use memdisk raw to boot it, one hide the system partition the other not.

Most machines will work using memdisk raw.

map --mem command titles are put there for your selection if found appropriate.

For some machines where map --mem works, as Little Angel Tutorial 2 -- the Best Scenario describes, you can choose Title 2 or Title 3 to boot the system partition to ram to boot.

memdisk raw however can work only with a .dsk image file and cannot be used to load a hard disk system partition up for booting.

So you are fortunate if your machine works with the native map --mem command that comes with grub4dos.

After booting the .dsk image file, you will be returned to the boot.ini menu, and you have to select booting into Microsoft Windows rather than selecting going into grub4dos menu again.

After booting into Microsoft Windows, if you are using language versions other than English version or Simplified Chinese, you may come across a black screen indicating that a file in the \WINDOWS\system32\ folder ending in .nls is missing. This is the language file required for your language version. Please reboot to start the hard disk system again and use imdisk to mount up your .dsk image file and copy the .nls file into the \WINDOWS\system32\ folder inside the mounted up drive for the .dsk image file.

You may also edit the wdlst.cfg file to include this .nls filename so that when building .dsk image file later using LA, it automatically copies such file into the .dsk image file thus made. For building xp sp3, there may be other files missing upon boot-up, you can jot down those filenames with their paths and copy them into the .dsk image file as well as to edit the wdlst.cfg file to include them likewise.

You may also edit wdlst.cfg to include other files you consider necessary, such as bootfont.bin, to be included into the every .dsk image you build when you select the add system option.

5. Copy the folder of Documents and Settings to the bootable .dsk image file thus made

To be more complete, after booting up the .dsk image file into ram, you can mount up the .dsk image file on the hard disk by imdisk, specifying 32256 as the offset or run up Little Angel to mount it by:

a. specifying mount_dsk_file.cfg in the User Option File field

b. pressing Help button

Then you can browse to select the .dsk image file you want to open.

After mounting the .dsk image file, you can you My Computer to copy the folder Documents and Settings of the hard disk system drive to the .dsk image file, which is made from the hard disk system drive in the process described earlier.

The bootable .dsk image file thus made is more complete. And you can then reboot and use this more complete bootable .dsk image file.

After running it up to ram, you could also run a Still SysBack against your system drive on the hard disk. This time you need not copy the registry backup made by erunt as described before. The Still SysBack .dsk image file made from the system drive on the hard disk this time is the best and bootable as you make it using the ramdisk system. Your system drive on the hard disk is in fact not a live running system image but a still system image. So all the system files in this Still System Image on the hard disk can be copied. And the bootable .dsk image file thus made by running Still SysBack is the best and most complete.

The above steps describe the best approach to making a good bootable .dsk image file for use, the best backup of your system drive.

The backup procedure presented above seldom fails on condition that you have sufficient disk space for saving the .dsk image file and your hard disk surface is good for use and that there is no virus infection that affects your system.

This is the same as that could be created by running Live SysBack of Little Angel or by running Copy Volume of Diskless Angel if vshadow sample code is downloaded for use from Microsoft website.

For some obscure reasons vshadow services do not always work nor are vshadow components files present in the system drive of your system. And you also have to take the trouble to download the sample code from Microsoft website for use. So vshadow services are not a good option that you can always rely on.

6. Fast Incremental Backup of your system image running on the DA virtual memory disk for re-use

Any changes to your system image running on the DA virtual memory disk in ram, if not saved back into the .disk image file on the hard disk, will be lost upon rebooting. If you want to preserve such changes, there is now a quick way for you to do this as follows:

a. run up LA

b. in the User Option File field, select incremental_backup.cfg in the dala folder

c. in the Source Field, select your system drive C: (the DA virtual memory disk in ram)

d. press Still SysBack button

(this assumes that the Microsoft vshadow code does not work for system drive in ram, so you could not use Live SysBack for backing up the DA virtual memory disk in ram.)

e. it then calcuates the size of the image, you just press Yes

f. and then after the size of the image is estimated, you press Still SysBack button again

g. when prompted for the Target, select the .dsk image file on the hard disk you just booted up to run in ram

h. when asked if you want to use the existing file, you answer Yes

i. after a while for backing up the files from the DA virtual memory disk to the .dsk image file on the hard disk, you will be asked if you want to copy the ERUNT backup registry files into the .dsk image file again, you answer Yes

j. close LA after you are told that the copying is finished and the .dsk image file is closed

The changes thus made to your system drive running in ram are now saved into the .dsk image file on the hard disk you use to boot up to run in ram.

So you better make 2 copies of the .dsk image file, one serving for daily use that incorporates all changes you want to backup every day. The other copy serves as the master backup that is good for use in case your daily copy is damaged or you wrongly backup the system drive running in ram that is infected with viruses.

The master backup copy however can be stored in the form of a bootable DVD or USB thumb drive that, when booted up, could boot and load your master backup copy into ram for use. This serves as an ultimate restoration tool or for emergency use when your hard disk is infected with viruses or has hardware failures.