Number: 1662

Date: 17-Jul-84 17':45':50

Submitter: Masinter.PA

Source: Schmidt@sumex

Subject: want customer supported versions of Etherwatch and PeekPup/NSPeek

Assigned To: 

Attn: vanMelle

Status: Open

In/By: 

Problem Type: Design - UI

Impact: Moderate

Difficulty: Hard

Frequency: 

Priority: Unlikely

System: Communications

Subsystem: Other

Machine: 

Disk: 

Lisp Version: 

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: 

Description: Received': from SUMEX-AIM.ARPA by PARC-MAXC.ARPA; 17 APR 84 11':51':14 PST'
Date': Tue, 17 Apr 84 11':49':52 PST'
From': Christopher Schmidt <SCHMIDT@SUMEX-AIM.ARPA>'
Subject': Re': InstallLispTool & TOPS-20'
To': JFung.pasa'
cc': Eric@SU-CSLI.ARPA, Spurgeon@SU-CSLI.ARPA'
In-Reply-To': Message from "JFung.pasa@PARC-MAXC.ARPA" of Tue 17 Apr 84 10':14':38-PST'
'
'
'
	By the way, suggesting use of the File Tool points up the fact that'
your customer diagnostic mechanism relies on the customer''s ability to bootleg such tools from PARC (as I did).  How would you handle this problem with a less fortunate customer?  I would rather we had these tools shipped directly with the machines.  Most tools are simply only rumors to me.  Eg., we would desperately like to have the 10 mb equivalent of Etherwatch and PeekPup to run on our 1108''s on our 10 mb ethernet.  The only way I was able to log the booting transaction was by booting off a server 3 hops away, one of the legs of which was a 3 mb net on which I had an Alto!  I would normally try to boot off a machine on the local 10 mb net; a transaction which we have no tools to monitor.  Thanks,'
'
'
--Christopher'
'


Workaround: 

Test Case: 

Edit-By: vanMelle

Edit-Date: 25-Jul-84 12':43':12