DBE‎ > ‎

Addenda


DBE RELEASE NOTES FROM 11-16-10


NEWER NOTES ARE AT THIS LINK

The Options SetID has been modified so that, in the event that you should accidentally modify the DiskID file present on a disk, the file's doubleword time stamp will be reset to the binary representation of the radix-36 ID field in the filename, if this is feasible.  This equivalence is necessary for unique disk identification by DBE; and if you find that DBE is creating any extra disk identifiers on a particular disk, you should press OS and then the drive letter for the drive containing that disk.  (This may occur in some versions of DBE without your having modified the ID file; probably due to the fact that DBE creates a timestamp from the local system time, calculates the radix-36 string representation of it, creates an ID file and sets the time stamp, checks the file's doubleword time stamp and calculates a check radix-36 string from it, and then renames the ID file to contain the latter ID field if they don't match.)  The Options SetID procedure now simply checks for a DiskID file, and using the first qualified entry which it finds, extracts the radix-36 ID field from the filename and calculates the binary doubleword time stamp from it.  Then it updates the disk file's time stamp to this value, so that the DiskID will be the same and its radix-36 ID field will match the calculated value.  Be aware that creating an arbitrary DiskID file yourself for a disk may not work because the binary file timestamp created from the filename must be a valid YYMMDDHHMMSS doubleword in which SS=seconds/2, and if this condition is not met, the result may be unpredictable (This is why DBE performs the additional step, when it creates a DiskID, of checking the file timestamp and renaming the file if necessary).

This change represents the only change in the operation of DBE.EXE between the 11-10-2010 and 11-16-2010 builds.  (See also:  Addenda 2: 11-16-10 Continued)

11-10-10:

DBE's Level List tracking and LFN directory name transfer have been upgraded.

Buffered file counts to date were being missed on exit from DBE for file Entries in Levels which were added to the list preceding the last flagged FirstEntry location. This has only been corrected for explicit AltB pre-buffering of files; and further changes may be made at the Scan point if it can be done without slowing down disk reads, in order to track the FirstEntry location with every possible change.

Discovery yesterday that creation of new LFN's for target directories during SubsScope copy operations was not being carried out (DOS filenames were being used to form the longfilename entries for the new directory names) necessitated changing the state of a BOOLEAN variable in the directory-name-copy procedure and adding an additional checkpoint for LFNs. This did not impact the file longfilenames. Up until today, only explicit directory LFN creation at the time a target is assigned was being carried out. (LFN directory name transfer during buffering may still work in spite of this.) During buffering, the file longfilenames are stored, and code is in place to implement this for directories, although it may not be called; so this might require further changes.



DBE CORRECTIONS AND NOTES AS OF 09-24-10



DISK SCAN FILE SPECIFICATION

  DBE v4.3N+
  Documentation supplied (up to 09-23-10) in DBX.D0C

  The behavior of keys F7, F8, RC, RF, RS in previous versions of DBE.EXE
  prior to DBE v4.3 is described in DBX.D0C correctly.  The documentation
  was not updated as of this date to reflect changes in this behavior for
  newer versions of DBE up to and including DBE v4.4O.

  These keys no longer allow you to enter an independent scan specification
  which has no effect on the default one entered previously.  These keys
  now use the previously entered default scan specification only as default,
  and the pattern entered when using the R CFS scans now sets a new default.

Levels - SelectDisk OPTION

  DBE v4.3N+
  Documentation supplied (up to 09-23-10) in DBX.D0C

  The behavior of keys ',' and '.' while the SelectDisk window is active in
  previous versions of DBE.EXE prior to DBE v4.3 is described in DBX.D0C
  correctly.  The documentation was not updated as of this date to reflect
  changes in this behavior for newer versions of DBE up to and including DBE
  v4.4O.

  These keys now move the selection bar up and down by one item, and do not
  skip past levels which are empty as they did previously.

FIND | AGAIN

  DBE v4.3N+
  Documentation supplied (up to 09-23-10) in DBX.D0C

  An inaccurate statement is made describing the number of key presses needed
  to select from the input box.  This should read as follows:

  "Only a single keypress is needed for numbers greater than 2.  For 1 or 2
  only a single keypress is needed when the number of search items is less
  than 10 or 20, respectively."

JUMP | MARKERS | TARGETS | CYCLES

  DBE v4.3N+
  Documentation supplied (up to 09-23-10) in DBX.D0C

  The behavior of the ShiftTab key in previous versions of DBE.EXE prior to
  DBE v4.3 is described in DBX.D0C correctly.  The documentation was not
  updated as of this date to reflect changes in this behavior for newer
  versions of DBE up to and including DBE v4.4O.

  The motivation for the ShiftTab functionality described led to inclusion
  of a new feature, the MRU Entry list, in DBE 4.4O, and in other versions
  as well since v4.3 this ShiftTab functionality was reduced as follows:

  ShiftTab no longer adds new jump points to a cyclic ring of entries.
  It returns to the first valid item added to the Entry list at startup.

  The previous functionality of ShiftTab as described in DBX.D0C is not at
  this time tied to a keypress, but may again be in future versions
  subsequent to DBE v4.4O.


GO/PROCESS FILE OPERATIONS


  DBE v4.3N+
  Documentation supplied (up to 09-23-10) in DBX.D0C

  The example of the DBE display included in the DBX.D0C file is correct for
  versions prior to DBE v.4.3N but has not been updated for later versions.

  Two changes in the keypresses were made so that the user may press
  the 'N' key twice instead of 'CN' when advancing to the next entry without
  removing the current one from the processing list or causing it to be
  ignored:

  'N' for "COPY SOURCE TO NEW NAME" has been replaced by
  'F' for "COPY SOURCE TO NEW FILENAME"

  'C' for "COPY NEXT FILE" has been replaced by
  'N' for "COPY NEXT FILE"

  In addition to this, the behavior of the RC key sequence with respect to
  the resetting of entry status flags in previous versions of DBE.EXE prior
  to DBE v4.3 is described in DBX.D0C correctly.  The documentation was not
  updated as of this date to clarify the remarks made concerning this topic.

  The <Written> status flag is the only active flag displayed for new entries
  added to the list during copying or moving files, and only the FileStatus
  indicator, which can have the values <Replace>, <Copied>, or <FileOK>,
  is affected by the RC key sequence.  The documentation states,

    ..."the file status will be reset for the new/updated files,
        and they will appear in their normal colors."

  This statement is still correct, but fails to mention that the <Replace>
  or <Copied> status indicators are changed to <FileOK> by the RC key
  sequence, and that the ';' key does not change this status, so that it
  can be used to scan levels containing entries with active source links
  without untagging entries having REPLace tags set.  Using RC means that
  you have to manually retag all <Replace> candidates by pressing 'X' for
  each one.




Comments