[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference jamin::pathworks32

Title:Digital PATHWORKS 32
Moderator:SPELNK::curless
Created:Fri Nov 01 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:337
Total number of notes:1612

161.0. "default FAL32 directory ????" by VMSNET::M_SMITH () Thu Mar 13 1997 12:10

     When I do "dir node::" from a vms system to an nt system running pw32,
        I get a directory of my wnt system32 directory.  Is there a way to
        change this default directory to something else?
    	
        Also, when I specify a valid nt user on the "dir" line, I still get
        the wnt system32 directory.  Shouldn't I get the nt user's default
        directory?   BTW, this did not work until I added the NT user to 
        the NCP database with the "def access" command!                  
    
        Very confused.
    
        Michael
    
T.RTitleUserPersonal
Name
DateLines
161.1JAMIN::RUZICHPATHWORKS Client EngineeringThu Mar 13 1997 13:1946
>     When I do "dir node::" from a vms system to an nt system running pw32,
>        I get a directory of my wnt system32 directory.  Is there a way to
>        change this default directory to something else?
>        Also, when I specify a valid nt user on the "dir" line, I still get
>        the wnt system32 directory.  Shouldn't I get the nt user's default
>        directory?   

Sorry, not at present. The spawner is running in the system32 directory, so
that will be the current working directory for the FAL executable. To get a 
different directory, you could turn off the spawner service, and then go to
a DOS box, CD to your favorite directory and invoke  c:\foo>spawn32 /console. 
But that's a lot of trouble, and of course doesn't get you per-user 
directories.

You could QAR the problem and maybe I can get management to buy into
investigating this for a future release.
   	
>        BTW, this did not work until I added the NT user to 
>        the NCP database with the "def access" command!                  

The spawner will recognise local NT accounts, but you have to turn on an
additional privilege in the User Manager: 

|     To grant proper access for DECnet objects using the NT user
|     accounts, follow these steps:
|
|     1. From the Start button, click Programs -->
|        Administrative Tools --> User Manager.
|
|     2. From the User Manager application's top-level menu, click
|        Policies --> User Rights.
|
|     3. In the User Rights Policy window, select the box preceding
|        "Show Advanced Rights".
|
|     4. Click on the "Right" box and select "Log on as a batch job".
|
|     5. Click "Add" to display the "Add Users and Groups" window.
|        To select users and groups, you might consider all the
|        choices in the "List Names From" list.  Once you select a
|        name (for example, a specific account name such as
|        "Administrators" or "Everyone"), click "OK" to return
|        to the User Rights Policy window.  Then click "OK" again,
|        and exit the User Manager.

-Steve
161.2QAR on the way!VMSNET::M_SMITHThu Mar 13 1997 13:3710
    Steve,
    
    Thanks for the quick response.  I can connect as the nt user after
    adding the policy and the spawn32 /console works although it is
    an ugly solution.
    
    We will QAR this since this functionality existed in the 4.1b kit.
    
    Michael
    
161.3QAR 413 EnteredVMSNET::S_VORESmile - Mickey's Watching!Thu Mar 13 1997 13:532
    
    
161.4how bout this?VMSNET::M_SMITHThu Mar 13 1997 13:565
    Could I copy spawn32*.* to the d:\foo directory and then change the
    registry to reflect this new location?
    
    Michael
    
161.5and another thingVMSNET::M_SMITHThu Mar 13 1997 14:097
    Also,
    
    Should connecting as the nt user show me the user's default directory
    or the nt system32 directory?
    
    michael
    
161.6SPELNK::curlessThu Mar 13 1997 18:046
It won't with the current codebase.

So.. QARaway

Jeff