adwinp
15th January 2009, 03:05 AM
Here's a list of options available during provisioning:
LOCK:Enabled lock the device so no user action is possible
CAB: \Extended_ROM\... install a CAB file use
EXEC:\Extended_ROM\... execute a file
CPY1:\Extended_ROM\sourcefile specify source for copy command
CPY2:\windows\targetfile copies CPY1 file to target
XML: \windows\... execute a provisioning XML file
LOCK:Disabled unlocks the device
RST: Reset execute a reset at the end
CFG: \Storage\Config2.txt include configuration from another file e.g. Config2.txt (same syntax as Config.txt)
HIDE:Enabled hides the autorun screen so that user interaction can take place.
HIDE:Disabled shows the autorun screen after user interaction.
SHOW:\Extended_ROM\... shows the image specified as the background to AutoRun. Must be a bmp.
My question is:
Did I miss any option to DELETE a file directly, without extended provisioning?
For example: DEL: \Windows\file_to_delete.ext
In general, we have to call an XML: and add further provisioning, like:
<parm name="RemoveAttributes" value="R" />
and THEN
<characteristic type="%CE2%\file_to_delete.ext" translation="install">
<characteristic type="Delete">
<parm name="ForceDelete"/>
Since not always can we delete the file directly.
LOCK:Enabled lock the device so no user action is possible
CAB: \Extended_ROM\... install a CAB file use
EXEC:\Extended_ROM\... execute a file
CPY1:\Extended_ROM\sourcefile specify source for copy command
CPY2:\windows\targetfile copies CPY1 file to target
XML: \windows\... execute a provisioning XML file
LOCK:Disabled unlocks the device
RST: Reset execute a reset at the end
CFG: \Storage\Config2.txt include configuration from another file e.g. Config2.txt (same syntax as Config.txt)
HIDE:Enabled hides the autorun screen so that user interaction can take place.
HIDE:Disabled shows the autorun screen after user interaction.
SHOW:\Extended_ROM\... shows the image specified as the background to AutoRun. Must be a bmp.
My question is:
Did I miss any option to DELETE a file directly, without extended provisioning?
For example: DEL: \Windows\file_to_delete.ext
In general, we have to call an XML: and add further provisioning, like:
<parm name="RemoveAttributes" value="R" />
and THEN
<characteristic type="%CE2%\file_to_delete.ext" translation="install">
<characteristic type="Delete">
<parm name="ForceDelete"/>
Since not always can we delete the file directly.