HDTenEightyP/NetNews huggingface dataset:
From: geoff@tyger.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs
Subject: Re: packed file corrupt
Date: 12 Jan 1993 22:49:49 GMT
Organization: SunSelect
Distribution: world
Reply-To: geoff@tyger.East.Sun.COM
NNTP-Posting-Host: tyger.east.sun.com

In article 17971@netnews.whoi.edu, eklein@whsun1.wh.whoi.edu (Edgar Kleindinst) writes:
##
##---
## 
##On various PC's when PCNFS.SYS is loaded high we get this error message upon
##trying to run certain applications. "packed file courrupt" I seem to remember some
##mention of this on the net but failed to keep a copy of the message. 
##Does anyone  know the reason this error occurs?

It's nice to have the archives on-line :-) The problem was due to a bug
in the Microsoft EXEPACK utility: when it was written, nobody imagined
that an executable would ever be loaded below 64K...:-(

Here's the fix that Michele Bergonzoni suggested a couple of years ago.

## >From: bergonz@keeper.sublink.ORG (Michele Bergonzoni)
## Message-ID: <68.27EFC762@keeper.sublink.ORG>
## Date: 26 Mar 91 20:57:53 GMT
## Organization: V. Angelo custode,9 40141 Bologna ITALY
## Lines: 24
## 
## 
##  > >option of DOS5.0, but I'm not sure about that. Nfsconf says 'packed file
##  > >corrupt', but the network itself works correctly. 
##  > 
##  > I was told by a quarterdeck engineer, that this result was due to a bug
##  > in some versions of EXEPACK, which manifested itself when programs 
## 
## You can try to work around this by a freeware package for MS-DOS, LZEXE (by   
## Fabrice Bellard). LZEXE  does the same job of EXEPACK, but using Lempel-Ziv  
## compression, and thus much better. In the LZEXE package there is an utility  
## (UPACKEXE) to de-EXEPACK EXEPACKed files, to achieve better result in  
## subsequent compression. Maybe you  could use that to  overcome the bug in  
## EXEPACK's unpacking code. If you don't  know where to find  LZEXE, try  
## +39516343719 (OCA System BBS), +3951554430  (BESIII BBS) [Sorry for  the long  
## distance...] or e-mail me if really desperate.
## HTH, ciao
## 
##                                                 Bergonz   
## --  
## Michele Bergonzoni                   | This
## internet: bergonz@keeper.sublink.org | is
## FidoNet : 2:332/401.7                | not
## Mail    : V. Angelo Custode, 9       | a
##           40141 Bologna ITALY        | pipe



---
Geoff Arnold, PC-NFS architect, Sun Select. (geoff.arnold@East.Sun.COM)

Newsgroups: comp.protocols.nfs
From: hartzman@kilroy.Jpl.Nasa.Gov (Les Hartzman)
Subject: PCNFS and 3C507-packet drivers:  HELP!
Followup-To: hartzman@kilroy.jpl.nasa.gov
Keywords: pcnfs, 3c507
Organization: Jet Propulsion Laboratory, Pasadena, CA
Distribution: NA
Date: Thu, 7 Jan 1993 21:25:25 GMT

HELP!

I'm trying to set up PCNFS 3.0.1 to use a 3C507 card and packet drivers
(the supplied one ETH507.SYS), but it keeps dying if I do a NET NAME * or
a NET USE ...  Is this a packet driver problem a card incompatibility or ...?

The only drivers I'm loading in the config.sys file are the ETH507.SYS, 
PCNFS.SYS, and SOCKDRV.SYS.  Am I missing something else?

Thanks in advance for any help.

Les



-- 
Les Hartzman                hartzman@kilroy.jpl.nasa.gov
Jet Propulsion Laboratory   M/S 238-528    (818) 354-5964
4800 Oak Grove Dr., Pasadena,  CA.  91109
Newsgroups: comp.protocols.nfs
From: eklein@whsun1.wh.whoi.edu (Edgar Kleindinst)
Subject: packed file corrupt
Reply-To: eklein@whsun1.wh.whoi.edu
Organization: NOAA - National Marine Fisheries
Date: Tue, 12 Jan 93 18:57:38 GMT


---
 
On various PC's when PCNFS.SYS is loaded high we get this error message upon
trying to run certain applications. "packed file courrupt" I seem to remember some
mention of this on the net but failed to keep a copy of the message. 
Does anyone  know the reason this error occurs?


 
                                      )
                                  0_ /    
          o<   o<     \__________(__/_______________/	
         ~0   ~0	 ----------/--------------	  
	    paddle faster, those ducks aren't real
	         eklein@whsun1.wh.whoi.edu
Newsgroups: comp.protocols.nfs
Subject: Help with NFS client!
From: olson@csufres.CSUFresno.EDU (Brian Olson)
Date: 11 Jan 93 21:36:53 PST
Distribution: world
Organization: California State University, Fresno


Dear NFS gurus:

I am relatively new to NFS (RPC for that matter) and have a few
questions that I would be very grateful for help with.  I am
flying blind with only RFC1094 to help me...

I am trying to implement a very simple NFS client, running on machine
A, which will contact the NFS server (running on machine B).  
First I make the RPC call to procedure MOUNTPROC_EXPORT (5) of the
mountd daemon on machine B.  It correctly responds with its exported
list of directories.  Then I RPC call to MOUNTPROC_MNT (1) with the
first directory that was returned to me.  The RPC call is accepted, but
the returned file handle is all zeros, and a error status of 13 is
reported.  I assume this is the standard NFSERR_ACCESS error (permission
denied)--true?

I don't know why this call is failing, as machine A is in machine
B's /etc/export file for the desired directory.  (Viewing machine B's 
/etc/xtab  or executing  exportfs  confirms this.)  Also the
exported directories are rwx for all.


HELP!!!  I am at my wits end!  Should what I am doing be
working?  I would be grateful for any replies, ANY AT ALL...
C source code would be great!  Please post to me or to the list--
I now read it daily!

Thanks in advance!
Brian Olson
olson@csufres.csufresno.edu



Newsgroups: comp.protocols.nfs
From: swaters@cs.utwente.nl (Henk Swaters)
Subject: Re: PKTD.SYS for PCNFS 4.0
Reply-To: swaters@cs.utwente.nl
Organization: University of Twente, Dept. of Computer Science
Date: Tue, 12 Jan 1993 08:47:40 GMT


Sorry, the filename is pktd40a.sys.Z in the directory /pcnfs on the anonymous ftp server bcm.tmc.edu.
From: olson@csufres.CSUFresno.EDU (Brian Olson)
Newsgroups: comp.protocols.nfs
Subject: Re: Re: Help with NFS client...
Date: 12 Jan 93 22:29:37 GMT
Organization: California State University, Fresno


My sincerest thanks to Surya Prasad Koneru (surya@enlil.premenos.sf.ca.us),
who writes:

>The problem lies in the mount server which authenticates clients based
>on the port number (client's).  In UNIX, ports 0-1023 are only assigned
>to priveledged services. And the mount server, only accepts requests from 
>clients that lie in this range.

That was it!!  

The fact that I couldn't find this nifty little tidbit of information
makes me feel that my documentation is not the best.  Could you recommend
other sources for NFS/RPC info (besides the RFCs, man pages)?  I have
read about something called the "RPC Programming Guide"--is this
FTPable?    Also, is there a FAQ for this newsgroup?

Many Many Thanks!  (-:

P.S.  Now this is my favorite newsgroup...


Brian Olson
olson@csufres.csufresno.edu
Newsgroups: comp.protocols.nfs
From: fr@eagle.mumath (Farid Rahmi)
Subject: Re : Diskless PCNFS?
Reply-To: fr@eagle.mumath
Organization: BIM sa
Date: Mon, 4 Jan 93 17:04:35 GMT

Hi Nick,


Here in United Europe people make a living out of selling a solution that allows PC's 
to boot diskless from a Unix box. The trick is to use bootp (a publicly available boot
protocol) and siliconize a DOS bootfloppy - burn it into a PROM.

Hope that you manage to get this running all this by yourself (bootp is on the net),
but if you don't, these are the coordinates (even found a signature which includes an
e-mail adress !). Pricing was moderate two years ago (about $150).


Farid


-----------------------------------------------------------------------------------
TCP/IP BOOT-PROM

        The TCP/IP BOOT-PROM is a ROM-based device which allows users to boot 
MS-DOS and PC-NFS from a network server.  The ROM plugs into the socket of 
the network controller and eliminates the need for a diskette- or fixed-disk 
drive to start up the operating system and PC-NFS.

        Bootstrap information, the operating system, and PC-NFS are held on 
the network server.  Every attached PC has its own entry in the configuration 
table on the file server.

        The server-based software uses standard TFTP and BOOTP protocols
available on common TCP/IP implementations.  No specialized software is needed 
on a network server based on UNIX or any other operating system that supports 
TCP/IP.

        BOOT-PROMs are available for the following Ethernet controllers:   
        
                Racal-InterLan's NI6510
                Western Digital's WD8003/8013
                3Com's EtherLink II
        
        Other controllers can be supported on request.
        
        
Special Requirements:           Ethernet controller with ROM socket.  
                                TFTP and BOOTP protocols on the network server.


For more information contact:

        Dirk Koppen EDV-Beratung
        Holzwiensenweg 22
        D-6050 Offenbach
        Germany
        +49 69 89 3000
        FAX +49 69 89 3004

-----------------------------------------------------------------------
>  Dirk Koeppen  -  Holzwiesenweg 22  -  D-6050 Offenbach  -  Germany
>  Phone: +49 69 89 3000 - FAX: +49 69 89 3004 - email: dirk@incom.de
From: mfavas@uniwa.uwa.edu.au (Mark Favas)
Newsgroups: comp.protocols.nfs
Subject: PCNFS & ISO9660 CDROM
Date: 13 Jan 1993 10:41:19 +0800
Organization: The University of Western Australia
NNTP-Posting-Host: uniwa.uwa.edu.au
X-Newsreader: NN version 6.4.19 #1

We have a CD-ROM drive attached to a DECStation 5000 running Ultrix4.2. An ISO
9660 CD can be mounted and read on the DECStation and by other DECstations on
the network. The CD-ROM can also be mounted without errors by a PC running
PCNFS. However, when doing a "dir" on that drive on the PC, no files appear to
be present, as if the G: drive was empty. No error messages appear - just no
filenames. Has anyone encountered this problem before? Thanks for any help...

Mark Favas, Department of Chemistry, The University of Western Australia
Newsgroups: comp.protocols.nfs
From: swaters@cs.utwente.nl (Henk Swaters)
Subject: Re: PKTD.SYS for PCNFS 4.0
Reply-To: swaters@cs.utwente.nl
Organization: University of Twente, Dept. of Computer Science
Date: Tue, 12 Jan 1993 08:38:42 GMT


There is a ptk40a.sys available on the anonymous ftp server bcm.tmc.edu.



Newsgroups: comp.protocols.nfs,comp.sys.sun.hardware
From: ckd@eff.org (Christopher Davis)
Subject: Re: Does a Prestoserve S-bus card improve local disk access too?
Organization: Electronic Frontier Foundation Tech Central
Date: Mon, 11 Jan 1993 06:19:32 GMT

SD> == Steve Dyer <dyer@spdcc.com>

 SD> I know that the Prestoserve board works to speed NFS writes by saving
 SD> the data to NVRAM and returning immediately to the client RPC, rather
 SD> than requiring the client process to block until the disk write
 SD> finishes.  I'm wondering if the support also speeds local operations
 SD> on the exported disks which are implicitly synchronous (at least with
 SD> the UFS file system).

Yes, and the same for unexported disks unless you configure it otherwise.

Note that unlink() is synchronous; /bin/rm -rf * runs REAL fast on a
PrestoServed machine.  Be even MORE careful than you used to be, because a
quick Ctrl-C may not save enough of your bacon.
--
Christopher K. Davis      | ``Usenet seems to run much like the Kif (or,
<ckd@eff.org>   EFF #14   |   for the TV generation, Klingon) high command.
System Administrator, EFF |   Whoever takes action and can be heard wins.''
+1 617 864 0665  [CKD1]   |   --Peter da Silva <peter@ferranti.com>
From: kozowski@OHSU.EDU (Eric Kozowski)
Newsgroups: comp.protocols.time.ntp
Subject: ADD TO LIST
Date: 5 Jan 93 19:46:00 GMT
Distribution: inet
Organization: The Internet

Please add kozowski@ohsu.edu to the ntp mailing list.
From: rbthomas@frogpond.rutgers.edu (Rick Thomas)
Newsgroups: comp.protocols.time.ntp
Subject: Re: Does anyone have a port of XNTP3 for SVR4.
Date: 7 Jan 93 20:48:07 GMT
Organization: Rutgers Engineering Supercomputer Lab
Cc: rbthomas

> I am trying to get XNTP V3 running on a SVR4 system.

On a similar subject, does anybody have a working port of xntp (any version)
to Sun's Solaris 2?

We are going to be forced to convert from SunOS 4 in the not too distant
future, and I would hate to re-invent the wheel.

Thanks!

Rick


========================================================================
Rick Thomas, Manager
Supercomputer Remote Access Center, Rm B113
Rutgers University, College of Engineering
Brett and Bowser Roads
Piscataway, NJ 08855-0909

Phone: (908) 932-4301
Fax:   (908) 932-5313
Internet: rbthomas@jove.rutgers.edu
UUCP: {any backbone site}!rutgers!rbthomas
========================================================================
Solaris 2.0, Just say NO!
========================================================================
Newsgroups: comp.protocols.time.ntp
From: elsen@imec.be (Marc  Elsen)
Subject: novice question related to xntp3 installation
Reply-To: elsen@imec.be (Marc  Elsen)
Organization: IMEC V.Z.W.
Date: Tue, 12 Jan 1993 15:59:59 GMT




 I am testing xntp3 between 2 DECstations.
 Using 'ntpdate server_station' always results in : 

/ntpdate -d tycho
/ntpdate: ntpdate version 3.1
transmit(146.103.1.105)
receive(146.103.1.105)
transmit(146.103.1.105)
receive(146.103.1.105)
transmit(146.103.1.105)
receive(146.103.1.105)
transmit(146.103.1.105)
receive(146.103.1.105)
transmit(146.103.1.105)
server 146.103.1.105, port 123
stratum 16, precision -3, leap 11, trust 000
refid [0.0.0.0], delay 0.1506, dispersion 0.0002
transmitted 4, in filter 4
reference time:      00000000.00000000  Thu, Feb  7 2036  7:28:16.000
originate timestamp: aefd6704.ce48a000  Tue, Jan 12 1993 16:49:24.805
transmit timestamp:  aefd6704.b8274000  Tue, Jan 12 1993 16:49:24.719
filter delay:  0.1506   0.1584   0.1623   0.1584
               0.0000   0.0000   0.0000   0.0000
filter offset: 0.08254  0.08254  0.08449  0.08254
               0.00000  0.00000  0.00000  0.00000
delay 0.1506, dispersion 0.0002
offset 0.0825415

/ntpdate: no server suitable for synchronization found




  What does the last message mean ?

  I played with various options for the server's /etc/ntp.conf file
 but I always get the same result.





 I am new to xntp so forgive me if the question is to simple.
 Please reply by e-mail


                                             Thanks,

--
    Marc (elsen@imec.be)
    'Waterdust is fine but even hydrogen would have lead
     to a never ending story...'
Newsgroups: comp.protocols.time.ntp
From: dglattin@trirex.com (Dennis Glatting)
Subject: problem with noprintf on NeXT
Keywords: ntp
Organization: Trirex Systems Inc.
Distribution: usa
Date: Mon, 11 Jan 1993 15:58:53 GMT


I went to run tickadj on my NeXT running OS 3.0 and it complained it  
couldn't find _noprintf.  I searched the kernel and found:

axys100:4# nm /sdmach | grep -i print
040232cc t __printf
04034d58 T _ether_sprintf
0409e7ec D _ipprintfs
04077152 T _np_init_printer
04077ce6 T _np_printing_shutdown
04077d64 T _np_printing_timeout
040786b4 T _np_wait_printer_ready
04023920 T _printf
0404110a T _printfhandle
0402394c t _printn
04023a4e T _sprintf
0409e81c D _tcpprintfs
04023abe T _tprintf
04023c0e T _uprintf

I have two questions:  1, What is _noprintf and what is it used for?  and  
2, What is a suitable substitute from the above variable list?

--
Dennis P. Glatting / Sr. Technical Manager / Trirex Systems Inc.
315 Post Road West / Westport, Connecticut 06880 / (203)221-4600
dennis_glatting@trirex.com (NeXTmail Ok)
Member League for Programming Freedom
Newsgroups: comp.protocols.time.ntp
From: rgrimes@agora.rain.com (Rodney Grimes)
Subject: Does anyone have a port of XNTP3 for SVR4.
Organization: Open Communications Forum
Date: Wed, 6 Jan 1993 22:27:57 GMT

Hi,
I am trying to get XNTP V3 running on a SVR4 system.  I got it to
compile and I can talk to it with xntpdc and ntpq.  It seems to 
come up and get the time from the servers I have listed and then
it just sits, it never seems to talk to the other servers again.

Has anyone got it running correctly on a SVR4 system, and if so
what did you have to do to make it work (looking for diff's)

Thanks,
		Rod
-- 
Rod Grimes						rgrimes@agora.rain.com
Accurate Automation Company          All opinions belong to me and my company!
From: Mills@UDEL.EDU
Newsgroups: comp.protocols.time.ntp
Subject: Update
Date: 8 Jan 93 14:56:43 GMT
Distribution: inet
Organization: The Internet

Folks,

All patches received as of 0500Z 8 January have been incorporated in the
distribution xntp3.tar.Z on louie.udel.edu. The patches have mostly to
do with portability things; however, there are a few that affect the
1-pps feature with Sun SPARCstations. With a good, jitterless source
such as a GPS receiver (this leaves WWVB and WWV receivers in the dust),
the residual jitter is down in the 10-microsecond range. I also had
to add another digit of precision to the ntpq billboards, since our
DECstation 5000s were showing mostly zeros in the delay field. Modern
workstations on FDDI rings bring a new dimension to timekeeping.

Dave
From: iglesias@draco.acs.uci.edu (Mike Iglesias)
Subject: Re: xntp3 refuses to talk from little-endian to big endian machines
Newsgroups: comp.protocols.time.ntp
Organization: University of California, Irvine
Date: 12 Jan 93 16:53:55 GMT
Distribution: inet

In article <1iukkuINNhmg@wintermute.phys.psu.edu> kenh@leps5.phys.psu.edu (Ken Hornstein) writes:
>I have been trying to get xntp3 (the latest version from louie.udel.edu)
>working on the following machines:
>
>	Vax 11/750 	    - BSD 4.3
>	DECstation 3100     - Ultrix 4.0
>	DECstation 5000/240 - Ultrix 4.3
>
>On all these machines, xntp3 has the same problem: it will only talk to
>another xntp daemon that is running on one of these machines.  Xntpdc will
>only talk to a daemon on one of these machines; when trying to talk to
>another machine, it times out.  Xntpdc's on other machines cannot talk
>to these daemons.  It _looks_ like there is a byte-order problem, but
>I have not gone that far into the problem.  Does anyone else run xntpd on
>a little endian machine?  If so, please let me know what you did to get it
>to work!

I have been running xntp3 on two DECstations for several months, using
them as campus servers.  They are being used by lots of Suns, HPs, and
other DECstations with no problems.  I just took the latest xntp3 from
louie and built it on a DECstation; it runs fine and xntpdc on a Sun
can query it with no problems.  I suspect there's some other problem
lurking here that's preventing xntp from working correctly.


Mike
From: Mills@UDEL.EDU
Newsgroups: comp.protocols.time.ntp
Subject: [Greg Woods:  ncarfuzz.ucar.edu status]
Date: 8 Jan 93 01:36:42 GMT
Distribution: inet
Organization: The Internet



----- Forwarded message # 1:

Received: from louie.udel.edu by huey.udel.edu id aa05028; 7 Jan 93 15:20 EST
Received: from ncar.ucar.edu by louie.udel.edu id aa18922; 7 Jan 93 15:12 EST
From: Greg Woods <woods@ncar.ucar.edu>
Message-Id: <9301072012.AA01669@ncar.ucar.EDU>
Received: by ncar.ucar.EDU (5.65/ NCAR Central Post Office 07/14/92)
	id AA01669; Thu, 7 Jan 93 13:12:00 MST
Subject: ncarfuzz.ucar.edu status
To: mills@udel.edu
Date: Thu, 7 Jan 93 13:11:59 MST
X-Mailer: ELM [version 2.3 PL11]

The old "ncarfuzz" Fuzzball system is dead. Permanently. You can't even find
any of those old floppy drives new any more, and we've had three refurbished
drives die in the last six months, so we have given up on that system. We
are working on getting our radio clock hooked up to a Sun running XNTP,
but for reasons that are more political than technical it is taking a very
long time to accomplish this. Eventually we intend to hook this host up to
the old IP address for ncarfuzz.ucar.edu and resume supplying stratum 1
time service, but I can't say when this will happen. I will keep you
informed. In the meantime, it should be noted that with the death of
the Fuzzball, Don Morris no longer has anything to do with time service 
here. I am now the contact person.

--Greg

----- End of forwarded messages
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.protocols.time.ntp
Subject: too many recvbufs allocated
Date: 6 Jan 1993 19:48:15 GMT
Organization: Thinking Machines Corporation, Cambridge MA, USA
Distribution: world
NNTP-Posting-Host: telecaster.think.com

We're running xntpd 1.3 on Sparcstations running SunOS 4.1.x (for x in
[1-3]).  Recently, a number of our machines started complaining
"xntpd[<pid>]: too many recvbufs allocated (30)".  What does this mean, why
might it have just started happening (we can't think of any network-wide
change that we made) and most importantly, what can we do to stop it?
-- 
Barry Margolin
System Manager, Thinking Machines Corp.

barmar@think.com          {uunet,harvard}!think!barmar
From: valdis@BLACK-ICE.CC.VT.EDU (Valdis Kletnieks)
Newsgroups: comp.protocols.time.ntp
Subject: Re: Seeking NTP for IBM MVS and OS/2
Date: 7 Jan 93 05:59:18 GMT
Distribution: inet
Organization: The Internet
X-Unparsable-Date: Thu, 07 Jan 1993 00:58:51 +22311841

On Wed, 06 Jan 1993 21:28:51 EST, you said:
> Are there any implementations of NTP available for IBM mainframes
> and for PC's running OS/2?
>                                                         -- Steve
> -------

Steve:

I assume you mean for IBM mainframes of the S/390 genre.  On those,
the 'sysplex timer' may provide the needed facilities.

On *all* S/360, S/370, 303x, 43xx, 308x, and 309x boxen, you had to hit
the 'TOD ENABLE' switch in order to let the operating system actually
modify the clock. This is a *HARDWARE* interlock implemented in the
processor controller.

AIX/370 (and presumably AIX/ESA) will run NTP OK, because they access
the clock via the 'gettimeofday()' call.  Unfortunately, MVS is a
lost cause, because once you hit TOD ENABLE during IPL, the value
returned by a Store Clock instruction is pretty immutable.

I have no information on what effect the S/390 Sysplex Timer has
on all of this - it may remove the hardware interlock restriction
and allow software tweaking of the TOD clock.
--
				Valdis Kletnieks
				Computer Systems Engineer
				Virginia Tech
From: ken@SDD.HP.COM (Ken Stone)
Newsgroups: comp.protocols.time.ntp
Subject: Re: adjtime on hp730 under hpux 8.07
Date: 6 Jan 93 22:22:51 GMT
Distribution: inet
Organization: The Internet


> Since about the start of the new year, the syslog file on my hp730 running
> hpux 8.07 has been filling up with the following error message:
> 
> Jan  6 16:37:38 hiauly1 xntpd[1770]: Previous time adjustment didn't complete
> 
> Do you have any suggestions as to what has gone wrong?

Try running adjtimed with a higher rate value ... ie ... "adjtimed -p 40" ?
Its sort of the equiv of tickadj for normal people :-)

  -- Ken
From: Mills@UDEL.EDU
Newsgroups: comp.protocols.time.ntp
Subject: Additions to NTP archive
Date: 7 Jan 93 05:02:00 GMT
Distribution: inet
Organization: The Internet

Folks,

I put up a compressed tar file for the NBS Automated Computer Time
Service built for the IBM PC by Judah Levine of NIST. Also, there
is a more recent port of that stuff to Microsoft C for the PC and
Unix C for Suns. Both files include sources and executables for the
PC. The former is called nbstime.tar.Z and the latter msctime.tar.Z,
both on louie.udel.edu in the directory pub/ntp.

In response to a couple of requests, I have put up a compressed tar
file loran.tar.Z containing detailed information, schematics and
sources for my hotshot LORAN-C timing receiver. Not exactly a
Heathkit (remember that?), but lots of documentation, annotation and
a technical report.

There is also a README file which briefly describes all the other
files. For those files not mentioned in the README, anything goes.

Dave