WHAT IS THIS DOCUMENT?

This is the HTML version of part 2 of the FAQ file for the Cello program. It contains information on configuring Cello. See part 1 for more information. Also available is a plain text version of both parts of this FAQ. Look for it to be posted about the same time as this one.

LIST OF QUESTIONS

Definitions

Setup

General

Complaints

* - Answers in part 1 of FAQ

Q2.1 What do I need to use Cello?

If you try to run Cello under MSDOS, you will be told that this program requires Microsoft Windows. It is telling you the truth. You also require a connection to a TCP/IP network, usually the Internet, and a WINSOCK.DLL compatible with that connection.

Actually, you could use Cello without a connection to a TCP/IP network or WINSOCK.DLL if all of your hypertext links point to local files. You'll need to change the CELLO.INI file so that LocalOnly=yes is in there. Note that you must use an editor to change CELLO.INI directly, since that option can't be changed from the menus in Cello.

Q2.2 What viewers should I use?

There is no right answer to this question. Use whatever works for you, and practice tolerance on all those ignoramuses that haven't made the same informed choice you have.

For convenience, a collection of viewers has been prepackaged for you and is available for FTP from ftp.law.cornell.edu, /pub/LII/Cello/viewers.zip.

To help you make sure you have the right choice, here is a list of viewers that have been recommended by CELLO-L readers (we are always soliciting more opinions, so write in with your choices):

IMAGES (gif, jpg, etc.) - There are all kinds of GIF and JPEG viewers available, with many different features. The most important feature when using Cello is generally the speed of decoding. GV057 is a fairly good package that comes in the VIEWERS.ZIP file. It can handle both GIF and JPEG formats, along with a number of others. Another choice is LView. It too can handle a variety of formats, including GIF and JPEG. It can be found at the ftp.bio.indiana.edu FTP site, in /util/ibmpc. The most current version at the time of this writing is LVIEW31.ZIP. WinGIF is another popular choice, and is available at oak.oakland.edu, in the /pub/msdos/windows3 directory. The most current version is WINGIF14.ZIP. It can only handle GIF files, but there is another program called WinJPEG that handles JPEG files as well as GIFs. It is available in the same place as WinGIF. The most current version is WNJP243.ZIP.

SOUNDS (wav, voc, au, etc.) - The VIEWERS.ZIP file contains a program, SNDTOOL, that can handle a variety of different sound formats. It also has a speaker driver so that your PC speaker can play the sounds when you are in Windows (if you don't have one already). Two other choices are WHAM, which is a sound player plus a whole lot more, and WPLANY, which is just a sound player but a very good one (see Question 4.2 for a caveat, however). The most current version of WHAM is WHAM131.ZIP, and of WPLANY is WPLNY09B.ZIP. And, of course, there is the MPLAYER.EXE program that Microsoft supplies with Windows for playing WAV files. It doesn't play any other types of sounds, however.

ANIMATIONS (mpg, avi) - Microsoft has provided a new MPLAYER.EXE that can handle AVI files as well as WAVs. It is installed using a program called MFWRUN. There is also a program called VIDVUE which will work. Look for it under the name VIDVUE10.ZIP on wuarchive.wustl.edu, directory /systems/ibmpc/win3/desktop. As for MPEG, there is a program called MFW available on ftp.uwp.edu, in the /pub/picture.viewers directory as MPEG2.ZIP. This is the latest Xing MPEG viewer and all associated video drivers. It has a problem, however, in that there are a number of MPEGs on the Web which it can't display (they display as garbage). MPEGW32 is another option. The latest version is MPEGW32E, available on wuarchive.wustl.edu in the /systems/ibmpc/win3/nt directory. It will display all the MPEGs, but there are two other problems with it. The first is that it is really written for Windows NT. It will work with Windows 3.1 and Windows for Workgroups, but it requires the installation of the Win32s extensions (which it includes). The second problem is more difficult to solve. At least with the tests we've done, MPEGW32 is SLOW! There is one known program that displays all MPEGs and is reasonably fast, VMPEG, but it won't run under Windows.

DOCUMENTS (ASCII, Postscript) - For an ASCII viewer, Microsoft provide NOTEPAD. It is an editor, but it can be used as a viewer as well. For postscript, we have Ghostscript available. Note that you will also require the Ghostscript viewer program as well, and probably a few fonts.

SERVICES (Telnet, TN3270) - Cello has its own built-in telnet client. You may prefer some element of your own, however, such as the lack of difficulty in logging in to Sun workstations (see question 4.1). If you are using the Trumpet Winsock, there are several applications which come with it including TELW, a telnet client. You may also want to consider the telnet that comes with QVTNET, most recent version QVTNT394.ZIP. Note that you must have QVTNET loaded in order to get the client to work.

Q2.3 What TCP/IP packages are available?

With the right WinSock, all you really need are packet drivers for an ethernet connection or a SL/IP driver for a modem connection. Note that the Trumpet WinSock has it's own internal SL/IP driver.

If you want a TCP/IP package, a better place to look for information is in the FAQ list for comp.protocols.tcp-ip.ibmpc. This newsgroup is ideal for finding out how to deal with nuisance problems with your particular configuration as well. It is recommended reading for anyone trying to set up a PC on the Internet.

Q2.4 What do I need to know about Cello with PC-NFS?

In fact, Cello works just fine with PC-NFS, but with a couple of conditions:

  1. You must have a version of PC-NFS (v5.0 or greater) that has WINSOCK.DLL
  2. You must have support for DNS
It is the second requirement that causes the most confusion. PC-NFS v5.1 will have DNS support built in, but until you get your copy you can make v5.0 do the job by ensuring that:

Q2.5 What about using Cello with FTP Software's PCTCP?

Assuming that you have PCTCP configured correctly for your particular machine you should not have any problems using Cello. You do need to make sure that you have the latest release of the winsock.dll for PCTCP. This file is available from vax.ftp.com in /pub/winsockapi/FTPSoftware/winsock.exe. It is a self extracting zip file.

PCTCP will work with ODI drivers. For windows, make sure that ethdrv is loaded before starting windows, and that you have added the following lines to your SYSTEM.INI file in their respective sections:

 [386enh]
 device=[drive]:[path]vpctcp.386
 [vpctcp]
 MinimumCopySpace=28
 HiTSRFenceSegment=A000H

Problems with PCTCP and Cello may include, but are not limited to:

One solution which has been suggested is to change the MAXBPs setting to MAXBPs=768. Give that a try and see if it improves your speed.

If you experience any of these, please report the specific instance to cellobug@fatty.law.cornell.edu

Q2.6 What about using Cello with OS/2?

Cello uses a very advanced method of communicating over a network (see question 4.10). The bad news is that OS/2's implementation of WinSock has bugs that only show themselves when using this method.

The good news is that IBM has come up with a solution to the problem. Call IBM Service and ask for a fix for APAR #PN52335.

Q2.7 What about using Cello with LAN Workgroup?

To get Cello running with LAN Workgroup, you need Novell's WinSock with NW3.11 as well as some bug fixes. Following the steps below will allow you to use all WinSock applications, Cello included.

You can also bring up Windows for Workgroups (W4WG) with LAN Workgroup, but you need to be aware of a couple of things. Novell uses ODI and runs TCP/IP as well as IPX over it. W4WG, however, requires NDIS rather than ODI. You can still run everything together, but you have to do a bit of fancy footwork. Here is the procedure:

Below are listed some key elements that should be in your files in order to get LAN Workgroup operating. Lines which are only required if you are also running W4WG are so marked.

AUTOEXEC.BAT

autoexec.bat                            Comments
------------                            --------
....
SET     NAME=horvaath                   Use your own name here, of course
...
:internet
lsl                                     Link Support
smc8000                                 MLID (Use your own network card driver)
odinsup                                 W4WG: ODI->NDIS shim
ipxodi                                  IPX for Netware
emsnetx                                 DOS interfacing to Netware (or netx)
:loging1
f:login                                 Login to the Novell server
IF  ERRORLEVEL = 1  GOTO loging1
wgtcpip.exe -c=i:\NET\NET.CFG           Load the TCP/IP protocol stack
telapi -SN 4                            For telnet based apps.
c:\net start                            Bring up NDIS for W4WG
....
CONFIG.SYS

config.sys                              Comments
----------                              --------
...
device  = C:\protman.dos /i:C:\.        W4WG, for NDIS protocol manager
device  = C:\workgrp.sys                W4WG interfacing
....
NET.CFG

net.cfg (for ODI)                         Comments
-------                                   --------
Link Support
 Buffers 8 8192
 MemPool 4096
 Max Boards 4                             # at least
 Max Stacks 4
#
#       NET.CFG File for SMC8000
#
Link Driver SMC8000
        Port #1 300 20                    # Board settings
        Mem #1 000CA000 2000/10
        Int #1 5
        Frame Ethernet_802.3              # Supported Frame types
        Frame Ethernet_II
        Frame Ethernet_802.2
        Frame Ethernet_SNAP
        Protocol IPX 8137 Ethernet_II

#
Protocol TCPIP
        Bind            SMC8000
        ip_address      152.66.79.129     # Your IP Addressing sceme
        ip_router       152.66.79.190
        ip_netmask      255.255.255.192   # We have Subnets
        tcp_sockets     8
        udp_sockets     8
        raw_sockets     1
        nb_sessions     4
        nb_commands     8
        nb_adapter      0
        nb_domain
#                                           only for W4WG based on NDIS
Protocol ODINSUP
        Bind            SMC8000
        BUFFERED
PROTOCOL.INI

protocol.ini (for NDIS, W4WG only)      Comments
------------                            --------

[network.setup]
version=0x3100
transport=ms$netbeui,MS$NETBEUI         # Only NETBEUI by NDIS
lana0=ms$w03ep,1,ms$netbeui

[protman]
DriverName=PROTMAN$
PRIORITY=MS$NETBEUI

[MS$NETBEUI]
DriverName=netbeui$
SESSIONS=10
NCBS=32
BINDINGS=SMC8000                        # ->ODINSUP->ODI->MLID SMC8000
LANABASE=1
Here is a list of files that you need:

(the root directory of our experimental workstaion)

 c: protman .dos     21680  92-10-01   3:11   \
 c: workgrp .sys      7268  92-10-01   3:11   \
 c: net     .cfg       815  94-01-13  12:35   \
 c: lsl     .com     17805  93-09-10  15:48   \
 c: smc8000 .com     30861  93-03-11  18:51   \
 c: protocol.ini       242  94-01-14  12:36   \
 c: odinsup .com     33515  93-03-11  18:50   \
 c: ipxodi  .com     30051  93-04-23   8:58   \
 c: emsnetx .exe     89390  93-02-17  13:43   \
(i: wgtcpip .exe     65348  93-10-14  12:55   \net\bin  from network)
 c: net     .exe    415252  92-10-01   3:11   \ .These files should
 c: net     .msg     70629  92-10-01   3:11   \ .come from
 c: neth    .msg    104570  92-10-01   3:11   \ .the
 c: protman .exe     13760  92-10-01   3:11   \ .network

Q2.8 How do I install Cello on a network so that the files are shared?

It is possible to set up Cello on a network, but there are two important things you should consider. Do you want each person to have their own CELLO.INI files, and do you want people to be able to edit their own file.

Making changes to the CELLO.INI file in the event of global changes to your network (such as your IP subnet changing) is much easier if there is only one copy, but there are problems with doing this. There is less flexibility since everyone must have the same set of options specified. No one can have a personal email address specified, for example. It has to be set to a generic address or left blank.

Whether to allow people the ability to edit their own CELLO.INI file is a philosophical matter. Regardless whether you do it or make each person responsible for their own, there are some things that must be set properly for Cello to work. In the CELLO.INI file be sure that the download directory, the cache directory, the bookmark and style files, and the email address are all either pointed at user-writable directories, or that they point to correct settings for everyone. Also, make sure that the network settings are correct.

If the CELLO.INI file is placed in a location where the Cello user has write capabilities (and it isn't flagged read only) then the user can change these settings as they please. If you want more control, use the Cello environment variable to set the location of the CELLO.INI file in the system login script (use DOS SET CELLO = [path] for Netware, for example) and do not give users write privileges in that directory.

There are similar issues affecting the Home Page. It can be set up so that every user on your network sees the same information each time they start Cello, or each person can see their own customized, editable home page.

Q2.9 What do the lines in CELLO.INI mean?

The CELLO.INI file is used by Cello to store various user configurable parameters. Cello will look for CELLO.INI in the directory specified by the CELLO environment variable. This variable is settable by adding the following line to you config.sys file:

SET CELLO = [drive]:[path]

for example:

set cello=c:\cello\cello.ini

Otherwise, Cello looks for the CELLO.INI file in the WINDOWS directory.

What follows is a typical CELLO.INI file with explanatory remarks. If you do not know the necessary information for any of these parameters you will need to contact someone at your local site for clarification.

 
[Cello]
NNTPServer=usenet.law.indiana.edu    #location of USENET news server
EMail=cello@law.indiana.edu          #Your EMAIL address (see warning below)
HomePage=g:\cello\iuhome.htm         #location of the first page Cello shows
                                     #Can be a valid URL
DLDir=c:\scratch                     #location of download directory
AutoSearchBox=no                     #Sets whether Cello will automatically
                                     #display a search box on documents with 
                                     #the ISINDEX tag.
Telnet=                              #path to external telnet client
TN3270=                              #same for TN client
WaisGate=http://www.w3.org:8001    #location of nearest WAIS gateway
MailRelay=129.79.131.8               #IP no. of SMTP MailRelay for your net
LowWaterMark=500000                  #Sets point at which cached files are
                                     #deleted from memory/disk 
BookmarkFile=c:\cello.bmk            #location of your bookmark file
StyleFile=c:\cello.sty               #same for style file
FetchGraphics=yes                    #Set this to no if using a slow connection 
LocalOnly=No                         #If Cello should use local files only and
                                     #not load network software, set to YES.
[Extensions]
ext=[drive]:[path]app.exe ^.ext         #use whichever viewer you like here
jpg=g:\pixfolio\pixfolio.exe ^.jpg      #these are examples
au=g:\wplany\wplany.exe -u -r 8000 ^.au
[Geometry]
StartupX=50                          # X position of Cello window in pixels
StartupY=25                          # Y position of Cello window in pixels
StartupHeight=200                    # Height of Cello window in pixels
StartupWidth= 400                    # Width of Cello window in pixels
IsMaximized=Yes                      # Start Cello as Maximized window?

Q2.10 How do I set up an external Telnet client?

The syntax for invoking an external client is the following:
[drive]:[path]telnet.exe #h #p
#h is the placeholder for the hostname you are telnetting to and #p is the port number.

If your telnet client doesn't support a port number on the command line, just use the #h by itself. Your external telnet will be launched when telnetting to a host at port 23, which is the default for most telnet services. When telnetting to other ports, Cello will invoke its built-in telnet.

Cello now supports TN3270 via an external application, a feature which was prompted by the appearance of a freely-distributed TN3270 for Windows (see comp.protocols.tcp-ip.ibmpc for announcements and location). Cello expects the same #h and #p parameters used in the "Use your own Telnet client" menu choice.

Q2.11 How do you launch Cello using DDE?

You can invoke Cello from other applications which support the DDE execute command. Here's how you'd do it with an MS-Word macro:
Sub MAIN
ChanNum = DDEInitiate("Cello", "URL")
DDEExecute(ChanNum, "http://www.law.cornell.edu")
DDETerminate(ChanNum)
End Sub
As you can see, the DDE service name is "Cello", the topic is "URL", and the data sent in the execute command is a URL.

OLE support and DDE client support are planned in the near future.