Done multi-job access

[Roedy]

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.

 

[rconn]

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.

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.

 

[Steve Fabian]

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

 

[rconn]

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

*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).

 

[Steve Fabian]

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