INFO-MAC-REQUEST@SUMEX-AIM.ARPA (Moderator Dwayne Virnau...) (07/02/86)
INFO-MAC Digest Wednesday, 2 Jul 1986 Volume 4 : Issue 81
Today's Topics:
System 3.2
System 3.2 anomaly?
Bug in lpr.c for Aztec C
MacInHebrew on the Mac+ and 512K Enhanced
Dialog item troubles
bugs in DrawDialog
Creating PostScript files from within MacWrite
sad MAC error message
uw question
Mac+ debugger help?
re: boing
Re: Boing crashes on Mac+
boing crashes on Mac+
Usenet Mac Digest V2 #51
Delphi Mac Digest V2 #26
Usenet Mac Digest V2 #52
Point Symmetry Demo.
Re: Font Changer
Chinese Character Font
Re: Consulair GREP
need help for using Mac in analog data sampling
----------------------------------------------------------------------
Date: Thu, 26 Jun 86 16:50:43 pdt
From: Dan Winkler <winkler%apple.csnet@CSNET-RELAY.ARPA>
Subject: System 3.2
There were some problem reports recently on info-mac regarding System
3.2. I've passed those reports on to the people who produced System
3.2, although as far as I can tell most of the problems were not caused
by System 3.2 itself but rather by using System 3.2 with old (pre 3.1)
Laserwriter files. For example:
> From: Joel Malman <malman@J.BBN.COM>
> Subject: New System bombs
>
> I have been getting quite a few Mac Bombs (#3, illegal instruction) while
> using the new System (3.2) and Finder (5.3) while either printing or
> starting to print on LaserWriter (not a Laser+), using version 3.0 LW
> software. I don't have 3.1 LW software.
You need to update your Laserwriter file to version 3.1. Note that you
have to cycle the power on the Laserwriter after upgrading so that the
Laserprep file gets downloaded again.
> Does anyone have version 3.1 LW software?
It is part of the Mac System Software Update. It's available on Compuserve
and (soon) at your friendly neighborhood Apple dealer.
> Reverting to system 3.1.1 / finder 5.2 stops the bombing.
The experts assure me that upgrading the Laserwriter file is by far the
preferred option.
> From: Peter Gergely <GERGELY@DREA-XX.ARPA>
> Subject: Incompatible software with System 3.2
>
> I have just found a couple of incompatibilities in software
> after having installed the latest Mac System 3.2. MacSpool from
> Mainstay, Inc. now crashes with an illegal instruction error (ID=03)
> bomb when you try to print anything or try to clear the ram print buffer
> from the MacSpool-Control desk accessory. If anyone knows of a patch to
> allow it to work I would appreciate it greatly.
Have you updated to Imagewriter 2.3 and Laserwriter 3.1? If not, that would
be your problem. If so, please send me more details about the problem.
> MacKermit 0.8(34) now sometimes doesn't handle direct address
> cursor movements correctly while in SYSDPY on a DEC-20. A minor
> annoyance, but a refresh fixes it for a while.
>
> - Peter
Interesting. Can you give me any more details?
> From: "pugh jon%e.mfenet"@LLL-MFE.ARPA
> Subject: TML Pascal and new System
>
>
> I was using TML Pascal with the newer systems (3.1.1 & 3.2) and my programs
> started failing. Even the example program started failing. It works fine if
> I compile under 2.0 but not if I compile under 3.n. It fails at the GetMenu
> call. Is this an example of a system bug or is it with TML? Would their
> update to 1.1 fix this? Does anyone have a clue what is going on? I am
> refering to the Grow.Pas example program provided with TML.
Please send me a copy of the program and additional details. I'll make sure
it gets to the right people here.
> By the by, will Macbugs work with a Ramdisk? How do you do it properly? Could
> someone post a brief intro to Macbugs or TMON and explain how they are used
> and the advantages of each? I am still a bit confused as to which to buy.
> I have heard good about both but can't even use them well enough to make an
> intelligent choice, and I hate buying randomly!
>
> Jon
Macsbug is widely available and does work with most RAM disks. However,
you may find the file system RAM cache more effective than RAM disks.
> From: Joel Malman <malman@j.bbn.com>
> Subject: System 3.2 Bugs
>
> System Software version 3.2 would seem to NOT be as bug free as Apple says
> it is. My Mac+/LW system crashes quite often with MacBomb #3 (Illegal
> Instruction). Especially so when printing, or "Looking for <LASERWRITER>".
> An informal survey (at BBN) indicates that other System 3.2 users have the
> same or similar problems. I have since reverted to System 3.1.1 .. where the
> problem does not occur. On the plus side: Finder version 5.3 seems
> wonderful.
Thanks! We like Finder 5.3 too. Are you sure you've upgraded to the
Laserwriter 3.1 and Laserprep 3.1 files?
> Question: Does anyone know if Apple is aware of the problem(s) with 3.2
> and/or if another attempt at a "bug free" Operating System is in the works?
As far as I know, the Mac system software Update, which includes System
3.2, Finder 5.3, Imagewriter 2.3, Laserwriter 3.1, etc. is very solid
and reliable, although in general Apple is anxious to hear of any
problems or suggestions you have regarding any of our products.
Dan Winkler
Apple Computer, Inc.
20525 Mariani Ave., MS: 22Y
Cupertino CA 95014
------------------------------
Date: Fri, 27 Jun 86 20:59 EDT
From: BELSLEY%BCVAX3.BITNET@WISCVM.ARPA (DAVID A. BELSLEY)
Subject: System 3.2 anomaly?
Open MS Word 1.05 with MacSpell+ installed. Open MacSpell+ from the Apple
menu. The Standard File Dialog Box will now appear for opening a
dictionary. Insert the dictionary disk in the external drive (now, not
earlier). It will not be recognized and mounted. Pressing Control-Shift 1 or
2 will cause it to be recognized, but it will not be mounted on its own.
Doing the same with System 3.1.1 works ok.
------------------------------
Date: Thu, 26 Jun 86 00:51:33 mdt
From: dlc%b@LANL.ARPA (Dale Carstensen)
Subject: Bug in lpr.c for Aztec C
The print utility I posted a few weeks ago has a bug which causes it to
ignore the second and succeeding files it is told to print. The fix is
to put the line:
neof = TRUE;
before the line:
for (pgno = 1; . . .
Sorry about that, it used to work, but I think the line was deleted by
a typo while screen editing.
------------------------------
Date: 27 Jun 1986 10:20-EDT
Sender: WEINSTEIN@G.BBN.COM
Subject: MacInHebrew on the Mac+ and 512K Enhanced
From: WEINSTEIN@G.BBN.COM
i have received several complaints that macinhebrew does not work at all on
the mac+ and 512k enhanced. the problem is due to the different way in which
fonts are handled in the new roms, coupled with what appears to be a bug in
the font/da mover. as a result of this bug, if a pre-mac+ era font happens to
have the same id number as a font already in the system file, the font/da mover
uses the name of the corresponding font from the system file rather than of
the font in the fonts file. consequently, such fonts get installed with the
wrong name, and macinhebrew -- which cues off the font name to determine which
fonts contain hebrew characters -- fails to recognize the fonts as containing
hebrew characters. the problem arises anytime macinhebrew is installed on a
mac+ or 512k enhanced, regardless of whether the old or new font mover is used,
and (with some variants) if the installation was done on an older mac but
using the mac+-compatible font/da mover, and an attempt is subsequently made
to use the disk on a mac+.
it is possible to solve the problem by modifying the installation procedure,
although there exist other, less serious, bugs on a mac+ as well.in particular,
automatic re-mapping of the system and geneva fonts, necessary to support
hebrew menus, filenames, dialogs, etc., does not work, the new keycaps
(in system 3.1 and later) does not work on hebrew, and at times the entire
line of text will flash when the insertion point should have blinked. a
completely mac+ compatible version is now in development, and will become
available shortly. provided these other bugs are livable, however, the
following modified installation procedure should produce a (marginally-usable)
result:
1. using the mac+-compatible font/da mover on a mac+ or 512k
enhanced, open the macinhebrew
fonts file, and create in the other window a new fonts file. ignore the font
names which appear in the fonts file; they are wrong. copy all the fonts from
the old macinhebrew fonts file to the new one. the effect of this procedure
will be to create the fond resources needed on a mac+.
2. now using resedit, open the new fonts file just created and
examine the fond and font resources. the names of the fonts will still be
wrong. reset the names of the fonts in accordance with the following table:
id 0 chicago w hebrew block
id 2 new york w hebrew block
id 3 geneva w hebrew stick
id 4 monaco w hebrew typewriter
hebrew cursive
rehovot
troyes
to change the name of a font, select the corresponding fond resource, select
info from the font menu, and edit the name in the info window. then, open
the font window while holding down the option key so as to get the generic
display (critical!), select those font resources which are named, and change
their names as indicated above (in the font window, the resource id numbers
are 128*the value given above).
3. continue with the installation instructions given in the manual,
using the new font file.
unless you understand the above instructions thoroughly, however, and are sure
you will be satisfied even so with an only half-functional version, i recommend
waiting until the mac+-compatible version becomes available in another week
or so.
------------------------------
Date: Sun, 29 Jun 86 02:08:04 mdt
From: dlc%b@LANL.ARPA (Dale Carstensen)
Subject: Dialog item troubles
I read your posting to info-mac and have a couple of thoughts that might help.
1. I haven't used a userItem or set up a "MyItem" function, so I have no
idea whether this will help, but shouldn't you make sure "itype" in your
SetDItem call is "userItem" (0)?
2. I have recently tried dialog statText items which didn't show up. I was
calling DialogSelect, so I thought that should update the dialog window
and draw the text. The problem went away when I made the rectangle for
the statText wider. I had set up the DITL resource with the Dialog
Creator, which evidently makes some real tight assumption about what font
you will use for statText and makes the rectangle too narrow for the text
to fit in a "fatter" font, which Aztec C assumes you want to use. What
TextEdit does is "line-wrap" the text right out of the rectangle, to the
next line (wonder why it thinks the next line is wide enough, though?).
I'm also having fits trying to get text other than left-justified in editText
items, and I have a program which always offsets the text returned by
GetIText up one byte (the length is in the correct byte, though, and sometimes
the second byte is the correct length, sometimes it is an "old" length).
It appears to me that the dialog routines use of TextEdit leaves a lot to be
desired. I have also had to call TEKey outside of DialogSelect, although
Inside Macintosh implies that DialogSelect handles keystrokes. And I get
update events for the dialog, but no update event for the non-dialog window
(which ends up having scroll bars and a grow icon, but no lines in the drag
area, when it is not the front window). Very confusing.
------------------------------
Date: Mon, 30 Jun 86 14:21:57 pdt
From: oster%ucblapis@BERKELEY.EDU (David Phillip Oster)
Subject: bugs in DrawDialog
Recently, I stumbled into the following peculiarity of the Mac system:
Dialogs allow item types called "userItems" useritems get a pointer to a
procedure inserted into them at runtime. That procedure is responsible
for drawing the item. Now: the bug:
If the dialog is being drawn in response to the disposal of another
dialog, at the time the userItem is executed, the current GrafPort might
still be the disposed dialog.
The solution:
when you write a useritem procedure for a dialog, always start with
pascal void myUserItem(myDialog, myItem)
DialogPtr myDialog;Integer myItem;{
SetPort(myDialog);
...
}
--- David Phillip Oster -- "We live in a Global Village."
Arpa: oster@lapis.berkeley.edu --
Uucp: ucbvax!ucblapis!oster -- "You are Number Six."
------------------------------
Date: Thu, 26 Jun 86 09:11+0100
From: Ralph <MartinRR%multics.cardiff.ac.uk@Cs.Ucl.AC.UK>
Subject: Creating PostScript files from within MacWrite
I have read repeatedly that you can do this by pressing CMD-F just after
pressing the ok button in the laserwriter dialog box that comes up, when
printing out of MacWrite (and other utilities too ?), or by pressing
CMD-K to get the laser prep header too.
Now, I just can't get this to work. At all. Can anyone out there
PLEASE give me some help as to what I might be doing wrong ?
I have a British keyboard, for what its worth. Is it perhaps that the
disk is too full ? (What is the minimum needed for a MacWrite "hello
world" document ?) Is it perrhaps the version of the laser prep or
laserwriter files I have ?
Any helpful suggestions would be welcomed !
Ralph
------------------------------
Date: Fri 27 Jun 86 15:21:31-EDT
From: Dave Helmkamp <DJH@CS.COLUMBIA.EDU>
Subject: sad MAC error message
How does one interpret the number that often appears under the "Sad
MAC" icon? Mine currently says "0F0064"..
-dave
------------------------------
From: caip!unirot!gib@seismo.CSS.GOV
Date: Sun, 29 Jun 86 08:20:31 edt
Subject: uw question
Reply-to: unirot!gib@seismo.CSS.GOV (gib wallis)
I just read a post in the new digest asking a question about
uw. MY question is: exactly WHAT does uw do from the UNIX side of the
connection, and what does it do from the Macintosh side of the connection?
gib
..!topaz!unirot!gib
------------------------------
Date: Sun Jun 29 08:01:39 1986
From: zimmer@lll-tis-a.ARPA (Mark Zimmermann)
Subject: Mac+ debugger help?
Could anybody give me pointers to a description of the Mac+'s
debug window (or whatever it is) that comes up upon pushing
the interrupt button? I would in particular like a command
summary (how to examine registers and memory, do a warm reboot
without losing RAMdisk contents, etc.). Tnx! ^z
[
from the moderator -- such a summary would be nice, as I have seen
things in several digests. Volunteers?
DoD
]
------------------------------
Date: Thu, 26 Jun 86 11:21:34 EDT
From: Meredith Lesly <mlesly@bbn-labs-b.arpa>
Subject: re: boing
It doesn't have sound because the Mac isn't fast enough. There aren't
enough cycles during the vertical retrace to have both fast enough
animation and sound. Mike (the author) tried it.
The problem with the Mac+ may be caching - the cache uses the second
screen buffer whether it's in use or not.
------------------------------
Date: Thu 26 Jun 86 12:45:41-EDT
From: "Walter E. Gillett" <GILLETT%OZ.AI.MIT.EDU@XX.LCS.MIT.EDU>
Subject: Re: Boing crashes on Mac+
Turning off the cache bit (via the Control Panel) seems to prevent Boing from
crashing the Mac+ (at least, this worked when I tried it). Boing is memory-
intensive, so it probably causes the crash by overwriting the cache area. If
this hypothesis is correct, then it may also be risky to run Boing on the
512K Mac when TurboControl is active.
------------------------------
Date: Thu, 26 Jun 86 12:08:53 PDT
From: <DAVEG%SLACVM.BITNET@Lindy>
Reply-to: DAVEG%SLACVM.BITNET@SU-Forsythe.ARPA
Subject: boing crashes on Mac+
It appears any program which uses the alternate screen buffer on the
Mac+ will crash when you exit to the finder IF YOU USE THE BUILT
IN RAM CACHE OF THE NEW ROMS. I think MacTutor had quite a bit of
info about this in the last issue (which had an article about the
use of the alternate screen buffer). I assume that BOING uses
the alt. screen buffer because: 1. it bombs when exiting to the finder
when using RAM caching and 2. it does good animation so it is a likely
candidate. Hope this is of help. David Gelphman
------------------------------
Date: 27 Jun 86 17:35:47 EDT
From: Jeffrey Shulman <SHULMAN@RED.RUTGERS.EDU>
Subject: Usenet Mac Digest V2 #51
Usenet Mac Digest Friday, 27 June 1986 Volume 2 : Issue 51
Today's Topics:
Lightspeed patchs in error?
Re: Megamax bug?
Re: Want info on SCSI hard disks (generic?)
fan and print spooler
Problem Using MacPascal 2.0 PSHELL
Re: MacAuthor Review (even longer)
System 3.2, Finder 5.3, and Paradise HD
Pagemaker and the LaserWriter
Making icons in menus
LightspeedC bug
Does anybody know any good computer stores in BOSTON?
Lightspeed and Ramdisk with 512K Mac
How do I get at a file's "information block"?
Mac Support Flame
Re: Problem Using MacPascal 2.0 PSHELL
Re: MacWorkStation Protocol
HP 150 -> Mac
Animation Query
Lightspeed troubles
[
archived as
[SUMEX-AIM.ARPA]<INFO-MAC>USENETV2-51.ARC
DoD
]
------------------------------
Date: 29 Jun 86 10:54:12 EDT
From: Jeffrey Shulman <SHULMAN@RED.RUTGERS.EDU>
Subject: Delphi Mac Digest V2 #26
Delphi Mac Digest Sunday, 29 June 1986 Volume 2 : Issue 26
Today's Topics:
RE: Usenet Mac Digest V2 #49 (Re: Msg 9403)
RE: Usenet Mac Digest V2 #50 (Re: Msg 9508)
Expo in Boston
RE: INFO-MAC Digest V4 #79 (Re: Msg 9480)
RE: Usenet Mac Digest V2 #50 (Re: Msg 9508)
The World of the System file
RE: Megamax SFGetFile bug? (Re: Msg 223)
RE: Megamax SFGetFile bug? (Re: Msg 230)
RE: Boing crashes on Mac+
RE: INFO-MAC Digest V4 #80 (Re: Msg 9594)
MacDraw Font Sizes!
Wierd Scenes Inside the Desktop
RE: Wierd Scenes Inside the Desktop (Re: Msg 9612)
RE: Wierd Scenes Inside the Desktop (Re: Msg 9613)
RE: Wierd Scenes Inside the Desktop (Re: Msg 9617)
RE: INFO-MAC Digest V4 #79 (Re: Msg 9480)
COBOL
[
archived as
[SUMEX-AIM.ARPA]<INFO-MAC>DELPHIV2-26.ARC
DoD
]
------------------------------
Date: 1 Jul 86 18:18:49 EDT
From: Jeffrey Shulman <SHULMAN@RED.RUTGERS.EDU>
Subject: Usenet Mac Digest V2 #52
Usenet Mac Digest Tuesday, 1 July 1986 Volume 2 : Issue 52
Today's Topics:
Re: MacAuthor Review (long)
Alternative MacDraw Menu
LaserWriter & LaserPrep bugs ver. 3.0 & 3.1
What is Multi-write?
Re: Lightspeed troubles
Re: LaserWriter & LaserPrep bugs ver. 3.0 & 3.1
Small bug in LaserWriter Driver?
MANX Aztec C -- as good as it looks?
phonelink by borland -- any good?
PageMaker 1.2 bugs
Re: MANX Aztec C -- as good as it looks?
Re: What is Multi-write?
Message from Apple Re: Licensing
Re: Making icons in menus
Microphone patch
Re: MacAuthor Review UPDATE
Flight Simulator: Mt. Rainier
Fontographer question
Re: Microsoft Flight Sim problem?
FEdit News
A word on Mac C
-----------------------------------------------------------------------
[
archived as
[SUMEX-AIM.ARPA]<INFO-MAC>USENETV2-52.ARC
DoD
]
------------------------------
Date: Mon, 30 Jun 86 12:04:17 pdt
From: Dhiren Fonseca <fonseca%cc.uofm.cdn%ubc.csnet@CSNET-RELAY.ARPA>
Subject: Point Symmetry Demo.
The following file is a Demonstration Version of the Point
Symmetry Application. This Demonstration version is Public
Domain. This program allows the user to design some beautiful
Point Symmetry graphics. It has wonderful Design, and Art
applications.
This is our first attempt at creating a program, so we would
welcome any comments you might have on the job we did. This
program knows about the Mac Plus ( that's what we wrote
it on ), and it works on a 512K mac. As for it working on
128K Mac, your guess is as good as mine ( we didn't have have
any 128K's around to test it on.)
Please pass this Demo on to everyone that you know, I'm sure
that everyone will find it interesting !!.
Dhiren Fonseca
UTS: fonseca%cc.uofm.cdn@ubc.csnet
Delphi: DHIREN
CompuServe: 72267,3461
Envoy 100: DH.FONSECA
CAUG NET: FONSECA,D
[
archived as
[SUMEX-AIM.ARPA]<INFO-MAC>DEMO-POINT-SYMMETRY.HQX
DoD
]
------------------------------
Date: 19 Jul 86 08:30 EST
From: CML5A9%IRISHMVS.BITNET@WISCVM.ARPA
Subject: Re: Font Changer
The following is a re-post of the Font Changer program.
Apparantly I had some troubles with the gateway.
For those of you who are curious, Font Changer will allow you
to do things such as:
- Change all Geneva to Helvetica w/o affecting other fonts.
This is esp handy in our lab where users type in Geneva and
Symbol because it "looks nice" and then want to print out
on our LaserWriter. Saves lots of work.
- Change all 12 pt superscripts to 9 pt superscripts
- Globally search and change to/from any combination of pt sizes
type style and/or fonts. This include "illegal" pt sizes,
so you could even make some of your text 7 or 8 pt if you
wanted, MacWrite seems to handle it okay, there just isn't a
way to do it from within the program.
- The program runs on XLs, 128s, 512K (both kinds), Mac+s,
and under switcher. I won't verify this, but the program uses
very little memory, so you could probably set the switcher
size very small.
It currently works with MacWrite 4.5 documents, but I suppose that
I could add Word documents if I could find a definative definition
of the format therein. Can anyone help?
- Tom Dowdy
"I'm increasingly convinced that a vast majority of wrong thinking
people are right."
[
archived once again as
[SUMEX-AIM.ARPA]<INFO-MAC>UTILITY-FONT-CHANGER.HQX
DoD
]
------------------------------
Date: Fri, 27 Jun 86 11:48:55 edt
From: chi%upenn-graded@CIS.UPENN.EDU
Subject: Chinese Character Font
I like to know if there exists CHINESE CHARACTER FONT
for the Macintosh programs. Also is there a MacWrite for Chinese
Word Processing?( you want to be able to write in both VERTICAL and
HORIZONTAL styles)
Any helps are welcome. Thank you in advance.
------------------------------
Date: Thu, 26 Jun 86 11:51:45 EDT
From: olson@harvard.HARVARD.EDU (Eric Olson)
Subject: Re: Consulair GREP
I just got a letter from Consulair saing that the Utilities (SuperMake,
Diff, Grep, and MPA) are on sale this summer for $50.
That should make it a little easier to justify getting it if you don't
have Mac C: I have Mac C and don't use SuperMake or MPA anayway.
-Eric
------------------------------
Date: Tue 1 Jul 86 21:12:37-CDT
From: Werner Uhrig <CMP.WERNER@R20.UTEXAS.EDU>
Subject: need help for using Mac in analog data sampling
A Univ. of Texas Mech. Engr. Research Project member is trying to
introduce the Macintosh into another previously exclusively IBM bastion.
To do this, an A to D converter is needed to allow analog readings to be
taken from some sensors and converted to digital inputs that can be fed
into a Mac.
They are ideally looking for an A/D converter that reads 12 bits on each
of 4 channels in the 0-5 or 0-10 volt range with response times quicker
than one reading on each channel every 5 minutes. That should be easy.
They would be happy with opportunities to obtain hardware, plans,
instructions, hints, anything that might help.
If anyone knows of this being done before please contact me and I'll
pass the info along. Any leads, rumors, etc. will be very useful and
appreciated!
for 'direct-links' to the interested party, please call Chiu at
(512)471-5731 during CDT-office-hours.
------------------------------
End of INFO-MAC Digest
**********************