1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

multi-job access

Discussion in 'Suggestions' started by Roedy, May 16, 2009.

  1. Roedy

    Joined:
    Jun 8, 2008
    Messages:
    120
    Likes Received:
    2
    The C:\Users\user\AppData\Local\JPSoft\jpstree.idx is essentially the same as it was in DOS days, as is the DESCRIPT.ION file mechanism.

    There are three problems.

    1. A BAT file tends to lock jpstree.idx preventing other BAT files from running.

    2. file copies of many small files are quite slow, since each copy requires reading and writing the entire descript.ion file. ditto for each describe command.

    3. Copying to DVD should wait until the entire descript.ion file is ready before copying it.

    It may be time to put this data in a little database, or possibly cached in RAM managed by a central background process. That way different bat files will not interfere with each other. You could then index the heck out of the directory tree for even faster access.
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,726
    Likes Received:
    80
    The DESCRIPT.ION file is obsolete and only maintained for backwards compatibility. I recommend switching to the NTFS descriptions, which are (1) faster, and (2) will be copied or moved by all apps, not just those few that are DESCRIPT.ION-aware.
     
  3. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,523
    Likes Received:
    4
    rconn wrote:
    | The DESCRIPT.ION file is obsolete and only maintained for backwards
    | compatibility. I recommend switching to the NTFS descriptions, which
    | are (1) faster, and (2) will be copied or moved by all apps, not
    | just those few that are DESCRIPT.ION-aware.

    How do they work when creating a back-up on CD, DVD, SD cards, etc., which
    are not NTFS? The DESCRIPT.ION file works with all media.
    --
    Steve
     
  4. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,726
    Likes Received:
    80
    *Provided* you do all of your file i/o in TCC. As soon as you use anything else the DESCRIPT.ION file isn't updated (and is sometimes lost).
     
  5. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,523
    Likes Received:
    4
    rconn wrote:
    | ---Quote (Originally by Steve Fábián)---
    | rconn wrote:
    || The DESCRIPT.ION file is obsolete and only maintained for backwards
    || compatibility. I recommend switching to the NTFS descriptions, which
    || are (1) faster, and (2) will be copied or moved by all apps, not
    || just those few that are DESCRIPT.ION-aware.
    |
    | How do they work when creating a back-up on CD, DVD, SD cards, etc.,
    | which
    | are not NTFS? The DESCRIPT.ION file works with all media.
    | --
    | Steve
    | ---End Quote---
    |
    | *Provided* you do all of your file i/o in TCC. As soon as you use
    | anything else the DESCRIPT.ION file isn't updated (and is sometimes
    | lost).

    Sorry, my question was not clear. What happens when NTFS streams are used
    for descriptions, and the directory is backed up - using TCC - to a non-NT
    file system, e.g., thumb drive, SD card, optical media, etc.?

    BTW, is it possible to describe directories and junctions / symbolic links
    when using NTFS streams for descriptions?
    --
    Steve
     

Share This Page