COMMAND-LINE EXAMPLES...
SCRAMDISK KEY-BLOCK UTILITY, SCD v1.21


Run SCD.exe from a floppy, Zip-Disk, another SD container, or from anywhere on your hard-drive by using the Start/Run command line, or a *.bat (batch) file

Usage:

       scd Remove|Merge [path]scd_file [path]block_file offset
       scd Xor [path]scd_file [path]mask_file offset
       scd Compare [path]scd_file1 [path]scd_file2 max_offset
              Offset range is 0x2000-0x5000


Example:

       scd r "C:\Program Files\Scramble.svl" a:Scramble.skb 0x2800
       scd m scramble.svl a:\scramble.skb 0x2800
       scd x c:\progra~1\scramble.svl d:\dog.jpg 0x2400
       scd c \temp\scramble.svl e:\erfssw 0x4444


MORE...Removing/merging the keyblock of a container:

   A...removes key-block from file1 and saves it as file2...
       scd r file1 file2 0x26FF
   B...merges the block back...
       scd m file1 file2 0x26FF
   C...from hd folder to the a:\ drive...
       scd r "c:\program files\data.svl" a:data2.svl 0x26FF
   D...merges from floppy to hd
       scd m "c:\program files\data.svl" a:data2.svl 0x26FF


NEW...One-time-keypad encryption...
masking the keyblock with XOR:


This is an interesting alternative to the removal of the block, and involves overwriting the key-block with a portion of another file in a XOR operation. As long as the same file is never used twice to mask the key-block, this method is very secure. This is the equivalent of the "console lock-out" feature of the updated DriveCrypt in practice; but on an individual per-file basis; and works with every SD version up to and including DriveCrypt....plus E4M.

Use a text file as a "scd_file" to examine and visualize the changes. Repeat the X command to re-enable your Scramdisk container.

Example using a jpg on another drive as a key-file:

     scd x c:\progra~1\scramble.svl d:\dog.jpg 0x2400

An AOL installation disk, your Win95/98/ME/2k installation disks, a cdr full of mp3’s, or any other such archived media are readily available sources for key-files :) .

CAUTION!

In order to avoid data loss when updating your containers, you must not disturb any part of the data portion of your target container when removing/merging or masking the key-blocks. Certain destruction of your container will be the result if you slip up on this. Make sure that just the key-block, or a substantial portion of it, is the ONLY thing altered in the container. You can estimate the correct offsets for your own containers key-blocks with the aid of SCD's new Compare function, or your favourite hex editor. Take great care at this stage, and work with copies, if possible, until you get familiar with the procedure.