[mod.mac] INFO-MAC Digest V4 #92

INFO-MAC-REQUEST@SUMEX-AIM.ARPA (Moderator David Gelphman...) (07/29/86)

INFO-MAC Digest          Monday, 28 Jul 1986       Volume 4 : Issue 92

Today's Topics:
        Re: System Problems reported in INFO-MAC Digest   V4 #89
                           RE: System 3.2 Bugs
                            RE: MacDraw bugs
                             re: OBJECTIVE C
              Strange System/Finder Behavior: Folder Sizes
                        Usenet Mac Digest V2 #59
                         Autoblack screen saver
                 MacroMind authoring system for the Mac
                      Underware ribbon suggestions


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

Date: Sun, 7 Dec 86 21:51:03 pst
From: Larry Rosenstein <lsr%apple.csnet@CSNET-RELAY.ARPA>
Subject: Re: System Problems reported in INFO-MAC Digest   V4 #89

In article <8607241855.AA19003@ucbvax.Berkeley.EDU> you write:
>
>Subject: New System Problems
>Date: Mon, 21 Jul 86 17:02:07 -0800
>From: Kathleen Huddleston <gregory@ICSE.UCI.EDU>
>
>Just echoing the concerns expressed about System 3.2 Finder 5.3. I had numerous
>crashes when I first tried using it, but since I had just updated by ROMs and
>drive, I wasn't sure about the cause. The Mac crashed when initializing a disk,
>trashing a disk (to eject it), and especially it crashed magnificently when
>running Font/DAMover 3.0. Running 3.2 seemed to correct the latter problem,
>but I was never convinced this error was consistent.
>

...

>I wish Apple would get a clean version of the system software out and hold it
>stable for a while. Maybe about the time they release the new machine.

System 3.2 and Finder 5.3 are intended to be the final, stable versions.  I
have been using them for 2-3 months and have had NO crashes.  (Certainly not
any crashes in common operations such as initializing disks and ejecting
disks.)

If someone has a reproducible case of a crash, send me all the details and I
will forward them to the Testing Group here.


>Date: 21 Jul 86 09:23:52 EDT (Mon)
>From: Jean-Francois Lamy <lamy%utai.toronto.edu@CSNET-RELAY.ARPA>
>Subject: Yet Another LaserWriter driver bug?
>
>
>Another LaserWriter 3.x bug: a PostScript file produced from MacDraw
>1.9 uses font names that begin with |______ (i.e. |______Times instead
>of Times). These phony fonts do not exist and Courier is used in their
>place. Editing the PostScript code to remove all occurences of |______
>fixes the problem.
>

I don't see how this can be considered a bug in the LaserWriter driver.
Clearly, normal printing works fine in MacDraw.

The reasons for the funny names has to do with coordinating screen fonts
with printer fonts.  The funny names are absolutely correct, given the
particular LaserPrep software.  If you intend on capturing Postscript
commands, you must play them back with the same version of the Laser Prep
file.



Larry Rosenstein

Object Specialist
Apple Computer

AppleLink: Rosenstein1
UUCP:  {sun, voder, nsc, mtxinu, dual}!apple!lsr
CSNET: lsr@Apple.CSNET

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

Date: Mon, 28 Jul 86 12:07 EDT
From: Paul Christensen <PCHRISTENSEN%rca.com@CSNET-RELAY.ARPA>
Subject: RE: System 3.2 Bugs


Recently, I've seen numerous bug reports on Info-Mac, documenting problems
with Apple's latest release of the system software:  System 3.2, Finder 5.3,
Font/DA Mover 3.2, LaserWriter 3.1, and ImageWriter 2.3.  Having put up with
most of these problems myself, and having survived system releases from Apple
going back to Finder 1.0 and System 0.9 [January, 1984] I'd like to shed some
light on a clouded issue.

My initial experiences with the 3.2 System distribution were very bad:  the
system bombed frequently, files were not copied correcctly, and boot blocks
were not written to disk.  I was using a system set downloaded from a popular
subscriber service.  When I copied Apple's actual distribution disks from my
local dealer, 85% of my problems disappeared!!!  Here's why....


**** BEWARE OF CORRUPT SYSTEM FILES! ****

The latest system software was distributed both electronically through
AppleLink and other databases, and physically by direct mailings from Apple.
Recently, I was informed that "SOME of the files loaded onto subscriber
databases and AppleLink are corrupt".  I have never gotten word on exactly
which files were corrupted, but I personally would not take ANY chances.

This means that you should go to your local dealer and ask to copy his
ORIGINAL Apple distribution disks ... do NOT use system software downloaded
from AppleLink or any other electronic distribution.

Apple's dealer distribution is on two 400K MFS disks:  System Installation
and Printer Installation.  These can be easily merged onto one 800K HFS disk,
and still have over 200K free.


*** ANOTHER DISTRIBUTION -- SYSTEM 3.3 and FINDER 5.4 ***

Even though Apple claimed that System 3.2 would be the standard for a while,
it seems that there were a couple nasty bugs that had to be corrected.  I've
learned that Apple released (perhaps only to developers) System 3.3,
Finder 5.4, Font/DA Mover 3.3, etc... some time last week.

I WISH APPLE WOULD GET THEIR ACT TOGETHER, STOP ARGUING
ABOUT KEYBOARDS AND CABINET COLOR, AND RELEASE STABLE
SYSTEM SOFTWARE!

NOTE:  the opinion above expressed is purely that of a disgruntled Macker,
       sick of updating the system folders of 50 disks each time Apple
       releases a new "bug-free" system folder set!!!


SYSTEM RELEASES: A BIT OF HISTORY

Generally, Apple's system releases have been relatively stable, until the
release of the MacPlus in January.  Then Apple had to support both the
64K ROM and 128K ROM, leading to MANY problems.  System 3.0 (Jan.) failed to
initialize 400K MFS disks properly, and would not compact when run under the
64K ROMs.  System 3.1 (Feb 11) initialized disks properly and did compact
files under the 64K ROMs, but would not print on the LaserWriter.  Apple
promptly released System 3.1.1 (Feb 22) to correct this problem and assured
us that a "bug-free" System was being developed for release in late April.

System 3.2 was finally released late in June, and Apple admitted that there
were some bugs that were so fundamental that they could not be corrected
without a total rewrite of the software.  One of these bugs I assume is the
Finder's difficulty with addition, for example showing that a file is 300192
bytes long, and only occupies 297K on disk.  (Ignore the K figure, the byte
figure is accurate.)



                         - Paul Christensen

         CSNET Address :  PCHRISTENSEN%HENRY@RCA.COM

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

Date: Mon, 28 Jul 86 12:17 EDT
From: Paul Christensen <PCHRISTENSEN%rca.com@CSNET-RELAY.ARPA>
Subject: RE: MacDraw bugs


Recent issues of Info-Mac have detailed numerous problems running
MacDraw 1.9 under the new system files.  I have been told that
System 3.2 is INNOCENT ... MacDraw is to blame.  Apple is apparently
aware of MacDraw's problems remembering which font to use from the
system file (especially with the LaserWriter), its loss of text
alignment when dragging many grouped text objects, its bombing on
the 512K unenhanced with the LaserWriter and new System software.

These problems are being corrected and will probably be released either
as a file patch or a new version of MacDraw.

Not too long ago it was rumored that MacDraw was so full of bug patches
that programmers were afraid to touch it for fear of chain-reactions
caused by modifying poorly-understood code.  The only patch I
have ever used on MacDraw was from Washington ApplePI ... the patch
involved over 20 Hex file searches, and enabled MacDraw's font menu
to support more than 11 fonts ... scrolling on the MacPlus or new
system files.  I have had absolutely no problem with this patch and
have been using it successfully for more than 4 months.


			- Paul Christensen

	CSNET Address:  PCHRISTENSEN%HENRY@RCA.COM

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

Date: 28 Jul 1986 10:18:36 PDT
Subject: re: OBJECTIVE C
From: Laurence I. Press <SWG.LPRESS@B.ISI.EDU>


See the current issue of byte mag for a survey
of object-oriuebted languages on the Mac.

Lar

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

Date: Mon 28 Jul 86 14:15:55-PDT
From: Tony Siegman  <SIEGMAN@Sierra.Stanford.EDU>
Subject: Strange System/Finder Behavior: Folder Sizes

Following occurs on 512K Extended Mac (128K ROM, 800K internal drive,
400K external drive) using System 3.2, Finder 5.3:

Start from 800K startup disk with usual System folder, various other
applications and folders.  Use View menu to display disk contents by
Name, Size, or anything but Icon.  No sizes are shown for any of the
folders -- they all have just " -- " in the size column.  If you view by
size, the folders are all at the bottom of the list

Put a 400K disk, no System, just various files and folders, in the 400K
external drive.  Drag any (unsized) folder from internal to external
disk window.  THE SIZE VALUE FOR THAT FOLDER SUDDENLY APPEARS IN THE
SIZE COLUMN ON THE INTERNAL DISK WINDOW.  This occurs whether the folder
is successfully copied over or not (i.e., even it there isn't enough
space for it in the external drive disk).

If you're Viewing the internal disk contents by Size, the next time you
click on the internal drive window, that particular folder leaps up to
its proper rank in the listing.  However, as soon as you shut down and
restart,that folder is unsized again.

Additional peculiarity:  If you copy a smaller folder from the internal
to external disk, it appears (with size) both places.  Drag it from the
external drive to the trash,then open the trash and drag it back again.
The folder now does NOT show in the external drive window (nor do its
contents).  However, it ( or its contents) are apparently there, because
if you try to drag the same folder again from the internal to the
external drive, you get the warning message "OK to replace items with
the same names with....".  Also, QD Filer shows the contents of the
folder as being on the external drive.  Shutting down and restarting
doesn't bring the folder back to visibility.

Is this a bug, or do I have a degraded system or finder?

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

Date: 28 Jul 86 18:34:43 EDT
From: Jeffrey Shulman <SHULMAN@RED.RUTGERS.EDU>
Subject: Usenet Mac Digest V2 #59

Usenet Mac Digest          Monday, 28 July 1986      Volume 2 : Issue 59

Today's Topics:
     Idle DA Bombs & QUED
     SCSD hd recommendations
     _Debugger trap failure
     Mac-Pc
     MacEqn update
     The new mac (price?)
     Calendar 1.1 and ramdisks
     Random Responses
     Problems with Chancery font on the laser+
     Analog board failures
     Follow up on Micah Drive Problem
     Re: Mac Cache
     Speeding up memory allocation
     Steve Wozniak on radio
     LaserWriter 3.1 bombs with Excel chart.
     TeX Previewer document format.
     Re: Got info on MacIntalk ???
     Re: The new mac (price?)
     Re: Info needed on Macintosh Programmer's Workshop (LONG)
     Re: Manx's Mac 1.06H.1 C and assembler bugs
     RedRyder 9.2 Term Emulation Problem
     Re: Mac Cache
[
archived as

[SUMEX-AIM.Stanford.EDU]<INFO-MAC>USENETV2-59

DAVEG
]28-Jul-86 14:58:49-PDT,1353;000000000011

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

Subject: Autoblack screen saver
Date: Mon, 28 Jul 86 14:54:19 -0800
From: Kathleen Huddleston <gregory@ICSE.UCI.EDU>


This is an excellent screen saver. It does not interupt printing or terminal
sessions, is easy to install and remove, works with MacPlus and New Roms or,
probably with any Macintosh. It's public domain from Itty Bitty Computers,
and is installed at start-up as Macsbug by placing it in the system folder.
If you need Macsbug as well, you can rename it dissassembler. The packitt
file contains instructions for use and the Macsbug file. The result? Your
screen goes black except for an accurate analog clock that appears randomly
on the screen after 5 minutes of inactivity. There is no impact on processes
in progress and it immediately cuts off with any mouse movement, keystroke or
disk insertion. You can also black the screen immediately or extend the delay
for 2 hours for long-term screen viewing.

Try it. You'll never need another screen saver.
[
archived as

[SUMEX-AIM.Stanford.EDU]<INFO-MAC>DA-AUTOBLACK.HQX

DAVEG
]

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

Date: Sun, 27 Jul 86 21:46:50 EDT
From: David A. Levitt <levitt@MEDIA-LAB.MIT.EDU>
Subject: MacroMind authoring system for the Mac


MacroMind has a system that has the kind of authoring capability you
seem to want.  It lets you create documents a la Videoworks, including
audio with MacNifty sampled sounds, but it has additional menus for
creating a control track with conditional branching, etc.  The Mac
Plus guided tours were done with it.  It has not been widely available.
Contact MacroMind in Chicago at (312)327-5821.

 David Levitt

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

Date: Mon 28 Jul 86 12:24:57-EDT
From: Richard A. Cowan <COWAN@XX.LCS.MIT.EDU>
Subject: Underware ribbon suggestions


I just made my first T-shirt transfer.  I would guess that you can
avoid the print head wear problem by shifting back to the regular
Imagewriter ribbon right after making a shirt or two.  But I have
not noticed any problem after limited use.

When ironing the transfers, a bit of advice:

Tape the transfer to the shift so that you can keep it in the
same place.

Use a very hot iron and be persistent.  The ink will run a bit
so that you don't get jagged edges.

Someone told me that if you dip the transfer in vinegar and dry before
washing the shirt, it will be better "fixed" and less likely to wash
out.

I found that putting a firm magazine inside the shirt made the ironing
a bit easier.  (I used "AI magazine.")

-rich

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

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