HDTenEightyP/NetNews huggingface dataset:
From: ilya@bourbaki.mit.edu (Ilya Zakharevich)
Subject: Re: DOS version of ghostscript
Organization: MIT Department of Mathematics, Cambridge, MA
Distribution: gnu
Date: Sat, 11 Apr 1992 06:49:54 GMT

Hello, netters!

	This is a reminder that the supplied version of the MSDOS Ghostscript
does not supports bgi drivers, and the supplied version of gs386 does not
support either the vesa (SVGA) drivers. 

	That means that a) the gs386 CANNOT work with SVGA at all;
			b) the gs cannot be used with SVGA since the calling
				syntax is not included in documentation (if it 
				is included, it cannot be found at least).

Yes, I RTFM.

	So I humbly suggest to the author of this excellent software to give
a chance to the user and include those drivers that is legally and technically
possible in the official distribution. A hint: While it is not deadly difficult
to compile gs, as well as I know 386-mode compilers usually reserve the 
copywrite of the compiled executables, so I cannot expect some kind user will
post a compiled by him version.

	A final note: the vesa version of gs kills my computer with the 
supplied vesa driver (et4000). However, the driver from prodesigner works(my 
card isnot Prodesigner though). And gs -sDEVICE=vesa -g1024x768 does not... 

	Best regards, Ilya

Newsgroups: gnu.ghostscript.bug
From: quanstro@stolaf.edu (goon)
Subject: ghostview dies in print_file
Organization: St. Olaf College
Distribution: gnu
Date: Wed, 8 Apr 1992 17:16:44 GMT

This is running ghostview on a Sparc running 4.1.1

; gdb  /home/accserv3/spec/stu/rosell/bin/ghostview core
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.4, Copyright 1991 Free Software Foundation, Inc...
(no debugging symbols found)...
Warning: core file may not match specified executable file.
Core was generated by `ghostview'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/local/X11/lib/libXaw.so.5.0...
(no debugging symbols found)...done.
Reading symbols from /usr/local/X11/lib/libXmu.so.4.10...
(no debugging symbols found)...done.
Reading symbols from /usr/local/X11/lib/libXt.so.4.10...
(no debugging symbols found)...done.
Reading symbols from /usr/local/X11/lib/libXext.so.4.10...
(no debugging symbols found)...done.
Reading symbols from /usr/local/X11/lib/libX11.so.4.10...
(no debugging symbols found)...done.
Reading symbols from /usr/lib/libc.so.1.6...(no debugging symbols found)...
done.
#0  0x9504 in print_file ()
(gdb) bt
#0  0x9504 in print_file ()
#1  0xafe0 in okay ()
#2  0xf76e0f0c in XtCallCallbackList ()
#3  0xf7774608 in XawAsciiSourceChanged ()
#4  0xf77065d4 in _XtMatchAtom ()
#5  0xf7706be4 in _XtMatchAtom ()
#6  0xf7707174 in _XtTranslateEvent ()
#7  0xf76e9db4 in _XtFreeWWTable ()
#8  0xf76ea518 in _XtOnGrabList ()
#9  0xf76ea5fc in XtDispatchEvent ()
#10 0xf76ea920 in XtAppMainLoop ()
#11 0x6048 in main ()
(gdb) 
--
quanstro@stolaf.edu (goon@uni-paderborn.de)
Erik Quanstrom		 
St. Olaf College	 
Northfield MN, 55057.5 USA			 

Newsgroups: gnu.ghostscript.bug
From: macphed@dvinci.usask.ca (Ian MacPhedran)
Subject: Re: pstoppm
Reply-To: macphed@dvinci.usask.ca
Organization: University of Saskatchewan
Distribution: gnu
Date: Mon, 6 Apr 1992 08:56:41 GMT

>From article <1992Apr3.121643.2296@tdb.uu.se>, by olle@bellatrix.tdb.uu.se (Olle Eriksson):
> We are using Ghostscript to convert postscript to ppmimages. I did install
> ghostscript on a Decstation 5000/120 (ultrix 4.2a, gcc 2.0) and tried it
> out.
> 
> The following works fine, just as it did in 2.3
> 
> gs pstoppm.ps
> (golfer) ppm1run
> 
> But
> 
> gs pstoppm.ps
> (escher) ppm8run
> 
> worked fine in 2.3 but fails with a range check in makeimagedevice in 2.4.
> I have not been able to use ppm8run on any ps-file
> 
> Why is this?

The pallette in pstoppm.ps appears to be missing several primary colours.
To wit
blue:     0000ff
green:    00ff00
cyan:     00ffff
magenta:  ff00ff

Find close values in the table, and replace them with these numbers.

Ian.
-- 
----------------------------------------------------------------------------
Ian MacPhedran, Engineering Computer Centre, University of Saskatchewan.
2B13 Engineering Building, U. of S. Campus, Saskatoon, Sask., CANADA S7N 0W0
macphed@dvinci.USask.CA  macphedran@sask.USask.CA

Newsgroups: gnu.ghostscript.bug
From: venable@faculty.coe.wvu.wvnet.EDU (WALLACE VENABLE)
Subject: MS-DOS extension (Not a BUG)
Organization: WVU College of Engineering
Distribution: gnu
Date: Tue, 14 Apr 1992 00:59:32 GMT

	I spent a very large amount of time trying, without success to get 
GS24 working on my machine.  Then someone posted a critical note.
	I was using GS CHEQ CHESS
	I needed GS CHEQ.PS CHESS.PS
	If there are other confused novices about, it appears the file 
extension for the PostScript files is REQUIRED.  It didn't get that from the 
sparse instructions, but was afraid to ask.
	GhostScript is REALLY IMPRESSIVE, even on the 286 and Okimate setup 
in my office.
			Thank you Alladin & Co.

Newsgroups: gnu.ghostscript.bug
From: refling@..ucsd.EDU (John P. Refling)
Subject: Another helpful hint while compiling under MSDOS
Organization: University of California, Irvine
Distribution: gnu
Date: Thu, 9 Apr 1992 23:10:27 GMT

I had trouble with the .swap line in the tbcplus.mak crashing my machine.
Could never figure out why.  I even tried it on a system with no TSRs.

I have a 286 with 1meg memory, the top 384k I normally use for ramdrive.
When compiling gs, I removed the ramdrive and added the -Qx switch to the
end of CCFLAGS definition.  That reduced compile time from 60 minutes to
34 minutes!  If you have extra memory, you may wish to investigate this.
--
-----------
John Refling, refling@sloth.eng.uci.edu

Newsgroups: gnu.ghostscript.bug
From: schultz@halley.ESt.3m.COM (John C. Schultz)
Subject: DOS version of ghostscript
Organization: 3M Company, 3M Center, Minnesota, USA
Distribution: gnu
Date: Thu, 9 Apr 1992 18:02:43 GMT

I retrieved ghostscript 2.4 from prep.ai.mit.edu for MSDOS (as well as
UNIX).

While gs and gs386 work on my Compaq, I have a couple questions.

1. What is the difference, if any between gs.exe and gs386.exe?

2. What is dos4gw.exe?  I am not familiar with the Watcom compiler.
If I do dos4gw gs386.exe, the previewer seems to work but is no faster
than gs386 by itself.

3. I can only run the .exe files from the installation directory.  If
for example I try to run gs.exe from another directory, I get the
GSPreview%Initializing.. message and then the program aborts with 
"Unexpected interpreter error -21!".  If I need to RTFM, which manual?
I put the set DOS4G=quiet in my autoexec.bat file if that is of any use.

4. I noticed mention of a version for Windows.  Is this available? Where?

Thanks.
Sorry if these are FAQ but I just started reading this group.
--
   John C. Schultz   +1 (612) 733-4047   schultz@halley.serc.3m.com
   How to include the taste of Glendronach in a multi-media system?

Newsgroups: gnu.ghostscript.bug
From: tange@daimi.aau.dk (Ole Tange)
Subject: SuperVGA display
Organization: DAIMI: Computer Science Department, Aarhus University, Denmark
Distribution: gnu
Date: Sat, 11 Apr 1992 14:17:34 GMT

How do I use my ET-4000 chipset? It says in the manual that there is a driver
for ET-4000, but I coldn't find an example on how to use the driver.
Please make some examples, e.g. resolution 1024x768x256.


--
        .:.=========================================================.:.
      .:::::.               ANTE TEMPORE - ][T WAS                .:::::.
    .:::::::::.Ole Tange, Noerre Alle 66B 3.3,  DK-8000 AArhus C.:::::::::.
  .::Have Fun!::.        INTERNET: tange@daimi.aau.dk         .:::See Ya!:::.

Newsgroups: gnu.ghostscript.bug
From: brianj@skat.usc.edu (Brian Jones)
Subject: Problems with ghostview1.1 and Openwin2.0
Organization: University Computing Services--U.S.C.
Distribution: gnu
Date: Tue, 14 Apr 1992 09:27:04 GMT

I was wondering if anybody was having problems with ghostview-1.1 using
openwindows 2.0?  It works fine and dandy the first time I use it, but
when I exit and try and go into it again, it gets flakey.  Sometimes, it
will cause the window server to crash, other times it will just give me
an error saying: "Error:  SmeBSB Object: Left Bitmap of entry "0" is not
one bit deep."  I have no idea what that means.

Ghostscirpt 2.4 works fine, and I have it compiled using both X11 and sunview.
Ghostview gives me no trouble in Openwindows 3.0 or in X11R4 or X11R5,  Just
Openwindows 2.0.  I was wondering if anybody else has come across this, or 
if I am just a unique case?

Thanks

Brian
 
-- 
==========================================================================
Brian Jones                                  email: brianj@skat.usc.edu  
University of Southern Cal                          bjones@aludra.usc.edu
Computing Services

Newsgroups: gnu.ghostscript.bug
From: ghost@aladdin.COM (L. Peter Deutsch)
Subject: Re: gs2.4 msdos386 executable w/TVGA16 device wanted
Organization: GNUs Not Usenet
Distribution: gnu
Date: Mon, 13 Apr 1992 16:04:16 GMT

Re <9204110449.AA10199@raisin-nut> <fnsbo.14@nsd.uib.no>:

> Having a Trident 8900 (1024k) I have understood that the best resolution
> I can get with gs2.4 is with the TVGA16 device (800x600x16).

If you have a VESA-compliant driver for this card, and if the card is
capable of higher resolution (with 256 colors, however), then you can
select the VESA device and run the display at a higher resolution.
Ghostscript can handle 1024x768 and 1280x1024.  With a 1 Mb memory,
you should be able to get 1024x768.

You will need a version of Ghostscript that includes the vesa driver.

L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306
ghost@aladdin.com, ...decwrl!aladdin!ghost ; 415-322-0103 8-9 AM M-F/msg
	    "Implementation is the sincerest form of flattery."


Newsgroups: gnu.ghostscript.bug
From: ghost@aladdin.COM (L. Peter Deutsch)
Subject: Re: Hercules driver
Organization: GNUs Not Usenet
Distribution: gnu
Date: Fri, 10 Apr 1992 08:45:15 GMT

Re <9204100513.AA06515@raisin-nut>
<1992Apr9.184753.7050@athena.mit.edu>:

> I want to run Ghostscript on my 386SX PC with a Hercules graphics card,
> outputting to screen.
> 
> I have the MSDOS executables and what I think are all the relevant files
> from the various *.zip archives.  From reading the doc files and even
> grepping them for references to Hercules, I gather that I need some
> sort of driver, and I gather that the characters BGI somehow figure into
> this.
> 
> I do not own C (I'm not a programmer), and thus am not equipped to build
> my own version.  Should I forget it, is there something I'm missing, or
> both?

You're out of luck.  The distributed executable doesn't include the
BGI driver, which is the only way I know of to use Ghostscript with a
Hercules card.  Contact me directly at ghost@aladdin.com to see about
getting a custom executable.

> Also, a possibly related question.  The program GS.EXE loads and runs,
> though without showing me my document, obviously.  On the other hand,
> GS386.EXE gives the error message:
> 
> 	DOS/4GW Protected Mode Run-time   Version 1.3
> 	Copyright (c) Rational Systems, Inc. 1990-1991
> 	DOS/4GW Fatal error: Can't initialize loader[1]  -- LINEXE_LOADER
> 
> What is this about?

Sorry, I don't know.  E-mail me your machine configuration and the
contents of your CONFIG.SYS file, and I might be able to guess.

L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306
ghost@aladdin.com, ...decwrl!aladdin!ghost ; 415-322-0103 8-9 AM M-F/msg
	    "Implementation is the sincerest form of flattery."


Newsgroups: gnu.ghostscript.bug
From: ghost@aladdin.COM (L. Peter Deutsch)
Subject: Re: gs2.4 on HP/UX 7.05
Organization: GNUs Not Usenet
Distribution: gnu
Date: Mon, 6 Apr 1992 13:53:57 GMT

Re <9204040815.AA19953@raisin-nut>
<9204032123.AA05984@gateway.bnr.ca>:

> Everything goes fine compiling gs2.4 on an HP 425 until:
> 
> ...
>         ./ccgs "cc  -O  -DSYSV -Wc,-Ns5000 -Wc,-Nw500" _temp_.c gxclist.c
> Global optimizer warning in "clist_render": Element cbuf[500] outside array boun
> ds, procedure not optimized.
> C1 internal error in "clist_render": unknown optype passed to find()
> mv: _temp_.o: Cannot access: No such file or directory
> *** Error code 1
> 
> Stop.
> 
> Any ideas?  Thanks.

Complain to H-P.  This is a compiler bug.  (ANSI C, as well as
traditional C, allows a reference to A[N], where N is the size of the
array.)

L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306
ghost@aladdin.com, ...decwrl!aladdin!ghost ; 415-322-0103 8-9 AM M-F/msg
	    "Implementation is the sincerest form of flattery."


Newsgroups: gnu.ghostscript.bug
From: ghost@aladdin.COM (L. Peter Deutsch)
Subject: Re: Canon BJ10E Bubblejet printing from DOS
Organization: GNUs Not Usenet
Distribution: gnu
Date: Sat, 11 Apr 1992 13:45:53 GMT

Re <9204110544.AA10255@raisin-nut>
<SCHULTZ.92Apr10134636@halley.est.3m.com>:

> I tried to use Ghostscript 2.4 to print a Postscrtip (tm) document on
> a Canon BJ10ex printer from a compaq 386sx laptop.  The printing
> started OK but after correctly printing about an inch, the printer
> started beeping and garbled the print.  For the rest of the page, the
> printer sometimes printed, sometimes beeped.  It sounded almost like
> the printer was getting data too fast.  Is handshaking a problem?

There are several possible problems here:

1) I do not know whether the BJ10ex is fully compatible with the
BJ10e.

2) The BJ10e has two different switch settings.  Ghostscript expects
it to be in what the manual calls mode 1 (DIP switch 10 OFF).

3) There is a known problem with the 386-only executable: NONE of the
printer drivers work properly.  This will be fixed in release 2.4.1,
next week.

L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306
ghost@aladdin.com, ...decwrl!aladdin!ghost ; 415-322-0103 8-9 AM M-F/msg
	    "Implementation is the sincerest form of flattery."


Newsgroups: gnu.ghostscript.bug
From: ghost@aladdin.COM (L. Peter Deutsch)
Subject: Asterix output vs. Ghostscript
Organization: GNUs Not Usenet
Distribution: gnu
Date: Tue, 7 Apr 1992 04:24:19 GMT

In <9204010537.AA09201@raisin-nut> <ktifm6INNggj@caldera.usc.edu>,
Danny Mitzel observes:

> I'm trying to use Ghostscript 2.4 to view some PostScript files
> generated by the word processor Asterix.  The files print fine on on
> the PS printers I've tried [QMS 820, DEC PrintServer 20, Imagen, Apple
> LW].  My problem with gs is that it's not loading all the fonts [always
> seems to only load Times-Roman].

The problem is that this file is testing for the presence of the font
name in FontDirectory as a way to tell whether the font exists or
not.  This violates Adobe's guidelines on this subject (2nd Edition,
p. 421).  Adobe's suggested fix is to use the Level 2 resource
machinery.  I think a better way to do this is to go ahead and do the
findfont and then check whether the font name was the expected one:
if not, findfont did a font substitution, which FINDFONT can then
discard; FINDFONT can then substitute TimesRoman itself.

In any case, I suggest you report this problem to the makers of
Asterix, since (in my opinion) it's their bug, not Ghostscript's.

L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306
ghost@aladdin.com, ...decwrl!aladdin!ghost ; 415-322-0103 8-9 AM M-F/msg
	    "Implementation is the sincerest form of flattery."


Newsgroups: gnu.ghostscript.bug
From: pavel@parc.xerox.COM (Pavel Curtis)
Subject: Bug in ghostscript 2.4's reflected stroke joints
Organization: Xerox PARC
Distribution: gnu
Date: Mon, 13 Apr 1992 23:14:16 GMT

I believe that there is a bug in ghostscript version 2.4, in the rendering of
strokes under reflected transformations; the following small PS file exhibits
the problem:

		      50 600 translate 1 -1 scale
		      30 setlinewidth
		      0 setlinejoin
		      0 setlinecap
		      100 100 moveto
		      0 100 rlineto
		      100 0 rlineto
		      closepath
		      stroke

As is, the mitered joints on the stroke do not appear; the output looks as if
the three lines of the triangle had been drawn as individual strokes, each with
butt caps.  If the first line, which establishes the reflected transformation,
is commented out, the triangle appears as expected, with normal mitered joints.

My guess, from taking a brief look at the code, is that the bug is in the
function stroke_add (file gxstroke.c), in the section of code with the
following comment:

		/*
		 * Set np to whichever of nplp->o.co or .ce
		 * is outside the current line.
		 * We use the interesting observation that
		 * point (x2,y2) is counter-clockwise from (x1,y1)
		 * relative to the origin iff x1*y2 < x2*y1.
		 * In this case x1,y1 are plp->width,
		 * x2,y2 are nplp->width, and the origin is
		 * their common point (plp->e.p, nplp->o.p).
		 */

This comment does appear (to me, anyway) to be taking into account that the
transformation might be reflected, so that clockwise is not in the direction it
expects.  This is sheer speculation on my part, though.

	Pavel
--

>>> I've joined the League for Programming Freedom; have you?
>>> Write me or league@prep.ai.mit.edu for information.


Newsgroups: gnu.ghostscript.bug
From: RJOHNS@bnr.ca (Richard  Johns, R.)
Subject: More HP/UX 7.05 gs2.4 problems
Organization: GNUs Not Usenet
Distribution: gnu
Date: Wed, 8 Apr 1992 19:07:00 GMT

Here's another problem, not related to HP cc optimization:

> make
        ./ccgs "cc  -O  -DSYSV -Wc,-Ns5000 -Wc,-Nw500" _temp_.c gdevmem1.c
"gdevmem1.c", line 456: operands of + have incompatible types

It certainly doesn't look like there're any problems that wouldn't show up
with any cc compiler.  Any suggestions?

Thanks,
 Rick
I speak for myself, not BNR.



Newsgroups: gnu.ghostscript.bug
From: ghost@aladdin.COM (L. Peter Deutsch)
Subject: Re: pstoppm.ps colormap still wrong?
Organization: GNUs Not Usenet
Distribution: gnu
Date: Thu, 16 Apr 1992 15:20:16 GMT

Re <9204160601.AA05559@raisin-nut>
<1992Apr16.051955.23318@msc.cornell.edu>:

> Most color postscript output has 
> the rgb color definitions embedded within it, right?

I don't understand what this question means.  There is no definition
or standard for "color PostScript output."  Some file formats (e.g.,
PCX) use a colormap; some (e.g., PPM) use RGB values directly.

> So why does pstoppm.ps define and use its own colormaps?

pstoppm.ps uses a colormap only for 8-bit output, where it is
unavoidable.

> ppm24run even seems to use the default X colormap.

ppm24run does not use a colormap: it outputs 24-bit values containing
8 bits each of unmapped R, G, and B.

> Is there a newer version of pstoppm.ps that addresses this 
> problem, i.e. that uses the colors defined in the
> postscript file?

pstoppm.ps always respects the colors defined in the PostScript file.
The question is how it represents them in the output:

	- ppm1run produces black-and-white output, so there is no issue.

	- ppm24run uses 8-bit-per-component true color as mentioned above.

	- ppm8run uses a colormap.

The output of ppm8run is actually a questionable use of the PPM
format.  As I understand it, the format includes PBM (1 bit per
pixel, black and white), PGM (N bits per pixel, gray levels), and PPM
(3*N bits per pixel, true color), so 8 bits with a colormap is not
really covered.

The person who wrote the original version of pstoppm used an X
colormap, but there is no particular reason for this.  If you really
want 8-bit, color-mapped output, you can change the color map
(palette) in pstoppm easily enough: the format is documented under
the makeimagedevice operator in language.doc.

L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306
ghost@aladdin.com, ...decwrl!aladdin!ghost ; 415-322-0103 8-9 AM M-F/msg
	    "Implementation is the sincerest form of flattery."


Newsgroups: gnu.ghostscript.bug
From: 81239@novell1.rz.fht-mannheim.DE (Andre SchrTer)
Subject: driver for a nec p6 printer
Summary: anyone who has a driver for a nec p6 printer ??
Keywords: driver for nec p6
Organization: Fachhochschule fuer Technik Mannheim
Distribution: gnu
Date: Tue, 7 Apr 1992 08:55:47 GMT

hallo,
is there anyone who has a driver for ghostscript and a nec p6 printer ????
the epson driver works fine but the nec p6 can handle 360x360 dpi. this
is not suportet by the epson driver

e-mail : 81239@novell1.rz.fht-manneim.de
         borneo.inet.dkfz-heidelberg.de

Newsgroups: rec.running
From: jjprior@athena.mit.edu (Jack Prior)
Subject: Re: Re: Boston Marathon ?'s: Get the facts first
Organization: Massachusetts Institute of Technology
Date: Fri, 17 Apr 1992 00:16:59 GMT

Does anyone have information on the Marathon Expo before the race? I
went last year and really enjoyed it.  There were seminars by Dr.
Sheehan and Nancy Clark (nutrition) and a Q&A session with Greta W.
and another runner.  The retail section had alot of discounted
products and free samples (food).  Polar (Heart Monitors) was there
and was offering there products at a discount.  I'm curious what they
will be selling their computer interface for.  Last year it was
discounted under $400 (the cheapest mail order price I've seen since).

Jack
--
--------------------------------------------------------------------------
Jack Prior		| Rm. 16-011, 77 Mass. Ave.	| Phn 617-253-0469  
jjprior@athena.mit.edu	| MIT Dept. of Chemical Eng.	| Fax 617-253-2400 
BioProcess Control Lab	| Cambridge, MA  02139	 USA	| Cserve 73617,2663
From: berkery@emmax5crd.ge.com (jack berkery)
Newsgroups: rec.running
Subject: Re: track measurement
Date: 9 Apr 92 14:54:03 GMT
Reply-To: berkery@emmax5crd.ge.com (jack berkery)
Distribution: rec
Organization: GE Research Center


Track distances : Most tracks are 400 meters around on the inside lane with
100 meters on each straight and 100 meters on each curve. 400 meters is 437.6
yards. (440 yards is 1/4 mile.) 2 laps, 800 meters, is just a few yards short
of a half-mile. 4 laps on the track is 1600 meters or 1750.4 yards. A mile is
1760 yards, so to get a full mile on a metric track you must start about ten
yards (28.8 feet) back from the finish line.

TAC Rule 62, paragraph 1.
Lane widths : wherever possible each lane should be 1.22 meters (4 feet) but
not greater than 1.25 meters (4'1.5") however on tracks which do not permit 8
lanes of 1.22m, the width may be less but never less than 91.4 cm (3 feet)

TAC Rule 62, paragraph 2.
All distances run or walked shall be determined on the basis of a hypothetical
line 30 centimeters (12 inches) outward from the inner edge of the track
-------------------------------------------------------------------------------
Jack Berkery, Computer Scientist, GE Research, Schenectady NY
  berkery@crd.ge.com  "The Common Sense Coach"
Xref: sparky rec.running:1006 misc.fitness:3252
From: agrawal@lipari.usc.edu (Amitabh Agrawal)
Newsgroups: rec.running,misc.fitness
Subject: Re: Max Acceleration, Min Space
Date: 6 Apr 1992 13:36:08 -0700
Organization: University of Southern California, Los Angeles, CA
	<AJ3U.92Apr5153316@topaz.cs.virginia.edu>
	<1992Apr6.200835.11341@news.Hawaii.Edu>
NNTP-Posting-Host: lipari.usc.edu
In-reply-to: robin@uhunix.uhcc.Hawaii.Edu's message of 6 Apr 92 20:08:35 GMT


In article <1992Apr6.200835.11341@news.Hawaii.Edu> robin@uhunix.uhcc.Hawaii.Edu (Robin Amano) writes: