Registry query relating to third-party product

A program I use on a daily basis in my work as a translator imports
files for translation and exports the translated files.

By default, the program uses the export path from the previous project
for the current project.

This suits some users, but others find it a pain in the neck.
Unfortunately the developers have so far resisted all calls to make the
export path setting more flexible.

It would appear that the export path is stored in a parameter called
LastExportPath.

Another registry parameter for this program is LastProjectPath, and it
would appear that this is the path I would want as the default export path.

I don't really know anything about the finer details of how the registry
works, but I wonder whether it might somehow be possible to overwrite
LastExportPath with LastProjectPath when a new project is created, so
that the export path is automatically set to the current path rather
than the previous one?

Or, dare I ask, what would happen if one was bold enough to delete the
LastExportPath parameter?

Herbert Eppel
www.HETranslation.co.uk

Another contributor may be able to provide a specific answer to
the problem. If not, you could try the following, as an
experiment:

1. Create a System Restore Point (just in case the subsequent
steps go pear-shaped)

2. Click on Start / Run - and type regedit. Click OK

3. Scroll down to through the registry until you come to
"LastExportPath".

4. Select the Key and click on File / Export . Save the
resulting Registry Entry to your desktop. You will need to give
a name to the *.reg file.

5. Also, export the "LastProjectPath" key.

6. Then, try amending the data in "LastExportPath". Or, you
could try deleting the data or the value, or the entire key.

7. You could also experiment with "LastProjectPath"

Having edited the registry, run the program, to discover the
effect of the various changes.

If you can't find a registry amendment that resolves your
problem, double click on the *reg files on your desktop - to
restore the original entries to the registry.



"Herbert Eppel" HE@UK wrote in message
...
A program I use on a daily basis in my work as a translator
imports files for translation and exports the translated files.

By default, the program uses the export path from the previous
project for the current project.

This suits some users, but others find it a pain in the neck.
Unfortunately the developers have so far resisted all calls to
make the export path setting more flexible.

It would appear that the export path is stored in a parameter
called LastExportPath.

Another registry parameter for this program is LastProjectPath,
and it would appear that this is the path I would want as the
default export path.

I don't really know anything about the finer details of how the
registry works, but I wonder whether it might somehow be
possible to overwrite LastExportPath with LastProjectPath when
a new project is created, so that the export path is
automatically set to the current path rather than the previous
one?

Or, dare I ask, what would happen if one was bold enough to
delete the LastExportPath parameter?

Herbert Eppel
www.HETranslation.co.uk

Hi Bob

Thanks for your reply.

I don't seem to be able to export individual keys from the registry,
only whole branches.

In any case, rather than modifying the actual key(s), I was thinking of
some mechanism that would automatically overwrite LastExportPath with
LastProjectPath as soon as I have created a new project, but I'm really
just speculating without having much of an idea of how the registry
actually works.

Herbert Eppel
www.HETranslation.co.uk

On 17.09.2009 14:09 UK Time, Bob Lucas wrote:
Another contributor may be able to provide a specific answer to the
problem. If not, you could try the following, as an experiment:

1. Create a System Restore Point (just in case the subsequent steps
go pear-shaped)

2. Click on Start / Run - and type regedit. Click OK

3. Scroll down to through the registry until you come to
"LastExportPath".

4. Select the Key and click on File / Export . Save the resulting
Registry Entry to your desktop. You will need to give a name to the
*.reg file.

5. Also, export the "LastProjectPath" key.

6. Then, try amending the data in "LastExportPath". Or, you could
try deleting the data or the value, or the entire key.

7. You could also experiment with "LastProjectPath"

Having edited the registry, run the program, to discover the effect of
the various changes.

If you can't find a registry amendment that resolves your problem,
double click on the *reg files on your desktop - to restore the original
entries to the registry.



"Herbert Eppel" HE@UK wrote in message
...
A program I use on a daily basis in my work as a translator imports
files for translation and exports the translated files.

By default, the program uses the export path from the previous project
for the current project.

This suits some users, but others find it a pain in the neck.
Unfortunately the developers have so far resisted all calls to make
the export path setting more flexible.

It would appear that the export path is stored in a parameter called
LastExportPath.

Another registry parameter for this program is LastProjectPath, and it
would appear that this is the path I would want as the default export
path.

I don't really know anything about the finer details of how the
registry works, but I wonder whether it might somehow be possible to
overwrite LastExportPath with LastProjectPath when a new project is
created, so that the export path is automatically set to the current
path rather than the previous one?

Or, dare I ask, what would happen if one was bold enough to delete the
LastExportPath parameter?

Herbert Eppel
www.HETranslation.co.uk

I suggested you should export registry content, to facilitate
restoration of the previous entries, if you encounter problems.
Registry changes are not for the faint hearted - so don't edit
the registry, if you cannot export the relevant entries.

If you can't export individual keys, then an export of the entire
branch will serve the same purpose. Better to export too much
than too little. I can't tell you what changes you should make
to individual keys in the registry. Deletion of the relevant key
or keys might do the trick - or might prevent the program from
working. (That is why you must export the registry entries,
before you change anything).

However, I am not aware of any way that you, as end-user, might
configure the registry to overwrite previous entries
automatically. I suspect the developers would need to
incorporate your requirements in a program update.


"Herbert Eppel" HE@UK wrote in message
...
Hi Bob

Thanks for your reply.

I don't seem to be able to export individual keys from the
registry, only whole branches.

In any case, rather than modifying the actual key(s), I was
thinking of some mechanism that would automatically overwrite
LastExportPath with LastProjectPath as soon as I have created a
new project, but I'm really just speculating without having
much of an idea of how the registry actually works.

Herbert Eppel
www.HETranslation.co.uk

On 17.09.2009 14:09 UK Time, Bob Lucas wrote:
Another contributor may be able to provide a specific answer
to the problem. If not, you could try the following, as an
experiment:

1. Create a System Restore Point (just in case the
subsequent steps go pear-shaped)

2. Click on Start / Run - and type regedit. Click OK

3. Scroll down to through the registry until you come to
"LastExportPath".

4. Select the Key and click on File / Export . Save the
resulting Registry Entry to your desktop. You will need to
give a name to the *.reg file.

5. Also, export the "LastProjectPath" key.

6. Then, try amending the data in "LastExportPath". Or,
you could try deleting the data or the value, or the entire
key.

7. You could also experiment with "LastProjectPath"

Having edited the registry, run the program, to discover the
effect of the various changes.

If you can't find a registry amendment that resolves your
problem, double click on the *reg files on your desktop - to
restore the original entries to the registry.



"Herbert Eppel" HE@UK wrote in message
...
A program I use on a daily basis in my work as a translator
imports files for translation and exports the translated
files.

By default, the program uses the export path from the
previous project for the current project.

This suits some users, but others find it a pain in the neck.
Unfortunately the developers have so far resisted all calls
to make the export path setting more flexible.

It would appear that the export path is stored in a parameter
called LastExportPath.

Another registry parameter for this program is
LastProjectPath, and it would appear that this is the path I
would want as the default export path.

I don't really know anything about the finer details of how
the registry works, but I wonder whether it might somehow be
possible to overwrite LastExportPath with LastProjectPath
when a new project is created, so that the export path is
automatically set to the current path rather than the
previous one?

Or, dare I ask, what would happen if one was bold enough to
delete the LastExportPath parameter?

Herbert Eppel
www.HETranslation.co.uk

Herbert Eppel wrote:

A program I use on a daily basis in my work as a translator imports
files for translation and exports the translated files. By default,
the program uses the export path from the previous project for the
current project. This suits some users, but others find it a pain in
the neck. Unfortunately the developers have so far resisted all calls
to make the export path setting more flexible.

It would appear that the export path is stored in a parameter called
LastExportPath. Another registry parameter for this program is
LastProjectPath, and it would appear that this is the path I would
want as the default export path.
snip

Rather than try to subvert the program's settings in the registry, why
not create a reparse point (junction) in the file system to replace the
program's targeted path? You must be using NTFS to use junctions. See:

http://en.wikipedia.org/wiki/Junction_point

Create the new target folder. Move the files there from the old folder.
Delete the old folder. Create a junction that looks like it is the old
folder but points to the new folder. Any file I/O that goes to the old
folder hits the junction and goes to the new folder.

Except for server versions of Windows, Microsoft doesn't provide any
tools for creating junctions. You can get some free utilities that help
you create junctions, like Redenwonder's Junction Link Magic (free); see
http://www.rekenwonder.com/linkmagic.htm.

Just be warned that you could end up doubling the files in your backups:
one copy of the files for the physical folder when it is found at its
real location, and another copy when the backup program hits the
junction to follow it to backup the same files again. Check if your
backup solution ignores junction points.

Also, it is possible a program uses direct calls to the device to
perform file operations rather than use the system API calls for file
I/O, but it is unlikely unless you are using a low-level utility that
directly accesses the drive.

Thanks for your further reply.

I'm might try deleting the key if I feel brave enough one day :-)

Herbert Eppel
www.HETranslation.co.uk

On 17.09.2009 18:44 UK Time, Bob Lucas wrote:
I suggested you should export registry content, to facilitate
restoration of the previous entries, if you encounter problems. Registry
changes are not for the faint hearted - so don't edit the registry, if
you cannot export the relevant entries.

If you can't export individual keys, then an export of the entire branch
will serve the same purpose. Better to export too much than too
little. I can't tell you what changes you should make to individual
keys in the registry. Deletion of the relevant key or keys might do the
trick - or might prevent the program from working. (That is why you
must export the registry entries, before you change anything).

However, I am not aware of any way that you, as end-user, might
configure the registry to overwrite previous entries automatically. I
suspect the developers would need to incorporate your requirements in a
program update.


"Herbert Eppel" HE@UK wrote in message
...
Hi Bob

Thanks for your reply.

I don't seem to be able to export individual keys from the registry,
only whole branches.

In any case, rather than modifying the actual key(s), I was thinking
of some mechanism that would automatically overwrite LastExportPath
with LastProjectPath as soon as I have created a new project, but I'm
really just speculating without having much of an idea of how the
registry actually works.

Herbert Eppel
www.HETranslation.co.uk

On 17.09.2009 14:09 UK Time, Bob Lucas wrote:
Another contributor may be able to provide a specific answer to the
problem. If not, you could try the following, as an experiment:

1. Create a System Restore Point (just in case the subsequent
steps go pear-shaped)

2. Click on Start / Run - and type regedit. Click OK

3. Scroll down to through the registry until you come to
"LastExportPath".

4. Select the Key and click on File / Export . Save the resulting
Registry Entry to your desktop. You will need to give a name to the
*.reg file.

5. Also, export the "LastProjectPath" key.

6. Then, try amending the data in "LastExportPath". Or, you could
try deleting the data or the value, or the entire key.

7. You could also experiment with "LastProjectPath"

Having edited the registry, run the program, to discover the effect
of the various changes.

If you can't find a registry amendment that resolves your problem,
double click on the *reg files on your desktop - to restore the
original entries to the registry.



"Herbert Eppel" HE@UK wrote in message
...
A program I use on a daily basis in my work as a translator imports
files for translation and exports the translated files.

By default, the program uses the export path from the previous
project for the current project.

This suits some users, but others find it a pain in the neck.
Unfortunately the developers have so far resisted all calls to make
the export path setting more flexible.

It would appear that the export path is stored in a parameter called
LastExportPath.

Another registry parameter for this program is LastProjectPath, and
it would appear that this is the path I would want as the default
export path.

I don't really know anything about the finer details of how the
registry works, but I wonder whether it might somehow be possible to
overwrite LastExportPath with LastProjectPath when a new project is
created, so that the export path is automatically set to the current
path rather than the previous one?

Or, dare I ask, what would happen if one was bold enough to delete
the LastExportPath parameter?

Herbert Eppel
www.HETranslation.co.uk

On 17.09.2009 22:42 UK Time, VanguardLH wrote:
Herbert Eppel wrote:

A program I use on a daily basis in my work as a translator imports
files for translation and exports the translated files. By default,
the program uses the export path from the previous project for the
current project. This suits some users, but others find it a pain in
the neck. Unfortunately the developers have so far resisted all calls
to make the export path setting more flexible.

It would appear that the export path is stored in a parameter called
LastExportPath. Another registry parameter for this program is
LastProjectPath, and it would appear that this is the path I would
want as the default export path.
snip

Rather than try to subvert the program's settings in the registry, why
not create a reparse point (junction) in the file system to replace the
program's targeted path? You must be using NTFS to use junctions. See:

http://en.wikipedia.org/wiki/Junction_point

Create the new target folder. Move the files there from the old folder.
Delete the old folder. Create a junction that looks like it is the old
folder but points to the new folder. Any file I/O that goes to the old
folder hits the junction and goes to the new folder.

Except for server versions of Windows, Microsoft doesn't provide any
tools for creating junctions. You can get some free utilities that help
you create junctions, like Redenwonder's Junction Link Magic (free); see
http://www.rekenwonder.com/linkmagic.htm.

Just be warned that you could end up doubling the files in your backups:
one copy of the files for the physical folder when it is found at its
real location, and another copy when the backup program hits the
junction to follow it to backup the same files again. Check if your
backup solution ignores junction points.

Also, it is possible a program uses direct calls to the device to
perform file operations rather than use the system API calls for file
I/O, but it is unlikely unless you are using a low-level utility that
directly accesses the drive.

Thanks for your reply.

I think this sounds a bit too complicated for my rudimentary IT skills,
so I think I'll just have to keep pasting the required path into the
program's export path box :-(

Herbert Eppel
www.HETranslation.co.uk