Difference between revisions of "Revision: Benderlink for Chiyoda/Keins 6.4"

From ATTWiki
Jump to: navigation, search
(Where Each User's Part Data is Stored)
 
(11 intermediate revisions by one user not shown)
Line 18: Line 18:
 
==[[image:Check.jpg|25px]] ENHANCED - Better Handling for Installations With Multiple User Accounts ==
 
==[[image:Check.jpg|25px]] ENHANCED - Better Handling for Installations With Multiple User Accounts ==
  
<table>
 
<tr>
 
<td width=300 valign=top>
 
 
This version of Benderlink allows for installation on Windows setups that use multiple users with different login names.  Benderlink can now properly handle unique configurations for each user by starting with a copy of common starting configuration files.
 
This version of Benderlink allows for installation on Windows setups that use multiple users with different login names.  Benderlink can now properly handle unique configurations for each user by starting with a copy of common starting configuration files.
 
<br><br>
 
<br><br>
Line 26: Line 23:
 
<br><br>The method described on the right follows the Microsoft-suggested method of handling program data for multi-user logins for Windows from Vista and newer (Examples: Vista, Windows 7, Windows 8)<br><br>
 
<br><br>The method described on the right follows the Microsoft-suggested method of handling program data for multi-user logins for Windows from Vista and newer (Examples: Vista, Windows 7, Windows 8)<br><br>
  
How it works:
+
* See for details: [[How Benderlink for Chiyoda/KEINS Handles Data for Multi-User Login]]
  
==Starting Common Setup Data==
 
The Benderlink installation program installs an initial set of common configuration files for all users.
 
 
Use an administration login to install the initial Benderlink.
 
 
In Vista, Windows 7, and Windows 8, these files are stored in '''c:\ProgramData\BenderlinkChiyodaKeins'''<br><br>
 
 
==What Happens When Benderlink is Used For a New User the First Time==
 
In this multi-user environment, you will eventually log in under other user names to use Benderlink.  When Benderlink is run the first time for any user log in, the common configuration files are copied to that user's private folder structure (also called a "namespace").<br><br>
 
 
The folder is assigned like this: '''c:\users\<username>\AppData\Roaming\BenderlinkChiyodaKeins'''<br><br>
 
 
Note: The common configuration folders and files are only copied when the same folders and files ''do not already exist'' in the user's private folder.<br><br>
 
 
==Where Each User's Part Data is Stored==
 
The bender and measuring center files are stored in '''Documents\BenderlinkChiyodaKeins'''.  If these folders and files do not exist when Benderlink starts, then Benderlink will copy common configuration files from the common folder into this folder to give the user a starting set of sample parts.<br><br>
 
Note: The common configuration folders and files are only copied when the same folders and files ''do not already exist'' in the user's private folder.<br><br>
 
 
==User's Initial Bender Part Path Assigned==
 
Benderlink will also automatically assign that Documents location as the default part storage path.  (This path can be configured inside Benderlink to other paths.)<br><br>
 
 
 
</td>
 
<td width=300>
 
 
</td>
 
</tr>
 
</table>
 
  
 
==OTHER PAGES==
 
==OTHER PAGES==

Latest revision as of 17:35, 20 February 2013

Blink keinschiyoda orangefire.jpg

Revision 6.4

Back to Benderlink for Chiyoda
Back to Benderlink for KEINS

Blink keinschiyoda screens 6.1.jpg



Check.jpg ENHANCED - Better Handling for Installations With Multiple User Accounts

This version of Benderlink allows for installation on Windows setups that use multiple users with different login names. Benderlink can now properly handle unique configurations for each user by starting with a copy of common starting configuration files.

Previous installations required that the installer be logged into Windows as the user name that will use the computer with Benderlink. When logging on as a different user, Benderlink would lose track of the configuration files.

The method described on the right follows the Microsoft-suggested method of handling program data for multi-user logins for Windows from Vista and newer (Examples: Vista, Windows 7, Windows 8)


OTHER PAGES