APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

Visionfs on SCO Unix

© July 2013 Anthony Lawrence

When the SCO operating systems were sold to Caldera, Visionfs remained owned by Tarantella (the company that was SCO). Therefore, Visionfs is no longer a free product. I recommend using Samba instead, and I'd recommend using it on Linux, not SCO.

However, should you find yourself on an old SCO machine, Visionfs is probably in /usr/vision/bin (you might want to add that to $PATH for root). Quick start:

cd /usr/vision/bin
./visionfs --help      will display the first level of commands
./visionfs status     will display interesting information including the connected users.
./visionfs setup      will configure it.

Visionfs puts your SCO box into the Network Neighborhood of your Windows machines. This lets your Windows users use the SCO machine for file space and also gives them access to Unix printers. Nothing needs to be installed on the Windows machines; it's all on the server.

Visionfs was included with both Unixware 7 and Openserver. With Unixware, it installs automatically; Openserver 5.0.4 and 5.0.5 (3.2v5.0.4/5) require a separate install.

I'm already installed and licensed, skip to configuration.

Do you have the latest version?

Update: You may be out of luck. I don't know of anywhere that you can get this any longer. The Xinuous product pages say Visionfs is "not available".

The latest version includes support for the Unix machine being an SMB client (seeing Windows shares from the Unix box). It also lets you set up roaming profiles just as you would if you were using NT- in fact, you can tell the Windows machines that they are logging on to an NT domain! The new version does not require licensing when installed on 5.0.4 and greater.

Patches are important! The 3.0 version had a print bug which caused it to lose print jobs greater than 2872 characters. That was fixed with a supplement ( see ftp://stage.sco.com/vision/VisionFS

Note that for 5.0.4 you do not install from the Vision CD thoughtfully packed with your distribution. Instead, you mount the OS installation CD and install from that. See https://aplawrence.com/cgi-bin/ta.pl?arg=108277 if you accidentally did install from the Vision CD.

OpenServer 5.0.4 requires RS504C: https://aplawrence.com/cgi-bin/ta.pl?arg=105811

The 5.0.5 release includes specific directions for installing Visionfs.

There are several things that can prevent a successful install. First, you can't run AFPS or LAN Manager Client. See https://aplawrence.com/cgi-bin/ta.pl?arg=108209 for directions on that.

Next, netbios can't run. I think the Unixware install takes care of that automatically, but on Openserver you'll need to do:

netbios stop

mv /etc./rc2.d/S86netbios /etc/rc2.d/s86netbios

If S86netbios doesn't exist, vi /etc/netbios and add an "exit 0" at the top.

Check that your hostname is correct by trying

grep `hostname` /etc/hosts


ping `hostname`

If these don't work, Visionfs won't license (latest versions on Unixware and OSR5 do not need licensing).

See https://aplawrence.com/cgi-bin/ta.pl?arg=108271 for other suggestions.

On Unixware, the automatic process installs a fully licensed version. On 5.0.4, you need to license the product separately (this is no longer true- the 3.x versions do not need to be licensed). The documentation implies that you get a chance to do this during the install; if this is correct I've somehow managed to miss that opportunity so far. To license after the fact, you need to run

/usr/vision/bin/visionfs license


There are numerous things that can keep this from working, the most likely of which would be a misconfiguration of TCP/IP. One simple test is to run

ping `hostname`

(note that those are backquotes: the left leaning single quote usually found under the "~" on your keyboard)

If this doesn't work, the visionfs license server won't be running, and you won't be able to license the product. In this case, either your hostname is wrong or you don't have proper routing to yourself (route add yourbox should fix that).

After getting things running on the Unix side, the machine should start to show up in Network Neighborhood on the Windows machines. Keep in mind that there are timing issues here: without a reboot it may take a few minutes for the Unix box to appear. Even with rebooting every machine on the network, it still may take a few minutes, so go have a break.

To speed things up, shoose "Start->Run" and just type the name of the Sco server preceded by two backslashes:


Once it does appear, you may have password issues. I'll cover some of them below, but if you run into trouble, I suggest you just access SCO's search pages, select "Visionfs" and search for "password".

Some articles of particular concern are:

Other issues involve Security levels and length of password: See https://aplawrence.com/cgi-bin/ta.pl?arg=108227 and https://aplawrence.com/cgi-bin/ta.pl?arg=108108 and


Things you need to understand about Windows passwords:

A windows user can have a password. That password may or may not be used for authentication. Whether or not it logs onto an NT domain depends on the setting in the Network portion of control panel.

If it isn't logging into a domain, the password is still used to authenticate network connections such as Visionfs.

The password on the windows machine and the password on Visionfs can be different, though it is easier if they are the same. More on this below.

If you configure a share to allow guest access, the Windows users won't need to have a password to access it.

Configure the Windows machines as "Client for Microsoft Networks". This gives you the opportunity to assign a Windows login and password that matches your Unix login, which makes things far less confusing.

Once you've done that, you have a choice on the Windows shutdown menu that lets you close all programs and login as a different user. This is an easy way to gain access to the Administrator's programs which give you a Windows based way to configure Visionfs.

When you ran the Visionfs setup program, you assigned a Visionfs Administrator-probably root. If you don't know who you assigned, run /usr/vision/bin/visionfs setup again.

If you have a user who can't get Visionfs shares to appear, you can either connect as the Visionfs administrator and use the Windows Visionfs Profile Editor (it's in the Visionfs share) or use the Unix command line method (covered below) to change their password).

Visionfs has 3 possible ways to authenticate passwords: it can use plain-text Unix passwords, encrypted Windows passwords, or it can pass authentication off to an NT server.

If you use Unix passwords, and are running Windows 98 or Windows 95 with certain patches, or Windows NT, you will need to run "regedit" and add a DWORD Value to allow plain text passwords:: open HKEY_LOCAL_MACHINE->System->CurrentControlSet->Services->VXD. Highlight VNETSUP, and then Edit, Add DWORD. Name it "EnablePlainTextPassword", and then modify it to have a value of "1".


For Windows 2000, wayne_v@my-deja.com offered this:

If your 3rd party SMB (Server Message Block) server requires
unencrypted passwords:
1.      Start / Programs / Administrative Tools / Local Security
2.      Expand the Security Settings / Local Policy / Security Options
3.      Double-click Send unencrypted passwords to connect to third-
party SMB servers.
4.      Press the Enabled radio button.
NOTE: If domain-level security is defined, it will take precedence.
This option will weaken your overall security. See if the vendor has an

As you'd have to do that on every Windows machine, it's better to use one of the other methods. Passing it off to an NT server takes the SCO box right out of the loop: if NT says the user is OK, then SCO believes it. Using encrypted Windows passwords requires more initial setup:

First, run /usr/vision/bin/visionfs password --wizard. This lets you import Unix users into the Visionfs password database. You can assign them a blank password, a random password, make everybody's password the same, or make their password match their Unix name. I'd suggest making every password the same or matching their user name initially.

You really want to use encrypted passwords if you possibly can.

If Windows users already have passwords (remember, even if they don't have any authentication, they can have passwords), you've got a couple of ways to handle this:

See Network Neighborhood, Visionfs, Samba Authentication and all that for more on authentication issues.

Dynamic bring-up and Visionfs

By default, Visionfs broadcasts on the network. If you have a dynamic outgoing ppp link on the same server, the broadcasts keep your dynamic ppp up even if otherwise idle. The Visionfs server "scobox" can be modified using Profile Editor to disable naming (Profile Editor-Server-Edit->Properties->Advanced->Disable Naming). This will stop the broadcast, but it will now be impossible for any windows machine to access "scobox" unless they have persistent network drives mapped to it, or run "//scobox" from the File menus, and have an Lmhosts file referencing "scobox":

If the IP address of "scobox" was, you would need C:\WINDOWS\LMHOSTS to look like:       scobox  #PRE

Note that the file name is LMHOSTS, not LMHOSTS.TXT or LMHOSTS.SAM (that's a sample file that explains how LMHOSTS works). Watch that if you are using NOTEPAD or WORDPAD to create this.

Also see https://aplawrence.com/cgi-bin/ta.pl?arg=110498

Printing to Windows Printers

If a Windows printer is shared ( see Windows Network Configuration, you can print to it from Unix programs. Note that the user of that machine does not necessarily need to be logged in to Unix or even to Visionfs; the printer just needs to be shared. To do this, see Visionfs Printing and the related Visionfs Laserjet Script

Command line print is easy:

cat file | ./visionfs print //computer_or_ip/printername - --user whatever --password whatever

Unless the shared printer is restricted to certain users, the "whatever" shouldn't matter.

Disable Browseable

Automatic printers are an annoying feature of Windows when there are printers you don't want users to choose. Usually I just tell the Windows side not to automatically add printers it sees on the network.

On XP, click Start, click Control Panel, Appearance and Themes, and then Folder Options. Click the View tab. Then In Advanced Settings, unclick the Automatically Search for Network Folders and Printers box.

To shut this off in Visionfs, use the Profile Editor, select the Master Printer share and uncheck both Active and Browseable. You can then set individual printers that you do want seen to be both Active and Browseable.

You can also have Visionfs share a printer using a different name from the Unix queue. Just select New Shared Printer, make the Share Name whatever you want itto be and point it at a Unix printer.

How can I add a formfeed or other control to jobs sent to a Visionfs printer?

Visionfs can create local printers that pass data to shared windows printers, but it's not easy to modify the interface they use.

You can do this with a virtual printer as described
at /SCOFAQ/scotec7.html

Create a printer that adds the \014 or whatever else you need, and have
it pass its output to the Visionfs created printer.

You can use the "dumb" interface to do it, wrapping part of it like this:

shift; shift; shift; shift; shift
# add this opening bracket
while [ $i -le $copies ]
        for file in $files
                0<${file} eval ${FILTER} 2>&1
                echo "\014\c"
        i=`expr $i + 1`
# add this closing bracket and the pipe to lp
} | lp -dvisionprinter

Visionfs Broadcasts

Visionfs broadcasts its presence and will appear in every workgroup on the network. That's all or nothing: everywhere or nowhere. You can turn off Windows Naming ( Profile Editor -> Server Properties -> Advanced -> Disable Naming). Users will then have to access it with \\servername or through mapped drives.

Why can't my other sub-net browse the Visionfs or Samba shares?

Because that's the way Microsoft wants it to work.

First, if all you want to do is ACCESS the shares, you can, even though they don't pop up in Network neighborhood. You'll need a \WINDOWS\LMHOSTS file, and all it needs in it is something like this: mysmbserver #PRE

For NT, it's "\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS" (assuming your system is in \WINNT)

The "#PRE" is not a comment, it needs to be there. With this in place (and you probably need to reboot), you can do Start->Run, type \\mysmbserver and, all other things being equal, it will pop up.

You could add "net use x: \\unixserver\sharename" to the auotoexec.bat.

I have a more complete example of configuring a Windows machine on another subnet here.

But if you want to browse across sub-nets, you need more. Microsoft wants you to put in an NT server on the subnet's LAN; you can do it with a Unix/Linux machine running Samba and get the same benefit.

See Cross-Subnet Browsing in the Samba HowTo Guide.

Can you run Visionfs across a VPN or the Internet?

Sure, if your routers will pass the port 139 packets. I did this once over a VPN to a branch office back in the days of very poor and very asymmetric internet connections. It was just this side of unbearable, but most VPN access was just as bad so they got used to it.

Bridging vs. Routing

When you connect two networks, you have two basic choices: bridges or routers. If the networks are small, and the connection is not low speed, then a bridge makes sense because it just passes every bit of traffic to both sides: the bridge really joins the two networks together transparently.

But that strength is a weakness if the networks are large or the link between them is slow. I have used bridging over 56K when there was just one machine at one end and two or three at the other, but if you get much beyond that, you realy want to use a router. A router will only pass packets that actually need to be passed. That can introduce problems for Windows networks though. Windows browsing relies on broadcasting, and broadcasts are not passed across routers. That means that one side of the router can't see NetWork Neighborhood on the other, and vice versa.

There are a number of ways to solve this. Many modern routers specifically support sending netbios broadcast packets - the router looks for these and passes them to the other side. Machines can be configured to use LMHOSTS files which tell them the addresses of other machines: see above.

You will have a sample file (LMHOSTS.SAM) in \WINDOWS or for NT, it's "\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS" (assuming your system is in \WINNT)

Here's an example that happens to use an NT server for validation but the SCO server is running visionfs:        NTSERV1  #PRE    #DOM:THISDOM        "THISDOM        \0x1b"  #PRE        SCOSERV1        #PRE
Read the lmhosts.sam file carefully..spacing is critical on that 0x1b line.

You can also run a WINS server and point machines at that. It will track and update Network Neighborhood information for both sides. Your router may refer to ths with different phrases: "ip helper-address" on Cisco, for example. Individual machines may be pointed at WINS too.

Somebody left this set for plain text passwords!

Yeah, because it was probably configured back when early Samba-like systems couldn't grok Windows encrypted passwords (early Windows didn't have that either).

Because of that early fault, I'd find systems set up for plain text plasswords many years after any need to do that had passed. Undoing it all of course required reversing settings at many machines.

Remember this?



Fun times..

How do I convert Visionfs to encrypted passwords?

Old versions of Visionfs could not handle encrypted passwords. Current versions can, and you should use this feature.

If you have clients using plain text passwords you do not have to change those- the server will accept both plain text and encrypted passwords.

First run the visionfs setup program:

 /usr/vision/bin/visionfs setup

Switch to Visionfs (encrypted) passwords (or pass the whole problem off to an NT server).

That will offer to run the password wizard. If it doesn't, or if you want to run it again, do:

 /usr/vision/bin/visionfs password --wizard

Here you can choose some automatic passwords. For example, you can start by making the passwords the same as the login name- so "sam" gets "sam" as a password.

The wizard lets you edit a file of names and passwords before it finishes. You also can change passwords at any time; to change Sam's password to "8y5fg" you can:

 /usr/vision/bin/visionfs password --amend sam 9y5fg

Windows 2000 and XP have a feature called "digital signing":

(So does 2003: https://support.microsoft.com/kb/555652 Microsoft moves stuff around a lot - if the link doesn't work, just search "Digital Signing" on their site) which is apparently turned on if the server is functioning as a domain controller. Samba and other non-Microsoft SMB products don't support this yet though Samba does have it in the 3.0.0 beta: https://us1.samba.org/samba/whatsnew/samba-3.0.0beta3.html.

Visionfs is only licensed for the number of users licensed for SCO

Well, not precisely. You could specify "soft" or "hard" licensing:

* With soft licensing, users can connect to the VisionFS server even if the
number of concurrent users has reached the limit defined by your VisionFS
license number.
* With hard licensing, users are denied access once the limit has been

You might wonder why people didn't use Samba instead. The reality was that early on, Visionfs actually was the superior choice.

This history of Visionfs talks about the features and design decisions for Visionfs.

Visionfs was not just a SCO product. SCO bought Visionware in 1994; they were already making products for major Unix platforms. Visionfs could run on Sun Solaris, SunOS 4.1.x, HP-UX, IBM AIX 3.2.5 and upwards, Digital UNIX 3.x, SCO UnixWare 2.x as well as SCO Openserver. I think Sun owns it now. At one time you could get it from Tarantella.com, but I think that may be gone also.

To see connections, try this:

/usr/vision/bin/visionfs status | grep -v "no files open" | more

Opening documents can take a LONG time

Indeed. Some apps try to open a LOT of files and of course each attempt consumes round-trip network time. This newsgroup post described a situation where opening a shared file with Notepad took one second, but opening the same file with Word took 60 seconds!/

Windows networks can be slow anyway. Anything misconfigured just made it worse. You could to force Visionfs to be the Master Browser with:

/usr/vision/visionfs/bin/visionfs election workgroup_name

If it didn't win the election, it would at least tell you who did win and maybe you could convince THAT machine not to be the Master.

As Samba improved, many Visionfs users switched and usually found it to be faster (though network confusion will mess up Samba equally well, of course). Some SCO users insisted that the opposite was true, so who knows?

Many others switched to Facetwin, which did everything Samba and Visionfs could do and more.

The lock daemon dies

Ayup. We used to run something like this from crontab:

ps -eocomm |grep -q vfslockd || /usr/vision/bin/visionfs start

I did something similar to check "/usr/vision/bin/visionfs", though I don't recall now hat "bad" output was.

Can Visionfs mount Windows shares on Unix?

Yes. See 'clientadmin' and 'client' commands.

This is a multi-step procedure that requires one of the newer versions of Visionfs (Samba has similar capabilities).

First: you have to export a NFS file system. That's as simple as doing this:

 mkdir /mynfsdir
 echo "/mynfsdir" >> /etc/exports
 exportfs -a

Next, run /usr/vision/bin/visionfs clientadmin --setup

If you want individual users to determine their own access to Windows shares, you are done: just have each user run /usr/vision/bin/visionfs client --wizard

However, if you want to setup a global spot that anyone can access, follow these steps:

As root, run

 /usr/vision/bin/visionfs client --unixperms 755

Use whatever permissions make sense for your system, of course: 755 gives everyone read access.

Next run /usr/vision/bin/visionfs client --wizard". Use the D (domain password) choice- even if you do NOT have NT domains. Assign a password (most Windows shares won't have a password, but assign it anyway), say "Y" to install the settings, and then choose "Q" to quit.

Now create symbolic links pointing at the machines you want to give access to. For example:

 ln -s /smb/root/compaq /Compaq

This gives access the the "compaq" machine (assumong you ran the clientadmin with the default to use /smb as your share directory). Any user simply cd's to /Compaq to gain access to the shares, and

 tar cvLf /dev/rStp0 /Compaq

will archive whatever resources are shared from that machine.

If you are running a domain, it's usually easiest to point Visionfs at the NT server for authentication - visionfs setup

A client can share a floppy drive so that an app can write to that, too.

Can Visionfs use a WINS server?

Sure. The Visionfs docs (which are easily found on the web in pdf format and are also on the server itself) more than adequately cover configuring it to be either a Wins server or a client of another server. You just run "profedit" logged in as the Administrator on a Windows machine, click Server Properties, and click the Wins tab, the "Register with these Wins servers" (or something close to that).

If you don't know who the Visionfs administrator is, login to the Unix box as root and run "/usr/vision/bin/visionfs status" or, if you need to change the admin, use "/usr/vision/bin/visionfs setup"

You can map a Windows name to a Unix name if you do change the admin. Let's say you want to use your Win2000 machine where you login as Fred with the password "foobar8". You can tell visionfs setup (on Unix now) that "fred" will be the admin and that the Unix name of fred is root. You would then need to change root's password IN VISIONFS (you aren't changing the unix login) by doing:

/usr/vision/bin/visionfs password --amend root foobar8

Notice that you use "fred"'s password here.

Then over on Windows, Network Neighborhood, find the Unix box, drill down to Visiontools, and run "profedit" to set Wins.

Samba is much easier- you can do everything by editing text files on the Unix side.

Can Visionfs convert line endings?

Yes. In the Profile Editor, select Vision Tools, then the Files tab, and click the Line Ending box. Here's the cut from Help describing it:

The options on the Line Endings dialog let you specify whether VisionFS converts line endings in files. Windows and UNIX use different styles of line endings in files. If a Windows user views a file saved from UNIX, or a UNIX user views a file saved from Windows, the user may not see line breaks in the correct places, or may see spurious characters at the end of lines. Converting UNIX-style line endings to Windows-style (and back again) solves this problem. VisionFS converts all files whose filenames match an entry in the list. VisionFS converts line endings from UNIX-style to Windows-style when a user reads the file, and from Windows-style to UNIX-style when a user writes the file. You can use the wildcard "*" to match multiple files. The wildcard can appear anywhere within the list entry. For example, if the list contains the entries *.txt and *.html, then files named report.txt and index.html would have their line endings converted.

You probably DON'T want "*.txt" converted.

Can Visionfs do roaming profiles?

Ayup. From the docs:

Network logon services let you configure what happens when Windows users log onto the network. When you enable network logon services, users Windows profiles (personal Windows settings, such as desktop icons and program groups) are stored centrally, on the VisionFS server. A VisionFS server can use one of its server names to provide network logon services to all the Windows PCs in a particular workgroup.

Once you've configured the VisionFS server and users PCs correctly, then whenever a user logs onto the network from a Windows PC, Windows retrieves their profile and user environment information from the VisionFS server. Retrieving profiles from a central location like this is called roaming profiles. Roaming profiles let users log onto different Windows PCs, yet always see the same, consistent Windows environment: the same icons on their desktops, the same applications started, and the same drive letters mapped.

Notice the .vfsclient file in users home directories - it's a text file that looks like this:

## This configuration file is used by SCO VisionFS.
## DO NOT edit this file by hand. This file is stored as UTF8, not ASCII.
## If VisionFS reports that this file is corrupt, use the visionfs command
## to fix it.

How can I send WinPopup messages to Windows machines?

John Hemo provided this:

VisionFS: use 'visionfs message' (this will show you the command arguments and syntax)

Samba: use 'smbclient -M {NetBIOS name}' to send messages.

At one time, I had written a shell script to assist me with the VisionFS command, it acted a bit like an email client, prompted me for NetBIOS or user to send to, and then let me type/edit a message before sending.

See Perl WinPopUp for a perl script which allows you to announce whatever you choose to every PC client currently connected to a Samba Server.

Of course, if the recipient isn't running WinPopup, this info won't help.

Visionfs licensing expires message

The other day a customer called saying that his Windows machines couldn't print to SCO printers. He runs Visionfs, which needs restarting every now and then, so I asked him to run "visionfs restart". He replied immediately "I already did. It won't start".

Hmmm.. probably netbios running or something silly like that. I sshed in to check.

# visionfs start
Starting SCO VisionFS 3.1 from /usr/vision/visionfs...
No licenses were located so VisionFS ran as a 30-day evaluation.
The evaluation period has run out. Contact SCO to obtain a valid license,
or uninstall VisionFS now.
        /usr/vision/bin/visionfs license
when you have a valid license key.

Huh? That was a new one for me. I looked around, saw nothing out of the ordinary. For the heck of it, I ran "visionfs setup" and ran through it as though I were changing something but actually leaving it as it was. Happily, that fixed the problem. Visionfs now ran, and could be stopped and restarted without complaint. I've never seen that before, but I did later find a TA that suggested this procedure for similar symptoms.


If you need a simple and pretty fair terminal emulator, consider the Termlite product. If you open the readme file in the Termlite folder on the CD (either locally on the PC or through the Visionfs share), you'll find the license key to use (on 5.0.5 it is the same as the Visionfs license). You can run the setup.exe program over the net or locally. Recent versions don't install correctly on Windows; you need to copy "termlite.no" from the share to the Program Files/Vision/Termlite directory.

Termlite can take options: -host, -port, and -proto (telnet | tcp/ip | vtp | netbios), which means you can have different shortcuts for different purposes.

If you can't get it to install, you might be able to run it directly from the server; just make a shortcut that finds it in the visionfs share. Another install issue: There's a file called termlite.no in the Termlite share (contains the license key). You have to copy this file in your Termlite folder (C:\Program Files\VISION\TERMLITE by default).

Windows 7 and Vista

These are problems. You may be able to fix it by running in the "XP Compatible" mode or by running gpedit.msc and changing Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options. But even if you can, that's a stopgap: this is a dying horse. Get off it.

See also Printing to Windows Printers

Got something to add? Send me email.

(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

-> All about Visionfs on old SCO Unix


Inexpensive and informative Apple related e-books:

Are Your Bits Flipped?

Take Control of IOS 11

Photos for Mac: A Take Control Crash Course

iOS 8: A Take Control Crash Course

Take Control of the Mac Command Line with Terminal, Second Edition

More Articles by © Anthony Lawrence

Tue Aug 27 18:45:40 2013: 12295   MichaelRoesner


We had a recent problem with Visionfs not showing shares.

I pulled a log from the Unix server from /usr/vision/vfsdata/logs directory. Here is what the log said when we couldn't get in.:
2013/08/12 08:37:18.450 log/logging/start
2013/08/12 09:01:07.300 session/authentication/failure
user2 account locked
2013/08/12 09:01:07.320 session/authentication/failure
user2 account locked

We figured it out. Here’s an example of what we did:

We looked at our visionfs password list. People who could login WERE NOT on the password list. People WHO COULD not login were on the password list.

So we removed the people (usernames) from the password list and they can login now.

Even though their passwords were removed they still can't get to the visionfstools folder or any other folder except their own.

So we ran this command: /usr/vision/bin/visionfs password --list

Then we ran this command: /usr/vision/bin/visionfs password --remove user2

The effect was immediate. I could get into the user2 folder on the SCO box.

We then mapped the drive.

Rebooted Windows 7 to make sure the mapped drive stayed and it did.

Wed Aug 28 18:00:51 2013: https://bcstechnology.net12297   BigDumbDinosaur


Gosh, this brings back memories. It's been nearly 10 years since I last configured a VisionFS server. We started moving clients off VisionFS and on to Samba in 2001 and by 2004 we had converted all our clients to Samba 3. One reason for doing this was the "Linux stole our code." lawsuits that were ultimately SCO's undoing. However, significant was that VisionFS couldn't act as a PDC, which was a feature that some clients wanted.

VisionFS was straightforward in setup and administration and (almost) always worked. I used it on our office file and print server until early 2005, at which time I switched it to Samba 3.

Tue May 20 16:14:10 2014: 12470   Mark


My SCO Vision has been running for so many years with no problems, that I no longer know how it is configured on the box or how to trouble-shoot it. Information on the Internet is scarce too. Basically, any attempt to connect with SCO ODBC comes up with:

"Unable to connect to data source. (No such process: Server program not registered with portmapper.)."

I was looking to start visionfs after reading your article, but there is no visionfs file. All the vision files appear to be in /usr/local/vision/bin but no visionfs and I'm absolutely certain no-one has been on this server and deleted it.

At the moment, I'm thinking reboot, but wondered if you might have a none reboot solution?

Tue May 20 16:17:36 2014: 12471   TonyLawrence


Sorry, it's been way too long since I've even seen Visionfs. I don't remember a thing about it :(

Tue May 20 16:20:13 2014: 12472   Mark


That's my problem too Tony! It's been running happily for over 10 years and now this!

Hopefully, a reboot will sort it out.

Thanks for replying though.


Printer Friendly Version

Have you tried Searching this site?

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us

Printer Friendly Version

Be respectful to your superiors, if you have any. (Mark Twain)

Linux posts

Troubleshooting posts

This post tagged:






Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode