Using a DFSee ISO file to create a bootable CDROM or USB stick
--------------------------------------------------------------

To verify the integrity of the ISO file, you can use the
MD5 check that is provided in the ZIP file. Compare the
contents of the .MD5 file with the results of running
the 'md5suml.exe' tool against the ISO file.
The tools can be downloaded from HOBBES:

   http://hobbes.nmsu.edu/pub/os2/util/encrypt/md5suml.zip

The output should be very similar to this 11.1 example:

   C464-B6DD-3F3D-4480-3C33-C2CF-E439-B734 dfsee11x.iso


Note:
When using the 'dfsee11x.iso', or the (much smaller) stripped
down ISO file for the bootable USB stick 'dfsee11x_stick.iso',
first rename it to the standard 'dfseedos.iso' name since that
is how it is referenced from the default PenDriveLinux bootmenu
that is on the stick as created by DFSee. You can use either
the full (large) ISO or the stripped down one, since only its
boot-image wil be used to run DFSDOS with FreeDOS.



Personalize your ISO image with key and default values
------------------------------------------------------

Do NOT burn the ISO file to CD, or copy it to a USB stick unmodified!
It will ONLY work for a very short evaluation period from the release
date, until you have added your own registration 'dfsee.key' to it!

Step 1: Add your key to the image

a- Copy your'dfsee.key' file to the same directory as the ISO

b- Add the key using:

   IKEYxxx dfsee11x.iso

   The IKEY program should be run from the operating system
   commandline for best results (and seeing the results :-)
   It should report at least 6 keys being replaced by yours ...
   (for the full ISO, for the stripped down one there are 2)

For xxx substitute the DOS, OS2 or WIN version as appropriate
for the operating system that you are running to update the ISO.
For Linux the IKEYxxx program is just called 'ikeyiso' without
a file extension, and the MAC version is called 'ikeymac'.

Note:
If you did not receive the 'dfsee.key' as a seperate file but
as part of a larger file or email, you can create it yourself:

+++++
Just put the line "DFSreg='.........'" into a file of its own, and
call it 'dfsee.key' Make sure the single quotes are kept in place.

One way to do that is mark the line in the file or email and copy
it to the clipboard, then start a NEW empty file in an editor like
the OS/2 Enhanced Editor, and paste in the line from the clipboard.

It does not even matter if there is more (garbage) in the file,
as long as the "DFSreg=" starts at the begin of the file.
+++++


Step 1a: Change the KEYBOARD setting for the CD boot
         from the default 'us' to another language (OPTIONAL!)

   IKBDxxx dfsee11x.iso  XX

   Where the 'XX' is a language code like 'gr', 'fr' etc.
   For a complete list, use 'IKBDxxx -?'


Step 1b: Change the MENUDEFAULT for the FreeDOS based CD boot menu
         from the default '1' in the full ISO, or '0' in the
         striped-down ISO to another selection (OPTIONAL!)

   IMDFxxx dfsee11x.iso  M

   Where the 'M' is a menu default selection in the range 0 .. 9:

   1 - Load Universal IDE driver  - FAST   - best for most systems
   2 - Use standard BIOS-driver   - STABLE - Press "2" to select
   3 - Automatic analysis of partition-table problems for all disks
   4 - Automatic analysis for all partitions recognized by DFSee
   5 - Automatic analysis of BOOT.INI on all FAT and NTFS partitions
   6 - Run a (recovery) script from diskette
   7 - Add USB access support, and use Universal IDE driver - FAST
   8 - Add USB access support, but use standard BIOS driver - STABLE
   9 - USB floppy boot; allow swap USB device to use for DFSee files
   0 - Boot from USB (stick), then use it as DFSee file storage too


Step 1c: Change the PROFILE.DFS in the ISO with a customized version
         Note: This is an OPTIONAL step, you only need it if you want
               to do something special, like setting a color scheme.
               Your replacement MUST be 512 bytes or less in size.

   IKEYxxx dfsee11x.iso  mystuff.dfs  ;DFSee:'profile'

   Where the 'mystuff.dfs' is your customized profile, the contents
   of which will be put into the 'profile.dfs' file in the ISO.


Step 2a: Copy the ISO to a bootable USB stick, prepared with DFSee
This step will put the customized ISO onto a bootable USB-stick.

First prepare that stick fromthe DFSee 'Actions' menu as described
in 'dfsusb32.txt' that comes with DFSee itself. This should result
in a stick that boots to the ISO-selection menu, but of course
fails to complete booting since there ar no ISO files on the stick.

Just copy your prepared ISO file to the root of the USB stick
as 'dfseedos.iso'. This name is mandatory since it is referenced
from the menu.lst on the stick.



Step 2b: Burn the ISO to a CDR, resulting in a bootable CDROM

This step depends on the burning software you are using.
Check the documentation of your software to find out how
to use the ISO image to create a CD.

Do NOT just copy the ISO file to a CDROM like any other file,
that will NOT work, it will result in a CDROM with the ISO
file on there :-)

In general, use a LOW writing speed, the DFSee image is not
very large anyway, and burning an ISO at high speeds yields
unreliable results on many systems ...


For using the RSJ or CDRECORD packages on OS/2 or eCS the
procedure is described below. For other operating systems
or burning software it will be similar ...



Burning an ISO using RSJ
------------------------

Using the graphical drag&drop method with CDVIEW, procedure is:

1- Open RSJ Desktop folder
2- Open CDView Folder
3- Double-click "CD Recorder" application within
4- Open folder containing the unzipped ISO file
   (e.g. D:\downloads\dfsee\dfsee*.iso)
5- Drag ISO file to visible "CD View [CDR:]" Window
6- Record to CD-R/CD-RW    (big red dot on toolbar)
7- Finalize CD             (CDROM image on toolbar)
---------------- to test/verify ------------------
8- Shutdown and reboot with CD-ROM as first BOOT-option
9- System *should* be up and running DFSDOS.
-------------------------------------------------------

Using the commandline version TRACKCPY.EXE, it would be something like:

trackcpy -speed 8 -copy D:\dfsee11x.iso 1 CDR:0.0 -finalize CDR:0.0 -eject CDR:0.0 -quit

It is MANDATORY to specify the full drive+path+filename for the ISO!
The device name (here CDR:0.0) depends on your hardware configuration,
the first number is the (simulated) SCSI-bus and the second the SCSI
device name on that bus. If you have a single drive, use just "CDR:"

On my system CDR:0.0 is the master on the 2nd IDE channel and
CDR:1.1 is the slave on that same channel.

You can use 'cdrecord -scanbus | find "CD"' to find the numbers.

On my system this reports:

++++++++++
0,0,0     0) 'ATAPI   ' 'CD-ROM 52X      ' '172A' Removable CD-ROM
1,1,0   101) 'DVDRW   ' 'IDE1004         ' '0048' Removable CD-ROM
++++++++++

So the RSJ device numbers x.y are the first two numbers reported.


You can also use the info displayed by DANIS506.ADD using the /V
switch in config.sys, or from 'COPY IBMS506$ con:'

As an example for my Thinpad T42 with the CDRW/DVDRW in the Ultrabay:

++++++++++ Copy IBMS506 output => writer on controller 1, unit 0
Controller:1  Port:0170 IRQ:0F  Status:OK BusMaster Scatter/Gather
  Intel ICH4 PATA host (8086:24CA rev:01) on PCI 0:31.1 @33MHz
 Unit:0 Status:OK ATAPI BusMaster UltraDMA2/PIO4
  Model:MATSHITADVD-RAM UJ-812                  K104
++++++++++

So on that system the RSJ device string is "CDR:1.0"
For an example 'BURNISO.CMD' for OS2, see below

++++++++++ Sample BURNISO.CMD for RSJ on OS2 or eComStation
@echo off
if "%1"=="" goto usage
if "%2"=="" goto burner
set burner=%2
goto isocopy

REM set burner to default (single DVD-writer on Thinkpad T42)
:burner
set burner=CDR:

:isocopy
echo.
echo About to burn ISO file: '%1' to burner: '%burner%'
echo Make sure an empty CDR is in the drive, and press ENTER ...
pause > NUL
echo.
trackcpy -speed 8 -copy %1 1 %burner% -finalize %burner% -eject %burner% -quit
goto end

:usage
echo.
echo Usage %0  filename  [device]
echo.
echo    filename = name of ISO imagefile to be burned to CDROM
echo               This MUST be a full drive+path+filename !!!
echo.
echo    device   = RSJ devicename for the burner: 'CDR:bus.dev'
echo               Default is a DVDRW on my Thinkpad: 'CDR:'
echo.
echo               Devices can be listed using 'cdrecord -scanbus'
echo.              or seen from 'COPY IBMS506$ con:' output
echo.

:end
++++++++++




Burning an ISO using CDRECORD
-----------------------------

Using the graphical front-end (CDARECORD ?) on OS2, the procedure is:

1.  Open CDRECORD - Create Data CD
2.  Check Write image and uncheck Test only
3.  Under imagename, enter fully qualified path name for the image file;
    OR select Browse, check if the *.iso mask is in the filter already,
    otherwise change the filter from *.raw  to *.iso, and select the image
4.  Click write CD, and then select the writer and writing speed (LOW!)


Using the commandline version directly, it would be something like:

    cdrecord.exe -v dev=1,0 speed=16 dfsee11x.iso

Where you might have to change the device from 1,0 to whatever
device numbers your burner is located, and the speed to the
maximum speed your media and burner support reliably.
To find the device numbers, you can use:

    cdrecord.exe -scanbus | find "CD"

On my system this reports:

++++++++++
0,0,0     0) 'ATAPI   ' 'CD-ROM 52X      ' '172A' Removable CD-ROM
1,1,0   101) 'DVDRW   ' 'IDE1004         ' '0048' Removable CD-ROM
++++++++++

So the actual CDRECORD command that works on my system, is:

    cdrecord -v dev=1,1,0 speed=8 dfsee11x.iso

For a Thinkpad with writer in the Ultrabay, it would be

    cdrecord -v dev=1,0,0 speed=8 dfsee11x.iso

