Backup Directory File Management; 4.10 Firmware Update - Datalogic Memor User Manual

USE AND FUNCTIONING
4
4.9

BACKUP DIRECTORY FILE MANAGEMENT

All of the Windows CE 5.0 system files reside in RAM (volatile memory) except
for the Backup directory, which resides in FLASH (non-volatile memory).
Therefore the contents of the Backup directory are persistent even if the mobile
computer is re-booted or the battery pack is changed.
You can save your more important files that you don't want to lose due to mobile
computer re-boot, in the Backup directory or create a sub-directory within
Backup.
Even though the Windows Directory resides in RAM, it often contains files or
sub-directories created by the user or by installation programs that you don't
want to lose at re-boot. To keep these files persistent it is necessary to copy
them to the directory \Backup\Windows. This directory doesn't exist originally
(only Backup exists), and therefore it must be created. At the next cold boot,
before activating the shell, Windows CE 5.0 will copy the contents including all
sub-directories of \Backup\Windows to \Windows.
Likewise, to maintain files that must be run at Windows CE 5.0 startup, (i.e.
.exe, .lnk, .vb, .htm, etc.), it is necessary to copy them to the directory
\Backup\Startup. This directory does not exist originally (only Backup exists),
and therefore it must be created. The application programs will be run after any
type of re-boot (both software and cold boot).
As an alternative to the Safe Setup function, it is possible to copy the .cab files
to the directory \Backup\Cabfiles (the Cabfiles sub-directory doesn't exists
originally and must therefore be created) and perform a mobile computer cold
boot to have the application installed. Once these files are copied to the
directory \Backup\Cabfiles, the application will be run after each re-boot.
From the second cold boot on, a message may be displayed such as
"<application name> is already installed. Re-install?". This message blocks the
boot process. Press the [Enter] key to continue the system initialization.
Even if the entire Windows Mobile file system reside in FLASH (non-volatile
memory), the mechanism described above is supported also on Windows
Mobile for backward compatibility.

4.10 FIRMWARE UPDATE

The Memor is equipped with a tool that implements a firmware update service.
For further information, refer to DFU Reference Guide.
75