|
Read through this information before using Application
Mover for the first time!!
Most Important
-
Most Important: Do not move paths (folders) that contain un-related program(s) underneath that parent path. For example, DO NOT move C:\Program Files to D:\Program
Files. Moving C:\Program Files\Editor to F:\Program Files\Editor is OK, where "Editor" is the name of a
program you have. But don't try moving all of C:\Program Files at once!. Plus, there are some paths in C:\Program Files
we recommend you not move.
-
Others You Should NOT Move:
- Paths directly related to
your operating system. Application Mover cannot be used to relocate a windows
installation. For example, do not try to move C:\Windows to D:\Windows!!
- Do not move any folders underneath your 'Windows' path. For example, don't move C:\Windows\System!!
- Do not move C:\Program Files\Common Files. Folders under this path is used by many programs and files there will be
probably be "busy". If you know what you are doing you can possibly move specific paths under C:\Program Files\Common Files, one at a
time. But in general we suggest you leave things be when it comes to C:\Program Files\Common Files.
-
We do not recommend moving highly complex programs such as Microsoft Office. Programs like MS Office install files in many different subdirectories and make hundreds (even
thousands) of registry entries. We have successfully moved components of MS
Office ourselves but we do not support this.
-
Do not move Norton System Works. By report, System Works may
come along after Application Mover and try to "correct" some registry
changes that Application Mover makes. Follow Symantec/Norton recommendations if you need to move System Works.
-
By report, moving Quicken may be problematic. Symptoms are that files are left behind after the
move. We have not been able to
repeat this ourselves so we do not know if this is because users ignored the "Some files are busy, reboot now?" prompt after
Application Mover was finished. Still, caution is advised.
-
Do not move the path Application Mover itself is in. If you need to relocate Application Mover, uninstall and
reinstall.
Logging and Backups
-
Please use the Log File feature. This is the "Log changes made to output file" setting in the main dialog. The info
may be helpful if something goes wrong.
-
Back up all data files associated with your program before you use
Application Mover. By this we mean any document collections, databases, and/or
data paths that are used by your program to store whatever information it is
your program is used for. Application Mover has been tested extensively but you
should update your backups first. You do have recent backups, right?
Before You Move Anything
-
Close all running programs before you run Application Mover. Most important,
close program(s) directly or indirectly related to the Current Path and New Path fields in the Application Mover main dialog. If you are
not sure about what this means, close all programs so that your Windows taskbar
is clear.
-
If you complete the Current Path and New Path
fields by hand in the main dialog be sure to specify only
subdirectory (folder) names. Do not specify a specific file!! The program
works on paths, not specific files within a path. For example, if the
program you want to move is in the folder C:\Program Files\MyApp,
specify that in the Current Path field. Do not specify C:\Program
Files\MyApp\MyApp.exe.
What Application Mover Is Not
-
Application Mover is not a 'migration' or 'installation clone' utility. Do
not use the program to move programs from one computer to another. It is not
designed for this.
-
Application Mover is not intended
to for drive swapping usage such as copying files to a new hard disk and
then swapping that hard disk. See Technical Notes below for more information.
-
Application Mover is not an 'installation discovery
tool'. It does not attempt to discover file references your program may have to
files outside of the Current Path field in the Application Mover main dialog.
Other Suggestions
-
Application Mover is not a substitute for buying a larger hard disk for drive C:. Consider other options if you are woefully low
on disk space and wonder if you can avoid replacing your drive C:\ by using Application Mover to, for example, move C:\Program Files\ to D:\Program Files\.
Did you try using Microsoft's Disk Clean Up first? Is your Internet Explorer cache using 20% of your hard drive? Maybe now is the time to
off-disk archive some of those old documents you haven't opened in years? Many drives come with 'clone
utilities' to copy your old drive to the new drive. Yes, putting in a new drive is technical and time consuming. For a few $$ more your
neighborhood computer shop will do it for you.
General Background About What Happens
-
Application Mover moves 'applications' based on the path specified in
Current Path field in the main dialog. The program moves all files from that
path (and any subdirectories under that path) to the path specified in the New
Path field. The program then uses the Current Path and New
Path strings to
make changes to the windows registry, Windows shortcuts, and .ini &
Install.log files in the program path.
-
The order of operations is: 1. Files are copied to the new path. 2. Registry
Changes are made. 3. Shortcuts are changed. 4. Files are deleted from the old
path. 5. .ini and Install.log files are changed.
-
Advanced Users: If you have a multi-boot system please consider the
consequences of moving a program that is installed under two operating
systems. Only the
actively loaded registry will be changed. Enable replacement confirmations if
you want to supervise the operation more closely.
Additional Notes
-
The program works on entire paths only.
You cannot move single files. For example, you cannot move only C:\Program
Files\MyApp\MyApp.exe to a different path. Application Mover
moves all of C:\Program Files\MyApp\.
-
If you use a "Start Menu" replacement utility or program launcher,
changes made by Application Mover may not be reflected in your utility. If your
utility keeps data in a database of some kind, Application Mover will not be
able to change those settings. If your utility stores program data in the
registry, refreshing the utility's menu after Application Mover is finished may
help.
-
Application Mover will not permit operations involving the root path of any
drive. For example, you cannot move C:\ to D:\.
-
The 'Update Current Path in Registry', 'Update Shortcuts to Current Path',
and 'Update Installer log Files' checkboxes in the main dialog are intended for
advanced users. Most users should leave these checked.
Some Technical Notes
Application Mover moves
'applications' based on the paths specified in 'Current Path' and 'New Path'
fields in the main dialog.
The table below lists some paths and results related to moving a fictitious program named 'MyEditor' from 'C:\Program Files\MyEditor' to 'D:\Programs\MyEditor':
|
Before |
After |
|
Main Program Path:
C:\Program Files\MyEditor
Files also installed in:
C:\Program Files\Common
Files
C:\Windows\Application
Data
C:\Windows\System
|
Main Program Path:
D:\Programs\MyEditor
Files remain in:
C:\Program Files\Common Files
C:\Windows\Application Data
C:\Windows\System
|
|
|
Registry references and windows shortcuts are
changed to D:\Programs\MyEditor. |
Assuming 'MyEditor' is a modern Windows program, as long as
physical hard drives retain their original letter assignments, 'MyEditor'
should continue to function normally from drive D: even though some files
remain in the paths on drive C:.
From the above you can see why problems will arise your goal is to
move 'MyEditor' to another computer. Why won't that work? Because some files related to 'MyEditor' are still on drive C:. For the same reasons you
can't move
'MyEditor' to a new hard disk and then physically swap that hard disk so it
has a new letter assignment.
If you have a strong technical knowledge about your program you
could potentially get around this by using Application Mover repeatedly on
various paths (and perhaps with some manual follow-up). However, this type of
usage is not supported.
|