
   Display File Systems; version 4.28 28-06-2002  (c) 1994-2002; Jan van Wijk
 ----------------------------[ www.dfsee.com ]-------------------------------


CONTENTS
--------
 Examples of DFS usage



Note on the format used:
I will write most examples in the form of a DFSee 'scenario' that begins
with starting DFSee, and then lists the commands to be used.

Starting DFS could be DFS.EXE (OS/2), DFSDOS.EXE (DOS) or DFSNT.EXE (Win-NT),
in the example I will just specify 'DFS', so just fill in whatever you use ...

Also, on commands I might add some commant at the end of the line, preceeded
with a ';' character. You can include that on the actual command, it will be
echoed to the screen (and possible log file) but otherwise has no effect.




Examples of DFS usage
---------------------

 1) Make a backup of all the important partition sectors in a file

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      psave * a:\dfspsave  Backup of partitioning sectors

    Where the last part (Backup of ...) can be any comment you like

    It can be restored at any time using the PRESTORE command, this will
    either restore all sectors, or just selected ones. See DFSFDISK.TXT


    Note:
    When running this command directly from the (operating system)
    commandline, you MUST make sure the DFSee FDISK mode is selected:

    DFS.EXE  fdisk  psave  *  a:\dfspsave  Backup of partitioning sectors


 2) Create logfile to keep DFSee output for analysis (or to send to me :-)

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      log  filename                     ;append logging to 'filename.log'
      ...

    or even simpler:

    DFS -log:filename
      ...

    Where you fill in a meaningfull filename, like part of your name ...

    Do NOT use output redirection (DFS xxxx > filename.log) because that
    will cause a lot of garbage to be logged into the file.


 3) Collect information to perform a manual un-fdisk (find all boot sectors):

    This is automated in the scripts DFSUNFD.BAT (DOS/WinNT versions) and
    DFSUNFD.CMD (OS/2 version). These collect info for every physical disk.

    For analysis, zip the resulting log file and send it to me:
    support@dfsee.com

    Add as many details as you can remember about the original disk layout,
    partition types, sizes etc. I'll use some of my spare-time to take
    a look at it, which might take some time!

    Note: When the geometry of the disk might have changed, after BIOS LBA
          change, SCSI adapter change etc, you should change the "bsfind"
          command above by: "find* ebrlsdf". This will take a lot more time
          but will find bootsectors even when the geometry does not match.


 4) Recover a 'lost' NTFS partition where the bootsector is damaged and
    the partition is not recognized by NT anymore (assuming 3rd partition):

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      log recover
      part 3
      fs NTFS
      fixboot


 5) Recover a 'lost' JFS partition where the bootsector is damaged and
    the partition is not recognized by OS/2 anymore (assuming 2nd partition):

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      log recover
      part 2
      fs JFS
      fixboot


 6) Recover a 'lost' HPFS partition where the bootsector is damaged and
    the partition is not recognized by OS/2 anymore (assuming 1st partition):

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      log recboot
      part 1
      fs HPFS
      fixboot


 7) Recover a 'lost' or damaged HPFS spareblock (sector 11) when the
    partition is not recognized by OS/2 anymore (assuming 1st partition):

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      log recspare
      part 1
      fs HPFS
      findcp
      fixspare

    Note: with a damaged spareblock you can get various error messages from
          OS/2 about codepages or other things. However when starting DFSee
          and selecting the partition it will tell the spareblock is damaged.


 8) Save and restore (parts of) a disk or volume

    The "sim" command can be used to save a complete disk, including partition
    information to one (very large!) file on a different (network) drive.
    The save the entire unit (opened disk/partition or volume) use:

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      sim img-name 0 $

    It can be restored using the "wrim" command, but will only work perfectly
    if the destination disk has the same geometry as the source disk.
    ('heads' and 'sectors' the same like "255, 63", cylinders same or larger).
    This can be used to clone one workstation to multiple machines.
    Note: Starting with version 4.14 this can be done easier with the CLONE cmd

    It can also be very usefull to save a single sector (like the bootsector)
    when you are experimenting with the filesystem.

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      part 04                           ;select the partition
      sim bootsecX 0 1                  ;save bootsector to file bootsecX.img


10) Undelete a file on HPFS or NTFS; Find the the files using:

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      part 01                           ;select the right partition
      delfind                           ;find ALL deleted files
      export   undel01                  ;save found fnode info to a file
      delshow                           ;optionaly list them (ALL !)
      delshow  *test*%100               ;or just a selection, here only 100%
                                        ;recoverable with 'test' in the name

    Use "delsave" command to copy the deleted files to a directory, see (11)



11) Recover a selection of the found "undeletable" files (NTFS or HPFS)

    First find the possibly deleted files using DELFIND, see (10)

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      part 01                           ;select the right partition
      import   undel01                  ;restore found info from file
      delshow  *inst*                   ;list files with 'inst' in the name
      delsave  X:\undel  *inst*         ;recover same ones to X:\undel\  dir

    Notes: - It's best to use a different drive to avoid overwriting

           - The wildcard used on delshow (and delsave/recover) can contain
             multiple wildcard characters, and deals with the FULL PATH and
             filename, so you can include (parts of) the directory too.

           - You can also undelete a single file using the 'saveto' command
             and specifying the files sequence-number: .NNNNN shown at the
             left of the 'list' output.


12) Update the HPFS bad-sector list with the results of a DFS-scan

    Find all sectors that are unreadable:

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      part 01                           ;select the right partition
      scan                              ;find unreadable sectors
      export b badguys                  ;save in an ASCII file badguys.lsn

    Now replace the internal bad-sector list with the new modified one:

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      part 01                           ;select the right partition
      import b badguys                  ;get the bad-sector list from file
      fixbs                             ;and insert in HPFS badsector list


    Notes: - You can do this in one step too, no need to export/import



13) Show all detected anomalies in the SLT (like allocation errors)
    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      check                             ;build SLT and report all errors


14) Display the FAT for a diskette in drive A:

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      dfs vol a
      fatshow


15) Display the FAT Root-directory for partition C:
    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      dfs part C
      root"


16) Save the master boot record (MBR) on a different PC connected with a
    parallel laplink cable and running the LPT tool:

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      disk 1
      sim [lpt.exe]d:\images\mbr.img 0 1


17) Restore the master boot sector from a different PC connected with LPT:

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      disk 1
      wrim [lpt.exe]d:\images\mbr.img 0 1


18) Resolve original name of FILExxxx.CHK files (created by CHKDSK)

    When CHKDSK recovers files it will place in a FOUND.xxx directory in
    the root-directory. This directory contains one or more recovered files
    with names like FILE0001.CHK
    The original name of the file is still in the Fnode, it can be shown
    using the following dhpfs commands (assuming partition 03) :

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      part 03                           ;Select partition 'id' (must be HPFS)
      \found.000\file0001.chk           ;Search and display Fnode for .CHK

    Now 15 characters of the original name are shown as "Fnode Name String"


19) Show freespace area's (HPFS)

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      slt $


20) Automatically FDISK a workstation using a batch- or command-file like:

    echo DFSee FDISK generic workstation >  dfsfdisk.log
    dfsmdos -b fdisk newmbr                 1  clean
    dfsmdos -b fdisk create primary bmgr
    dfsmdos -b fdisk startable 1
    dfsmdos -b fdisk create logical fat  6  1  -1,c MAINT
    dfsmdos -b fdisk create primary hpfs *  1  +0   WARP

    This will create a disk with bootmanager (image prepared with DFSIBMGR)
    a small maintenance partition at the end of the disk minus 1 cylinder
    and a primary partition filling the rest of the disk.


21) Automatically FDISK a server-machine using a batch- or command-file like:

    echo DFSee FDISK RAID  server          >  dfsfdisk.log
    dfsmdos -b fdisk newmbr                   *  clean
    dfsmdos -b fdisk create primary bmgr
    dfsmdos -b fdisk startable 1
    dfsmdos -b fdisk create primary hpfs 300  1  0  SYSTEM
    dfsmdos -b fdisk create logical fat  200  1
    dfsmdos -b fdisk create logical hpfs *    1  0  RESTORE
    dfsmdos -b fdisk create logical hpfs *    2
    dfsmdos -b fdisk create logical fat  *    3
    dfsmdos -b fdisk setboot 0:SYSTEM
    dfsmdos -b fdisk setboot m:advanced


22) Make a clean master boot record, getting rid of all old partitions

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      newmbr 1 clean                    ;Create fresh MBR on disk 1 with
                                        ;clean, empty partition table


23) Restore saved backup of all the important partition sectors from a file

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      prestore * a:\dfspsave

    Each of the available *.PDn files will be restored to the same disk
    it was created from. All saved sectors will be restored and, when
    not using batch mode, the user will be prompted for each of them
    allowing a more selective restore.


24) Restore PSAVE file of one disk, to a different one, clone partition tables

    Command                             Explanation

    DFS                                 ;Start DFS and scan physical disks
      prestore 3 a:\dfspsave.pd1

    Assuming a PSAVE has been run with at least one disk present, the file
    dfspsave.pd1 will contain all important partition sector for disk 1.
    This will be restored to the specified disknumber 3.



25) Create a detailed overview of all your disks and partitions in a text file

    Command                             Explanation

    DFS  -log:diskpart                  ;Start DFS and open a logfile
      part ++a

    This can also be run directly from the commandline, as in:

    DFS.EXE  -log:diskpart  -Q  part ++a



26) Clone a physical disk to another (identical) one, including all data

    Command                             Explanation

    DFS  -log:dskclone                  ;Start DFS and open a logfile
      disk   2                          ;select/open the TARGET disk
      clone  -disk:1                    ;clone disk-1 to disk-2

    This can also be run directly from the commandline (batch mode!), using:

    DFS.EXE  -log:dskclone  -b  -Q  disk 2#clone -disk:1



27) Clone partition from another partition (data only, no partition table)

    Command                             Explanation

    DFS  -log:pclone                    ;Start DFS and open a logfile
      part  7                           ;select/open the TARGET partition
      clone  -part:1                    ;clone part-1 to part-7


    This could be used to clone the BMGR to another disk, including all
    code and configuration data.



28) Truncate the first partition (FAT, HPFS or NTFS), making 500Mb available

    Command                             Explanation

    DFS  -log:truncate                  ;Start DFS and open a logfile
      part  1                           ;select/open the partition
      trunc  -free:500                  ;truncate to current size - 500 Mb



29) Create an imagefile for a partition, using CLONE instead of SIM

    Step 1: Create a dummy image file at the destination
    Stap 2: Open the created dummy and CLONE an existing partition to it

    echo dummy > v:\part05_backup.img
    DFS  -log:imgclone
      im  v:\part05_backup.img
      clone  -part:05
      q

    Note: The resulting image will be as large as the partition!
          In real life, SIM is the better alternative.


30) Expand an HPFS partition using DFSee and CHKDSK (updated for 4.27)

    While testing the TRUNCATE command for HPFS, where CHKDSK is needed to
    fixup the allocation bitmaps, I found that it also works the other way!

    a) Make some freespace AFTER your HPFS partition (using DFSee delete)
    b) Wipe this freespace to all binary zeroes (to avoid garbage info)
    c) Delete the HPFS partition, and create it again in the same place
       but with a larger size. (using the freespace from step a)
    d) Use the 'RESIZE -max' command to update the HPFS internal size info
    e) Reboot for non-LVM systems, or run LVM.EXE to (re)assign driveletter
    f) Run CHKDSK on the partition, this will expand the allocation bitmaps
       to use the whole new partition-size for the HPFS filesystem.

    On LVM systems, you might need to create the volume for that partition
    again to update all LVM info (in step e). Make sure that you create that
    volume "from existing partition", otherwise it might CLEAR the bootsector
    as well, leaving the partition unformatted. You can recover from that by
    using "fs hpfs" and "fixboot" on the partition, or be saving the bootsector
    with the SIM command before deleting the volume and restore with WRIM.

    In my tests I only needed to create the volume "from existing partition"
    and select the resized partition (identify by size).

    As an alternative for testing with minimal risk, you could create a new
    (larger) partition and CLONE the smaller one to that location.
    The scenario for that (and as I used it) is:

    a) Make a new partition, larger than the current on at different location
    b) Wipe this new partition to all binary zeroes (to avoid garbage info)
    c) Reboot for non-LVM systems, or run LVM.EXE to (re)assign driveletter
    d) Clone the source HPFS partition to this new, larger, location
    e) Use the 'RESIZE -max' command to update the HPFS internal size info
    f) Run CHKDSK on the partition, this will expand the allocation bitmaps
       to use the whole new partition-size for the HPFS filesystem.

       Note that the reboot/LVM step has been moved to an earlier stage here
       to avoid any risk of clearing the bootsector. (by LVM.EXE)


    Note: I am not sure if there is a limit to how much you can expand your
          HPFS partition. All experiences and info on that is welcome!
          My largest test was expanding a 2000 Mb eComstation bootable partition
          to a new size of 3500 Mb, the result was a working HPFS partition!

          Version 5.xx of DFSee will probably integrate some of the steps above
          to get a more user-friendly 'RESIZE' with a minimal nr of steps.




31) Create a DOS boot diskette that has enough free memory for DFSDOS.EXE

    Since DFSDOS.EXE has been growing over the years, it will only run
    reliably now, with at least 650 Kb of free memory. That can ONLY be
    achieved using memory managers such as EMM386 or QUEMM.
    Because EMM386 comes standard with al modern DOS versions, including
    Windows-9x, I will outline here how to create a "DFSee DOS boot disk"

    DR-DOS can be downloaded free of charge from:

        ftp://ftp.lineo.com/pub/drdos/


    The most important tricks used are load the DOS kernel in the so called
    "hi memory area" (HMA) and mapping the reserved graphic-video memory
    area to be used as DOS memory.

    For Windows-9x the procedure is as follows:

    a) Create a bootable diskette in a DOS command prompt with the command:

       format  a:  /s

    b) Copy the following files from the windows directories to the floppy:

       \WINDOWS\EMM386.EXE                   ==> A:\
       \WINDOWS\HIMEM.SYS                    ==> A:\
       \WINDOWS\COMMAND\MEM.EXE              ==> A:\
       \WINDOWS\COMMAND\ANSI.SYS             ==> A:\

    c) Put the following lines in config.sys:

       DEVICE=a:\himem.sys
       DEVICE=a:\emm386.exe NOEMS I=A000-B7FF
       SHELL=A:\COMMAND.COM A:\ /E:512 /P
       DOS=HIGH,UMB
       DEVICEHIGH=A:\ANSI.SYS


    d) Put the following lines in autoexec.bat

       @ECHO Off
       prompt=$e[0;1;32m[DFSee-Win98] $p -$g $e[0m
       mem
       echo.
       echo Type 'DFSDOS' to start DFSee ...


    e) Copy DFSDOS.EXE to the diskette

    On booting, the mem command should show more than 700 Kb for the
    largest executable that can be loaded ...



    For Caldera/DR-DOS the procedure is as follows:

    a) Create a bootable diskette in a DOS command prompt with the command:
       (assuming DR-DOS is installed on your harddisk)

       format  a:  /s

       Or, as an alternative, create one using the "install" program on
       the distribution disk. Warning: that install does need/use some
       space on your C: drive for temporary files, so C: must be FAT!


    b) Copy the following files from the windows directories to the floppy:

       EMM386.EXE                           ==> A:\
       MEMMAX.COM                           ==> A:\
       MEM.EXE                              ==> A:\
       ANSI.SYS                             ==> A:\

    c) Put the following lines in config.sys:

       DEVICE=a:\emm386.exe NOEMS VIDEO
       SHELL=A:\COMMAND.COM A:\ /E:512 /P
       DOS=HIGH,UMB
       DEVICEHIGH=A:\ANSI.SYS


    d) Put the following lines in autoexec.bat

       @ECHO Off
       prompt=$e[0;1;32m[DFSee-DRDOS] $p -$g $e[0m
       memmax +v
       mem
       echo.
       echo Type 'DFSDOS' to start DFSee ...


    e) Copy DFSDOS.EXE to the diskette

    On booting, the mem command should show more than 730 Kb for the
    largest executable that can be loaded ...


    Note: Example config.sys and autoexec.bat for Win9x and DRDOS are
          distributed with DFSee in the file DOSBOOT.ZIP


32) Change the filename in an HPFS directory and Fnode

    This is sometimes needed to get rid of a file that has 'illegal'
    characters in the name like '>' or other strange characters
    created in a different codepage.

    High-level:

    a) Find the FNODE for the file       ('find' command or '\path+filename')
    b) Update shortname if needed        ('H .' + 'edit' command)
    c) Check and write back              ('show' + 'write' command)
    d) Find related directory block      ('u' + 'd' command)
    e) Find the long-filename in there   ( 'H . ' + some 'd' commands)
    f) Edit the long-filename in there   ('edit' command)
    g) Check and write back              ('show' + 'write' command)

    Low-level: change '\tmp\filename.bad' to 'filename.txt'

    DFS.EXE
      part  03
      \tmp\filename.bad
      h  .
      edit  -p:16  -a:"txt"
      show
      write  .
      u
      d
      H  .
      d
      d
      edit  -p:0xa4  -a:"txt"
      show
      write  .
      q


33) Reboot to a different operating-system partition (IBM bootmanager installed)

    OS/2 or eComStation installations with IBM bootmanager installed can use
    the standard SETBOOT.EXE program to reboot to any bootable partition.

    You can do the same using the DFSee program, added benefit is that you
    can use it from a Windows partition as well (to boot back to OS/2) and
    that you can have an extra confirmation step if you like.


    Example to boot from eComStation to an XP partition called "WinXP":

    Create a new program-object by locating any existing program icon,
    right-click and select "Create another -> Program" and fill in:

    Path and filename:   H:\T\DFS.EXE
    Parameters:          -w+ setboot -iba:WinXP
    Working Directory:   h:\t

    Session type should be "OS/2 Window" (or "eCS Window") type of program.
    For the icon you can use DFS.ICO or DFSEE.ICO from the distribution ZIP
    file, or any other icon you like.

    As setup like this ("-w+") it will ask for a confirmation (are you sure)
    If you want to skip that too, just add the "-B" switch to the parameters
    and specify to start the program "minimized".


    Example to boot back to "eComStation" from the XP partition:

    In Windows (NT, W2K, XP) just create a 'shortcut' to the DFSNT.EXE program
    and specify the right parameters, example: "-w+ setboot -iba:eComStation"


    For Windows-9x you can do the same using DFSLDOS.EXE, however that also
    requires the Windows-9x reboot program DFSDOSX.EXE to be present, this
    will perform a regular Windows shutdown and reboot after the right
    bootmanager info has been set to boot into the wanted partition.

    Note that DFSLDOS does NOT support a windowed user-interface so any "-w+"
    option will be ignored, and the confirmation is a simple text message.

    From a commandline the reboot is initiated (without confirmation) using:

           DFSLDOS  -B setboot  -iba:eComStation

    To create a shortcut on the desktop that does the same (with confirmation):

    Right-click on the Desktop, select "New->Shortcut"
    In "Command line" field: "c:\tools\dfsldos.exe setboot -iba:eComStation"
    Use [Next] to select a Name, then an Icon and [Finish] ...

    Make sure DFSLDOS.EXE and DFSDOSX.EXE are in the specified directory.


34) Copy files from a damaged or inaccessible NTFS or HPFS partition

    Sometimes you loose access to NTFS files because of some kind of crash,
    a failed update or whatever.  DFSee is often still capable of finding
    files within the NTFS filesystem and copy them to another disk.

    This can be very usefull to save a few very important files before
    reinstalling or trying other recovery methods.


    DFS.EXE  -log:myproj
      part  02
      filefind  .java
      list +f   *myproj*
      recover   a: *myproj*
      q

    This will first find all filenames containing ".java" in their name
    on partition number 2 (must be NTFS or HPFS) and then list all the ones
    that also have "myproj" somewhere in the full path specification.
    Finally the same files as displayed by list are recovered by copying
    them to the diskette in A:

    The recover could use a more specific wildcard, like *myproj*dialogs*
    based on your judgement of the "list +f" output.
    You can also recover them in several groups to make the files fit on
    more than one diskette ...

    Make sure the diskette has enough space to hold all the files to recover,
    a disk-full situation will cause ungracefull failure!

    Of course you can recover to any volume (driveletter, path) that you have
    access to when running DFSee, it could be another disk-partition or a
    networkdrive or whatever ...


35) Copy files from a damaged or inaccessible HPFS or FAT partition (DIRFIND)

    This is an alternative to scenario (34) that works on HPFS and FAT and
    could be a lot faster too because it searches the directory-structures
    instead of the whole diskarea. It uses DIRFIND instead of FILEFIND.

    DFS.EXE  -log:myimages
      part  15
      dirfind  s  \  -l:*.jpg
      recover d:\images *.jpg
      q

    This will first find, then list and finally recover ALL .JPG files
    from partition 15 to the directory 'D:\images\' on driveletter D:
    Any paths (subdirectories) from the source partition 15 will be
    preserved when possible, or be replaced by unique numbers.

    Note: This requires DFSee version 4.27 or later.


36) Show (nothing but) the disk geometry for all disks

    Allthough never designed to this, some options of the 'PART' command
    can be combined to display the disk geometry for all disks, without
    showing any warnings or the complete table.

    part  -r  -w:1  -t-

    -r     = read disks and show geo
    -w:1   = show all warnings with uneven nr (none, as 1 is not used :-)
    -t-    = do NOT show the partition table display

    So, from the commandline:

    DFS.EXE  part  -r  -w:1  -t-

    Will leave you in an interactive DFSee window with the geo displayed.
    To display it and directly quit again:

    DFS.EXE  -Q  -w-  part  -r  -w:1  -t-

    That will display the geo and automatically quit.
    Or if you want it in a logfile:

    DFS.EXE  -log:geometry  -Q  -w-  part  -r  -w:1  -t-

    Will put it in 'geometry.log'

    If you want some or all warnings, check the required option in DFSCMDS.TXT,
    as an example, to show the geo and any CHS related warnings:


    DFS.EXE  part  -r  -w:chs  -t-


37) Expand an NTFS partition using DFSee and Windows 'check' (updated for 4.28)

    The scenario listed in (30) for HPFS works for NTFS as well, with some
    minor changes due to the 'other operating system' involved.
    Actually it is even easier because I found that an explicit 'check'
    operation is often not needed because Windows (XP) will do that at
    startup automatically.

    WARNING: Do NOT resize the NTFS partition you are booted from!
             I strongly advise to use the OS/2 version, or the DOS version
             DFSDOS.EXE from a DOS bootdiskette (requires 700 Kb free mem)

    a) Make some freespace AFTER your NTFS partition (using DFSee delete)
    b) Wipe this freespace to all binary zeroes (to avoid garbage info)
    c) Delete the NTFS partition, and create it again in the same place
       but with a larger size. (using the freespace from step a)
    d) Use the 'RESIZE -max' command to update the NTFS internal size info
    e) Reboot to Windows (tested with XP, bit NT and and W2K should be OK too)
    f) Run the 'check' option on the partition in the 'disk management' tool.
       I found that this step was not really needed, but it can't hurt and
       you can see if the partition is healthy after the resize.

    Of course the alternative as outlined in scenario (30) with using a newly
    created partition and CLONE works too, it is just a different way to get
    that larger partition-table entry for the filesystem to be resized.

    Note: I am not sure if there is a limit to how much you can expand your
          NTFS partition. I have tested a 4Gb NTFS data partition, and resized
          that succesfully to 6Gb. The resulting filesystem was accessible by
          the XP operating system. I will run another test expanding a bootable
          Windows-XP that is now 3.5 Gb to take up 7Gb ...

          Version 5.xx of DFSee will probably integrate some of the steps above
          to get a more user-friendly 'RESIZE' with a minimal nr of steps.

