INFO-MAC@SUMEX-AIM.STANFORD.EDU.UUCP (01/03/87)
INFO-MAC Digest Friday, 2 Jan 1987 Volume 5 : Issue 34
Today's Topics:
Full directory in Thomas Coradeschi's disk
re:LSP vs TML Pascals
Blob Manager Source - Introducton
1986 Tax Templates
Re: Excel Formula Protection
Re: Hidding Excel formulas
More on TeXtures
TeXtures vs MacTeX
Unix, macget/macput, and Red Ryder
Copy II Mac 6.3
Distress Call from Dark Castle
Delphi Mac Digest V2 #69
Usenet Mac Digest V3 #1
----------------------------------------------------------------------
Date: Fri, 2 Jan 87 10:51:39 PST
From: dplatt@teknowledge-vaxc (David Platt)
Subject: Full directory in Thomas Coradeschi's disk
I wonder... is there any chance that you (or someone else) might have
initially formatted this diskette using the "Fat Disk Maker" utility
that's been poking around the MacUniverse for the last year or so? If
so, it's almost certainly responsible for your problems. "Fat Disk
Maker" increases the effective size of a standard (400k) disk by 2k or
so, by calling the disk-formatting routines and specifying a somewhat
smaller-than-usual size for the directory. So, you gain several k of
data/resource space, at the cost of room in the directory area. It's
meant for use when, and only when you want to squeeze a small number of
files onto a diskette and must maximize the available filespace.
The actual number of files that you can create on one of these
diskettes (or any MFS diskette) depends on the length of the filenames,
as well as on the size of the files themselves. I'm not sure whether
directories are fixed-size on HFS diskettes also... I'd guess not, but
you know what guesses are worth!
If your diskette was initialized normally (e.g. via the Finder or one
of the multi-disk formatting utilities), then it does sound as if you
may have "lost" some directory entries. I imagine that FEdit is
probably powerful enough to clean things up somehow; it *might* be
able to reset and rebuild the directory based solely on the file-tags
[risky], or you could use it to manually rebuild the directory. The
FEdit documentation may have enough information to enable you to puzzle
your way through this task; an up-to-date copy of Inside Macintosh
would also be a valuable reference.
In any case, before hacking with the disk's directory, BACK IT UP! If
you have a sector-copier, use that, and then hack the sector copy.
You could probably save yourself trouble in the long run by simply
initializing a new disk, dragging the files over onto it, and using
that disk from here on out (unless, of course, your original disk is
copy-protected in some fashion... in which case you've got an even
bigger problem!)
------------------------------
Date: Fri, 2 Jan 87 16:34:31 PST
From: digiorgi@Jpl-VLSI.ARPA
Subject: re:LSP vs TML Pascals
re: Lightspeed Pascal vs. TML (Paul Christensen of 29DEC86)
(ref: digest v5 #33)
I also just recently got my copy of LSP and spent the past couple of days
reading the manual and playing with it. Not too shabby! I haven't
written anything of great consequence yet, but my cursory glances seem
to bear out your experience.
the small Sieve benchmark distributed with TML and compiled with small
modifications under LSP gave a 5.93 second time as opposed to TML's
5.89 seconds. If you disable the R and V compiler options, the code size
is nearly 6K as opposed to TML 2K (!). I think there might be a way to
decrease library size by using all 'build it yourself' windows via InLine
calls and a custom SmallPasLib. Perhaps. And remember that the
R and V options take up space (as do the D and N options)/slow down the
execution, so shut them off before you build an application. The equivalents
are off by default in TML.
I found a couple small stickies: a demo program for window updating and
controls taken from "Hidden Powers of the Macintosh" (Lisa Pascal) finally
ran without modification under TML v2.0, when he added the EXIT(<block>)
procedure. I had to put GOTOs in again for LSP. Annoyances like that aren't
really critical although they are ugly.
There seems to be no way to Build and Save an application with the its
own icon/TYPE-CREATOR fields set/Finder attributes set without resorting to
RMaker or ResEdit. I'd appreciate hearing from anyone who knows how to do
this.
And, I found an undocumented procedure in TML in the BOXES.PAS 3D Quickdraw
example : INC(var dummy:integer); increments dummy by 1. Also the companion
DEC(var dummy:integer); exists. So far I haven't gotten the Boxes
demo to compile and run successfully under LSP. I keep getting an odd
address exception or just hanging with no error check. I haven't found any
LSP code that didn't compile under TML unless it called some of the LSP
environment windows or other specific features.
Happily, there is a list provided in the LSP manual which tells
which Lisa Pascal functions are not supported, and fairly complete info
regarding ANS Pascal compatibility and extensions as well. I love the
debugging and ease of use of the environment, although the editor needs some
nicer 'programming' features (split screen viewing, on-keyboard cursor
movement/save/tile-windows etc). The miniWriter DA is very useful here,
particularly for RMaker sources, as is ACTA.
A commented ASM dump, support of Object Pascal extensions, function/procedure
oriented segmentation, bigger than 32K data structures, etc, still make TML
valuable, as would be MPW Pascal if I could stand the pain of learning all the
features/tools/commands. TML needs a better editor also. (I use MEdit, which
at least prints correctly at the cost of some Transfer clumsiness.) But
I'll probably use LSP more because it is easier to figure things out when you
are starting a project or need to find an error. The segmentation and use of
units/libraries becomes particularly easy to figure out in LSP also.
Perhaps a useful strategy is to use LSP to develop and prototype the code
and then move the sources into TML (or MPW) for the finished product. I don't
see too many incompatibilities if you are aware of the differences.
BTW, TML v2.0 is actually quite fast to compile in a 2Meg environment
with a hard disk; fix code errors with miniWriter and don't unload the big
library files between compilation attempts and it is very acceptable.
And then there's TurboPascal from Borland...
godfrey digiorgi
arpa: digiorgi@jpl-vlsi
January 2, 1987
--
general disclaimer number 9-0K8-345.1B:
My usual apologies for the length of this blather.
My employer has no idea why I have access to this net at all and doesn't
care.
None of the products mentioned above have either my endorsement nor my
financial well being at stake.
I have a full body force-field to deflect the slings and arrows of
insipid fortune and other malcontents.
for all other disclaimers, see number 9-0K8-345.1A.
--
"the middle and not both ends"
------------------------------
Date: Fri, 2 Jan 87 17:29:04 CST
From: Paul DuBois <dubois@unix.macc.wisc.edu>
Subject: Blob Manager Source - Introducton
[note from moderator: This is Paul DuBois Blob Manager, with a demo program
along with it. This posting contains ONLY the source for Lightspeed C
and is appropriate for version 2.01. To construct the demo program you
need to follow his instructions below. DAVEG ]
To make the Demo, you should be able to download all the stuff,
go into Lightspeed, open the project file and say Run. This will
make Blob Manager Demo 1.01, which is slightly different than the
Demo that was posted a while ago: (a) you can drag globs back onto
the home blob to detach them (detaches were only by double-click before),
and (b) the Hebrew Alephbet scenario has been fixed - two of the letters
were reversed.
I have a report from Canada that the Demo crashes on a Mac Plus when
launched from Finder 5.4A. I don't know what to say about this, since
I don't program on a Plus.
Here's how the project is laid out:
Header files:
-rw-r--r-- 1 dubois 1569 Jan 2 10:46 BlobDemo.h
-rw-r--r-- 1 dubois 4305 Jan 2 10:44 BlobMgr.h
Segment A:
-rw-r--r-- 1 dubois 2715 Jan 2 10:46 DemoAnagram.c
-rw-r--r-- 1 dubois 3605 Jan 2 10:46 DemoFar.c
-rw-r--r-- 1 dubois 6427 Jan 2 10:46 DemoFgg.c
-rw-r--r-- 1 dubois 3786 Jan 2 10:46 DemoFsh.c
-rw-r--r-- 1 dubois 5247 Jan 2 10:46 DemoHang.c
-rw-r--r-- 1 dubois 7388 Jan 2 10:47 DemoHeb.c
-rw-r--r-- 1 dubois 6170 Jan 2 10:47 DemoLib.c
-rw-r--r-- 1 dubois 3401 Jan 2 10:47 DemoMagicSquare.c
-rw-r--r-- 1 dubois 804 Jan 2 10:47 DemoMain.c
-rw-r--r-- 1 dubois 2954 Jan 2 10:47 DemoMenu.c
-rw-r--r-- 1 dubois 13811 Jan 2 10:47 DemoPeg.c
-rw-r--r-- 1 dubois 7667 Jan 2 10:47 DemoPong.c
-rw-r--r-- 1 dubois 9730 Jan 2 10:47 DemoPyramid.c
-rw-r--r-- 1 dubois 11410 Jan 2 10:47 DemoRadix.c
-rw-r--r-- 1 dubois 4920 Jan 2 10:48 DemoStates.c
-rw-r--r-- 1 dubois 4921 Jan 2 10:48 DemoSwap.c
-rw-r--r-- 1 dubois 5232 Jan 2 10:48 DemoToh.c
-rw-r--r-- 1 dubois 6561 Jan 2 10:48 DemoTtt.c
-rw-r--r-- 1 dubois 935 Jan 2 10:48 DemoWind.c
-rw-r--r-- 1 dubois 8762 Jan 2 10:49 DemoWolf.c
Segment B:
(you could also make these into a project and include the project)
-rw-r--r-- 1 dubois 457 Jan 2 10:44 BMgrCalcRegion.c
-rw-r--r-- 1 dubois 10870 Jan 2 10:44 BMgrClick.c
-rw-r--r-- 1 dubois 2940 Jan 2 10:44 BMgrDrag.c
-rw-r--r-- 1 dubois 4985 Jan 2 10:44 BMgrDraw.c
-rw-r--r-- 1 dubois 3193 Jan 2 10:44 BMgrFlags.c
-rw-r--r-- 1 dubois 1033 Jan 2 10:44 BMgrFreeze.c
-rw-r--r-- 1 dubois 873 Jan 2 10:44 BMgrHideShow.c
-rw-r--r-- 1 dubois 1824 Jan 2 10:44 BMgrHilite.c
-rw-r--r-- 1 dubois 1311 Jan 2 10:44 BMgrHitTest.c
-rw-r--r-- 1 dubois 896 Jan 2 10:44 BMgrIndex.c
-rw-r--r-- 1 dubois 758 Jan 2 10:44 BMgrLoop.c
-rw-r--r-- 1 dubois 2142 Jan 2 10:44 BMgrMatch.c
-rw-r--r-- 1 dubois 1552 Jan 2 10:44 BMgrMove.c
-rw-r--r-- 1 dubois 6041 Jan 2 10:44 BMgrNew.c
-rw-r--r-- 1 dubois 2721 Jan 2 10:44 BMgrPict.c
-rw-r--r-- 1 dubois 528 Jan 2 10:44 BMgrRand.c
-rw-r--r-- 1 dubois 1257 Jan 2 10:44 BMgrSetProc.c
-rw-r--r-- 1 dubois 1235 Jan 2 10:44 BMgrSetRgns.c
-rw-r--r-- 1 dubois 1835 Jan 2 10:44 BMgrShuffle.c
-rw-r--r-- 1 dubois 709 Jan 2 10:44 BMgrTrackMouse.c
-rw-r--r-- 1 dubois 2801 Jan 2 10:44 BMgrTrans.c
-rw-r--r-- 1 dubois 1510 Jan 2 10:44 BMgrZTrans.c
-rw-r--r-- 1 dubois 1720 Jan 2 10:44 BMgrZoom.c
Segment C:
-rw-r--r-- 1 dubois 10066 Jan 2 10:49 PickWord.c
-rw-r--r-- 1 dubois 4508 Jan 2 10:49 TextDlog.c
and MacTraps and TransSkel
BMgr.pit.Hqx Blob Manager source
BlobDemo1.pit.Hqx Blob Manager Demo source
BlobDemo2.pit.Hqx
BlobDemo3.pit.Hqx
BlobDemo4.pit.Hqx
BlobDemo5.pit.Hqx
BlobDemo.proj.Hqx Blob Manager Demo project shell (LSC 2.01)
BlobDemo.proj.rsrc.Hqx Blob Manager Demo resource file
[ archived as
[SUMEX-AIM.Stanford.EDU]<INFO-MAC>BLOBMANAGER-SOURCE.HQX
[SUMEX-AIM.Stanford.EDU]<INFO-MAC>BLOBMANAGER-DEMO-SOURCE-PART1.HQX
[SUMEX-AIM.Stanford.EDU]<INFO-MAC>BLOBMANAGER-DEMO-SOURCE-PART2.HQX
[SUMEX-AIM.Stanford.EDU]<INFO-MAC>BLOBMANAGER-DEMO-SOURCE-PART3.HQX
[SUMEX-AIM.Stanford.EDU]<INFO-MAC>BLOBMANAGER-DEMO-SOURCE-PART4.HQX
[SUMEX-AIM.Stanford.EDU]<INFO-MAC>BLOBMANAGER-DEMO-SOURCE-PART5.HQX
[SUMEX-AIM.Stanford.EDU]<INFO-MAC>BLOBMANAGER-DEMO-PROJECT.HQX
[SUMEX-AIM.Stanford.EDU]<INFO-MAC>BLOBMANAGER-DEMO-RSRC.HQX
DAVEG
]
------------------------------
Date: Fri, 2 Jan 87 08:59:40 PST
From: barad%macbeth.usc.edu@usc-oberon.ARPA (Herb Barad)
Subject: 1986 Tax Templates
Here are the 1986 Excel tax templates. I
created these from a free 1985 version that came over the net
last year. Happy Tax Season.
Herb Barad [USC - Signal and Image Processing Institute]
USENET: ...!sdcrdcf!usc-oberon!brand!barad or
...!mcvax!seismo!sdcsvax!sdcrdcf!usc-oberon!brand!barad
ARPANET: barad@brand.usc.edu
USMail: Univ. of Southern California
Powell Hall 306, MC-0272
Los Angeles, CA 90089-0272
phone: (213) 743-0911
[ archived as
[SUMEX-AIM.Stanford.EDU]<INFO-MAC>EXCEL-TAXTEMPLATES-1986.HQX
DAVEG
]
------------------------------
Date: Fri, 2 Jan 87 11:50:56 EST
From: Mark Nodine <mnodine@labs-b.bbn.com>
Subject: Re: Excel Formula Protection
In the Format menu, there is an item called Cell Protection... If you open
this up, you have a choice of whether the cell should be protected or whether
the formula should be hidden. The default is protected/not hidden. These
states do not take effect until you choose Protect Document... from the Options
menu. Simply hitting a return will create a document protected with no
password.
So, to create the form you want, select the cells which are allowed to be
modified, choose Cell Protection... and un-choose the Protected option. Then
choose Protect Document... and everything will be set up.
--Mark
------------------------------
Date: 2 Jan 87 13:28 CST
From: MACA.AFCC@AFCC-4.ARPA
Subject: Re: Hidding Excel formulas
Select the cell to have its formula hidden and use the Cell Protection option
from the menus - click on the "hidden" box - OK
Select the cells for which the user still needs access, choose the Cell
Protection menu option and deselect the protected option.
Choose the Protect Document option and protect your spreadsheet. Voila. now
check it out by selecting a cell with a formula you wanted hidden - it
shouldn't appear in the command window anymore. If you didn't put any borders
around the unprotected cells, you will now be able to spot the
"open"/changeable cells with a dotted underline.
I wish excell had the same kind of password protection that Double Helix has,
it would really be nice to create an entire work environment for someone (such
as a client) which would be fool proof. Excell can still be diddled with in
such a way as to confuse the user (widows off the screen - too many menu
options for your specific sheet etc). I'd like to be able to just create a
menu sheet of macros and thats all the user would have to fiddle with.... More
than you asked for so I'll shut-up. Hope this helps.
------------------------------
Date: Wed, 31 Dec 86 14:03:52 PST
From: <DAVEG@slacvm.bitnet>
Reply-to: DAVEG%SLACVM.BITNET@forsythe.stanford.edu
Subject: More on TeXtures
We just got version 0.95 of TeXtures in the mail from Addison Wesley.
This version is getting there but unfortunately is still less than useful
for production work, especially if you wish to do math (and that is the main
reason for using TeX on the Mac as far as I'm concerned). Here are some
things I've encountered:
1. The quality of the Fonts as printed on the LaserWriter is still not up
to snuff. As far as I'm concerned, printout on the LaserWriter should be
EXACTLY like printout on other laser printers if you use the TeX fonts.
Unfortunately this is not the case. The fonts are much lighter than the
equivalent fonts on our mainframe. Using a larger font than 10 or 12 point
looks very poor. The math fonts still leave a lot to be desired. They are
much poorer quality than our mainframe fonts. This is the number 1 problem
I have seen with this package...the final quality of documents is still not
up good enough, there are bugs in the print routines when doing italicized text
which made it impossible to use the standard italic fonts.
2. You can now use the built in postscript fonts in your document and that
gives MUCH better quality output. Unfortunately the mapping of characters
does not allow you to use the LaserWriter symbol fonts instead of the standard
TeX math fonts (which look poor in this package, but normally are excellent).
One bad thing about using the postscript fonts in your files is that you
can't transport a DVI file to a non-postscript printer if you are using them.
3. You now can export a DVI file from TeXtures. I uploaded a DVI file and it
printed more or less OK on our mainframe. Now they need to let you include
just the DVI file for preview.
4. Keeping the old DVI part around all the time sure makes a hassle. You
frequently have to wait for the Preview window to update before you can
go about your business. They should disable update events to the preview
window when it isn't the foremost window.
5. Using fonts besides those in the standard font file is a pain since you
have to load them by hand. There may be a way to include the fact that you
want them in your TeX file but the manual is far too incomplete to let
you know how. Basically you have to load them by hand EVERY time you start
TeXtures if you use anything but the basic fonts.
6. There still are some printer bugs. The italicized stuff is one of the major
ones and the spacing on the page doesn't correspond yet with what it should
be. I also found that if I included postscript in my file as per the SPECIAL
command (not yet well documented) then my coordinate system starts in some
crazy orientation, not a standard one. This doesn't work properly as far
as I'm concerned.
7. So far the imagewriter printing is pathetic. If you have an imagewriter
and want to use TeX, this package is not well suited for it yet.
8. It is easy to create a format file (.FMT) using the \dump command in
TeX. All you need to do is make a TeX file with the stuff you want to
be included in your format file and then place a \dump at the end of
it. You will get a standard file dialog at the proper time to allow
you to name your format file and place it in the folder of choice.
You can then double-click this file to start TeX which selects this
format file as the one to use. I downloaded TeX macro files from our mainframe
and they were used without change to generate format files.
9. The inclusion of Macintosh pictures in a TeX document is easy
and looks great. Basically you just paste your pictures into your TeX
document and tell TeX where to put them. Unfortunately there is no
moving your pictures around interactively, only in the batch mode. One
thing which could be improved here is to allow TeX to find the size of
the picture from the picture itself. As it stands you need to look up
the size and manually type the size into your source.
Well I've bitched a lot about problems with this package here and it
is deserved. The biggest problem is the FONT problem which really degrades
from the final quality of output. I think the program is VERY promising
but needs some polishing.
David Gelphman BITNET address: DAVEG@SLACVM
Bin #88 SLAC ARPANET address: DAVEG@SLACVM.BITNET
Stanford, Calif. 94305 UUCP address: ...psuvax1!daveg%slacvm.bitnet
415-854-3300 x2538
usual disclaimer #432 applies: my employer apologies for the fact
that I have access to this net.
------------------------------
Date: 2 Jan 87 15:58:00 EST
From: <bouldin@ceee-sed.ARPA>
Subject: TeXtures vs MacTeX
Reply-to: <bouldin@ceee-sed.ARPA>
In the Oct, 1986 Notices of the American Mathematical
Society (pg. 741), there is a column on Mathematical Typsetting by
Richard Palais. There is a general discussion of TeX, technical word
processing on the Mac, and a comparison of TeXtures and MacTeX.
His general conclusions were that TeXtures is the winner (so far) in the
Macintosh TeX competition. TeXtures won in typesetting and previewing
speed and ease of including graphics. MacTeX won in handling error
messages from TeX. Both programs are validated by running the trip.tex
file for formatting, and so are guaranteed to be "full" TeX.
I would be interested in hearing from anyone who has seen TeXtures and
MacTeX running (side-by-side if possible). I will summarize responses to
the net.
------------------------------
Subject: Unix, macget/macput, and Red Ryder
Date: Fri, 02 Jan 87 15:28:17 -0800
From: leiner@riacs.edu
Up/down loading from a Unix machine to the MAC using Macterminal and
macget/macput on Unix is real easy. You select Macterminal 1.1 as the
protocol and away you go.
Red Ryder doesn't appear to support Macterminal 1.1, though. Does
anyone know if there are settings to Red Ryder that will allow it to
work with macget/macput?
Thanks for the help.
Barry
------------------------------
Date: Wed 31 Dec 86 23:21:40-PST
From: David L. Edwards <DLE@SRI-STRIPE.ARPA>
Subject: Copy II Mac 6.3
I just received my update copy from Central Point. I am hoping that this
version fixes the problems described with 6.2 but I obviously don't have
much experience with it yet.
My first impression was that I was disappointed by the very short list of
programs which Copy II Hard Disk worked with. The list didn't seem to
increase much since version 4... I think that having now bought two
upgrades, the version 6 will be the last.
-dle
PS: Maybe they could find an unemployed Mac program to pretty up the user
interface... it's pretty poor.
------------------------------
Date: Fri, 2 Jan 87 22:09 N
From: <FRUIN%HLERUL5.BITNET@WISCVM.WISC.EDU> (Thomas Fruin)
Subject: Distress Call from Dark Castle
PLEASE HELP!
I've been having a terrific time mastering the depths and dangers of the
fantastic new game Dark Castle, but... HOW DO I AVOID BEING 'POUNDED' (pun
intended) by the heavy weight in the dungeon when I try to grab one of the
keys that is supposed to help me out of there?
I'm aware that I don't sound to coherent in the above sentence, but players
of the game will know the feeling of frustration :) Can anybody give me a
clue or are you simply going to have to abide by the laws of statistics built
into the game that are going to make sure you will be splatterend at least
x times out of 100? Sigh. Deep sigh. Make it about 60 splatterings per 100.
There's got to be a way around it! And me, a budding player, who's just
getting the hang of the game, shouldn't get this weight to bear each time he's
just managed to master the dungeon (don't you *love* the groan of the guy who
bears the whip) when you hit him with what we call in Dutch a 'goedendag'?
Goedendag means 'good day' in that language :)
HELP!
-- Thomas
FRUIN@HLERUL5.BITNET
(Leiden, Netherlands)
------------------------------
Date: 31 Dec 86 20:47:25 EST
From: Jeffrey Shulman <SHULMAN@RED.RUTGERS.EDU>
Subject: Delphi Mac Digest V2 #69
Delphi Mac Digest Wednesday, 31 December 1986 Volume 2 : Issue 69
Today's Topics:
RE: The Flying HD20 Bros. (2 messages)
Colored LaserWriter Toner??
RE: dMac III bought by Nantucket
Fred's Soap Box (2 messages)
A+ Magazine Third Annual Software Poll
RE: A+ Magazine Third Annual Software Po
Silliness
LightspeedC & Merry Xmas
Not again...
DiskTimerII results
RE: Sample FKEY info desired
RE: Delphi Diegsts (PSU problems)
RE: DiskExpress/DataFrame problems
Acta Format (5 messages)
Disk Drive help
HD 20 (3 messages)
RE: MIDI Programming Advice Wanted
RE: Warp-9
Wall Street Journal
completion routines in L.Pascal? (3 messages)
Double height or wide letters (3 messages)
Question on MacWrite & Laserwriters....
RE: Question on MacWrite & Laserwriters.
Lightspeed C Report
Disk Express and MacXL (2 messages)
[ archived as
[SUMEX-AIM.Stanford.EDU]<INFO-MAC>DELPHIV2-69.ARC
DAVEG
]
------------------------------
Date: 1 Jan 87 10:02:57 EST
From: Jeffrey Shulman <SHULMAN@RED.RUTGERS.EDU>
Subject: Usenet Mac Digest V3 #1
Usenet Mac Digest Thursday, 1 January 1987 Volume 3 : Issue 1
Today's Topics:
Re: Is there uEMACS for the Mac??
Invisible folders
Macsbug Question
Comp.Sys.Mac convention at Macworld Expo?
Reflections on InfoWorld
MacEnhancer (2 messages)
Macs in England
Re: Sample FKEY info desired
Packit checksum problem (was Re: MIDI Programming Advice Wanted.)
Editing item numbers in resources
Reflex
Ugly Icon
Re: Invisible folders
Re: Macs in England
Thin lines from the LaserWriter
Mac Snap by DOVE
MacIntax?
Re: MIDI Programming Advice Wanted.
Re: Editing item numbers in resources
Need tty <--> AppleTalk hack
Re: Thin lines from the LaserWriter
STELLA
Re: Thin lines from the LaserWriter
Scientific Text Processing: Overstriking Symbols.
Re: MacIntax?
Re: Thin lines from the LaserWriter
Re: Ugly SCSI Icon
Re: Ugly Icon
[ archived as
[SUMEX-AIM.Stanford.EDU]<INFO-MAC>USENETV3-1.ARC
DAVEG
]
------------------------------
End of INFO-MAC Digest
**********************