nbc2134@dsacg2.dsac.dla.mil (Robert F Solon) (06/01/91)
About two weeks ago I posted the following request:
"We are considering implementing Microsoft Windows on our micros.
Many of our users use PC-NFS, by Sun Microsystems, to telnet to
other machines and to print to network mounted printers.
Unfortunately, initial tests indicate that Windows 3.00 doesn't
recognize PC-NFS as a loaded network. Has anyone else attempted
to use both products simultaneously? If so, what problems have
you encountered?"
The responses have been gratifying. I received 34 responses as of
today (1 June 91). 5 were requests to forward responses I might get.
I have sent this posting directly to those responders.
Twenty-eight others offered information concerning PC-NFS and
Windows 3.00; one was a request to re-send a previous e-mail letter.
A summary of the twenty-eight responses follows.
A list of all correspondents is given at the end of the summary.
1. PC-NFS 3.0.1 is not completely compatible with Windows 3.00.
2. PC-NFS 3.5 is comptaible with Windows 3.00.
3. Paul Carroll, from Sun Microsystems, suggests the following
work-around solutions when using NFS 3.0.1. He emphasizes that
these should not be needed if running ver. 3.5:
A. The File Manager in Windows tries to read all drives,
all the way up to V:. To solve this problem (it's really more of
an annoyance, since the user can just click on Cancel to skip the
non-mounted drives), modify the CONFIG.SYS file as follows:
Change DEVICE=C:\NFS\PCNFS.SYS to
DEVICE=C:\NFS\PCNFS.SYS /d4.
The /d4 tells nfs to only allow up to four mounted drives
or printers. In this case they would be d:, e:, f:, anf g:.
B. Printers should be redirected to LPT1.OS2 or LPT2.OS2 to
work effectively. Hot keys are not supported within Windows;
however, I like to use them, so I created a .BAT file with the
NET PRINT command and then included it in every group. This allows
me to use varous Windows applications, print my documents, and then
run the NET PRINT icon to release the output from the queue. Works
pretty well.
C. Telnets should run in Exclusive mode, with 640 KB desired,
when using 386 Enhanced. In real or Standard Modes, KB required should
be set to 128K. In all modes Close Window on Exit should be selected.
4. Many correspondents basically reiterated the above suggestions.
5. Some responders have had better or worse luck with version 3.0.1.
Almost all have recommend ver 3.5 in order to best utilize windows.
6. One responder has said he doesn't have any problems with telnet;
most, however, have found some problems with it. Sun recommends that
you do not switch out of a running Telnet session; trying to do so will
crash your system. This last is true; I tried it while accessing a
mainframe, and I died and had to have another mainframe user cancel my
session before I could sign back on.
7. There were recommendations for other networks to try:
Beame & Whiteside client NFS to an RS/6000 (twice)
OS/2 1.3 with IBM's or FTP's TCP/IP package
8. One responder suggested modifying the WIN.INI file when using
vers. 3.0.1 as follows:
[Ports]
lpt2.os2=//server/printer_name_queue
I haven't tried this so I don't know if works.
9. List of responders (in no particular order):
Ralph Brown, pcad!thor!rob@uunet.UU.NET
David Giller, rafetmad@cub.oxy.edu
Vince Kovarik, vjk@sps.com
borkeles@dcs.gmw.ac.uk
Paul Carroll, pcarroll@East.Sun.COM
Ian Roberts, iroberts@pichem.adelaide.edu.au
Brian D. Howard, bdh@gsbsun.uchicago.edu
David Wright, wright@fluke.COM
Matthias Kring, kring@phibsi.pki-si.philips.de
Charles Ditzel, chas@sunup.Wset.Sun.COM
Dan Greening, dgreen@cs.ucla.edu
Tom Ranwuiler, tran@ads.com
Tim Lange, tim@cc.purdue.edu
Richard robinson, rr@isye.UUCP
Phil Ngai, phil@brahms.AMD.COM
Kim Wallen, kim@mathcs.emory.edu
Frank Greco, fgreco@govt.shearson.com
Rodrogo Lopez Serrano, rodrigol@biomed.uio.no
Dale Frye, dale@cec2.wustl.edu
James Lee Peterson, petersja@debussy.cs.colostate.edu
Peter Knight, prk@planet.by.co.uk
Jonathan Cave, cave@rand.org
Lance P. Welsh, lpw@sgi.com
Dean Grammas, dxg@cai.com
Ed van Leeuwen, Ed.van.Leeuwen@fel.tno.nl
Steve Cohen, cohen@mips2.ma30.bull.com
Michelle Neves, neves@virga.rap.ucar.EDU
10. My own conclusion is that I'm not going to use Windows to run telnets,
since it interferes with screen printing and I do a lot of that. However,
I will use it to do purely PC functions, even those for which the software
exists on virtual, i.e., network, drives. I've been meaning to see what
will happen if I telnet from a DOS shell running in Windows, but I haven't
done it yet. If you have tried this or would like to, please send me your
discoveries.
My thanks to all who responded. If you'd like a complete unedited set or
responses (headers removed), I'll be happy to send one to you.
Bob
--
Bob Solon, rsolon@dsacg2.dsac.dla.mil
Administrative Information Branch -- "We Code, You Explode!!"
Directorate of Resource Management Systems (APCAPS)
DLA Systems Automation Center, DSAC-BCC (614) 238-8256 AV: 850-8256