|
| (Documentation for the Edit menu) |
|
|
|
|
| DFSee main page | File | Edit | Actions | Display | Help |
| Mode=FDISK | AUX | EXT2+3 | FAT | HFS+ | HPFS | JFS | NTFS | REISER | XFS | SWAP |
Edit a partition table in an MBR/EBR sector using the P-Table-Editor dialog
This will start the interactive partition-table editor,
positioned on the starting-partition selected from a list.
It will allow direct updating of the various fields in the table
and update related fields in the same table accordingly.
Edit LVM information related to disk partitions, LVM-volumes and BMGR-menu
This will start the interactive LVM-information editor,
positioned on the starting-partition selected from a list.
It will allow direct updating of most of the LVM entities:
- volumename
- partitionname
- driveletter
- bootable flag
- installable flag
Start interactive sector-editor on the selected file, allow HEX/ASCII edit
This will allow full editing of a (binary) file using a sector
editor interface with an HEX-pair and an ASCII edit area.
The exact size of the file (in bytes) will be preserved,
DELETE or INSERT of data in the file is NOT possible.
Start interactive sector-editor on the current sector, allow HEX/ASCII edit
This will allow full editing of sector values using an interactive
sector editor interface with an HEX-pair and an ASCII edit area.
From the HEX-editor you can switch to the disassembler with <F2>
Start interactive disassembler on the current sector, coupled with HexEdit
This will show the current sector as disassembled x86 code.
Full navigation is possible using the cursor and PgUp/PgDn key,
and the disassembler is coupled with the HEX-editor in the
positioning and navigation
You can export the disassembled code to an ASCII file for
further processing.
On exit, the HEX-editor will be positioned on the same location
and the current instruction will be highlighted.
Replace data in current sector using HEX/ASCII/UNICODE replacement strings
This will allow partial editing of sector values using dialogs
to specify an edit-offset and a replacement string in HEX, ASCII
or UNICODE to replace the data at the specified offset.
Replace some data in the current sector with supplied offset and HEX pairs
This will allow some direct editing of sector values,
using hexadecimal specified replacement values.
The position in the sector to be updated will be requested,
and the current values for 16 hexadecimal pairs will be
displayed for reference and double-checking.
The replacement value can be typed in in hexadecimal pairs,
and on completion the sector can be written back to the same
or a different sector-number.
Up to a maximum of 120 hexadecimal pairs can be specified.
Replace some data in the current sector with supplied offset and ASCII str
This will allow some direct editing of sector values,
using a plain ASCII specified replacement string.
The position in the sector to be updated will be requested,
and the current string of 16 ASCII characters at that
position are displayed for reference and double-checking.
The replacement value can be typed in as a regular string,
and on completion the sector can be written back to the same
or a different sector-number.
A string of up to 255 characters can be specified.
Replace some data in the current sector with supplied offset and UNICODE str
This will allow some direct editing of sector values,
using a UNICODE specified replacement string.
The position in the sector to be updated will be requested,
and the current string of 8 UNICODE characters at that
position are displayed for reference and double-checking.
The replacement value can be typed in as a regular string,
and on completion the sector can be written back to the same
or a different sector-number.
A string of up to 255 characters can be specified.
Search for Ascii/Unicode/Hex data in all sectors for currently open object
This will search for the specified string in sectors for the
currently opened object, starting at the current sector (this).
You can specify the string to be searched in the FIND dialog.
Many options to change the search criteria can be specified in
that dialog as well. For a more detailed explanation of those
options than available here, check the regular documentation
on the corresponding options for the FIND command (DFSCMDS.TXT)
The string(s) can be specified as ASCII, UNICODE, HEXadecimal or
even a MIX of those by checking the corresponding radiobutton.
The available options with their defaults are:
() Ascii : interpret search string(s) as regular ASCII
( ) Unicode : interpret search string(s) as UNICODE data
( ) Hex pairs : interpret as (pairs of) HEXADECIMAL data
( ) Mixed string : interpret as 'mixed-string' format, see DOC
[ ] Verbose output : Display each found sector in default format
[û] Show arguments : Display a single line per found sector only
() Repeat, 1 hit/sector : Repeat the search, add sectors to list
( ) Repeat multiple hits : Repeat allowing multiple hits per sector
( ) Search once, display : Just search a single time, verbose display
[ ] Case-sensitive match : Require exact case match on primary string
[ ] Search backwards : Search towards LOWER sector numbers
[ ] NOT containing ... : Find sectors NOT containing the string(s)
() Search in every sector : Search every sector in opened object
( ) On Cylinder boundaries : Search specific sectors per cylinder
( ) In freespace (undelete) : Search in filesystem freespace only
( ) In allocated (filegrep) : Search in filesystem allocated area
[ ] Start at NEXT/PREV sect : Skip 'this', start at NEXT/PREV sector
[û] No sector span (faster) : Will not find search string(s) that
cross a sector (512 bytes) boundary
[...] StartOffset : Offset from begin of object to start search
mcs-number, default is the current sector
[...] @Position : Position in sector for primary string
[...] Types : Sector types considered (default ALL)
[...] Secondary ... : Secondary search string, AND with 1st
When specifying a StartOffset, the default unit is MEGABYTES!
When using a hexadecimal sectornumber, make sure to include the
'0x' prefix on the mcs-number and the ',s' unit postfix.
For KiB and GiB use the ',k' and ',g' postfix respectively.
When specifying the '@Position' value, only sectors that have the
primary string AT that position in a sector will be considered.
The position is a DECIMAL value in the range 0..511.
When specifying a 'Types' string, only sectors of that type will be
considered in the search, to show available types for the current
filesystem, use the '???' command or Help -> Available sector types
To search for 2 strings (sectors containing string1 AND string2),
you can specify the 2nd search argument, which will have the
same data interpretation (ascii/unicode/hex) as the primary one,
but will always be considered CASE-SENSITIVE!
Repeat the last search specified through the dialog, exact same arguments
This will repeat the previous search specified in a FIND dialog
using exactly the same search parameters.
When no valid search parameters are available yet, the FIND
dialog will be presented as with a regular FIND action.
NO writing to opened objects for safety, do allow writing log or image-files
This will toggle the 'Read-Only' status for ALL objects that
might be opened using DFSee. The current status is indicated
in the menu itself, in the first column for the menu-item.
When set to Read-Only, no changes are allowed that write to
the opened object. This will save you from unintended actions
that could cause problems.
Writing to normal files like logfiles and imagefiles is still
possible, so you can make imagebackups, or PSAVE backups even
when working Read-Only.
Get disk geometry from disk contents (tables and LVM) instead of the OS/BIOS
This will toggle the 'geocalc' setting, that controls the way
the disk geometry to use for each disk is determined by DFSee.
When 'checked' geocalc in ON, and disk geometry is calculated
from the actual disk contents like partition tables and LVM info.
This is often the most reliable way, and is the default.
When 'unchecked', geocalc is OFF, and disk geometry is queried
directly from the operating system (or the BIOS for DFSDOS).
You may need this in situations where the disk-contents does NOT
represent the desired disk geometry, including the disk size.
This may happen with disk damage (garbage contents) or when
the disk is cloned/imaged from a different size disk.
Note: Unchecking the 'geocalc' setting, and using the menu item:
Mode=FDISK ->
OS/2 LVM and BootManager ->
Set LVM-Geo to DFSee L-Geo ->
... select disk to be updated
Will update the new disk size after a disk-to-disk clone for
disks that have LVM information on them (in eCS, OS/2 4.50).
The startup default (geocalc ON) can be changed using the
startup '-geocalc-' switch, and can be modified on-the-fly
using the 'SET GEOCALC on/off' command, as this menu does.
Force specific Mode=xxx (Fdisk or FS) Can be dangerous, for expert use only!
This allows a specific mode to be forced when automatic setting
of that mode does not work correctly.
This might be needed on damaged or unformatted disks.
Be carefull though using any FIX or other commands that write to
the disk or partition unless you are REALLY sure the selected
mode is the correct one.
Create, update, display, recover or fix partition-tables or LVM information
This is the default operation mode for DFSee and enables commands
and menus that are working at the DISK level (like Fdisk and LVM)
with partitioning, LVM as well as imaging and cloning functions.
FDISK is the classic disk-partitioning tool as used with DOS.
It is used to create primary partitions, extended partitions
and logical volumes in the extended partition.
LVM, the Logical Volume Manager, is an 'FDISK-like' program plus
some related drivers on all OS/2 kernel versions starting at 4.50,
including eComStation. It allows more flexible naming and usage of
partitions and drive-letters, including joining multiple partitions
on more than one disk into a single volume.
DFSee respects the drive-letters as assigned with LVM and has
special display options like the 'PLIST LVM' command in FDISK
mode. Also the 'part' display will show volume and partition
Check, analyse, display or fix EXT2 or EXT3 filesystem, used on Linux
This will enable all EXT2+3-specific commands and menus
Forcing the FS-mode in itself is not dangerous in any case, however,
FS-specific commands like 'fixboot' in an incorrect mode CAN be!
The 2nd extended filesystem for Linux is the default FS on almost
all modern Linux distributions. The standard version is EXT2 while
Check, analyse, display or fix FAT12, FAT16 or FAT32 filesystems
This will enable all FAT-specific commands and menus
Forcing the FS-mode in itself is not dangerous in any case, however,
FS-specific commands like 'fixboot' in an incorrect mode CAN be!
File Allocation Table, the most important structure in the
classic DOS filesystem that also gave it its name.
It is a table of cluster-numbers that indicates the cluster
that holds the next part of the current file or directory,
or indicates that this was the last cluster.
The first cluster of a file is pointed to by the directory
entry that also has the filename, size and the flags.
This way the location of each cluster of a file can be easily
found by following this 'allocation-chain'.
The size of one entry in this FAT is usually 2 bytes (16bit),
and clusters of maximum 32KiB, resulting in the largest FAT16
filesystem of 2GiB. (4GiB on Win-NT with 64KiB clusters)
On small disks (and diskettes) a 12-bit FAT is used, and for
really large disks the FAT32 filesystem was introduced.
DFSee supports 12, 16 and 32-bit FAT filesystems.
The FAT32 version of the filesystem uses 4-byte = 32-bit FAT
entries. This makes the maximum size of a FAT32 filesystem
nearly unlimited. The FAT structure itself does take up a lot
of space on the disk, and in memory when using the filesystem.
FAT32 was introduced with Windows95, and is also supported on
the other newer Windows versions (98, ME, 2000 and XP).
OS/2 and eCS also support it through the 3rd-party installable
filesystem FAT32.IFS made by Henk Kelder.
The FAT has no redundancy and is sensitive to errors like:
- lost clusters where no directory entry points to the chain
- cross links where two allocation chains point to the same
cluster at some point.
The lack of redundancy also makes it VERY hard to undelete files
in a reliable way. At this point DFSee does NOT support undelete
Check, analyse, display or fix the HFS+, journalled filesystem for the MAC
This will enable all HFS-specific commands and menus
Forcing the FS-mode in itself is not dangerous in any case, however,
FS-specific commands like 'fixboot' in an incorrect mode CAN be!
The original HFS was used with the MAC for several years, and was
enhanced with journalling and several other improvements in HFS+
Check, analyse, display, undelete or fix HPFS or HPFS386 filesystems
This will enable all HPFS-specific commands and menus
Forcing the FS-mode in itself is not dangerous in any case, however,
FS-specific commands like 'fixboot' in an incorrect mode CAN be!
High Performance FileSystem
Offered as a real improvement over the classic FAT filesystems
with the OS/2 and eCS Operating System. Its main advantages are
faster access, more reliable error recovery and better handling
of large disks. There is also a (server) version called HPFS386
Check, analyse, display or fix JFS filesystem, IBM OS2/eCS or Linux flavour
This will enable all JFS-specific commands and menus
Forcing the FS-mode in itself is not dangerous in any case, however,
FS-specific commands like 'fixboot' in an incorrect mode CAN be!
Journalling File System
A filesystem originally developed by IBM for the AIX operating
system sharing a lot of features with other UNIX filesystems
and adding journalling on all filesystem metadata operations.
This greatly reduces the time to check and repair any damage
after crashes or other disasters (CHKDSK).
First offered for OS/2 with WSeB and now also available in eCS
and the Convenience Packs 1 & 2 for the desktop.
Check, analyse, display, undelete or fix NTFS filesystem (NT/W2K/XP)
This will enable all NTFS-specific commands and menus
Forcing the FS-mode in itself is not dangerous in any case, however,
FS-specific commands like 'fixboot' in an incorrect mode CAN be!
New Technology File System
The new (journalling) filesystem introduced with Windows-NT.
It has many of the same improvements over FAT as HPFS, but has
a totally different internal structure. It also adds security
information and compression and is expandable by defining new
stream-types. Several versions exist that added specific
Check, analyse, display or fix ReiserFS, journalled filesystem on Linux
This will enable all ReiserFS-specific commands and menus
Forcing the FS-mode in itself is not dangerous in any case, however,
FS-specific commands like 'fixboot' in an incorrect mode CAN be!
The ReiserFS, designed by Hans Reiser, is one of the newer file
systems used with Linux (and Unix) and is known for high performance.
It implements journalling as well and uses database-like structures.
Check, analyse, display or fix the XFS, journalled filesystem on Linux
This will enable all XFS-specific commands and menus
Forcing the FS-mode in itself is not dangerous in any case, however,
FS-specific commands like 'fixboot' in an incorrect mode CAN be!
The original XFS design was circulated within SGI in October 1993
as 'xFS: the extension of EFS'. XFS was first released in IRIX 5.3.
The port to Linux began in 1999 against 2.3.40. It was accepted into
the mainline in the 2.5 kernel in 2002, and the 2.4 kernel in 2004.
Check, analyse, display a Linux SWAP space area, enabling 'smart' imaging
This will enable all SWAP-specific commands and menus
The main reason for a seperat 'swap' mode is allowing
smart disk imaging and cloning, using the available
logic to skip all SWAP blocks except the first one.
Generic analysis and display for any filesystem unknown to DFSee
This will disable all FS-specific commands and menus
Modify several DFSee program settings and TxWin user-interface properties
This menu contains a few selections that change the
appearance and behaviour of the DFSee user interface.
Changes made in this menu will only affect the current
DFSee session. On the next startup of the program the
default settings will be active again.
Select and activate any of the available window-color schemes
This will present a menu with the available color schemes to be used
for all the windowing parts of the user interface.
It does NOT change the colors used in the main output window!
The current color scheme will be highlighted on opening the menu.
Use the '-scheme:xxx' EXE switch to start with a specific scheme.
Selection of this item leads to a dynamic created submenu, to select a colorscheme to be used
Use inverted colors on the scrollable output screen
This will invert ALL colors used in the text-output window.
Both background and foreground colors are affected.
The resulting colors also depend on other settings like the
background black/blue and the bright-foreground setting.
Note that the colors used in the rest of the application like
menus and dialog windows does NOT change with this setting.
Use bright foreground colors only on the scrollable output screen
This will make any low-intensity color used as foreground to
be changed to high-intensity (bright colors).
The setting is most useful on lighter (inverted) backgrounds.
Note that the colors used in the rest of the application like
menus and dialog windows does NOT change with this setting.
Use blue (or brown inverted) background instead of classic black or white
This toggles between a default Black or Blue background color.
The default foreground color in both cases will remain white.
When combined with the 'Inverted output-screen' setting, it will
toggle between white (inverted black) and brown (inverted blue).
Note that the colors used in the rest of the application like
menus and dialog windows does NOT change with this setting.
Use 7-bit ASCII character only, avoid non-standard 'drawing chars'
This will restrict the use of ASCII characters to the range
of 0 through 127 decimal. This may avoid problems re-using
the text through cut-and-paste (to email or word-processor).
The setting is NOT needed to get a 'clean' logfile, since the
logfile in DFSee is 7-bit ASCII by default.
Use ANSI-like colored text string on the scrollable output screen
This will avoid the use of ANSI escape-sequences to be used
in the output-screen, avoiding possible problems when re-using
the text via the clipboard or otherwise.
The setting is NOT needed to get a 'clean' logfile, since the
logfile in DFSee is cleaned from ANSI sequences by default.
Automatically open menu pulldown on selecting menu-heading in the MenuBar
This toggles the automatic opening of pulldowns from the main menu.
When ON, each menu-heading selected on the menubar will automatically
be opened, expanding to a list of menu-choices.
When OFF, the menu-heading selected will be highlighted but requires
another <Enter> or <Down> key to open.
This can be set at startup using the '-M:2' switch.
Re-initialize the DFSee windowing system to use the full (resized) window
This will re-initialize the windowing component in DFSee to take
advantage of a new, probably larger, OS window size.
It is useful after changing window 'properties' on NT/W2K/XP
You can also resize and initialize in one go by using a command like:
mode 90,45
directly from the DFSee command-line.
Re-initialize DFSee, using a simple command-driven non-windowed interface
This will change the user-interface to e very simple command-driven
one without any output scrolling. Commands may be typed, and resulting
output will be displayed but scrolls off the screen eventually.
You can also startup in this mode by using the switch '-w-'.
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 |
| (Edit page) | DFSee menu documentation for pulldown : Edit |
| Views: 69430 |
|
Created by Jan van Wijk: Aug 2007, last update: 08-Dec-2007 |
|