Hi Randall,

I ran VFP apps on Win95/Win98/W2k workstations from a Novell server for years now. The workstations ALSO authenticated to Win NT and W2k servers so we had both client software installed. It is important to stick with the Novell client software if you are accessing a Novell server for many reasons, but most notably security and functionality. Having said that, I would recommend you ensure the context script and any user/group/etc scripts being run on the local machines after the client logs into Novell are the correct drive mappings you desire. Keep in mind the order scripts are run in Novell (is a user is in a specific context, is a member of a group, or has their own script). Also, verify the 'force first network drive' setting in the novell client on the workstation as well as the 'first network drive' settting. If it is set to 'yes,' and the user's novell client's first network drive is set to 'f', and the user has drives mapped locally THROUGH 'F' for instance, when he/she logs into Novell, the F drive will be remapped to Novell.
It is a good practice to setup context/group scripts for consistent drive mappings and test each user before the user himself logs in. That way you can verify no conflicts with local drive mappings. This should always be done in a login script in Novell and NOT on the workstation using 'map network drive' OR 'Novell map network drive.' If it is NOT set in a script and it is set at the workstation level instead, you will find yourself continuously fixing/troubleshooting drive mapping problems when users make changes, lose their hard drive, etc. Also, if the network is down and they are prompted during boot to try to find that network drive mapping in the future, and the user selects 'no' then you really have problems. Remember that drive mappings in scripts in Novell on the server will take effect NO MATTER where the user logs in from or from what machine so it will be consistent (unless you tell it differently with Novell profiles). Hope this helps somewhat.
Tracy