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 Initially)
 
(One intermediate revision 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 28: Line 25:
 
* See for details: [[How Benderlink for Chiyoda/KEINS Handles Data for Multi-User Login]]
 
* See for details: [[How Benderlink for Chiyoda/KEINS Handles Data for Multi-User Login]]
  
 
 
 
 
 
 
==Bender Part Path Assigned Inside Benderlink Initially==
 
Benderlink will also automatically assign that Documents location as the default part storage path for each bender inside Benderlink.
 
 
This path can be configured inside Benderlink to other paths if you want to store Benderlink parts on the network.<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