From: maf10@po.CWRU.Edu (Moses A. Fridman)
Newsgroups: alt.cascade
Subject: Nuclear Smurfs and 'Shroom Anuerysms!
Date: 16 Oct 1992 00:31:18 GMT
Organization: Case Western Reserve University, Cleveland, Ohio (USA)
NNTP-Posting-Host: slc5.ins.cwru.edu




		  COURTESY OF ALT.ROCK-N-ROLL.METAL.GNR,


                           CASCADE THIS!!!!!!!!







			     Quick Reference Guide

			    CWRU-PC/IP Version 1.1

	      Case Western Reserve University's Network Software
			for MS-DOS and PC-DOS computers

   Copyright (c) 1989 by the Board of Trustees of the Leland Stanford
			      Junior University.
  Copyright 1990, 1991 Case Western Reserve University.  All Rights
Reserved.
				 March 4, 1991


PURPOSE

    CWRU-PC/IP provides applications for IBM PC's, PC/XT's, PC/AT's, and
    PS/2's:

        - Mail handling with local PC commands (MAIL, MH)
        - VT100 and 3270 terminal emulation (TELNET, TN3270)
        - File transfers between PC and host (FTP, FTPSRV)
        - Access to information about computer users (FINGER)
        - Qualitative testing of a network path (PING)


PC REQUIREMENTS

    1. At least 280K of free memory

    2. MS-DOS or PC-DOS Version 3.0 or higher

    3. A hard disk (Required by mail software only)

    For additional requirements, see Unit 2 of the User's Manual.


HELP

    Help is available in the INS area on FreeNet.  Type "go ins" at any
"==>"    prompt.  In addition, you can contact the INS Help Desk by calling
    368-USER.


ALL APPLICATIONS

    Press the carriage return or enter key after each command.

TELNET - VT100 TERMINAL EMULATION

    1.  Connect PC to host with command
            C:\>telnet hostname

    2.  Log in as you normally would.

    3.  Set your terminal type to VT100.

    4.  For the VT-100 key mapping on a PC keyboard, see Section 3.1.2 of
the	User's Manual.

    5.  Log out as you normally would.  If you cannot, press F10 followed
by	"c".  If that fails, use F10 followed by "q".


    OPTIONAL FUNCTIONS: While in telnet, hold down Alt and press
        H       command summary
        A       open concurrent Telnet session
        N       switch between Telnet sessions
        L       switch to previous session
        P       pick from a list of Telnet sessions
	T       open concurrent FTP session or switch to session already
open                (In FTP, type "telnet" to switch to telnet.)
        I       Take Input from a disk file
        O       Capture telnet session in an output file
        E       execute a DOS command


    COLOR FUNCTIONS: While in telnet, hold down Alt and press
        B       change background color
        F       change foreground color
        R       change "reverse video" color
        U       change "underline" color


TN3270 - IBM 3270 TERMINAL EMULATION

    1.  Connect PC to host with command
            C:\>tn3270 hostname

    2.  Log on as you normally would.

    3.  Conduct terminal session.  Use key mapping in Section 3.2.2, User's
	Manual.

    OPTIONAL FUNCTIONS: Press Ctrl-], then --
        F8          open concurrent FTP session (1 allowed)
        F9          issue a DOS command
        F5, then F1 toggle status line off/on

    4.  Log out as you normally would.  If you cannot, press Ctrl-] then F2
to	close.  As a last resort, use Ctrl-] F10.

FILE TRANSFER PROTOCOL (FTP)

    1.  Open an FTP session with command
            C:\>ftp hostname

        If hostname was mistyped, you may try again with the "open"
command.            ftp>open hostname

	FTP is also accessible from within Telnet and TN3270; see the
Telnet	and TN3270 summaries for more information.

    2.  Log in on the host computer.  If username or password are mistyped,
	issue the "user" command and log in again.
	    ftp>user

    3.  Specify a file transfer mode.

            ftp>binary    To transfer executable or compressed files
            ftp>ascii     To transfer text files
	    ftp>tenex     Only when transferring binary data with a
			  DECsystem-20

    4.  Select the correct host directory with the "cd" command.
            ftp>cd directoryname

    5.  To send a file to the host, issue a "put" command.

            ftp>put filename
            ftp>put filename newfilename

    6.  To copy a file from the host to your computer, issue a "get"
command.
            ftp>get filename
            ftp>get filename newfilename

    7.  Additional commands

            ftp>help             List all FTP commands
            ftp>?                List all FTP commands (same as "help")
            ftp>help command     Help with command
	    ftp>!command         Tell DOS to run command
	    ftp>ls               Short-form list of host files
	    ftp>dir              Long-form list of host files

    8.  Exit an FTP session with either "quit" or "bye".
            ftp>quit
            ftp>bye


PING

    You may check the network connection to a remote computer with the ping
    command.
	    C:\>ping hostname

LOGGING IN (LOGIN, LOGOUT, WHOAMI)

    You must log in before using the mail, MH, or lpr programs.  It is not
    necessary to log in before using Telnet, TN3270, FTP, Whois, Finger, or
    Ping.

    1.  Log in with the LOGIN command.  Enter your username and password.
	    C:\>login

            login: sqf                 Your CWRUnet ID.
            Password: password         Your CWRUnet password (invisible).

    2.  When you are done using mail or lpr, log out with the LOGOUT
command.	    C:\>logout

    3.  Check your identity with WHOAMI.
	    C:\>whoami


ELECTRONIC MAIL (MAIL)

    1.  Start the mailer with the command "mail".
            C:\>mail

    2.  Get new mail by pressing "n".  Summary lines will be displayed for
all	new messages.

    3.  Select a folder by moving the grey bar with the arrow keys.
            INBOX                All new mail arrives here.
            OUTBOX               Copies of outbound mail are stored here.
            others               Create other folders with the "s" command.

    4.  Press Space or Enter to open the folder.

    5.  Select a message from inside the folder.  Use the arrow keys to
move up
	and down, and press Space or Enter to read.

    6.  Press "c" or "m" to write a new message.  Fill in the blanks with
the	editor.  Hold down Ctrl and press "x" to save the message, then
select	"s" from the "Send, List, Edit, Quit?" menu.

    7.  Press "r" to reply to a message.

    8.  Press "d" to delete the current message.  It will be marked with a
"D"	by its number.  Deletions are only made permanent when you leave a
	folder and answer "y" to the question "Delete Marked Messages?"
Until	then, deleted messages may be restored with the "u" command.

    9.  Press "p" to pick a different folder.

    10. Press "q" or "x" to leave the mail program.

PRINTING (LPR, LPQ, LPRM)

    Log in before using LPR or LPRM.  Print a file with the following
command:        C:\>lpr -Pprinter file

    Check the print queue with the following command:
        C:\>lpq -Pprinter

    To delete all of your print jobs, use the following command:
        C:\>lprm -Pprinter -


FINGER

    1.  Find out when users last logged on to host computers, when they
last	read their electronic mail, and other information with command
	    C:\>finger user@hostname

    2.  Get a list of users currently logged on to a host with command
            C:\>finger @hostname


SOFTWARE SERVERS (NOVELL NETWARE)

    The CWRUnet software libraries are available from special-purpose
servers    accessible via the Novell NetWare protocols.  To access these
libraries,    use the following command:

	    C:\>novell south

    This command will automatically connect your computer to the South
server,    starting the menu system.  Note that it is not necessary to run
the TCPIP
    program before using the software libraries.  In fact, it is often best
to    unload the TCPIP program before using the software servers.  To do
this,    use the following command:

	    C:\>tcpip -k

    (This command should be issued before the "novell south" command
above.)

TItle:     Jimi Hendrix, God of Guitar

Note:     Please edit minimally

I am one of those many who have sold their souls to a record club,  lured
by promises of truckloads of free
CD's .  Recently I got a disc called Jimi Hendrix: Live at Winterland, and
I have not been able to take it out
of my CD player for weeks.  BUY, ORDER, STEAL THIS ALBUM, YOU HAVE TO HAVE
IT.
This is a digitally remastered and remixed recording ot The Jimi Hendrix
Experience playing at Winterland, San Fransisco in 1968.  It sounds great,
probably better than any other live album I have ever heard.  In fact, the
sound quality is better than many studio recordings.  The songs on it are:
Fire, Manic Depression, Sunshine of Your Love, Spanish Castle Magic, Red
House, Killing Floor, Tax Free, Foxy Lady, Hey Joe, Purple Haze, and Wild
Thing; total time is 71:40.

This particular CD proves Hendrix' deity status.  Besides his infamous
stage presence, consisting of such 
things as playing his guitar behind his head, picking it with his teeth,
setting it on fire, and the old standby, 
smashing it to bits (don't forget he played it lefthanded, upside down, and
strung upside down),  Hendrix shows off his technique and style.  The solos
are passionate, soaring, and gut wrenching in their performance.  The other
band members, Noel Redding on bass and Mitch Mitchell on drums are also
extremely good.   Their parts are perfectly done, timed and perfomed to
compliment and
interact with Hendrix' playing.  

The first song, Fire, is played about twice as fast  as the recorded
virsion, but it is a minute longer; this is
because of an additional bridge thrown in the middle of the song, allowing
Hendrix to do more soloing than 
in the original . In between songs, Hendrix talks a bit, joking around or
just introducing the next song;  This is a bonus, because I had never heard
him talk before,  much less about his songs.  The next big surprise is
Sunshine of Your Love, a cover of the Cream's classic.  They play the song
without the lyrics, "an instrumental  jam scene", in tribute to Cream, who
just broke up.  The song sounds better than when Cream played it
originally, and really rocks with Hendrix various little quirks and
improvisations.
Red House is just unbelievable.  The original is something like three
minutes long, and this live version is 
stretched to 10:58, unbelievable for a "little blues song".  It is just one
huge blues solo, from beginning to end, and I would guess that it is
improvised as well.  Hendrix takes a twelve bar blues progression and 
wrings out something amazing, the best blues I have ever heard.  Hendrix
goofs up the little bit of singing 
somewhat,  though: "if my baby won't love me no more, lord I sure know her
big fat sister .... wait let me say it right... her sister will".   

Hendrix' best known songs, Hey Joe, Purple Haze, and Foxey Lady appear at
the end of the concert.  Hey Joe is played much differently than the studio
version, with a longer intro and various other little changes.  Hey Joe
launches right into a scorching version of Purple Haze, the definitive
Hendrix song.
The last song, Wild Thing, is the same one that signalled the destruction
of amps and the burning sacrifice
of Jimi's guitar at the Monterey Pop festival.  

Like I said, you need this CD.  Like a bad drug, your blood will boil and
your brain will shut down if you
don't hear it.  Any classic rock fan, any serious music fan, and any guitar
player simply cannot live without it.

 
Release 1.25 includes the following changes and bug fixes:

internals - Reported 8/5/92 by Rob Browarek.  Fixed 8/5/92 by sct.

    Version 1.24 was accidentally released with an experimental kernel.
    It must be replaced with 1.25 AS SOON AS POSSIBLE.  Continued use
    of 1.24 could cause significant problems to your network neighbors.

    Fortunately, 1.24 was in circulation for all of 3 hours before the
    problem was noticed by Rob Browarek.

Release 1.24 includes the following changes and bug fixes:

telnet - Requested 3/92 by Library Information Technologies.  Approved by
    R.K. Neff and J. Gumpf, 3/92.  Implemented 3/23/92 by sct.

    Telnet now supports the VT-102 printer functions.  It understands the
    printer controller and auto print modes, as well as the print- screen
    and print-line commands.  It understands the print extents option, and
    gives an intelligent reply to the device status request for the
    printer.

    In order to enable printing, type Alt-P and enter the printer device
    name.  For example, most users would simply enter "lpt1" or "prn".
    The device name takes effect in only the current telnet session unless
    you use the Alt-W command to save it for future use.

    Once you have a printer device configured, the remote computer has
    full control over when it will be used.

    There are several tricks possible with the printer option.  First, it
    is possible to "fake" a printer with a disk file.  This is useful if
    you do not have a printer or if you want to save data for later use
    without wasting paper.  To do this, type Alt-P and enter a filename
    instead of a printer device.  As usual, typing Alt-W afterwords will
    save the new setting for permanent use, if desired.

    Another trick to be aware of is that different simultaneous sessions
    (created with Alt-A) can have different print devices or files.  By
    typing Alt-P in each one, you can make the "printer" output in each
    session go to a different printer or file.

    Finally, telnet only supports two of the three possible responses to
    the printer Device Status Request command.  It will tell the remote
    host "Printer Not Present" if the Alt-P configuration is not correct,
    or "Printer OK" if it has what it thinks is a valid Alt-P setting.
    It never sends the "Printer Busy" code.  Instead, it just waits until
    the printer stops being busy.

telnet - Reported years ago by Ernie Ellenberger.  Fixed 3/23/92 by sct.

    Telnet's little-known screen copy command (Alt-S) has been fixed so
    that it no longer puts in hundreds of extra spaces.  This should make
    it a much more palatable command.

    This command makes it possible to save a copy of the screen to a
    file.  Type Alt-S, then enter the name of the file.  The screen image
    will be appended to whatever is already in the file, which makes it
    possible to save several screen images to one file.

    For the power users, it is also possible to use this command to
    do printer screen images without the extra garbage printed with the
    Print Screen (PrntScrn) key.  Type Alt-S, then the name of your
    printer, typically lpt1.  Telnet will send a copy of the screen to
    the printer, skipping the clock line at the bottom.

whoami - Reported 3/31/92 by William P. Taylor.  Fixed 3/31/92 by sct.

    Whoami was reporting a mailbox computer of "pop.cwru.edu" when it
    should have been using "po.cwru.edu".  This turned out to be a
    simple typo.  (It was my keyboard's fault, honest!)

tcpip - Known to be needed for a long time.  Implemented 7/27/92 by sct.

    Implemented a simple exponential backoff algorithm.  The delay between
    retransmissions now rises exponentially while errors are occuring,
    instead of linearly.  This is a neighborly thing to do when dealing
    with congested network links.

    More importantly, I also implemented a linear decrease of the
    retransmission timer.  Previous versions would increase the delay
    but never decrease it!  This should significantly improve
    performance.

    The timer grows exponentially but decreases linearly so that we
    will oscillate on the "good" side of the ideal retry rate when
    congestion occurs.

    This won't be as useful as it could be until I also add Jacobson's
    Slow Start algorithm and Karn's connection-timing algorithm, but
    it is a step in the right direction

                          Abstract

        To utilize the full potential of the computer being
used within the General Motors sponsored Engines Laboratory
at Case Western Reserve University, software that
incorporated real time processing of data and could be used
on any of the engine set-ups was developed.

                        Introduction

        The software used with computers should use the
computer's full potential while at the same time be flexible
in nature. This is especially true for computers that are
used in any type of laboratory setting. The exeperimentor
wants to be able to use one software package for as many
tests as possible.
        At the GM Engines Laboratory located in the Mechanical
and Aerospace Department at Case Western Reserve University
problems were encountered during the testing of engines. The
problems focused around the inability to read the top dead
center (t.d.c.) of the engine simultaneously with the
pressure of the main cylinder and the rigid structure of the
software that was being used which affected the calculation
of engine efficiency and ability to modify the tests being
performed respectively.         
        These problems were solved by purchasing another high-
speed voltmeter which allows the simultaneous reading of the
the t.d.c. and pressure signals and by rewriting the data
acquisition software in Turbo Pascal as opposed to
interpretative BASIC (the language previously used).

Improvements
        The high-speed voltmeter was a necessary addition to
the hardware used in the engines laboratory. Without this
addition there was no simple way to modify the existing

hardware or software to allow the simultaneous collection of
the t.d.c. and pressure signals.
        There were several reasons to use Turbo Pascal instead
of interpretative BASIC, all of which center around the way
that Turbo Pascal allocates its memory (see Figure 1 in
Appendix A). This allowed for one large program to be
written instead of several small programs chained together
and allowed for the program to run compiled, which helped
improve the data processing time.

                        Possible Modifications

        The program that has been created handles twenty
thousand data points. This number could possible be enlarged
through the use of dynamic arrays.
        Another modification that could be made to enhance data
collection is to collect data from the multiplexer over a
time interval and then provide a means of analyzing this
data.
                        Main Screen

        When the program is initially run the first screen that
is viewed is called the main screen. While in this mode the
user views a list of options which looks like this:
                         (1) Control Panel
                         (2) View Saved Data
                         (3) Select Throttle Controller
                         (4) Stop the Program
                         (5) Help

             Press the key corresponding to your choice.


        This menu helps to separate the two main functions of
the programs. The first function being data acquisition and
the second being data viewing and manipulation. Also through
the use of this menu the user can designate which throttle
controller to use. The user will have to do this before
he/she is able to manipulate the throttle via the control
panel.
        

                        Control Panel


        The control panel is accessed by choosing option number
one on the main menu. Once the control panel has been
chosen the user will see (working from the top of the

 screen to the bottom) a list of options, a channel list 0-
19, and then an open space which is used for the plotting of
the pressure/t.d.c. data.
        The options the user has to choose from are:

(1) Read/Display Analog Data    (2) Save Analog Data
(3) Collect Pressure/Analog Data(4) Exit to Main Menu
(-) Decrease Throttle           (+) Increase Throttle

        By choosing option 1, Read/Display Analog Data, the
signals that are being sent to the HP3258a Controller are
read and then displayed under the appropriate channel
heading. The reading and displaying of the signals is
continuously updated. This updating of information
continues until the user chooses an option other than
decreasing or increasing the throttle. When the user
configures the channels to be read, the channel number
should be replaced with a title (ie Exhaust (C) or Torque
(N) ). Notice that the units are displayed beside the title;
this is allowed because the user can have the voltage
converted to the correct units via a user supplied
conversion factor. It should be noted that this option does
not save any data; it only displays what is being read on
the configured channels.
        Note: Using option 1 does not affect the other options.
        Option 2, Save Analog Data, allows the user to save one
"set" of signals being sent to the multiplexer. Once the
user has chosen option 2 the screen will change, a list of
all the files in the current directory with a suffix of
'dat' (ie *.dat in dos notation) will be listed and then a
prompt asking for a filename will be given. In order to exit
this screen an appropriate filename (ie one that does not
have any suffix and is dos correct) must be entered. Below
is a sample file created by using option 2:

Example of a data file created throught the use of option 2:

Analog Measurements Listed Sequentially
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
22.34
0.00
0.00
0.00
0.00
19.25
0.00


        The user can use this program to view the files. By
using the program to view the analog data files the readings
are displayed under their appropriate titles which could
make the analysis of the data easier.

        Option 3, Collect Pressure/Analog Data, collects the
analog data and then collects the pressure and t.d.c. data
simultaneously. After all the data has been collected the
pressure data is plotted and the t.d.c. data is scanned to
find the specific locations of t.d.c. Once the locations of
t.d.c. have been determined they are marked on the pressure
plot.   
        After the plotting is done the user is given the option
of saving the data. If the user decides to save the data the
screen changes, the files with a 'pre' and a 'dat' suffix
are listed, and the user is prompted for a filename. The
filename entered will be used for both the pressure data and
the analog data, the only difference being the data file
containing the pressure information has a 'pre' suffix and
the data file containing the analog information has a 'dat'
suffix. In order this screen an appropriate filename (ie one
without a suffix and dos correct) must be entered. The
following page contains an example of this type of data
file.

        Option 4, Exit to the Main Menu, returns the user back
to the main screen.

                             View Saved Data

        The View Saved Data mode is accessed by choosing optino
number two on the main menu. Once this mode has been
accessed the user will see the following options:

                        (1) Load Analog Data File
                        (2) Load Pressure/Analog Data File
                        (3) View Analog Data
                        (4) Plot Pressure Data
                        (5) View Pressure Data
                        (6) Save Pressure Data in Decimal Form
                        (7) Exit to Main Menu

        If the user only wants to view an analog data file then
option 1 should be selected, but if pressure and analog data
are wanted to be viewed then option 2 should be chosen. Once
1 or 2 have been selected the screen changes, files with the
appropriate suffix are listed, and the user is prompted for
a filename. In order to exit this screen an appropriate
filename must be entered. Once data has been loaded into the
computer, options 3-6 can be chosen.
        Option 3, View Analog Data, displays the contents of
the 'dat' file that was loaded (see the following page for
the display format).
        Option 4, Plot Pressure, initially plots the
pressure/t.d.c. signal just as it did when it was first
collected via the control panel. The user is then asked if
he/she wishes to change the plotting parameters. If 'y' is
selected then the user can select a beginning and ending
data point and plot the data between these extremes. The
user can also enlarge the plot via the scale factor. This
mode can be exited by typing in an 'n' when asked if the
plotting parameters should be changed.
        Option 5, View Pressure Data, allows the user to view
the pressure data. Once selected the screen changes, the
user is prompted for beginning and ending points and the
number of points to skip. After this information has been
entered the data is listed sequentially starting and
stopping at the points entered, skipping the number of
points designated by the number called the step factor.
        Option 6, Save Pressure in Decimal Form, follows the
same format as option 5, but instead of displaying the data
it is stored under the filename entered by the user.



                Selecting the Throttle Controller

        Inorder to be able to decrease and increase the
throttle from the control panel a throttle controller must
be chosen. To enter the mode where a throttle controller can
be chosen the user should choose option number three from
the main menu. Once the number three is pressed the screen
will change and the user will be given the option to choose
between the throttle controllers that work with the large,
small, and brake dynomometers.


		CONFIGURATION OF THE SOFTWARE CONTROLLER

        The Hp3852a software controller must be configured to
read the proper multiplexer channels before it can be used
as data acquisition software. In order to do this, the user
should be familiar with or have access to the Hp3852a
programming manuals, it is also beneficial for the user to
have some knowledge of Turbo Pascal 4.0 or greater (though
it is not necessary).
        Located at the end of this manual is a full listing of
the code used to create the Hp3852a software controller. It
will be helpful to the first time user to familiarize
him/her self with it before continuing.
        This part of the manual is written with the assumption
that the Hp3852a controller is set-up according to Table 1.0
in Appendix A.
        To set-up the software controller the user must first
decide what measurements need to be made and what channel of
the multiplexer needs to be read to collect these
measurements. Once this has been decided the appropriate
commands must be entered to tell the controller to read
these signals. This is done by modifying the procedure
named:
                           'analog'
        
        Within this procedure the user will see a list of
channel numbers. Below the appropriate channel number the
user will enter the following commands:

        cmd:='(user specified command) into analog(channel #)';
        command(cmd);
For example if the user wanted to read a type t thermocouple
connected to channel 18 he/she would enter the following
lines:
        cmd:='confmeas tempt,318 into analog(18)';
        command(cmd);

        The user now moves to the procedure named:
                         'chanlist'
Within this procedure the user will see a list of channel
numbers. The user should modify the command that looks like
this 'outtextxy(x,y,'channel #'); so that the 'channel #' is
replaced with the desired channel title.

        The last change needed is in the procedure named:
                         'display'

        Within this procedure the user will see a listing of
channel numbers. Beneath the appropriate channel number the
following commands should be entered:

        setcolor(black);
        str(oldread[channel#]:4:1,s);
        outtextxy(x,y,s);
        setcolor(color);
        str(readings[channel#]:4:1,s);
        outtextxy(x,y,s);



Where channel# = the actual channel number

        x = x corresponding to appropriate channel as found in
                Table 2.0 in Appendix A.

        y = y corresponding to appropriate channel as found in
                Table 2.0 in Appendix A.

        color = desired color; (list in Table 3.0,Appendix A).


        
        If a conversion factor is needed to convert from the
signal being read to the desired signal then the user must
specify this conversion factor. This is done by locating the
procedures named:
             'collectanalog' and 'getanalog'

Where {PUT CONVERSION FACTORS HERE} is located within these
procedures put:
        readings[channel#]:=cf*readings[channel#];

Note: cf = a number (ie the conversion factor).
        channel# = the number of the channel.

        If in the course of running tests the voltage range of
the pressure signal changes the variable 'rng' in the
procedure 'graphpress' should be changed to the appropriate
number. It is currently set at 10.



                
        
1Q




In the recent release, Countdown To Extinction, Megadeth has followed bands
like Metallica and 
Nirvana by writing simple though catchy music.  There's something about
songs like "Skin of My
Teeth" or "Symphony of Destruction" , which the band released as a single
and on MTV, that make them stick in your head.  I walked around for days
humming (sometimes subconsciously) the chorus to "Symphony".  Usually, this
is a rare event reserved for certain commercial jingles or  some
particularlly annoying piece of Muzak heard while waiting on hold.  Being
catchy isn't bad, but I prefer music that is more complex and fuels the
imagination.  

Dave Mustaine, the singer and guitarist, has toned down his world famous
attitude a little bit on this album, as opposed to songs like "Hook In
Mouth" off of So Far, So Good...So What!, where Dave applies a pH 1.2
tongue lashing to the PMRC and other censorship advocates.  There's still
plenty of anger, like in the song "Sweating Bullets": "Yeah, just keep on
thinking it's my fault/And keep an inch or two out of kicking
distance/Mankind has got to know it's limitations".  The subjects of the
various songs are still typical Megadeth; schizophrenia-"Sweating Bullets",
environment- "Countdown to Extinction", fallen love-"This Was My Life",
politics-"Symphony of Destruction" and "Foreclosure of a Dream", etc. 
"Psychotron" is a particularly good song with a sci-fi theme.

Musically, the album is very tightly put together and well produced.  Like
Metallica, all the songs sound very clean and powerfull, unlike previous
recordings, i.e. Peace Sells, that sounded a little two dimensional.  The 
guitar solos aren't really explosive, but technically good and seem to fit
the songs alright. Some songs have powerful musical hooks, like the chorus
riff to "Countdown to Extinction", which is reminiscent of Iron Maiden's
Somewhere In Time baroque guitar duets.  The drums are very aptly played,
with the usual and very effective double bass.  Again like Metallica,
Megadeth has fallen back on harder, simpler riffs that support the lyrics
more than stand out on their own.  The songs are also slower, which I
regret because I really like the lightning-fast nose-bleed style.  This
forces more attention on Mustaine's high little-boy voice, which he
distorts to a metal growl in appropriate places.  It is sometimes annoying,
but not too bad. Some of the robot like voice effects get a little corny,
but Megadeth always had a little weakness for corny.

Overall, I really like the album, although it does have its drawbacks, and
I would advise anyone who likes Megadeth, heavy metal, or hard rock to buy
it or get a copy from a friend.  I'll rate Countdown to Extinction  with a
3.3 on the dreaded four point scale.e Metallica and 
Nirvana by writing simple thowrni e `\W
S$NQJ
sxvCss  ssJ
sL
<

 music.  There's something about songs like "Skin of My
 Arialand on MTV, that make them stick in your head.  I walked around for
days humming (sometimes subconsciously) the choTeeth" or "Symphony of Destruction" , which the band released  <sSsQJ< 
\'' '
 








		      CWRUnet User Troubleshooting Guide

			     PC-Compatible Edition

















			Case Western Reserve University


			 Information Network Services


				October 1, 1991
                                          













Copyright 1990, 1991 by Case Western Reserve University.  All rights
reserved.
Chapter 7 and the Acknowledgements page are derived from the SU-PC/IP 3.10
Installation Manual, which bears the following copyright notice:
   Copyright (c) 1989 by the Board of Trustees of the Leland Stanford
Junior   University.  The contents of this document may not be used for any
   commercial purposes.  All rights reserved.

		       ACKNOWLEDGEMENTS AND DISCLAIMERS


Case Western Reserve University's Internet Protocol programs, CWRU-PC/IP,
arebased on the following:

PC/IP, which was developed and copyrighted in 1984 by the Massachusetts
Institute of Technology.

LPR, which was developed and copyrighted in 1986 by Carnegie Mellon
University.
Work done on FTP by Samuel J.  Leffler, copyrighted 1983 by the University
ofCalifornia at Berkeley.

Work done on IBM 3270 terminal emulation by Greg Minshall, copyrighted 1986
bythe University of California at Berkeley.

MH Message Handling System, which was developed by the Rand Corporation and
placed in the public domain.

Work done on MH by Marshall T.  Rose, copyrighted 1985 by the University of
California at Irvine.

Work done to adapt PC/IP for the Apple Macintosh computer, copyrighted 1986
byCornell University.

SU-PC/IP, written at Stanford University by Saman Amarasinghe, Abraham
Bleiberg, Alex Danel, Raman Khanna, Chia-Chi Kuan, Andy Maas, Thomas
Malloy,Rajeev Newarikar, Aaron Reizes, and Stanley Yau.

CWRU-PC/IP is derived from Stanford's SU-PC/IP package.  Extensive changes
weremade at CWRU by Ernie Ellenberger and Stephen Trier to add packet
driversupport, remove bugs, and enhance Telnet, FTP, and the mail system. 
Changes to
TCP/IP kernel, telnet, and FTP by Ernie Ellenberger; changes to mail system
byStephen Trier.

This document was written by Stephen Trier.  Chapter 7 and this page are
derived from portions of the Stanford SU-PC/IP 3.1 Installation Manual.





Stanford makes no representations or warranties, express or implied.  By
way of
example, but not limitation, Stanford makes no representations or
warranties of
merchantability or fitness for any particular purpose, or that the use of
thelicensed software components or documentation will not infringe any
patents,copyrights, trademarks, or other rights.  Stanford shall not be
held liable for
any liability nor for any direct, indirect, or consequential damages with
respect to any claim by licensee or any third party on account of or
arisingfrom this agreement or use of the program.

Case Western Reserve University, referred to hereafter as "CWRU", makes no
representations or warranties, express or implied.  By way of example, but
notlimitation, CWRU makes no representations or warranties of
merchantability or
fitness for any particular purpose, or that the use of the licensed
softwarecomponents or documentation will not infringe any patents,
copyrights,trademarks, or other rights.  CWRU shall not be held liable for
any liability
nor for any direct, indirect, or consequential damages with respect to any
claim by licensee or any third party on account of or arising from this
agreement or use of the program.

			       TABLE OF CONTENTS

ACKNOWLEDGEMENTS AND DISCLAIMERS . . . . . . . . . . . . . . . . . . . . . 
i
TABLE OF CONTENTS. . . . . . . . . . . . . . . . . . . . . . . . . . . .
.iii
UNIT 1: BEGINNING TROUBLESHOOTING. . . . . . . . . . . . . . . . . . . . . 
1   1.1 Purpose of this guide . . . . . . . . . . . . . . . . . . . . . . .
 1
   1.2 The CWRUnet software. . . . . . . . . . . . . . . . . . . . . . . . 
1   1.3 How do I get help?. . . . . . . . . . . . . . . . . . . . . . . . .
 1
   1.4 Is it really my computer? . . . . . . . . . . . . . . . . . . . . . 
1
UNIT 2: HARDWARE REQUIREMENTS. . . . . . . . . . . . . . . . . . . . . . . 
3   2.1 Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . .
 3
   2.2 MS-DOS Version. . . . . . . . . . . . . . . . . . . . . . . . . . . 
3   2.3 Disk Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . .
 4
   2.4 Ethernet Adapters . . . . . . . . . . . . . . . . . . . . . . . . . 
4
UNIT 3: COMMON PROBLEMS. . . . . . . . . . . . . . . . . . . . . . . . . . 
5   3.1 Wrong version of the software . . . . . . . . . . . . . . . . . . .
 5
   3.2 Software not loaded . . . . . . . . . . . . . . . . . . . . . . . . 
5   3.3 Not enough memory . . . . . . . . . . . . . . . . . . . . . . . . .
 6

UNIT 4: FIBER-OPTIC TROUBLESHOOTING. . . . . . . . . . . . . . . . . . . . 
7   4.1 Switched transmit and receive cables. . . . . . . . . . . . . . . .
 7
   4.2 Damaged cable . . . . . . . . . . . . . . . . . . . . . . . . . . . 
7   4.3 Dirty cable ends. . . . . . . . . . . . . . . . . . . . . . . . . .
 7
   4.4 Faceplate not activated . . . . . . . . . . . . . . . . . . . . . . 
7   4.5 Cable bent too tightly. . . . . . . . . . . . . . . . . . . . . . .
 8

UNIT 5: CONFIGURATION ERRORS . . . . . . . . . . . . . . . . . . . . . . . 
9   5.1 Software Configuration on a hard disk . . . . . . . . . . . . . . .
 9
       5.1.1 Directory structure . . . . . . . . . . . . . . . . . . . . . 
9       5.1.2 Checking the path . . . . . . . . . . . . . . . . . . . . . .
 9
       5.1.3 Checking CONFIG.SYS . . . . . . . . . . . . . . . . . . . . .
10	  5.1.3.1 SHELL=command.com. . . . . . . . . . . . . . . . . . . .
10	  5.1.3.2 LASTDRIVE=g. . . . . . . . . . . . . . . . . . . . . . .
10	  5.1.3.3 DEVICE=C:\IP\NET_PD.SYS. . . . . . . . . . . . . . . . .
10	  5.1.3.4 FILES=20 . . . . . . . . . . . . . . . . . . . . . . . .
11   5.2 Software configuration on a floppy disk . . . . . . . . . . . . .
. 11
   5.3 Mail configuration. . . . . . . . . . . . . . . . . . . . . . . . .
11       5.3.1 Checking the MH variable. . . . . . . . . . . . . . . . . .
. 11
       5.3.2 Checking the "COMP" command . . . . . . . . . . . . . . . . .
11       5.3.3 Checking the inbox. . . . . . . . . . . . . . . . . . . . .
. 13
       5.3.4 Moving the MAIL directory . . . . . . . . . . . . . . . . . .
13   5.4 Hardware Configuration. . . . . . . . . . . . . . . . . . . . . .
. 13

UNIT 6: PROBLEMS ELSEWHERE . . . . . . . . . . . . . . . . . . . . . . . .
15   6.1 Host name not found . . . . . . . . . . . . . . . . . . . . . . .
. 15
   6.2 Name servers not responding . . . . . . . . . . . . . . . . . . . .
15   6.3 BOOTP problems. . . . . . . . . . . . . . . . . . . . . . . . . .
. 15
   6.4 Not responding. . . . . . . . . . . . . . . . . . . . . . . . . . .
15   6.5 Server not found. . . . . . . . . . . . . . . . . . . . . . . . .
. 15

UNIT 7: USING PING . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17   7.1 Basic PING Command. . . . . . . . . . . . . . . . . . . . . . . .
. 17
   7.2 Multiple Echo Requests. . . . . . . . . . . . . . . . . . . . . . .
17   7.3 Continuous Stream of Echo Requests. . . . . . . . . . . . . . . .
. 17
   7.4 PING Server . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18   7.5 Using PING to Isolate Network Trouble . . . . . . . . . . . . . .
. 18

APPENDIX A: IDENTIFYING AN ETHERNET CARD . . . . . . . . . . . . . . . . .
19

		       UNIT 1: BEGINNING TROUBLESHOOTING


1.1 Purpose of this guide

   This guide is designed to help a PC user on the CWRUnet find and solve
some   of the more common operating problems that will arise.  Chapters
cover   hardware and software requirements, and examples are provided to
help   beginning users.


1.2 The CWRUnet software

   Hundreds of different network protocols have been proposed and
implemented   on various computer systems.  Of these, perhaps a dozen are
in use on the
   CWRUnet.  The CWRUnet software for your PC supports two different
protocol   families, with different features provided by each.

   The first protocol family, usually known as "TCP/IP", is run by the
   CWRU-PC/IP software.  The programs supporting this family of protocols
are   located in the directories C:\IP and C:\MAIL on your hard drive, or
in A:\IP
   on a floppy disk.  These protocols were designed to run on many
different   computers, interconnecting them into the global network known
as the
   Internet.  The TCPIP, Telnet, FTP, and Mail software falls into this
   category.

   A second protocol family is also included in the CWRUnet software
release.   This family is Novell NetWare, developed and sold by Novell,
Inc.  of Utah.
   NetWare is used for local-area PC-to-PC communications.  The NetWare
   software for the CWRUnet is provided in the directory C:\NET or A:\NET
for   hard disk and floppy disk systems, respectively.

   Both protocol families can be active at once, thanks to a central
program   called a packet driver.  The packet driver also hides the
differences   between the many Ethernet cards used on the CWRUnet, allowing
exactly the
   same programs to be used on any PC on the CWRUnet.  Only one program,
the   packet driver, must be changed in order to change network cards.


1.3 How do I get help?

   Information Network Services has established a Service Desk to provide a
   single, reliable source of information about the network.  If your
network   connection is not functioning correctly, contact the Service Desk
for   assistance.  The problem will be resolved over the telephone, or, if
   necessary, an appointment will be made for a technician's visit.

   The IRIS/INS CWRUnet Service Desk can be reached by telephone at
368-USER.

1.4 Is it really my computer?

   Problems accessing the CWRUnet may not be caused by your computer at
all.   If the CWRUnet hardware and software has just been installed in your
   computer, there may be a delay of up to 24 hours before you can access
the   CWRUnet.  This time is used to update the various CWRUnet databases
about   your computer, and is unavoidable.

   If you have waited for 24 hours and the difficulties persist, consult
   chapters 2 through 6 of this guide.  If, instead, your computer has
   communicated on the CWRUnet in the past, consult other computer users in
   your building to see if their systems are working.  Wide-spread errors
   indicates a network fault which INS must correct.  If this is the case,
   please call the IRIS/INS CWRUnet Service Desk so that work to correct
the   fault can begin quickly.  If the errors are confined to your
computer, look
   through this troubleshooting guide to determine a cure.  Chapters 3, 4,
and   6 will be the most helpful.

			 UNIT 2: HARDWARE REQUIREMENTS


When troubleshooting, the first issue to consider is whether the computer
system is capable of supporting the software and hardware at hand.  This
chapter describes the essential memory, DOS, and hardware requirements for
running the CWRUnet software.


2.1 Memory Requirements

   One of the first areas to check is whether the PC is capable of
supporting   CWRU-PC/IP in the first place.  If CWRU-PC/IP has functioned
correctly in
   the past, you may skip this section.

   In order to run CWRU-PC/IP, a PC or PC-compatible computer must have at
   least 320K of free memory.  This allows 60K for DOS, 100K for the TCP/IP
   kernel, and 160 K for the CWRU-PC/IP applications.  "Free memory" does
not   include memory for resident or "pop-up" programs like PC- Tools,
Norton   Guides, or SideKick.  It also does not include the memory needed
for other
   network software like Novell NetWare, nor for the memory consumed by
   keyboard enhancers and similar utilities.

   Also, please note that many of the application programs that can be
accessed   from the Novell servers require more memory, from 500K free for
the CD-ROM
   databases to 2 Megabytes for Mathematica-386.

   Check the amount of free memory by running the CHKDSK utility included
with   MS-DOS.  For example:

             C:\>chkdsk <Enter>

             Volume ARJCC     created Aug 4, 1989 1:36p

              33409024 bytes total disk space
                 71680 bytes in 11 hidden files
                202624 bytes in 136 directories
              29122560 bytes in 1652 user files
               3932160 bytes available on disk

                655360 bytes total memory
                542000 bytes free

             C:\>

   The last line of output from the chkdsk command is the one to check in
this   case.  The term "K" when describing memory is short for "kilobyte",
so a
   320K minimum translates to 320,000 bytes.  This computer has 542,000
bytes   free, which is far above the 280,000 minimum.


2.2 MS-DOS Version

   The next software issue to consider is whether the computer is running a
   correct version of MS- DOS.  CWRU-PC/IP requires MS-DOS or PC-DOS
version   3.1 or higher.  To check your version, issue the MS-DOS command
"ver".  For
   example,

             C:\>ver <Enter>

             AT&T Personal Computer MS-DOS Version 3.30a  Rev 1.01

             C:\>

   Another manufacturer's computer will report the following:

             C:\>ver <Enter>

             Zenith DOS Version 3.30
                   BIOS Version 3.30.12

             C:\>

   The version in both of these examples turns out to be 3.30, which is
   compatible with CWRU- PC/IP's requirement of version 3.1 or higher.


2.3 Disk Drives

   Your PC must have two floppy disk drives or a hard disk drive. 
Computers   with hard disks can run all of the CWRU-PC/IP software. 
Computers with only
   floppy disks can run all of the software except the mail software. 
Users of
   floppy-only machines must instead send and receive their e- mail on the
   FreeNet system.


2.4 Ethernet Adapters

   Each PC must be equipped with an Ethernet adapter board that is
connected to
   your building's Ethernet network.  Furthermore, your software must be
   configured for the card that is installed.  For more information on
   identifying the card in use, see the Appendix.  In most cases, it is
   sufficient to know whether your ethernet card is fiber-optic or
thin-wire   Ethernet.


			    UNIT 3: COMMON PROBLEMS


The most common problems on the CWRUnet can be easily diagnosed and
corrected.This chapter is devoted to these problems, and should usually be
your first
stop as you seek a solution.

3.1 Wrong version of the software

   Do not mix versions of the CWRU-PC/IP software.  The rewrites that give
rise   to a new version also make the versions incompatible.

   With Novell NetWare, the NETx.COM program must match the version of
MS-DOS   running on the computer.  NetWare will not function correctly if
you use the
   wrong version of NETx.COM.  For MS-DOS version 3.0, 3.1, 3.2, or 3.3,
use   NET3.COM.  For MS-DOS version 4.0 and 4.01, use NET4.COM.  To check
the   version currently in use, type the command "DIR C:\NET".  Check for
NET3.COM   or NET4.COM.  See section 2.2 if you are unsure what version of
MS-DOS you
   are running.

   If you are running the wrong version of NETx.COM for your version of
MS-DOS,   please redo your software upgrade.


3.2 Software not loaded

   Both CWRU-PC/IP and Novell NetWare use support programs that remain in
   memory after they are run.  The following list demonstrates which
programs   must be run in order to run each package.

          CWRU-PC/IP:                  LOADDRV, TCPIP
          NetWare on MS-DOS 3.x:       LOADDRV, IPX.COM, NET3.COM
          NetWare on MS-DOS 4.x:       LOADDRV, IPX.COM, NET4.COM

   All of the networking software depends on the LOADDRV batch file, which
   loads the program that controls the Ethernet card in your computer. 
LOADDRV   is automatically loaded when the computer starts, so in most
cases you do
   not need to worry about its usage.  If, however, it is inadvertently
removed   from the AUTOEXEC.BAT file, your networking software will stop
functioning   with error messages like the following:

          C:\>novell south
          Could not find packet driver interface.

          C:\>

   or, when running CWRU-PC/IP:

          C:\>tcpip
          Copyright 1985, 1986, 1987, 1988, 1989 by Stanford University
          Copyright 1990, Case Western Reserve University.  All Rights
Reserved.          CWRU-PC/IP Version 1.0
          Can't access IP packet type
          Packet driver probably not loaded

          C:\>

   CWRU-PC/IP requires the TCPIP program to be loaded manually before using
   Telnet, FTP, Whois, Mail, or any of the PC-MH commands.  To do this,
simply   type "TCPIP" at the MS-DOS prompt.  Failure to load TCPIP before
using a
   CWRU-PC/IP command will result in a message like the following:

          C:\>telnet cwlim
          INIT_ALL: TCPIP service module not loaded.
                    Please use TCPIP.EXE to install TCPIP service.

          C:\>

   If you receive this message, run TCPIP and try your command again.

          C:\>tcpip
          Copyright 1985, 1986, 1987, 1988, 1989 by Stanford University
          Copyright 1990, Case Western Reserve Univerisity.  All Rights
Reserved.          CWRU-PC/IP Version 1.0

          TCPIP service module initialized.
          Your hostname is proto-pc3
          Your IP address is 129.22.8.56
          TCPIP occupies 94K of memory space.

          C:\>telnet cwlim

   Novell NetWare users do not need to worry about loading IPX and
NETx.COM.   These programs are loaded automatically by the NOVELL.BAT batch
file when it
   is invoked.  For example:

          C:\>novell south


3.3 Not enough memory

   With so many resident programs active, the limited memory space of
MS-DOS   can shrink rapidly.  The worst offender is TCPIP, which consumes
94K to 98K
   of memory.  Novell NetWare also consumes roughly 53K.  This memory is
used   only after the corresponding programs are run and is released when
you   reboot the computer.

   Error messages returned because of a memory shortage will vary depending
on   the program being run.  WordPerfect prints the message "Not enough
memory to
   run WordPerfect", while MS-DOS may simply print ".EXE file too large". 
In   all of these cases, the programs will run successfully once the memory
used   by networking software is released.

   Two approaches will release the memory used by the networking software. 
The   first, and simplest, is to reboot your computer by pressing
Ctrl-Alt-Delete,   pushing the reset button, or turning off the power.  In
addition, the TCPIP
   program includes an option to unload itself, returning its memory to the
   pool for other programs to use.  For example:

     C:\>tcpip -k
     Copyright 1985, 1986, 1987, 1988, 1989 by Stanford University
     Copyright 1990, 1991 Case Western Reserve University.  All Rights
Reserved.     CWRU-PC/IP Version 1.2

     TCPIP module unloaded.

     C:\>

		      UNIT 4: FIBER-OPTIC TROUBLESHOOTING


The fiber-optic interfaces used by much of the CWRUnet have their own
mannersof failing.  This chapter discusses some of the common difficulties
users of
the fiber-optic cards face and their solutions.  All of the dorms use
fiber-optic interfaces, and many of the academic buildings will have
fiber-optics installed.  Some older buildings and buildings slated for
removal,such as the Baker Building, use thin- wire Ethernet.  This section
does not
apply to buildings using thin-wire Ethernet.


4.1 Switched transmit and receive cables

   Perhaps the most common problem with the fiber-optic network interfaces
   occurs when the transmit and receive cables are mistakenly crossed.  In
this   event, the green light or lights on the back of the fiber-optic card
will be
   off, and the network connection appears to be dead.  To test for this
   problem, simply switch the two connectors on one end of the cable.  If
the   network software on the computer no longer gives error messages, the
problem   has been solved.


4.2 Damaged cable

   The tips of the fiber-optic cables used by the CWRUnet must be properly
   cared for.  Careless handling of a cable can scratch the polished end
   surface or break the tip outright, either of which will sever the
network   connection.  In addition, the cable can break along its length if
subjected   to unusually rough handling.

   In order to check your cable for a break, check the lights on the back
of   your network card.  Cards with a single green light, manufactured by
AT&T,   should have that light on.  Cards with a cluster of four lights,
   manufactured by Cabletron, should have one green light on and one yellow
   light flashing.  If the lights on your computer do not match this
   description, you may have a cable problem.

   This test checks only the receive connection of the cable, so you must
swap   the transmit and receive sides to check the other half of the cable.
 (Be
   sure to switch the transmit and receive connectors on both ends!) Once
the   cable sides are switched, the lights should have the same pattern as
on the
   first half of this test.

   If the lights are not on for either half of this test, your network
   faceplate may not be activated.  Read the next section, then call the
   IRIS/INS CWRUnet Service Desk.  In addition, if the cable has a
noticable   break, call the IRIS/INS CWRUnet Service Desk to obtain a
replacement.

4.3 Dirty cable ends

   Be careful to avoid touching the tips of the cable to any object except
a   fiber-optic connector.  If the ends become dirty or scratched, your
network   connection will suffer in quality or fail outright.  Do not
attempt to clean
   the ends yourself.  Instead, call the IRIS/INS CWRUnet Service Desk for
   assistance.


4.4 Faceplate not activated

   Each faceplate must be individually activated before it will function. 
If   you have just moved into your room, or if your have just had your
network   card installed, your faceplate may not be activated.  Call the
IRIS/INS   CWRUnet Service Desk at 368-USER to have the faceplate
activated.

4.5 Cable bent too tightly

   Although light normally travels in straight rays, the fiber-optic cable
can   guide light impulses around corners without losing effectiveness. 
However,   the cable will not be able to function if it is bent into a turn
with a
   radius smaller than three inches.  In addition, a cable bent too tightly
may   break internally, ruining it.


			 UNIT 5: CONFIGURATION ERRORS


Many problems can appear when a new piece of software is installed on a
computer.  Because of the wide range of disk setups and the hundreds of
expansion cards available for PC-compatibles, it is not possible to find a
single configuration that will work for all situations.  This chapter
addressesthese issues by discussing the hardware and software configuration
needed in
order to run CWRU-PC/IP.


5.1 Software Configuration on a hard disk

5.1.1 Directory structure

   The CWRUnet software resides in three directories on your hard disk,
known   as C:\IP, C:\MAIL, and C:\NET.  The following sequence of commands
will   confirm that all three directories exist:

             C:\>c:  <Enter>

             C:\>cd \IP  <Enter>

             C:\IP>cd \MAIL  <Enter>

             C:\MAIL>cd \NET  <Enter>

             C:\NET>cd \  <Enter>

   If you receive any error messages from MS-DOS while executing this
sequence   of commands, please connect to the INS software upgrade server
and go
   through the software upgrade process, selecting the "Install from
scratch"   option.

   Note that this directory structure is not mandatory.  Advanced users may
   move the directories if they desire, but this manual is written for this
   directory structure.  Furthermore, alternate directory organizations may
not   work properly with the INS software upgrade servers.  Therefore, INS
   recommends that the standard directory structure be retained by all
users.

5.1.2 Checking the path

   In order to function properly, the MS-DOS search path must be set up to
   include the network software directories.  Check the search path with
the   command "PATH", as shown below:

             C:\>path  <Enter>
             PATH=C:\;C:\DOS;C:\WINDOWS;C:\IP;C:\MAIL;C:\NET

             C:\>

   The path printed on your computer will be different, but the three
network   directories (C:\IP, C:\MAIL, and C:\NET) must be included.


5.1.3 Checking CONFIG.SYS

   Check your CONFIG.SYS file for the proper CWRU-PC/IP software drivers. 
An   example follows:

             C:\>type c:\config.sys  <Enter>
             buffers=40
             files=20
             shell=command.com /P /E:512
             lastdrive=g
             device=c:\ansi.sys

             C:\>

   The important lines are "shell=command.com", "lastdrive=g", and
"files=20".   Each line is discussed below.


5.1.3.1 SHELL=command.com

   This line should include enough environment space for the network
software   to function, or errors will result.  The format of the line is
the   following:

	     shell=command.com /P /E:###

   For MS-DOS versions 3.2 and higher, "###" should be between 384 and 768.
   For versions before 3.2, "###" should be at least 24, but not more than
48.
   If you need to change this line, do so by editing the CONFIG.SYS file
with   the PED editor.  For example:

	     C:\>ped c:\config.sys <Enter>

   Add the line and press Ctrl-X to exit.  You will need to reboot before
the   change will take effect.


5.1.3.2 LASTDRIVE=g

   The "lastdrive" command informs DOS how many disk drives you plan to
attach   to the computer.  This option is tricky, since both numbers too
small and
   too large can cause the software servers to malfunction.  The rule of
thumb   to use is that the letter used should be at least two letters
higher than
   your highest drive letter, but not more than four letters higher.

   In other words, take the highest drive on your computer (C: on most, E:
on   AT&T's, D: on many clones) and go two letters higher.  Use that letter
in   the lastdrive statement.

   If you are in doubt about your lastdrive setting, use the "lastdrive=g"
   statement shown.


5.1.3.3 DEVICE=C:\IP\NET_PD.SYS

   This line loads the device driver essential to CWRU-PC/IP.  It should be
   included as-is in the CONFIG.SYS file.  If it is not present, please
   re-install your software from the INS upgrade server.

   There should be no other network drivers listed in the CONFIG.SYS file. 
If   you see DEVICE= lines for ATTNAU.SYS, IPCUST.SYS, NET3c523.SYS,
   NET3c503.SYS, or similar names, please re-install your software from the
INS   upgrade server.


5.1.3.4 FILES=20

   This line sets the maximum number of files that can be used
simultaneously   by an MS-DOS program.  Because the Mail program and many
of the programs
   used by Novell NetWare must be able to access several files
simultaneously,   this line should allow room for at least 20 files:

	     files=20

   Most application software recommends setting this number to at least 20.
   However, because a surplus can often improve performance, many users
   recommend a value of 35 or 40.  For example:

	     files=35

   Consult your DOS manual for more information about the FILES= statement.


5.2 Software configuration on a floppy disk

   The INS floppy disk is pre-configured for CWRU-PC/IP.  If you wish to
   rearrange the files on it, please DISKCOPY the disk and then delete the
   unneeded files.  This way, the configuration information will remain
intact.

5.3 Mail configuration

5.3.1 Checking the MH variable

   The mail program requires an environment variable "MH" to be defined,
   pointing to the directory that holds profile.mh.  Check this environment
   variable with the following sequence:

             C:\>set  <Enter>
             COMSPEC=C:\COMMAND.COM
             PATH=C:\DOS;C:\;C:\WINDOWS;C:\IP;C:\MAIL;C:\NET
             MH=c:\mail\

             C:\>

   If the environment variable is not set, please re-install your software
with   the INS software upgrade server.


5.3.2 Checking the "COMP" command

   Standard MS-DOS includes a little-used command called "COMP".  This
command   will compare two binary files, but only if they are exactly the
same   length.  At the same time, MH and Mail use a "comp" command that is
used to
   compose a new message.  This name conflict can cause many odd problems
on a
   system running e-mail.

   There are two possible solutions.  The first is to rename the MS-DOS
"comp"   command.  For example:

             C:\>c:  <Enter>

             C:\>cd \dos  <Enter>

             C:\>rename comp.* comp!.*  <Enter>

   The above applies to the conventionally configured AT&T or other
computer.   On a Zenith, use the following:

             C:\>c:  <Enter>

             C:\>cd \bin  <Enter>

             C:\>rename comp.* comp!.*  <Enter>

   Either of these procedures will change the name of the comp command to
   "comp!".  That way, it is still available, but will not conflict with
the   Mail and MH version.  Do not rename the MH comp command, because that
will   interfere with the operation of the Mail program.

   Another solution for the problem exists.  Rather than rename the MS-DOS
   comp, it is possible to rewrite the DOS search path so that the Mail
comp is
   found before the MS-DOS comp.  To do this, edit the autoexec.bat file
with   the PED editor:

	     C:\>ped c:\autoexec.bat <Enter>

   Once autoexec.bat appears on the screen, find the line that starts with
   "PATH=" or "SET PATH=".  This line will look something like the
following:
             PATH=C:\WINDOWS;C:\;C:\DOS;C:\IP;C:\MAIL;C:\NET

   On a Zenith computer, it will look something like this:

             PATH=C:\WINDOWS;C:\;C:\BIN;C:\IP;C:\MAIL;C:\NET

   Edit that line so that the directory C:\MAIL comes before C:\DOS, or on
a   Zenith, so that C:\MAIL comes before C:\BIN.  For example, both of the
   following are fixed versions of the above lines:

             PATH=C:\WINDOWS;C:\;C:\MAIL;C:\DOS;C:\IP;C:\NET

             PATH=C:\WINDOWS;C:\;C:\MAIL;C:\BIN;C:\IP;C:\NET

   Do not remove any of the entries in the PATH statement, and make certain
   that there are no spaces and no double semicolons (";") in the line.

   Save the autoexec.bat file with Ctrl-X, answer "Y" to the "Are you
sure?"   prompt, and reboot the computer to make the change take effect.

   Either approach will solve the problem; the first is recommended because
of   its simplicity.


5.3.3 Checking the inbox

   Another cause of problems with Mail is a missing INBOX folder.  To
correct   this problem, use the MH "folder" command.  For example:

             C:\>folder +inbox  <Enter>
             Create directory c:\mail\inbox as a folder? (Y/N) Y  <Enter>

             Set folder to +inbox
             FOLDER       # of messages            range        current
message #
             ------       -------------            -----       
----------------             +inbox             0                  (0-0)   
            0

             C:\>

   You may not receive the "Create directory" prompt.  In this case, INBOX
   already exists, and the MH folder pointer has been reset to point to it.


5.3.4 Moving the MAIL directory

   If you choose to rearrange your network software directories, you will
have   to edit the profile.mh file to reflect the new structure. 
Furthermore, you
   will need to update the MH environment variable in AUTOEXEC.BAT to point
to   the new location of profile.mh.  These changes are for advanced users
only.

5.4 Hardware Configuration

   One of the purposes of a packet driver is to concentrate all of the
   information about the hardware configuration of an Ethernet card in one
   location, so that it can be easily changed.  This also means that it is
easy   to check.  In order to check that the packet driver installed for
your   computer is the correct one, type the following command right after
   rebooting the computer:

          C:\>tcpip  <Enter>
          Copyright 1985, 1986, 1987, 1988, 1989 by Stanford University
          Copyright 1990, Case Western Reserve University.  All Rights
Reserved.          CWRU-PC/IP Version 1.0
          Can't access IP packet type
          Packet driver probably not loaded

          C:\>

   If you receive the message above, your packet driver is not properly
   configured.  If this is the case, please read Appendix A to determine
your   Ethernet card type and re-install your software from the INS
software   upgrade server.


			  UNIT 6: PROBLEMS ELSEWHERE


Some error messages returned by the network software are not indications of
problems with the local machine, but instead indicate trouble elsewhere on
thenet.  This section describes some of the errors that may occur, along
withexplanations.

6.1 Host name not found (CWRU-PC/IP)

   The Internet Protocol used by CWRU-PC/IP represents all network
addresses as
   a series of four numbers, all less than 256.  Humans, however, find
names   easier to remember than sequences of numbers, so certain computers
on the
   network serve as translators, looking up names and returning the
numerical   addresses.  This error message means that when CWRU-PC/IP tried
to contact
   one of these "name servers", the name you gave was not found.

   The most likely cause of this problem is a typing error.  Try retyping
the   command, making certain that the name is spelled correctly. 
Alternately,   use the numerical IP address for the host, if it is
available.

6.2 Name servers not responding (CWRU-PC/IP)

   This is a more serious problem with the name servers described in
section   5.1.  In this instance, the name server computers could not be
reached,   making the name-to-address translation impossible.

   The most likely cause of this problem is a failure in a critical segment
of   the CWRUnet.  The solution is to wait for some time and try again; INS
will   repair the problem as soon as possible.  A work-around solution is
to use
   the numerical IP address for the host if it is available, since this
address   does not require translation by the name servers.  This solution
will work
   in most cases, but may not always succeed.  If it does not, you must
wait   for the network failure to be repaired.


6.3 BOOTP problems (CWRU-PC/IP)

   CWRU-PC/IP uses a the Boot Protocol, "BOOTP", to configure itself for
the   CWRUnet.  If the TCPIP module is unable to execute the BOOTP
protocol, it
   will fail with a message about a bad or invalid BOOTP response.  In this
   event, call the IRIS/INS CWRUnet Service Desk at 368-USER for
assistance.

6.4 Not responding (CWRU-PC/IP)

   This error indicates that the host machine you are trying to contact is
not   reachable, either because it is down or because of a network link
problem   somewhere between it and your computer.  Again, wait for some
period of time
   and try again.  If the problem is prolonged, contact the administrator
of   the host system about the problem.


6.5 Server not found (NetWare)

   This is similar to the Not Responding error message generated by
   CWRU-PC/IP.  It indicates that either a network link has failed or the
   NetWare server you are trying to reach is down.  Try to contact the
server   later, when it should be back on-line.


			      UNIT 7: USING PING


The PING service allows you to find out if a host is running and to isolate
trouble on a network.  In general, only advanced users will need this
command.
7.1 Basic PING Command

   To find out if a host computer is running, issue the command ping
host_name   or ping host_internet_address from the DOS prompt.  Example:

          C:\>ping freenet-b  <Enter>
          Send Echo Request:
          Host 129.22.8.45 responding

   If the host is not running, the last line of the response will report
that   the host is timed out instead of responding.  For example:

          C:\>ping freenet-b  <Enter>
          Send Echo Request:
          Host 129.22.8.45 timed out
 
   If the response to the ping command is that the name servers are not
   responding, substitute the Internet Protocol (IP) address of the host
for   its name.  Example:

          C:\>ping freenet-b  <Enter>
          Send Echo Request:
          Name Servers Not Responding

          C:\>ping 129.22.8.45  <Enter>
          Send Echo Request:
          Host 129.22.8.45 responding


   (To determine the IP address of a particular host, issue the command
whois   host_name, as explained in Section 6.2.4 of the User's Manual.)

 
7.2 Multiple Echo Requests

   To send more than one echo request to a host, use the command ping -n X
host   where X is the number of times in succession you want the request
sent.   Example:

          C:\>ping -n 6 score  <Enter>


7.3 Continuous Stream of Echo Requests

   To send a continuous stream of echo requests, use the command ping -t
host.   At any time during the series of responses, you can type the letter
Q to get
   a summary of the statistics and exit.

   This technique is not recommended and is included only for historical
   reasons.  A continuous stream puts a significant load on the network,
   decreasing its speed for all network users.  Please use the -n option
   instead, as explained in section 7.2.


7.4 PING Server

   To designate a PC as a PING server, issue the command ping -s from that
PC.   A PC dedicated to this function cannot be used for other purposes. 
To end
   the server function for a PC, type the letter Q.


7.5 Using PING to Isolate Network Trouble

   When a host fails to respond, it might mean one of the following: the
host   is not running; some network or gateway in the path from the user to
the   host is not running; or the host does not implement the Internet
Control   Message Protocol/Internet Protocol (ICMP/IP).  Further PING
experiments can
   usually pinpoint the problem.  If sending an echo request to a second
host   on the same network shows that it is responding, the likelihood is
that the
   first host is not running or not listening to the network.  Failure to
get   echoes from any other host on that network means that the trouble is
along   the path somewhere.  A PING directed to the gateway into the
network in
   question is the next step.  You can continue to work back from the
target   toward the originator until you find the point at which
communication breaks
   down.

   The echo request sent by the PING command is dispatched using a
low-level   protocol that does not try to guarantee delivery.  As a result,
there is a
   possibility that any one echo request could be lost for some reason,
such as
   a temporary overload in a gateway.  Therefore, you cannot be sure that a
   particular network or gateway has failed unless several, consecutive
PING   experiments consistently succeed in getting to the point in question
and   consistently fail to get beyond that point.


		   APPENDIX A: IDENTIFYING AN ETHERNET CARD


As noted in Unit 1, Requirements, each PC must be equipped with an Ethernet
adapter board.

This appendix gives you the information needed to determine the type of
card in
your computer.  This will allow you to check the configuration of
CWRU-PC/IP to
make sure that it is configured for your card.

This section is divided up into a series of numbered questions that attempt
todiscern the type of network card a computer is using.  Each question
indicatesanother question number to which you should refer to further
narrow the
possibilities.  Eventually, you will be able to narrow the possibilities
downto one or two cards.  Start with question 1.

   1.  What kind of cable is connected to the card?

       Examine the back of your computer and find the network card.  If it
has       two thin cables plugged in, with the cable resembling a
conventional       lamp cord, go to question 2.

       If the cable has a single thin cable connected with a "T" connector,
       read question 3.

       If there is a single thick cable, with a connector about one inch
long,       go to question 4.

   2.  The card uses fiber optics.

       How many lights does the card have on the back?
	  If there is one green light, see question 5.
	  If there is a cluster of four lights of various colors, see
question	      7.

   3.  The card uses thin-wire Ethernet.

       Does the card have a cluster of four small lights on the back?
          If so, see question 11.
          If not, see question 12.

   4.  The card uses thick-wire Ethernet.

       Does the thick cable running from the card connect to another
external	  box?
      If so, see question 8.
      Otherwise, call the Service Desk (368-USER) for assistance.

   5.  The computer has an AT&T Fiber-Optic NAU.  Please continue with the
next       section of this troubleshooting guide.

   6.  The card is a 3Com 3c501 Etherlink.  Please continue with the next
       section of this troubleshooting guide.

   7.  The card is a 3Com 3c503 Etherlink II.  Please continue with the
next       section of this troubleshooting guide.

   8.  Does the box have a pair of wires strongly resembling lamp cord
running       from one side?

       If so, please go to question 10.
       If not, please go to question 9.

   9.  You have an unknown card.  Call the IRIS/INS CWRUnet Service Desk
for       assistance.

   10.  You have a fiber-optic transceiver attached to your card.

       If you have an IBM PS/2 system, you have a 3Com 3c523 card.
       If this is another brand of computer, this is some other type of
card.	  Call the IRIS/INS CWRUnet Service Desk for assistance.

   11.  This card is a Cabletron thinwire card, probably a Cabletron 1020.

   12.  This card is probably a 3Com thinwire card.  To determine the
model,	please open the cover of the computer and examine the color of the
card.	  If it is blue, see question 6.
          If it is green, see question 7.
 
-- 
 | |^\   /\   \   |   \   |   /| | |\   +--- \   | "Ask for thyself another
 | | / /    \ | \ |   | \/|  X | | | \  |--  | \ |  kingdom, for that which
 | | \ \____/ |  \|   |   | / \| | |__/ \___ |  \|  I leave is too small 
      \           |       |                      |  for thee"