|
| (Documentation for the Actions menu) |
|
|
|
|
| DFSee main page | File | Edit | Actions | Display | Help |
| Mode=FDISK | AUX | EXT2+3 | FAT | HFS+ | HPFS | JFS | NTFS | REISER | XFS | SWAP |
Scan for bad-sectors using Read-Only (fast); Shows the disk-speed as well
This will try to read every sector of the current opened object,
and report on any read-errors encountered along the way.
The object may be a disk, partition, volume or even an image.
All unreadable sectors will be added to the sector-list for later
reference and can be exported to a file from there as well.
After ending the SCAN at the end of the object, or when <Esc> is
used to terminate it, the speed of reading is calculated and
displayed too. This is a good indication for read-performce.
Scan for bad-sectors using Read-Invert-Write-Read-Write algorithm (slow)
This is similar to the readonly SCAN, but it will write to the
object as well as read. To make sure no data is lost or damaged
doing that, it is actually a read-invert-write-read-invert-write'
cycle with a verify of the data after the second read.
This makes it a very reliable and safe method of finding bad sectors
but it also makes it VERY SLOW! (up to 20 times slower than a RO-SCAN)
All unreadable sectors will be added to the sector-list for later
reference and can be exported to a file from there as well.
After ending the SCAN the speed of scanning is calculated and
displayed too. This is an indication for read/write-performce, but
since there are TWO reads and writes in every cycle the number must
at least be doubled.
Combined read/write is much slower than just reading or just writing
because it messes up the disk-caching.
Create DFSCHECK analysis files, checking for most filesystem related issues
This will perform a check on all supported partitions by running
the corresponding DOxxxx.DFS script on it, and creating extensive
information about the specified partition(s) in a logfile.
This is often referred to as the 'DFSCHECK procedure'
The action will result in one file for every partition:
DFSCxxxx.Pnn verbose analysis information and logfile
where the 'xxxx' is the filesystem-name like 'FAT' and
'nn' is the DFSee partition-ID for the partition
The most important data-structures for the partition will be shown,
with the bootsector as a bare minimum.
Most filesystem specific scripts will display:
- some superblock or meta-information
- location and some contents of the ROOT directory
- a display of allocation information (ALLOC)
- an allocation-integrity report (CHECK)
- a layout for the start of the partition (SLT)
You can choose to run it on a single, or on ALL partitions.
Selection of this item leads to a dynamic created submenu, to select a partition to be used , including 'ALL partitions'
Create DFSDISK analysis and backup files, checking for partitioning issues
This will make backups of all important partitioning information,
including deleted/damaged ones, and create extensive information
about the specified disk(s) and partitions in a logfile.
This is often referred to as the 'DFSDISK procedure'
From the menu you can select a specific disk, or all of them.
The action will result in SIX files for every physical disk:
DFSDISK?.SKx verbose analysis information and logfile
DFSDISK?.PDx saved partitioning information (PSAVE)
DFSDISK?.SNx list of sectornumbers for found sectors
DFSDISK?.BNx binary file with related sector-data
DFSDISK?.IMx compressed imagefile, with start of disk
DFSDISK?.MBx RAW image with the MBR sector for the disk
where the 'x' is the disk-number for the physical disk
and '?' is a letter based on the DFSee version.
d = DOS, o = OS/2, w = Windows, l = Linux
Note: A different basefilename from DFSDISK? can be specified in
the DFSDISK dialog, together with several other parameters.
The whole disk will be searched for any partition-table sectors
(MBR/EBR), bootsectors or LVM-information sectors. This will find
almost all deleted partitions, or missing ones after the partition
tables have been damaged.
Selection of this item leads to a dynamic created submenu, to select a disk to be used , including 'ALL disks'
Erase or wipe selected object, freespace areas or unused filesystem sectors
This submenu contains all menu-items related to WIPING sectors.
Wiping is clearing, erasing selected sectors with a pattern,
quite often of all ZERO bytes.
Several selections are possible including the current object,
being a disk, volume or partition, or the freespace in an
opened filesystem, or a freespace area on a partitioned disk.
Wipe one or more sectors to ZEROES at the 'this' sector in current object
This will erase one or more sectors on the current object with
ZEROES, starting at the current sector 'this'
This can be very useful to selectively erase specific filesystem
structures like an Fnode, MFT record or similar.
The number of sectors to be erased can be specified in a popup
dialog-box that will also show the start sector number 'this'.
After specifying the #sectors, there will be a final confirmation
Wipe object (disk/part/vol) completely clean with zeroes. (ALL DATA LOST!)
This will erase ALL DATA on the current object by filling all
sectors with ZEROES. Only the most advanced data-recovery methods
would be able to recover data after wiping it this way.
It removes any remains of partitioning information when used on a
disk, or of confidential file-data when used on a partition or
a whole disk.
Wipe object (disk/part/vol) in DoD SECURE way. (slow and UNRECOVERABLE!)
This will securely erase ALL DATA on the current object by writing
a pattern, an inverted pattern and random data, then verifying that
it really got written. DATA WILL NOT BE RECOVERABLE IN ANY WAY!
This is an algorithm aproved + specified by the USA
departement of defense in 'Standard DoD 5220.22-M'.
It removes any remains of partitioning information when used on a
disk, or of confidential file-data when used on a partition or
a whole disk.
Wipe all sectors in the area of freespace to be selected (clean old garbage)
This will clear ALL SECTORS in an area of freespace to be selected
with ZEROES. Only the most advanced data-recovery methods would
be able to recover data after wiping it this way.
It removes any remains of partitioning information or confidential
file-data that might have resided in this area before it became
freespace.
Freespace areas are all areas on a disk that are NOT in-use by any
partition or by partition-tables or related structures.
Selection of this item leads to a dynamic created submenu, to select a freespace area to be used
Wipe all sectors in the sectorlist to ZEROES (as listed by 'list -w')
This will WIPE every sector in the sector-list to ZEROES.
There are several possible uses for this function, like:
- Erasing filenodes (HPFS) for deleted files
This will exclude the files from subsequent searching
for deleted files, making UNDELETE impossible.
Create list using: Mode=HPFS -> Search deleted files => list
- Erasing all partitioning related sectors from a disk
This will make sure new partitioning will not inherit
ANYTHING from the previous setup of the same disk.
Create list using: Mode=FDISK -> Search partitioning sectors
Wipe all FREE sectors/clusters in the filesystem to ZERO. (.IMZ optimizer)
This will wipe all unused sectors or clusters in the current filesystem
with ZEROES.
This will remove any remains of deleted files or other garbage that was
on the partition. This will make any UNDELETE of files impossible!
(except for files in the Windows trashcan or OS/2 DELDIR)
Clearing the freespace will make compressing a filesystem much more
effective, including creating a compressed IMAGE file (.IMZ).
SECUREWIPE FREE sectors/clusters in the filesystem, SLOW! (DoD 5520.22 spec)
This will wipe all unused sectors or clusters in the current filesystem
repeatedly as specified by the US military Dod 5520.22 specification.
It will remove any remains of deleted files or other garbage that was
on the partition. This will make any UNDELETE of files impossible!
(except for files in the Windows trashcan or OS/2 DELDIR)
This will make ANY recovery of the wiped (file) areas impossible!
FORMAT a partition to be selected from a list, selecting options in a dialog
This submenu contains menu-items to FORMAT a disk partition
to be selected, or the current opened object with a FAT or
FAT32 filesystem.
Several properties of the new filesystem can be selected in
the FAT format dialog, or by using one of the pre-configured
choices in the lower part of the submenu (like OS2LDR).
Formatting is writing new filesystem structures into the area,
making it an EMPTY but valid filesystem of the desired type.
FORMAT a partition to an EMPTY FAT or FAT32 filesystem (all data is LOST!)
This selection will perform a FORMAT of the partition to be
selected to the FAT or FAT32 filesystem format, after setting
options in a dialog with the following fields:
Cluster size Only VALID clustersizes will be presented,
( ) 512 bytes and an optimal default value will be set
( ) 1 KiB as the active selection.
( ) 2 KiB
() 4 KiB Small clusters may reduce wasted space with
( ) 8 KiB many small files, while large clusters may
( ) 16 KiB decrease fragmentation and increase the read
( ) 32 KiB and write performance for large files.
( ) 12-bit FAT Used below 4096 clusters (like diskettes)
( ) 16-bit FAT Used up to 2 GiB, readable on many OS's
() 32-bit FAT Used beyond 2 GiB, or when a small cluster
size is desired for other reasons.
Use boot-code aimed at OS: [Windows 9x ]
This allows you to select between several
bootcode variants allowing it to actually
boot that related operating system.
NOT RELEVANT for data partitions!
Root entries The number of directory entries that are
[512 ] available in the ROOT directory (FAT12/16)
Volume Label The label as recorded in the bootsector as
[DFSee123456 ] well as the ROOT directory of the FAT FS
The default reflects the partition location
SerialNumber Volume serial number, should be unique for
[ee123456 ] removable media. Default based on location
or timestamp when it is not a partition.
Offset FAT-1 Offset from the bootsector to first FAT area
[1 ] default 1 for FAT12/16 and hex 20 for FAT32.
[ ] Use LONG format, initialize all clusters to ZERO contents
This will erase the whole data-area, making sure no old
information is retained. Note that, unlike regular FORMAT
the current DFSee version does NOT check for bad-clusters!
Formatting a partition or volume will destroy ALL data
that is currently on it, and is NOT recoverable!
Selection of this item leads to a dynamic created submenu, to select a partition to be used
Format the CURRENT opened object with a FAT filesystem specified in a dialog
This selection will perform a FORMAT of the current object to
the FAT or FAT32 filesystem format, after setting options in
a dialog with the following fields:
Cluster size Only VALID clustersizes will be presented,
( ) 512 bytes and an optimal default value will be set
( ) 1 KiB as the active selection.
( ) 2 KiB
() 4 KiB Small clusters may reduce wasted space with
( ) 8 KiB many small files, while large clusters may
( ) 16 KiB decrease fragmentation and increase the read
( ) 32 KiB and write performance for large files.
( ) 12-bit FAT Used below 4096 clusters (like diskettes)
( ) 16-bit FAT Used up to 2 GiB, readable on many OS's
() 32-bit FAT Used beyond 2 GiB, or when a small cluster
size is desired for other reasons.
Use boot-code aimed at OS: [Classic MS-DOS ]
This allows you to select between several
bootcode variants allowing it to actually
boot that related operating system.
NOT RELEVANT for data partitions!
Root entries The number of directory entries that are
[512 ] available in the ROOT directory (FAT12/16)
Volume Label The label as recorded in the bootsector as
[DFSee123456 ] well as the ROOT directory of the FAT FS
The default reflects the partition location
SerialNumber Volume serial number, should be unique for
[ee123456 ] removable media. Default based on location
or timestamp when it is not a partition.
Offset FAT-1 Offset from the bootsector to first FAT area
[1 ] default 1 for FAT12/16 and hex 20 for FAT32.
[ ] Use LONG format, initialize all clusters to ZERO contents
This will erase the whole data-area, making sure no old
information is retained. Note that, unlike regular FORMAT
the current DFSee version does NOT check for bad-clusters!
Formatting a partition or volume will destroy ALL data
that is currently on it, and is NOT recoverable!
Format CURRENT object as FAT16 + OS2LDR code (Bootable USB, Large Floppy)
This is a pre-configured FORMAT of the CURRENT opened object
to a FAT16 filesystem, using the 'OS2LDR.SEK' boot code.
All other properties like clustersize are automatically set
to optimal values for the size of the filesystem.
The resulting FAT filesystem and bootcode may be used to
create a bootable OS/2 system on so called 'Large Floppy'
media like USB memory sticks.
Note: Menu item will be DISABLED if the current object
is too large for a FAT16 filesystem.
Resize partition (-tables) and the filesystem structures in that partition
This submenu contains all menu-items related to RESIZING
In all cases, you NEED to have a harddisk-partition selected for
the menu-entries to be enabled, making the functions available.
Resize the current partition, making it smaller (truncating, make freespace)
This will resize the current partition to a size that is SMALLER
than its present size, in other words, TRUNCATE the partition
You will be prompted to specify a new size for the partition, with
a minimum and a maximum value displayed for your convenience.
The size entered will be rounded to make the partition cylinder
aligned, just like any newly created partitions.
When the system uses (IBM-style) LVM-information, it will be
updated to reflect the new size of the partition.
Data within the partition will NOT BE MOVED by DFSee, so to make a
resize possible it may be needed to defragment it, or otherwise
optimize the partition so that the data is moved to the beginning.
A reason to resize partitions is to make freespace available to
allow installation of another operating system.
Resize the current partition, making it larger (expanding, using freespace)
This will resize the current partition to a size that is LARGER
than its present size, in other words, EXPAND the partition
You will be prompted to specify a new size for the partition, with
a minimum and a maximum value displayed for your convenience.
The size entered will be rounded to make the partition cylinder
aligned, just like any newly created partitions.
When the system uses (IBM-style) LVM-information, it will be
updated to reflect the new size of the partition.
Expanding a partition is often done to use remaining freespace
on the disk for an existing partition. However, DFSee will only
allow expanding a partition to use freespace that is DIRECTLY
after the partition.
Expanding is supported for the NTFS and HPFS filesystems.
FAT and FAT32 fileystems can not be expanded yet, unless they
were previously truncated by DFSee. In that case they can be
expanded to the original size.
Resize the filesystem in current partition to use the WHOLE partition size
This will adjust the filesystem present in the current partition
to take up the WHOLE size of the partition ('resize -max')
Usually this will mean making the filesystem LARGER so it fills
the whole partition, and not just the start of it as may happen
after restoring a filesystem-image to a partition that is larger
than the original one was.
Note: making the FS larger is NOT supported for FAT filesystems,
at the moment it is implemented for NTFS and HPFS only!
In some cases it could also make the filesystem SMALLER to make
it fit in the current partition. This will only work correctly
if the end of the partition (that does not fit) was EMPTY.
This may happen when restoring a filesystem-image into a
a partition that is smaller than the original was.
Move or Copy the CURRENT open partition to a freespace area, or within area
This submenu contains all menu-items related to MOVING or
COPYING complete partitions within, or to other freespace areas.
In all cases, you NEED to have a harddisk-partition selected for
the menu-entries to be enabled, making the functions available.
Copy current partition to a different freespace area, do NOT delete original
This will CLONE the whole partition contents to another freespace
area selected from a list of suitable ones. The original partition
will NOT be deleted making the result a true COPY ...
Only freespace areas that are large enough, and are compatible with
the PRIMARY/LOGICAL property of the partition, are suitable.
The partition tables and LVM-information when present, will be
updated to reflect the new position.
When the partition is a bootable one (ACTIVE), the new partition
created in the freespace area will be made bootable as well.
MOVE/COPY of a partition that is part of a multi-partition
LVM volume is NOT supported yet! In that case the menu
items related to MOVE/COPY will be disabled!
Selection of this item leads to a dynamic created submenu, to select a freespace area to be used
Move current partition to a different freespace area (deleting the original)
This will CLONE the whole partition contents to another freespace
area selected from a list of suitable ones. The original partition
will be DELETED making the result a true MOVE ...
Only freespace areas that are large enough, and are compatible with
the PRIMARY/LOGICAL property of the partition, are suitable.
The partition tables and LVM-information when present, will be
updated to reflect the new position.
When the partition is a bootable one (ACTIVE), the new partition
created in the freespace area will be made bootable as well.
MOVE/COPY of a partition that is part of a multi-partition
LVM volume is NOT supported yet! In that case the menu
items related to MOVE/COPY will be disabled!
Selection of this item leads to a dynamic created submenu, to select a freespace area to be used
Move current partition towards the END of freespace (higher cylinder-number)
This will move the whole partition contents towards the end of
the freespace area, to higher sector/cylinder numbers.
The partition tables and LVM-information when present, will be
updated to reflect the new position.
In moving the actual data, unused sectors/clusters are skipped
(smart) UNLESS the original and new location are OVERLAPPING.
In that case the 'smart' option is ignored, and the
copy action will be significantly slower!
MOVE/COPY of a partition that is part of a multi-partition
LVM volume is NOT supported yet! In that case the menu
items related to MOVE/COPY will be disabled!
Move current partition towards BEGIN of freespace (lower cylinder-number)
This will move the whole partition contents towards the beginning
of the freespace area, to lower sector/cylinder numbers.
The partition tables and LVM-information when present, will be
updated to reflect the new position.
In moving the actual data, unused sectors/clusters are skipped
(smart) UNLESS the original and new location are OVERLAPPING.
In that case the 'smart' option is ignored, and the
copy action will be significantly slower!
MOVE/COPY of a partition that is part of a multi-partition
LVM volume is NOT supported yet! In that case the menu
items related to MOVE/COPY will be disabled!
Clone or compare an object to the CURRENT open or another selected object
This submenu contains all menu-items related to CLONING
between objects like Disks, Partitions, Volumes or Images.
Cloning will make a sector-by-sector exact copy from one object
to another one of the same or a different type. The size to be
copied is the lesser of both objects and it is advised to clone
only objects that have the exact same sizes to avoid truncation.
Only the object CONTENTS is copied, related sectors like LVM-info
or partition-table sectors (EBR) are NOT part of the clone.
For copying or moving Partitions to or within freespace areas,
where the partition-tables ARE updated, see the MOVE and COPY
items elsewhere in this menu.
Clone a to-be-selected Disk to another to-be-selected Disk (copy whole disk)
Cloning will make a sector-by-sector exact copy from one Disk
to another one. The size to be copied is the lesser of both and
it is advised to clone TO a Disk of the same or larger size.
The WHOLE disk CONTENTS is copied, including LVM-information
and partition-table sectors (MBR/EBR).
Clone a to-be-selected Partition to another to-be-selected Partition, backup
Cloning will make a sector-by-sector exact copy from one Partition
to another one. The size to be copied is the lesser of both and
it is advised to clone TO a Partition of the same size.
Only the partition CONTENTS is copied, related sectors like LVM
or partition-table sectors (EBR) are NOT part of the clone.
Cloning partitions is an excellent way to make a BACKUP of important
partitions (like your system boot partition) since it can be restored
quickly in case of problems with the original (after viruses etc).
Clone a to-be-selected Volume to another to-be-selected Volume (diskette)
Cloning will make a sector-by-sector exact copy from one Volume
to another one. The size to be copied is the lesser of both and
it is advised to clone TO a Volume of the same size.
Clone a to-be-selected Disk to the currently opened object (dangerous!)
Cloning will make a sector-by-sector exact copy from a Disk
to the CURRENT opened object, which can be any type.
The WHOLE disk CONTENTS is copied, including LVM-information
and partition-table sectors (MBR/EBR).
Clone a to-be-selected Partition to the currently opened object (dangerous!)
Cloning will make a sector-by-sector exact copy from a Partition
to the CURRENT opened object, which can be any type.
Only the partition CONTENTS is copied, related sectors like LVM
or partition-table sectors (EBR) are NOT part of the clone.
Clone a to-be-selected Volume to the currently opened object (dangerous!)
Cloning will make a sector-by-sector exact copy from a Volume
to the CURRENT opened object, which can be any type.
Save RAW or compressed IMAGE-files, incl. size-limited files/removable media
This submenu contains all menu-items related to creating IMAGES
from objects like Disks, Partitions, Volumes or other Images.
Imaging will make a sector-by-sector exact copy from the object
to a binary file, wich can either be RAW or compressed.
RAW images are often used for bootable diskette-images, while
compressed images are good for backup purposes.
Compressed images can be stored in multiple-files, each limited
to a certain size to allow storage of the files on removable
media like CD-R/RW or DVD-R/RW.
Note that DFSee itself does NOT contain CD-burning software!
Create RAW or Compressed imagefile from current or to-be-selected Disk
This will create one or more IMAGE files for (all or part of)
a disk, to be selected in the next dialog ...
Context sensitive help within the dialog will be related to the FILE
dialog when in that area, and specific to imaging in the rest ...
Create RAW or Compressed imagefile from current or to-be-selected Partition
This will create one or more IMAGE files for (al or part of)
a partition, to be selected in the next dialog ...
Context sensitive help within the dialog will be related to the FILE
dialog when in that area, and specific to imaging in the rest ...
Create RAW or Compressed imagefile from current or to-be-selected Volume
This will create one or more IMAGE files for (all or part of)
a volume (like a diskette), to be selected in the next dialog ...
Context sensitive help within the dialog will be related to the FILE
dialog when in that area, and specific to imaging in the rest ...
Create RAW or Compressed imagefile from currently opened object, of any type
This will create one or more IMAGE files for (all or part of)
the CURRENT opened object, which can be any type.
Context sensitive help within the dialog will be related to the FILE
dialog when in that area, and specific to imaging in the rest ...
Create IMZ compressed imagefile from an existing RAW image (.IMG, .HDD etc)
This will create one or more compressed IMAGE files for an existing
uncompressed RAW imagefile like a DFSee .IMG or SVISTA .HDD file.
You first select the RAW image in an Open-file dialog, and then you
can further specify the options for the compressed .IMZ imagefile to
be created in the regular create-image dialog.
Create RAW uncompressed imagefile from an existing IMZ compressed image
This will create one uncompressed IMAGE file for an existing
compressed IMZ imagefile (DFSee specific).
The IMZ file may be part of a multiple, size-limited set of
files to fit a CDROM or similar (.IMZ .002 .003 and so on).
You first select the IMZ image in an Open-file dialog, and then
you can further specify the options for the uncompressed RAW
imagefile to be created in the regular create-image dialog.
Restore imagefiles, or Compare contents to current or to-be-selected object
This submenu contains all menu-items related to RESTORING or
COMPARING images to objects like Disks, Partitions, Volumes
or other Images.
Images are sector-by-sector exact copies from an object
in a binary file, wich can either be RAW or compressed.
RAW images are often used for bootable diskette-images, while
compressed images are good for backup purposes.
Compressed images can be stored in multiple-files, each limited
to a certain size to allow storage of the files on removable
media like CD-R/RW or DVD-R/RW.
Restore RAW or Compressed imagefile to current or to-be-selected Disk
This will RESTORE an imagefile or COMPARE an imagefile to (all or part of)
a physical or virtual disk, to be selected in the next dialog ...
Context sensitive help within the dialog will be related to the FILE
dialog when in that area, and specific to imaging in the rest ...
Restore RAW or Compressed imagefile to current or to-be-selected Partition
This will RESTORE an imagefile or COMPARE an imagefile to (all or part of)
a partition, to be selected in the next dialog ...
Context sensitive help within the dialog will be related to the FILE
dialog when in that area, and specific to imaging in the rest ...
Restore RAW or Compressed imagefile to current or to-be-selected Volume
This will RESTORE an imagefile or COMPARE an imagefile to (all or part of)
a volume (like a diskette), to be selected in the next dialog ...
Context sensitive help within the dialog will be related to the FILE
dialog when in that area, and specific to imaging in the rest ...
Restore RAW or Compressed imagefile to currently opened object, of any type
This will RESTORE an imagefile or COMPARE an imagefile to (all or part of)
the currently selected object
Context sensitive help within the dialog will be related to the FILE
dialog when in that area, and specific to imaging in the rest ...
Verify the integrity of a (DFSee) compressed imagefile with verbose report
This will VERIFY the structural integrity of an imagefile, without
actually restoring or comparing against any selected object.
Internal structures including 32-bit CRC values are verified.
Operate on the list of files/sectors, including display and file-recovery
This submenu contains several actions upon the list of sectors,
often each sector representing a single file or an important
partitioning related sector.
The list can be imported, exported, displayed in several ways
and when containing file references, the files can be recovered.
Export the list of sectors to an ASCII file for later use (or for import)
This will write the DFSee sector-list to an ASCII file
(.SN?/.LSN) containing one sectornumber on every line.
When you select the checkbox for 'Export each DATA sector ...'
the data for those sectors is written to a related binary file
as well (.BN?/.BIN) so you can later restore that to the same
location using the corresponding import menu-selection.
Import ASCII file with sectornumbers to the DFSee sector list (exported)
This will restore the DFSee sector-list from an ASCII file
(.SN?/.LSN) containing one sectornumber on every line.
Each line may contain other text after the sectornumber, to
allow importing from a logfile with more verbose find results
like a DELFIND of FILEFIND action.
When you select the checkbox for 'Import each DATA sector ...'
the data for those sectors is restored from the related binary
file (.BN?/.BIN) as well
Show values in the list with sector numbers in the most compact format
This will display the DFSee sector-list in the most compact format,
with 8 sectornumbers per line in hexadecimal format (list -w)
Show values in the list with sector numbers in a default compact format
This will display the DFSee sector-list in a compact format, suited
to the data contained in the list
This usually is a 'list -f' or a 'list -s' variant.
Show contents of the sectors in the list in verbose-data or filename format
This will display the DFSee sector-list in a more verbose format,
suited to the data contained in the list. This could be in the form
of one path+filename on a line for lists representing filenames, to
detailed sector-dumps for lists related to partitioning information.
This usually is a 'list -d' or a 'list -b' variant.
Show allocation status, path+filename/sectortype + related info from the SLT
This will display the Free/Allocated status for each sectornumber
in the list, and when available, it will display additional info
by using the 'Sector Lookup Table' (SLT)
When the sector is related to a file, the filename and some related
information like the directory it is in will be displayed, otherwise
a filesystem-area or freespace area is indicated.
The SLT will be built when using a 'CHECK xxx filesystem' selection
or when the 'Show Sector-Lookup-Table' menu selection is used.
(or the SLT or CHECK commands from the commandline)
Show list with sector numbers as 1-liners, using a recorded filesystem-mode
This will display the DFSee sector-list in a compact format,
suited to the data contained in the list, when known
This usually is a 'list -f' or a 'list -s' variant.
The FS-mode, reflected by the 'Mode=xxxx' menu and the 'mode=xxxx'
display in the DFSee status line, will be temporarily set to the
mode it was during creation of the list, to make sure any additional
intelligence or formatting of the list is preserved.
Show contents of the sectors in the list, using a recorded filesystem-mode
This will display the DFSee sector-list in a more verbose format,
suited to the data contained in the list. This could be in the form
of one path+filename on a line for lists representing filenames, to
detailed sector-dumps for lists related to partitioning information.
This usually is a 'list -d' or a 'list -b' variant.
The FS-mode, reflected by the 'Mode=xxxx' menu and the 'mode=xxxx'
display in the DFSee status line, will be temporarily set to the
mode it was during creation of the list, to make sure any additional
intelligence or formatting of the list is preserved.
Recover (selected) files from the list to a supplied recovery directory
This will allow you to recover (copy) one or more of the files in the
list to any local or network directory on your system.
It will prompt for a destination directory first, using the last used
one as a default. All files recovered in one go, will be recovered to
this same directory, with their original path appended to retain the
directory structure whenever possible.
It will also prompt for a selection specification in the form of a
full PATH+FILENAME wildcard and an optional allocation-percentage.
As an example, the specification:
'*mydoc*\*project_x*.doc%100'
will recover all files that have 'mydoc' somewhere in the PATH,
'project_x' in the filename and have an extension of '.doc' that
seem to be 100% recoverable. (100% allocation-OK ranking).
Wipe all sectors in the sectorlist to ZEROES (as listed by 'list -w')
This will WIPE every sector in the sector-list to ZEROES.
There are several possible uses for this function, like:
- Erasing filenodes (HPFS) for deleted files
This will exclude the files from subsequent searching
for deleted files, making UNDELETE impossible.
Create list using: Mode=HPFS -> Search deleted files => list
- Erasing all partitioning related sectors from a disk
This will make sure new partitioning will not inherit
ANYTHING from the previous setup of the same disk.
Create list using: Mode=FDISK -> Search partitioning sectors
Copy sectors marked with errors in the SLT, to the sector-list for analysis
Copy sector numbers for sectors marked with errors
to the sector-list for further analysis
All sectors marked with any error except 0x01 are copied.
After being copied to the sector-list they can be listed,
and more important they can be EXPORTED including data, so
the sectors can be analysed remotely (support)
When a finer selection of sectors is required, the SLT2LIST
command may be used directly with the appropriate parameters
Download the complete menu-documentation as static HTML (15 Mb ZIP)
| DFSee main page | File | Edit | Actions | Display | Help |
| Mode=FDISK | AUX | EXT2+3 | FAT | HFS+ | HPFS | JFS | NTFS | REISER | XFS | SWAP |
| (Actions page) | DFSee menu documentation for pulldown : Actions |
| Views: 69412 |
|
Created by Jan van Wijk: Aug 2007, last update: 08-Dec-2007 |
|