[fa.info-mac] INFO-MAC Digest V3 #45

info-mac@uw-beaver (10/04/85)

From: Moderator Richard M. Alderson <INFO-MAC-REQUEST@SUMEX-AIM.arpa>


INFO-MAC Digest          Thursday, 3 Oct 1985      Volume 3 : Issue 45

Today's Topics:
                           Paintmover success!
                New version of xbin -- fixed checksum bug
                   MacDraw/MacPaint Conversion Utility
                       FastEddie -- A Text Editor
                       New version of SimpleTools
                             DES Application
                          Vt52 DA, version 1.4
                      AppleTalk cabling components
                         teScrpLen, menu buffers
                      Re; MacTerminal SAVE Command
                            Xinet information
                                ExperLISP
      RE: Book Review (of Micro Analyst's book on Copy Protection)
             problems with macwrite 4.5 and the laserwriter


----------------------------------------------------------------------

Subject: Paintmover success!
Date: 30 Sep 85 10:51:30 EDT (Mon)
From: Alan Dahlbom <adahlbom@BBNCC4.ARPA>

I have managed to get the Paintmover program to start. It seems that it
requires a *full* 512k mac to start-up (No ram-disks, etc). I haven't been
able to get it to do very much once it starts (it doesn't crash though),
but thats probably my problem.

Alan

------------------------------

Date: 1 Oct 85 (Tue) 01:29:50 EDT
From: Dave Johnson <ddj%brown.csnet@CSNET-RELAY.ARPA>
Subject: New version of xbin -- fixed checksum bug

After an hour or two of bug-chasing, I tracked down the cause of the
recently reported checksum errors in "xbin".

The problem showed up when there was a run of three or more 0x90
characters.  The sequence 0x90NN indicates that the previous character
should be repeated NN times, with the exception that 0x9000 specifies a
literal 0x90.  The bug was when a literal 0x90 was supposed to be repeated,
the character before the 0x90 was used instead.  So where 2090009003 should
have produced a 20 and 3- 90's, it came out 20 90 20 20.

Here is the fix to version 2.1, if you can't get 2.3 right away:
*** xbin.c	Tue Oct  1 01:16:20 1985
--- xbin.c.fixed	Tue Oct  1 01:17:21 1985
***************
*** 545,550
  		if ((rep = getq_raw()) == EOF)
  			return EOF;
  		if (rep == 0) {
  			return RUNCHAR;
  		}
  		else {

--- 545,551 -----
  		if ((rep = getq_raw()) == EOF)
  			return EOF;
  		if (rep == 0) {
+ 			lastc = RUNCHAR;
  			return RUNCHAR;
  		}
  		else {

Source for version 2.3 (there was no 2.2) accompanies this message, and
should be archived on [sumex]<info-mac>unix-xbin.shar.  The source is also
being posted to net.sources.mac

In addition to the above-described bug fix, this version includes fixes
people have sent me during the last 6 months or so, and the performance
improvements done by Dan LaLiberte at UIUC (sorry for the delay...).

	Dave Johnson
	Brown University Computer Science
	ddj%brown@csnet-relay.ARPA
	{ihnp4,decvax,allegra,ulysses,linus}!brunix!ddj

[This version has replaced the older one in [SUMEX]<INFO-MAC>UNIX-XBIN.SHAR.
--RMA]

------------------------------

Subject: MacDraw/MacPaint Conversion Utility
Date: 30 Aug 85 09:39:49 EDT (Fri)
From: Alan Dahlbom <adahlbom@BBNCC4.ARPA>

Here is a quick and dirty utility you may wish to add to info-mac.  I have
been calling it MakePaint.  It takes as input either PICT type files (e.g.
from MacDraw), MacPaint files, or PICTs from the clipboard and generates as
output MacPaint files.  MakePaint shows you a mini-version of the MacPaint
image it is manipulating.  Use the mouse on the mini-image to cut, copy,
paste, invert, clear or zoom.  The net result is you can:

1) Convert MacDraw PICT files to MacPaint files (handy if you want to print
MacDraw docs using MacQMS, etc).

2) Cut, Copy, Paste sections of MacPaint documents that are up to a full
page in size.

3) 'Zoom' small sections of a picture up to full page size.

4) Mouse can be used to indicate rectangle for pasting from clipboard.

Caveat:  MakePaint is a small program that uses *lots* of memory.  On 128k
machines the size of images and PICTs you can manipulate is constrained.
Use a Fat-Mac if possible.  Also:  I have pasted full page pictures from
the MacPaint documents via MakePaint and the clipboard into MacWrite with
no problem, but I don't know how other applications or even MacWrite
running in 128K will react to these huge images.  Good Luck!

[Archived as [SUMEX]<INFO-MAC>UTILITY-MAKEPAINT.HQX.  The month-long delay
in posting was caused by it being submitted to INFO-MAC-REQUEST; more than
one person checks this mailbox, so if something doesn't get flagged, it may
get missed.

PLEASE, everybody, send administrivia to info-mac-request, and items for
posting/archiving to info-mac.  --RMA]

------------------------------

Date: Mon 30 Sep 85 08:11:54-CDT
From: CS.RICHMANN@R20.UTEXAS.EDU
Subject: FastEddie -- A Text Editor

FastEddie is a 37K text editor designed for speed, but containing many
features that make it especially useful for programmers.  Features include
auto save, glossary, automatic parenthesis matching, use of 11 copy-paste
buffers, block move of text right or left, and source code, error listing
correlation for Megamax-C.  You can change the startup defaults and/or use
menu commands to change the font, word wrap around mode, auto indent, and
insert vs. overwrite mode.  All menu commands and the search/find/change
dialog have keyboard equivalents.  The number of simultaneously open files
is limited only by memory.  Output is a text file compatible with the Apple
MDS editor or MockWrite.

The author, Daniel Grossbard, is a Univ of Texas student who is making a
demo version available for free, unlimited distribution.  This freeware
version is limited to editing files of 11K or less, but is totally
functional in every other respect.  A 10K documentation file is included as
a sample.  Both the demo and the documentation are attached in a Packit
file.  (Suggested info-mac name is Utility-Fasteddie.Hqx)

Please note the usual disclaimers apply.  I am helping Daniel promote his
work because I think the free demo is useful in its own right.

[Archived as [SUMEX]<INFO-MAC>DEMO-FASTEDDIE.HQX.  --RMA]

------------------------------

Date: Tue, 1 Oct 85 23:39:35 pdt
From: erik@ucbssl.CC.Berkeley.EDU (Erik Kilk)
Subject: New version of SimpleTools

Here is an updated version of SimpleTools.  Included are the SimpleTools
sources, a MacWrite document, and an example using some of the easy and
advanced features in the SimpleTools library.

SimpleTools is a set of subroutines which greatly ease the use of the
Macintosh toolbox.  It is mainly intended to be used for your smaller
applications where you would rather not be too concerned with reading
Inside Macintosh over again.  The subroutines are currently written in C
and were done so using the Megamax compiler.  They are designed to be
compiled into an object file.  Your program will then link in this object
file at the same time it links in the toolbox interface.  When you receive
the SimpleTools source, you should compile it into SimpleTools.o.  You can
then compile the demo, SimpleDemo, and link it to SimpleTools.o.

For example, lets say you want the menu items named "Zoom" and "Widen"
under the menu "View".  You would like the procedure:

	zoom()
	{
	 zoomfactor++;
	}

to be executed when the user selects Zoom and:

	widen()
	{
	 zoomfactor--;
	}

to execute when Widen is selected.  You would both create the menus on the
menu bar AND inform SimpleTools what to do with the calls:

	menu ("View", "Zoom", zoom);
	menu ("View", "Widen", widen);

Then, your program would run by repeatedly calling SimpleEvents, like:

	main()
	{
	 setup();
	 for (;;) SimpleEvents();
	}

Several other features are included in SimpleTools:

1.  Window creation with assignment of procedures to be executed on window
activation, deactivation, when the mouse is clicked in it, and when an
update occurs.

2.  Assignment of procedures to be "run" each time SimpleEvents() is
called.  This can easily make it look like multi-subroutines are running
concurrently.

3.  Generic prompt() and message() routines which pop up a small dialog box
for you.  For example:

	prompt("What is your name?", answer)

is all yo have to do to get a dialog box up requesting the user's name.
The answer goes into the string answer.

4.  Automatic setup of the Apple, File, and Edit menu so even your simplest
of programs will still have Desk Accessories.

5.  Many, many, hidden options that you will never know about unless you
care to know about them.  (This was a major design goal of SimpleTools--
hide options and use the most common default.)

This has just been a summary of the SimpleTools routines.  I'm sure you
could find them very useful.  Many users of SimpleTools have been very
pleased with this idea and have saved many hours of studying and
programming.  To those people, thanks for your letters, they are very
highly appreciated.

                                    Erik

P.S.  If you don't have access to the network library, feel free to send a
self-addressed, stamped envelope and a disk (full of any goodies you have)
to Erik Kilk, 1325 Nord Ave #155, Chico, CA 95926, and I'll copy my master
disk for you.

[The new files are to be found on [SUMEX]<INFO-MAC>, as
DEMO-SIMPLETOOLS.HQX, DEMO-SIMPLETOOLS-C.HQX, UTILITY-SIMPLETOOLS-C.HQX,
and UTILITY-SIMPLETOOLS.DQC.  --RMA]

------------------------------

Date: Mon, 30 Sep 85 13:05:15 EDT
From: Robert E. Yellen (MISD-SEAD) <ryellen@Ardc.ARPA>
Subject: DES Application

This is an application based on the National Bureau of Standards Data
Encryption Standard. It appears that it will encrypt and type of Macintosh
file. I have used it on MacWrite (entire) documents and on MacPaint
documents with success. It is written by John P. Powers and is Shareware
($15). I downloaded it from Mass Mac Elec.

[Find this program in [SUMEX]<INFO-MAC>UTILITY-DES-ENCRYPTION.HQX.  --RMA]

------------------------------

Date: Mon, 30 Sep 85 12:46:37 EDT
From: Robert E. Yellen (MISD-SEAD) <ryellen@Ardc.ARPA>
Subject: Vt52 DA, version 1.4

Here's a nice DA that is a vt52 emulator. It is written by Alan Dahlbom.
He has place it in the public domain.

He can be reached at adahlbom@bbncc4.arpa

[Archived in [SUMEX]<INFO-MAC>DA-VT52.HQX.  --RMA]

------------------------------

Date: Mon, 30 Sep 85 10:23:44 pdt
From: Leo Hourvitz <leo%apple.csnet@CSNET-RELAY.ARPA>
Subject: AppleTalk cabling components

AppleTalk-compatible connectors, barrels, and wire is available from:

HB Associates
(Hank Lorta is the person I spoke with)
(800) 423 4224 in CA
(800) 423 3014 outside CA

As of last Friday, here's the info about AppleTalk-compatible cabling
parts:

Assembly Plug: Part # 815-0878A $2.75 ea.

Extender (barrel): Part # 519-0300B $3.00 ea.

Cable is available in 500 or 1000 foot reels:

FEP cable (Teflon-coated, req'd by many building codes for ducts or other
parts of buildings) Part #CBL 6228 $0.90/ft

PVC cable (for other places) Part #CBL 6242 $0.25/ft

Quantity discounts may be available for orders of over 25 pieces of any
individual item.

The AppleTalk cable that comes in the Connector Kits (the 2 m. cables) is
equivalent to the PVC cable; however, the custom wiring kit comes with the
equivalent of the more expensive FEP cable.

Usual disclaimers apply:  furthermore, I'm not even a customer, I just know
about this stuff's being available, and report it for any interested
parties.

String those AppleTalks!

Leovitch

Leo Hourvitz
Apple Computer, Inc.

------------------------------

Date: Fri, 27 Sep 85 15:35:47 pdt
From: Leo Hourvitz <leo%apple.csnet@CSNET-RELAY.ARPA>
Subject: teScrpLen, menu buffers

Two answers to posted questions:

TEScrpLength, the variable at $AB0 in low memory, is a word.  The word at
$AB2 is used for future system software.

The buffer that saves the bits when a menu is pulled down is allocated in
the heap, with a good old NewHandle call.

Keep on Macking,
Leovitch

Leo Hourvitz
Apple Computer, Inc.

------------------------------

Date: 30 Sep 85 13:35:13 GMT
From: miquelon @ DCA-EUR
Subject: Re; MacTerminal SAVE Command

In Vol 3, Issue 43, Tony Siegman noted some problems in trying to use SAVE
and SAVE AS... commands in MacTerminal.

I constantly use this feature and, while it is admittedly not totally
consistant with other applications, SAVE AS... works in a very logical way
to save a downloaded file.

If I am in MacTerminal and discover something I want to download; I first
CLEAR LINES OFF THE TOP and RESET (so as not to garbage up my download
file) then read the desired file (in whatever way is required by the host).
Then I pull down the FILE menu, select SAVE AS... and assign a name, NEW
for example, then click the SAVE button.  Next, and here is apparently
where Tony is having his problem, pull down the FILE menu again and CLOSE
NEW.  Once again pull down the FILE menu, select OPEN and open the ORIGINAL
MacTerminal document (You will still be logged in to the host).  Now to
free up disk space, CLEAR LINES OFF THE TOP; and proceed with your session.
With two drives, you can change drives in the SAVE AS...  dialog box before
clicking to SAVE NEW; just remember to change drives again when ready to
OPEN the original document.  When you log off the host, you can then OPEN
NEW and do whatever you want with it.  Or you can QUIT MacTerminal, and you
will have a MacTerminal format document named NEW to do with as you wish.

The logic is not quite as Tony explained.  All MacTerminal commands operate
only on the currently open MacTerminal document.  So, if you CLEAR LINES
OFF THE TOP while NEW is open, sure enough they are all erased.  However,
all those lines are still in the closed original document, so you can
easily recover if you goof.  Since the contents of any MacTerminal document
are saved when you CLOSE or QUIT, the only time I have found SAVE useful is
when I have modified the control settings for a previously set up document.
I agree, the manual is not very clear on this.  I discovered it by trial
and error after a number of frustrating attempts.  I just started
intuitively hacking around; that is the beauty of the Mac and most of the
applications.

Dave Miquelon <miquelon @ dca-eur.arpa>
HQ USEUCOM, WSE-E, Box 832
APO NY 09128

------------------------------

Subject: Xinet information
Date: 01 Oct 85 12:05:44 EDT (Tue)
From: meltsner@athena.MIT.EDU

I finally received a packet on Xinet, Mt. Xinu's Appletalk to Unix (BSD)
package.

There are two versions, Xinet/DDP, which gives you DDP capabilities for Vax
to Appletalk (and is claimed to be available now) and Xinet/ATP, which will
give you name-binding, data transfer (FTP??), and Mac diskette emulation on
the Unix host (available 3Q '85).

Currently, the interconnection hardware is a version of the Seagate board,
and they are working on getting a production version of it (from another
Berkeley company, Kinetics, which hasn't sent me any info), as well as
Unibus, Q-bus, or Multibus interfaces.  (When I called Mt. Xinu, the
engineer said that the Ethernet-Appletalk gateway was the only one which
seemed probable.)

Sources and binaries are available, ranging from $1,500 for Xinet/DDP
binary to $20,000 for source and unlimited internal binaries for Xinet/ATP.
The current price of the Ethernet-Appletalk gateway is $7000.

When I talked to the engineer there, he said they have a "rudimentary"
terminal emulator, and were working on a better one.  He said they also
were planning to provide Unix-Laserwriter spooling software.

Personally, I'm thrilled about everything but the price (which is a bit of
shock to those of used to microcomputer software prices.)  If they get the
terminal emulation and spooler working, I'll try to get the money together
to put it on our (planned) uVaxen and Macintosh lab.

					Ken

------------------------------

Date: Mon 30 Sep 85 15:25:02-PDT
From: Marvin Zauderer <ZAUDERER@SU-SUSHI.ARPA>
Subject: ExperLISP

I've been using ExperLISP Version 1.04, and I've come to the point where
I'd like to use CopyBits.  Unfortunately, V1.04 doesn't support CopyBits.
In order to use the CopyBits procedure, I believe that an assembly-language
interface would have to be written, so that the parameters are in the right
places, the correct registers are saved, etc.  Is anyone using CopyBits in
ExperLISP (and hence has written the interface)?

-- Marvin

------------------------------

Date: Sun 29 Sep 85 19:47:11-CDT
From: Werner Uhrig  <CMP.WERNER@R20.UTEXAS.EDU>
Subject: RE: Book Review (of Micro Analyst's book on Copy Protection)

RE: Book Review (of Micro Analyst's book on Copy Protection)

Given that I know both the author and contents and history of this book, I
thought this group may be interested in a follow-up on the matter, so I called
up Les Herbst, both to inform him about this posting and to ask his reaction.

Even though the posting was anonymous (at least I assume that Paul Springer,
pds@pdc750.UUCP, was the party that forwarded, rather than the author - BTW, I
don't think anonymity is justified here), Les immediately said that he thinks
he knows who the offended party is, remembering a very unpleasant caller, who
expected and insisted on receiving more or less a recipe for copy-protection on
the MAC (or maybe cracking it ??!!).  And given that the conversation turned
unpleasant and unproductive, Les hung up on the caller.  And my impression of
Les as a person and a businessman leads me to think, that I would have probably
hung up a lot sooner than he did.  But let's put all of this aside as hearsay,
and get to some facts.

Les wrote his thesis on the topic of Copy Protection (Dec 83, EE-Dept, U-Texas
at Austin), and given that there is very little published in this field, a
"popularized" book version was an idea many of us would have had, too.  I
assume, Les did most of his research before the MAC was out, and adding a
chapter on the MAC (and developing the MacZAP software) was, probably, an
afterthought.  When I read the book summer 84, I, too was disappointed by both
the list-price of $40 dollars and the lack of info about the MAC, and told Les
as much, and he shared my concern but also did a reasonable job of justifying
both.  He also indicated at that time, that he hoped that both the MAC and his
MacZAP software would be succesful enough to justify writing an update to the
book. He has since done so (about 30 pages), and expects to be marketing a
second edition of his book late this year.  Owners of the first edition should
be able to acquire this at a nominal cost (between $5 and $10), Les indicated.

But he will NOT provide a cooking-recipe for either CONSTRUCTING or BREAKING
copy-protection software; he also has in the past rejected offers to consult
companies in the design of copy-protection, as he found that incompatible with
improving his MacZAP-software - which may seem logical on first sight, but then
again such an offer could be quite lucrative, I could imagine.

If and when I get to read the additional 30 pages, I may be able to post a
follow-up, but don't bet on it.  Over the past year, I never did get to post
the review of the first edition of the book (or of MacZAP), even though I had
intended to.  Which again reminds me how valuable this forum here is, to
collect facts and info which allow all of us to make "the right decisions" ...

            Cheers, Werner (biased, maybe, but with nothing to lose or gain)

------------------------------

Date: Wed,  2 Oct 85 11:47:25 PDT
From: DAVEG%SLACVM.BITNET@Forsythe
Subject: problems with macwrite 4.5 and the laserwriter

From: David M. Gelphman         415-854-3300 x3186   DAVEG    at SLACVM

I just got a copy of InsideSwitcher from the INFO-MAC bboard and tried
printing it on the laserwriter.  Most of my experience with the LaserWriter
was with graphics and this was pure text.  The only fonts available from
the system for MacWrite to use was the minimal set of Geneva, NewYork,
Monaco, and the LaserWriter fonts.  If the document was in a font other
than those I don't know, but it showed up on the screen in Helvetica which
was fine by me.  When I printed the document, there were many pages which
had missing lines of text at the top.  I'm not sure what the problem is
(problems with HEADER, problems with possible font substitution on the
LASERWRITER, problems with a lack of footers since the laserwriter page is
shorter than an Imagewriter page) but it is a diaster!!!  Anyone else seen
such a problem?  Is Apple aware?  The text looks great, but if you can't
count on all the lines in a document being printed, you sure are in
trouble.

------------------------------

End of INFO-MAC Digest
**********************