------------------------------------------------------------------------ SCO VisionFS 2.01 ------------------------------------------------------------------------ This README.vfs file contains important information about this release. You should read this file: - If you've just set up VisionFS for the first time, and you'd like to know what to do next. - If you'd like a summary of the new features in this release. - If the VisionFS server won't start, or you can't start the Profile Editor. - To find any last-minute information that couldn't make it into the online Help or printed documentation. Please read carefully. ------------------------------------------------------------------------ What's new since SCO VisionFS 1.2 ------------------------------------------------------------------------ Here's a summary of the new features in this release. For full details, see the online Help. - Authenticate users on Windows NT or VisionFS servers For this release VisionFS can authenticate users on a Windows NT server before they access the VisionFS server. This provides better integration with your existing Windows NT servers. Alternatively, you can authenticate users on a different VisionFS server. If you have a number of VisionFS servers on your network, you can use just one of them to authenticate all users. This provides centralized password storage for all your VisionFS servers. - Print to shared printers from UNIX The versatile "visionfs print" command lets you use shared printers on your network from the UNIX command line. Note: If you're upgrading from VisionFS 1.1 or 1.2, your existing license number is no longer valid. You can evaluate this version of VisionFS, but you must obtain a new license number to carry on using it after your 30-day evaluation period has expired. ------------------------------------------------------------------------ Finding and starting the Profile Editor ------------------------------------------------------------------------ You use the VisionFS Profile Editor to configure the VisionFS server. A complete VisionFS configuration is called a server profile. The VisionFS Profile Editor is stored on the UNIX host, and isn't installed on any PC. Every VisionFS server has its own Profile Editor -- you can't use a Profile Editor to configure more than one server. You access a VisionFS server's Profile Editor through a share on the server. This share, called visiontools, is created automatically by Setup. The visiontools share holds the Profile Editor and other useful tools, such as the License Manager and SCO TermLite. How you access the visiontools share depends on your version of Windows: - Windows 95 and Windows NT 4 users can use Network Neighborhood (or Windows Explorer). - Windows for Workgroups and Windows NT 3.51 users need to map a drive using File Manager. Note: Only users with VisionFS Administrator privileges can run the Profile Editor. A VisionFS Administrator is named during Setup; this user can add and remove other VisionFS Administrators using the Profile Editor. To learn how to use the Profile Editor, look in the Help or read the "Introducing SCO VisionFS" book. ------------------------------------------------------------------------ To find and start the Profile Editor using Network Neighborhood ------------------------------------------------------------------------ 1 Log into Windows as a user with VisionFS Administrator privileges. 2 Double-click Network Neighborhood and locate the VisionFS server. If it's not in your workgroup, double-click Entire Network and open the workgroup it's in. 3 Double-click the VisionFS server. If prompted, type the VisionFS Administrator's password for this VisionFS server. By default, this is the user's UNIX password. 4 Double-click the visiontools share. 5 Double-click the visionfs folder. 6 Double-click the Profile Editor, profedit.exe. You can also click the Start button, click Run, then type \\\visiontools\visionfs\profedit.exe (replacing with the name of your VisionFS server) to start the Profile Editor without browsing the network. ------------------------------------------------------------------------ To find and start the Profile Editor using File Manager ------------------------------------------------------------------------ 1 Log into Windows as a user with VisionFS Administrator privileges. 2 In File Manager, click Connect Network Drive on the Disk menu. 3 Choose an unused drive letter. 4 In the Path box, type the following, replacing with the name of your VisionFS server: \\\visiontools 5 Click OK. 6 If prompted, type the VisionFS Administrator's password for this VisionFS server. By default, this is the user's UNIX password. 7 Double-click the visionfs folder. 8 Double-click profedit.exe In place of step 4, you can also click Browse, and browse the workgroups for your VisionFS server. When you've found the server, click it, then click visiontools. If Windows reports an error when you click the server, or doesn't list any shares, type the path as shown in step 4. You'll need to do this if your password for this VisionFS server is different to your Windows password, or if you're using UNIX passwords (the default authentication mode) from Windows NT 3.51. Note: This is a Windows problem, beyond the control of VisionFS. ------------------------------------------------------------------------ If you can't start the VisionFS server or Profile Editor ------------------------------------------------------------------------ The profile may be corrupt, or a VisionFS Administrator may have accidentally changed some settings that mean you are no longer allowed to access the Profile Editor. You can fix a profile by running VisionFS Setup. To run VisionFS Setup, after installation: 1 Log in as root on the UNIX host. 2 Type the following, replacing with the name of the Vision97 shared directory, by default /usr/vision: /bin/visionfs setup 3 Follow the instructions on your screen. See also the "Troubleshooting" section in the "Introducing SCO VisionFS" book. ------------------------------------------------------------------------ To uninstall SCO VisionFS ------------------------------------------------------------------------ 1 Log in as root on the UNIX host. 2 Use the Software Manager. Click on SCO VisionFS. Select Software -> Remove Software. 3 Follow the instructions on your screen. ------------------------------------------------------------------------ PC system requirements ------------------------------------------------------------------------ To access the server, PCs must use TCP/IP as their transport protocol. - For Windows 95 and NT, a TCP/IP protocol stack is provided with the operating system. - For Windows for Workgroups, you can install the protocol stack provided in the \misc\mstcpip folder on the Vision97 CD, or found on the Microsoft web site, www.microsoft.com. ------------------------------------------------------------------------ If you have suggestions or comments ------------------------------------------------------------------------ The VisionFS team welcomes any comments you have about the product, or any suggestions for improvements. Though we can't guarantee to include them all, we promise to consider any ideas you may have. Send your suggestions or comments to visionfs@sco.com. ------------------------------------------------------------------------ Reporting problems ------------------------------------------------------------------------ To report a problem in SCO VisionFS 2.01, you can: - Contact SCO Support: North America Europe Phone: (408) 425 4726 +44 (0)113 251 2222 Fax: (408) 427 5443 +44 (0)113 251 2223 Email: support@sco.com ukvision@sco.com - Fill in the problem report form via the World-Wide Web. Point your browser at: http://www.sco.com/Support/ciservices - Look up "Support, contacting" in the Help index, and follow the instructions. When reporting problems, please report the exact version of the server. To find out the version number, you can: - Look in the file /visionfs/version, replacing with the name of the Vision97 shared directory, by default /usr/vision. - Click About SCO VisionFS on the Profile Editor's Help menu. - Look in the on-line Help. - Run the Software Manager (custom). The version number also appears when you start the VisionFS server. ------------------------------------------------------------------------ Known problems ------------------------------------------------------------------------ Problem: - On Windows NT 4, you see the error message "This account is not authorized to login from this server". - On later versions of Windows 95, you're not authenticated even if you type the correct password. Cause: New versions of Windows and some new Windows patches prevent the PC from sending any plain text (unencrypted) passwords. Solution: Do one of the following: - (Recommended) Use another server (either Windows NT or VisionFS) to authenticate users using encrypted passwords. 1 Run Setup. 2 When Setup displays the recommended settings and the message "OK to use these settings?", type N to change the settings. 3 Change the authentication server to another VisionFS server or a Windows NT server. 4 Continue with Setup. - Change the authentication mode of the VisionFS server to use encrypted passwords. You may need to enable plain text passwords (as described below) on a single PC temporarily to run the Profile Editor. 1 Start the Profile Editor. 2 In Server properties, click the Passwords tab. 3 Choose an authentication mode that uses encrypted passwords: - Click Use Only VisionFS Passwords if you want to store passwords in encrypted form on the host. - Click Use A Domain Or Another Server if you want to authenticate users using Windows NT or VisionFS encrypted passwords on another server. 4 Click OK, then click Update Server on the Profile menu. - Enable plain text passwords on PCs. You will need to follow these instructions for each affected PC. 1 Start the program "regedit". 2 On Windows 95, under the key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VNETSUP add a new DWORD value, "EnablePlainTextPassword", and set it to 1. On Windows NT, under the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters add a new DWORD value, "EnablePlainTextPassword", and set it to 1. 3 Reboot the PC. ------------------------------------------------------------------------ Problem: When you click a VisionFS server in File Manager's Connect Network Drive dialog, or Print Manager's Connect Network Printer dialog, Windows displays an "Access Denied" dialog, or doesn't list the resources on the server. Cause: Windows for Workgroups: Windows has tried to authenticate you on the VisionFS server using your Windows password, and this has failed as your Windows password is different to your password for accessing the VisionFS server. Windows NT 3.51: The cause is one of the following: - VisionFS is using UNIX (unencrypted) passwords, and Windows has not tried to authenticate you. - Your Windows password and your password for accessing this VisionFS server are different. Both versions of Windows have generated an error rather than prompt you for the correct password. This is a Windows problem. Solution: - Type the server and share names in the Path box, in the form \\\. - To connect a network printer, first connect a network drive using solution 1 above. You can disconnect the drive afterwards. ------------------------------------------------------------------------ Problem: On Windows 95 or Windows NT 4, the Profile Editor gives an error "Invalid file format", and doesn't start. Cause: Another program may have installed an old version of the file vsvbx.vbx in your PC's Windows system directory. This file is used instead of the Profile Editor's own version of vsvbx.vbx, stored in the same folder as profedit.exe. Solution: To run the Profile Editor, first map a drive to the visiontools share on the server. DO NOT overwrite or delete the copy of vsvbx.vbx in your Windows system directory, as this may cause other programs to stop working. ------------------------------------------------------------------------ Problem: The VisionFS server doesn't appear in any workgroups. Cause: PC and/or UNIX network settings may be wrong. Solution: Check the subnet mask is the same on PC clients and the UNIX host. For now, type \\\ explicitly rather than browse the network. ------------------------------------------------------------------------ Problem: On SCO OpenServer Release 5, you cannot use VisionFS if you're running SCO NetBIOS over TCP/IP, for example with SCO Advanced File and Print Server. Cause: SCO NetBIOS over TCP/IP conflicts with the NetBIOS over TCP/IP used by VisionFS. Solution: - Remove SCO NetBIOS over TCP/IP from your system before running VisionFS. You can do this using the Network Configuration Manager. You can still use SCO Advanced File and Print Server over NetBEUI. - Stop SCO NetBIOS over TCP/IP using the command "/etc/netbios stop". To make sure SCO NetBIOS over TCP/IP doesn't start when the UNIX host reboots, remove or edit the /etc/rc2.d/S86netbios UNIX boot script. ------------------------------------------------------------------------ Problem: Restarting the VisionFS server can cause problems for users. Cause: Some Windows programs can't cope if the server restarts while they are using it, and will display error dialogs. This typically affects programs accessing the server heavily, such as Setup programs. Solutions: - Database programs normally require you to re-open the database. - Don't restart the server while a user is running a Setup program. The Profile Editor tells you who's connected to a server. ------------------------------------------------------------------------ Tips: - Check out the SCO Vision97 web site, www.vision.sco.com, for the latest news about VisionFS. - Check out the Microsoft web site, www.microsoft.com, for Windows 95 service packs and solutions to various Windows problems. ------------------------------------------------------------------------ Copyright (C) 1996-1997 The Santa Cruz Operation. All Rights Reserved. $Id: README,v 1.37.2.8 1997/12/02 17:55:54 duncans Exp $ ------------------------------------------------------------------------