First, Mark Antrobus, your statement #'s 1, 2, and 3 are all correct in that this is what I want to do. However, as you indicated, you--normally--cannot map to a folder below a share. But I have tried sharing the user's home directory, but mapping to this share does not work.

I tried your script suggestion, but that did not work either. The error I get is:

85 the local device name is already in use.
Cannot SUBST a network drive.
1 Inncorrect function.

(I don't understand what the SHELL command is supposed to accomplish in the script you suggested).

Second, NTDOC, yes, BSMITH has share and NTFS rights to his share.

However, adding the line, USE P: /DELETE before USE P: @HOMESHR, as you suggested, did work. The user was successfully able to map to his share.

But here is the problem. I do NOT want to map it this way because then I have to share the user's home directory. I understand that you cannot normally connect to a folder below a share on W9x systems, but isn't there a work around?

Consider this; let's say I have 1,000 users already on the network. Now, to run this script to automap home directories, I'll need to go back and share all 1,000 of those user home drives! Also, for any new users created, I'll have to remember to go back and share their home directories once their user profile is created. It's so much easier to add new users with a template using the %username% command in their profile to auto create their home directory.

Having to go back and manually share each and every home directory seems like a chore that scripting is supposed to get rid of, right? Or am I missing something here?

-Thanks in advance for your help!