[OpenAFS] Small Windows client installer bug

Jacob Gorm Hansen jg@ioi.dk
Sat, 2 Mar 2002 15:03:16 +0100


I've recently install the latest AFSForWindows.exe on a number of Win2k client
without problems.

However, on one machine the following happened:

- User selects S: as /afs. Disables U: mapping.

- Is told to reboot, does so.

- AFS doesn't start which is usual because our cell is not in his CellServDB 

- Configures our cell, then tries to start client, which fails because 
 'Drive N: can not be mapped' or similar error.

- In the mapped drives tab, the drive N: is the only drive (even though N: was 
  never input by user). It is greyed-out, and so are all of the Add/Remove
  buttons as well. So the list of mapped drives is basically locked, and even
  though N: is available (not used for anything else), it fails too.

I guess this is a simple bug in the installer or control panel, maybe due to 
not mapping the U: drive?

Any ideas?