Re: Re: Use of the Windows Registry

Meghadri Ghosh wrote:

> Perhaps the afsdbmt.ini containing the drive mappings could be moved 
> to be per user.
>
> I believe the current code could be maintained by simply create the 
> following key: (The default value can be set to some suitable key, 
> perhaps under 'Software\\OpenAFS.org\\Client'?)
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows 
> NT\CurrentVersion\IniFileMapping\afsdbmt.ini]
> @="#USR:Software\\OpenAFS.org\\afsdbmt
>
> Thus per user mapping settings could be maintained.

Interesting.  I will have to try this.

> By the way, I installed v1.2.10 on XP and noticed that it installs the 
> loopback adapter and binds to it. This is good, but the MS loopback 
> adapter was already installed on the system and a second instance was 
> inserted by the installation. Additionally, on removing the new 
> instance of the loopback adapter, and restarting the client service, 
> the binding was to the (real) NIC instead of the existing loopback 
> adapter.

The loopback adapter is found by its MAC address.  If the binding was to 
a real NIC it is because
the MAC address of the loopback adapter which is installed on your 
machine is not the default
value.  Perhaps that is why the second loopback adapter was installed.

In the future, OpenAFS will look for the adapter to bind to by name.  
Loopback adapters (if
installed by the installer) will be assigned the name "AFS".

> Some time back I had emailed a URL that contained the diffs of a local 
> version we have at Stanford that installed the loopback adaptor, if 
> necessary, and if automatic binding was specificed, detected any 
> existing instance of the MS loopback adaptor and bound to its LANA.

The proper way to submit patches is to use the OpenAFS Request Tracker 
which is linked off of
the OpenAFS.ORG web page.

> The installer has been written with Installshield Developer 8. The 
> code diffs and the install project can be found at
>
> http://www.stanford.edu/~meghadri/OpenAFS/

Install Shield is no longer being supported by OpenAFS.ORG.  None of 
those who have volunteered to build installers have licenses to the 
Install Shield products any longer.  Instead we are supporting
installers built with NSIS 2.0.  Please see the 1.3.52 build.  The 
1.2.10 source tree is very
out of date and in my opinion is extremely unstable.

> Please let me know if there are any questions, or these could be 
> otherwise modified to be amenable for useful integration into OpenAFS.
>
> -- 
> megh
>
>
>
> _______________________________________________
> OpenAFS-Win32-devel mailing list
> [email protected]
> http://lists.openafs.org/mailman/listinfo/openafs-win32-devel