![[Home]](gif/home6.gif)
------------------------------------------------------------------------
SCO VisionFS 1.2
------------------------------------------------------------------------
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 in SCO VisionFS 1.2
------------------------------------------------------------------------
Here's a summary of the new features in this release. For full details,
see the online Help.
- New authentication modes
VisionFS can now encrypt passwords on the network, to increase
security and enable better co-operation with Windows NT. Users and
VisionFS Administrators can set and change passwords from Windows
and the Profile Editor.
- WINS
VisionFS can now register its names with WINS servers, and be a
WINS server itself.
- Internet workgroups
VisionFS servers on different subnets can now communicate, so you
can see workgroups in your subnet containing computers in other
subnets, anywhere on the intranet or Internet (firewalls permitting).
- CIFS Bridge technology
You can now access remote CIFS servers -- either VisionFS or
Windows NT -- as if they were local computers.
- Enhanced server presentation in multiple workgroups
You now have more control over the names and descriptions your
VisionFS server uses in different workgroups. VisionFS can become a
master browser, making your workgroups more reliable.
- Username mapping
VisionFS maintains a set of mappings, so users with different Windows
and UNIX usernames can now access VisionFS servers.
- Multiple VisionFS Administrators
You can now have as many VisionFS Administrators as you want.
- Network diagnostic tool
VisionFS now includes UNIX utilities for diagnosing problems on your
local network.
- Updated licensing model
VisionFS now uses Vision97 licensing, which lets you quickly and
efficiently manage your licenses for all Vision97 products. When
VisionFS is running, you can find the Vision97 License Manager
in the visiontools share.
- Terminal emulator
VisionFS includes SCO TermLite, a simple yet powerful 16-bit
terminal emulator for all Windows platforms. When VisionFS is
running, you can find this in the visiontools share.
------------------------------------------------------------------------
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
\<server>\visiontools\visionfsrofedit.exe
(replacing <server> 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 <server> with the
name of your VisionFS server:
\<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 again.
To run VisionFS Setup, *after* installation:
1 Log in as root on the UNIX host.
2 Type the following, replacing <vision_dir> with the name of
the Vision97 shared directory, by default /usr/local/vision:
<vision_dir>/bin/visionfs setup
3 Follow the instructions on your screen.
See also the "Troubleshooting" section in the "Introducing SCO VisionFS"
book.
------------------------------------------------------------------------
To remove 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 1.2, 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 <vision_dir>/visionfs/version, replacing
<vision_dir> with the name of the Vision97 shared directory, by
default /usr/local/vision.
- Click About SCO VisionFS on the Profile Editor's Help menu.
- Look in the on-line Help.
The version number also appears when you start the VisionFS server.
------------------------------------------------------------------------
Known problems
------------------------------------------------------------------------
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: VisionFS can run in two authentication modes:
UNIX passwords (not encrypted), or VisionFS passwords (encrypted).
The cause is one of the following:
- VisionFS is using unencrypted passwords, and Windows has not
tried to authenticate you.
- VisionFS is using encrypted passwords, and your Windows and VisionFS
passwords 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
\<server>\<share>.
- 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 \<server>\<share> 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".
Check your UNIX boot scripts to make sure you don't start
SCO NetBIOS over TCP/IP if you want to start VisionFS automatically
on reboot.
------------------------------------------------------------------------
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 Vision family 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.36.2.5 1997/03/06 15:35:40 davidsm Exp $
------------------------------------------------------------------------