From: russur@convex.com (Russ Urquhart)
Subject: PC-NFS 4.0 & Windows 3.1 & Xvision 4.0 - A Solution
Summary: A solution for "Can these all work together?"
Keywords: NFS,Windows, Xvision
Organization: Engineering, CONVEX Computer Corp., Richardson, Tx., USA
Date: Thu, 16 Apr 1992 18:26:05 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

I want to thank everyone who sent personal mail, either with what they have
learned about putting these products together, or with comments requesting
info if I found any, since they were going that path as well.


Well, here goes:

My question was whether, since Windows is now 3.1, and NFS is 4.0, and Xvision
hasn't changed, these products would all play nice together? If not, what
could I expect, what would play nice, which should I install first, etc.

I contacted both Sun, and Unipress (tech support for Xvision). (I figured that
even if I COULD get in touch with a Microsoft rep .re Windows 3.1, he'd just
tell me it was the apps fault.) The first that I heard back from was the
product manager for NFS from Sun. He assured me that NFS 4.0 had the highest
compatiblity and was totally compatible with products that had run with
version 3.5. IF a product didn't work with NFS version 4.0, then it was the
fault of THAT product and not NFS 4.0! The Unipress tech support person that I
talked so, and since, Cynthia Roe, at first told me that Xvision 4.0 (current
version) did work with Windows 3.1. She wasn't sure about NFS 4.0. There was a
work around to get Xvision to run with Windows 3.1, however. To install it,
you needed to load Windows 3.1, then REINSTALL Xvision 4.0! She acknowledged
that this was a pain, but assured me that it would work.

So here I was, what do I install first? I installed NFS 4.0 first! Using the
commmand line install is very fast and efficient. I recommnd this process with
the following points, however. When you do this, NFS updates both your
autoexec.bat and config.sys BUT, IT DOESN'T TELL YOU THAT IT DID THAT! This
really isn't a big deal, I knew to look there before I rebooted, but just be
aware! (Also, If you have a PATH= statement in your AUTOEXEC that entends over
one line, NFS will only write to your new AUTOEXEC.BAT file the FIRST line it
finds! NFS writes the old files to AUTOEXEC.OLD and CONFIG.OLD)

Another gripe to Sun, in all of the five, count em 5, pieces of documentation.
Installation through Reference, there is not a SINGLE occurrence of the Sun
help/Tech support line! Being a tech writer, I looked through all the
documentation several times. (If it is indeed there, please someone let me
know here it is!) I had to call the sales rep in Mass. to get the number. (I've
since wrote that number in the front of the book.)

After Installing nfs, I installed Windows 3.1. This installation actually went
much smoother that I expected. I did the express installation and was up
without a hitch! I started Xvision and it hung tighter than a drum! Even
ctrl-alt-del key sequence COULD NOT bring Windows back. I had to do a hard
boot! (All this happened to me on a Saturday afternoon, I had a great
Saturday!) Anyway, monday I received a fax from Xvision Tech support stating
that to get Xvision to run under 3.1, I needed to not only REINSTALL Xvision,
I needed to change the network configuration in WINSETUP to DEC Pathworks 4.0.
Once I did this, Xvision did start, and worked fine. Oh, by the way, the fax,
also stated that the forthcoming new release of Xvision (4.1) scheduled for
June, WOULD NOT support NFS 4.0. It probably would support NFS 4.0 in a
release after that, but NOT in the forthcoming one. I didn't know what to do
at this point, because it seemed to kind of worked! 

I was kind of bummed because, since I had changed to the DEC Pathworks 4.0
network driver, I was unable to use the new drive/printer configuration tools
under Windows. I called Sun tech support ( I had the number now !
1-800-872-4786) The tech that called me back was VERY knowledgeable and
helpful! He told me that I could just install NFS again over itself, and I
would update the proper Windows files. To use the configuration tools, you
need to load RTM before going into Windows. According to him, this is all it
really does. (Great, another TSR, thats big and takes up memory, but it DOES
work!)

I was all prepared to lock up Xvision, but I just wanted to see if, since RTM
was loaded, if the DEC Pathworks 4.0 driver would/could use the configuration
tools. I almost fell out of my chair when Xvision WORKED WITH NFS 4.0!!!!!

And its been working ever since (approx. 3-4 days). The trick for people
installing these configurations, to make it the easiest install, is to go as
follows:

	Install Windows 3.1
	Install NFS 4.0
	Try loading Xvision to see if it locks up (optional)
	In Windows 3.1, change network configuration to DEC Pathworks 4.0
	Load Xvision, and make sure all things work!
	Leave Windows 3.1
	Reinstall NFS 4.0
	Load Windows
	Load Xvision, and see if it works!? It should!

Thanks for everyone's help, if I can be of help to anyone please let me know!


Russ
Newsgroups: comp.protocols.nfs