This will allow full editing of sector values using an interactive
sector editor interface with an HEX-pair and an ASCII edit area.
It is the only view that allows editing, and modifications will
be written back to the opened object (disk, partition, volume)
when moving to other sectors, or on <Enter>.
You can switch to other views with <F2>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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.
You can switch to other views with <F2>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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
[x] 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
[x] 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!
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

Check, analyse, display or fix the HFS+, journaled 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+
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

This will enable all EFAT-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!
EFAT filesystem
Enhanced FAT filesystem developed to work around the FAT32
limits when storing large files exceeding 2Gb on SD cards and
other removable media.
The design of the filesystem is also optimized for fast writing
by using a bitmap instead of the FAT datastructure for allocation
and its internal structures are aligned to get maximum performance
when used on solid-state media like SD cards and SSD disks.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

This will present a menu with the available number of colors
both for the windowing system as the output-window itself.
It will be either MONOCHROME, with 1 foreground, 1 background color,
or 16 FG on 8 or 16 BG colors, from a palette of 16
The current number of colors will be highlighted on opening the menu.
Use the '-C:xxx' EXE switch to start with a specific nr of colors.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

Selection of this item leads to a dynamic created submenu, to select a color palette to be used

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.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

Selection of this item leads to a dynamic created submenu, to select a colorscheme to be used

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.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

This toggles the display of the 3..4 line prompt after every command
executed from the command-line or from most of the menu selections.
These lines contain the returncode for the last command executed,
and some related sector numbers for 'likely interesting' sectors.
When switched off, there are 3 to 4 more lines of information that
fit on the screen, which could be very useful to show larger amounts
of data (like whole sector HEX-dumps) without having to scroll back.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

Test generated (DFSee/Txlib) keyboard codes and mouse response
Will display a keycode for each key pressed, with the TxLib/DFSee
assigned name for that key, or 'unknown' as well as a timstamp in
seconds from the start of the program.
For the mouse it shows the X and Y char position (top left is 0 0),
the mousebutton pressed and the state of the modifiers (Ctrl/Alt)
and the timestamp, followed by '(DBLCLK)' if the click was within
the double-click time
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

This will toggle the ERROR Strategy setting, that controls the way
read- write- and other low level errors are handled while performing
operations like WIPE, CLONE, IMAGE, RESTORE and similar commands.
When 'checked' the error strategy is IGNORE, meaning errors are ignored,
and any non-zero returncodes will be suppressed (made 0) so they will NOT
surfeace in a script.
When 'unchecked', the ERROR strategy is either CONFIRM (user confirmation)
or it is QUIT, in which case the running operation will be aborted and the
non-zero returncode surfaces to the script or DFSee user-interface level.
The startup default (Strategy CONFIRM) can be changed using the startup
'-E:i' or '-E:q' switch, it can be overridden just for the CURRENT command
using the option '-E:i' or '-E:q' with that command, and finally the global
strategy can be modified on-the-fly using the 'SET ERROR confirm/ignore/quit'
command from the commandline or a script
You can put a command like 'set error quit' in your profile.dfs to
set the error strategy without a startup-switch when starting DFSee.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

This will toggle the 'gptAuto' setting, that controls the way
the partitiontables for GPT style disks are interpreted by DFSee.
When 'checked' gptAuto is ON, and the actual GPT-style partitions
will be retrieved from the GPT database and displayed in DFSee.
This is the most useful way of looking at it, and is the default.
When 'unchecked', gptAuto is OFF, and the GPT databse in ignored!
Instead the 'protective MBR' entry in the regular tables is shown.
The startup default (gptAuto ON) can be changed using the
startup '-gptauto-' switch, and can be modified on-the-fly
using the 'SET GPTAUTO on/off' command, as this menu does.
You can put a command like 'set gptauto OFF' in your profile.dfs to
disable this feature without a startup-switch when starting DFSee.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

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 is 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.
You can put a command like 'set geocalc OFF' in your profile.dfs to
disable this feature without a startup-switch when starting DFSee.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

This will toggle the 'SyncLVM' setting, that controls the automatic
synchronisation of the OS/2 LVM-Engine with new DFSee information.
When 'checked' SyncLVM is ON, and all changes to driveletters etc
are passed on to the LVM-Engine dynamically, without the need to
reboot the system to make changes visible.
WARNING: Synchronising LVM information from DFSee to the LVM Engine
is known to cause TRAPS on some systems, most often when
REMOVABLE media are present (like USB disks/memory sticks)
Because of this, using it is NOT RECOMMENDED!
When 'unchecked', SyncLVM is OFF, and you need a system reboot before
any change to driveletters of volumenames is visible in LVM and the
rest of the operating system. For safety reasons, this is the default.
The startup default (SyncLVM OFF) can be changed using the
startup '-synclvm' switch, and can be modified on-the-fly
using the 'SET SYNCLVM on/off' command, as this menu does.
You can put a command like 'set synclvm ON' in your profile.dfs to
enable this feature without a startup-switch when starting DFSee.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

This will toggle the 'floppy' setting, that determines if diskettes
are included in the volume/driveletter lists in menus and dialogs.
Having diskettes in those lists can cause delays of several seconds
when presenting the main DFSee menu.
The startup default ('floppy' OFF) can be changed using the
startup '-floppy' switch, and can be modified on-the-fly
using the 'SET FLOPPY on/off' command, as this menu does.
You can put a command like 'set floppy ON' in your profile.dfs to
enable this feature without a startup-switch when starting DFSee.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

This will toggle the 'logAuto' setting, that controls the way the
name for the logfile specified in the LOG dialog screen is handled.
When 'checked' logAuto is ON, and a sequence number from 001 to 999
will be appended to the specified filename, incrementing it each time
a log is started (typically at DFSee startup).
When 'unchecked', logAuto is OFF, and the filename is unchnaged.
The startup default (logAuto OFF) can be changed using the
startup '-logauto' switch, and can be modified on-the-fly
using the 'SET LOGAUTO on/off' command, as this menu does.
You can put a command like 'set logauto ON' in your profile.dfs to
enable this feature without a startup-switch when starting DFSee.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'

This will toggle the 'pt0' setting, that controls the way type 0x00
entries in the MBR partition table for primaries is handled.
When 'checked' pt0 is ON, and type 0x00 entries are handled as PARTITIONS
allowing all sorts of manipulation of such 'hidden' partitions/filesystems.
Note that for a type 0x00 entry to show up, it MUST have a valid size and
start-location in the partition table!
Also note that as long as the 'pt0' setting is ON, you will not be able to
create a partition in this 'freespace', since it is seen as a partition
When 'unchecked' (the default), pt0 is OFF, and type 0x00 entries are
seen as regular FREESPACE, available for creation of new partitions.
Type 0x00 'partitions' are useful to HIDE such areas (temporarily) for
the operating system, so it does not get mounted/attached or locked as
long as it is being manipulated (by DFSee :)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'