diff --git a/help/Basic_use.htm b/help/Basic_use.htm
index 9fc3480f2..602187464 100644
--- a/help/Basic_use.htm
+++ b/help/Basic_use.htm
@@ -563,7 +563,7 @@ Simulators
The settings to
control
Auto-exposure are on the Camera Tab
-of the Advanced Settings dialog.
Multi-Star Guiding
Most guiding configurations can benefit from guiding on multiple stars
+of the Advanced Settings dialog.
Multi-Star Guiding and Star-Selection
Most guiding configurations can benefit from guiding on multiple stars
rather than just one. This results in using a
weighted average centroid position of multiple stars rather than just the
centroid of a single star. Multi-star guiding is enabled using a
@@ -591,7 +591,53 @@ Simulators
will depend on many factors including image scale, star and background
sky brightness, star size, focus, tube currents, and camera noise. Because of the way the
algorithm is implemented, your best option will be to try it and decide
-for yourself. Note: if you don't use the auto-select function and instead choose a guide star manually, multi-star guiding will be inactive.
+for yourself. Note: if you don't use the auto-select function and instead choose a guide star manually, multi-star guiding will be inactive.
Since
+the multi-star selection and guiding feature was introduced, users have
+asked for a means to override guide star selection based on what they
+see on the display. These requests have not been acted upon
+because they would disrupt the underlying mathematics of the multi-star
+process. More importantly, they would lead to inferior results for
+reasons described below. The algorithm applies the basic
+principle that the accuracy of centroid calculation - the fundamental
+calculation of where a star is located on the sensor - it proportional
+to that star's SNR. It has nothing to do with the shape of the
+star, its location on the sensor, its proximity to the sensor edge, or
+any other visual characteristics of the star candidate. The algorithm
+will always choose the set of stars with the highest SNR values subject
+to user-controlled parameters that define what a star should look like
+on a particular system. Two parameters, Min-HFD and Max-HFD,
+define a range of star "sizes" that control whether a bright area on
+the sensor can be accepted as a star candidate rather than being
+rejected as sensor noise, internal reflections, or close pairs of
+stars. The third parameter, Saturation ADU, defines an upper
+limit to the peak brightness of a star candidate, usually defined as
+the maximum ADU value produced by the guide camera. The algorithm
+tries to avoid saturated stars and will accept one only if there are no
+other viable candidates. Setting these parameters correctly is
+the single most important thing for a user to do in order to get the
+best possible sets of guide stars. The "Min" and "Max" HFD values
+can be determined empirically by using the Star Profile tool or by
+examining the PHD2 guide logs to see the range of star sizes that are
+typical for the guiding system and its seeing conditions. Once set,
+they should rarely need to be changed unless something in the
+configuration or the atmospheric conditions has substantially changed.
Users
+are commonly fooled by what they see on the display and think they can
+do a better job of guide star selection. This is a mistaken
+impression. The single biggest reason is that many of the
+"attractive" guide stars on the display are saturated.
+Secondarily, they are often just sensor noise, e.g. hot or warm pixels,
+that look like stars once the image has been down-sampled and
+gamma-stretched for display. No dark library or bad-pixel map can
+completely eliminate these artifacts. In summary, simply squinting at
+the screen and clicking on bright spots will produce inferior results
+compared to the quantitative, systematic approach taken by the
+auto-select star-finding mechanism. Of course, die-hard users can
+still manually choose a guide star, but they won't then be able to use
+multi-star guiding. For people who are not convinced about the merits
+of the auto-select process, the debug log file contains a detailed
+list, for every auto-find, of the location and properties of every
+single candidate object in the guide frame and how these were included
+or excluded to compile the final list.
Automatic
Calibration
Conventional Mounts
diff --git a/help/Supplemental_Info.htm b/help/Supplemental_Info.htm
index 3be5feb42..bbe86529f 100644
--- a/help/Supplemental_Info.htm
+++ b/help/Supplemental_Info.htm
@@ -802,12 +802,21 @@ Managing
during a PHD2
session. Finally, you can import and export
profiles for purposes of debugging, backup, or exchange
-between computers. When you export a profile to a new computer,
-remember that the dark library and bad-pixel maps will not be migrated
-automatically because they are stored in the file system - in the
+between computers.
Migrating PHD2 Settings to a Different Computer
On
+Windows, the profile information is kept in the Windows registry, so
+you can't simply do file transfers to move your settings from one
+computer to another. Instead, you should 'export' your profiles
+into files on the old computer, copy those files to the new one,
+then 'import' them on the new system. This will transfer all the
+settings associated with the profile except for the dark libraries and
+bad-pixel maps. The dark and bad-pix map data are stored in the file
+system because of their size. They are located in the
'AppData\Local\PHD2' logical directory used by your operating system.
You will need to transfer that directory and all of its files to
-the new computer manually.
+the new computer manually without changing the directory location or
+file names. That said, the best practice is to simply rebuild
+them on the new system in order to have data that reflects the current
+behavior of the guide camera sensor.
Aux-Mount
Connection using "Ask for coordinates"