From: Treble@asc.slb.com (John Treble)
Newsgroups: comp.sys.mac.system
Followup-To: comp.sys.mac.system
Distribution: world
Subject: Sad Mac Error codes
Organization: ASC-Austin

PLEASE SAVE THIS FILE FOR FUTURE REFERENCE -- I'LL NOT POST IT
AGAIN!

When you turn on the Macintosh or press the reset button on the
programmers switch, several memory and system diagnostics take place. If
any test fails, the Sad Mac appears. The code number below it indicates the
nature of the malfunction.

The first two digits indicate the type of error. If it is a RAM test failure,
(first two digits - 02, 03, 04 or 05) the last four digits identify the
suspect
chips. The last four digits must be converted from hexadecimal numbers to
a 16 digit number to learn which chips are bad.

If the Sad Mac appears after the disk starts spinning, the first two digits of
the code number under the icon are 0F, and the next four digits indicate
the type of error. If you get a Sad Mac with an 0F code, try restarting the
Mac while holding down the Option and Command keys (rebuild the
desktop file.) You may also be able to fix a faulty startup disk by replacing
its System File.

The error 0F000D most likely means that you have something pressed
against the interrupt button on the programmer switch! (Move those books
anyway, you're blocking precious air flow into your Mac) The error 0F0064
means that the startup disk you have inserted (mounted) into the disk
drive is missing the system file.

Code     Meaning
01XXXX   ROM test
02XXXX   RAM test-bus subtest
03XXXX   RAM test-byte write
04XXXX   RAM test-mod3 test
05XXXX   RAM test-address uniqueness
0F0001   Bus error
0F0002   Address error
0F0003   Illegal instruction (may be a damaged system file)
0F0004   Zero divide error
0F0005   Check trap-CHK instruction
0F0006   Overflow trap
0F0007   Privilege violation
0F0008   Trace trap
0F0009   Trap dispatch error
0F000A   Line 1111 trap
0F000B   Other trap
0F000C   Unimplemented trap executed
0F000D   Interrupt button on programmers switch pressed in
0F0064   Bad System File
0F0065   Bad Finder

I'm no Mac super-guru.  The above information was provided to me via
Apple Technical notes and various books and manuals I've read over the
years. I hope this helps someone.

John Treble
Schlumberger Well Services - Austin Systems Center
Austin Texas

treble@asc.slb.com "My humble, but accurate, opinion does not necessarily
reflect that of my employer. I get full credit for my insightful and witty
comments!"

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

Date: Mon, 25 Jan 93 10:14:56 MST
From: Jim Powlesland <powlesla@acs.ucalgary.ca>
Subject: SuperClock! 4.0.1

Bug Notice: SuperClock! 4.0.1 generates an unimplemented trap
error on Mac SEs running 7.0 + Tune-up 1.1.1. Also, the alarm
options do not work on a Mac IIfx running 7.0.1 + Tune-up 1.1.1.
Needless to say, I've gone back to 3.9.1.

I'm posting this here because the author, Steve Christensen, did
not provide an Internet email address in his ReadMe files. Great
program nonetheless.

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

Date: Mon, 25 Jan 93 09:07:36 EST
From: williams <williams@tours.inra.fr>
Subject: SuperClock 4.0.1

	This is really intended for Steve Christensen (the author of
SuperClock) whom I can't reach directly as I don't know how to mail America
OnLine or Compuserve from Europe..... Hope you read Info-Mac, Steve!

	Well, version 4.0.1 runs just fine on a Mac IIci with system 7.0.1 but
it crashes a PB 100 on startup because of an ID 12 error.  Pity, because 4.0.1
was produced to get around other PowerBook problems.

	BTW, version 3.9 works fine.

John Williams (INRA Station de Recherches Avicoles, C.R.Tours, Nouzilly,
France)
williams@tours.inra.fr

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

Date: Mon, 25 Jan 93 12:03:21 MEZ
From: David Steiner <DSTEINER@dosuni1.rz.Uni-Osnabrueck.DE>
Subject: The IIsi is no more????

Okay, maybe I was asleep when the news came down but...

A couple of issues ago (I'm always behind a bit) someone mentioned in the
context of a discussion of the sound problems with the IIsi that it would be
discontinued in Febuary.

I had heard that the IIci might be discontiued due to the introduction of the
V-series but I missed the discussion on the IIsi.

As I am getting ready to buy one of the two within the next couple of months,
I would appreciate some light on the subject.

As a follow-up, if the IIsi is indeed no more, what is the next comparable
alternative?

Thanks.

David R. Steiner
Research Assoc. - Remote Sensing & GIS
ISPA - Uni. Osnabrueck, Vechta Germany

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

Date: 25 Jan 1993 15:58:18 -0500 (CDT)
From: GG4921S@ACAD.DRAKE.EDU
Subject: Trailer for HyperCard XFCN

  Archivists:
    I am sending a file called bRead.hqx that contains a
hyperCard stack called binaryRead. binaryRead demonstrates a usefull XFCN by
the same name.  binaryRead XFCN allows you to read the data fork of any file,
and return the data in a variety of formats:  character, decimal ascii,
binary, hexadecimal, 2 byte integer or 4 byte integer.  It was created by me
to file the "file" gap that exists in hyperCard and would be usefull for
anyone
wishing to read non ascii files.
Gordon Graber, Academic Computing, Drake University, Des Moines, Iowa

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

Date: Mon, 25 Jan 93 12:17:43 MST
From: "Paul Gilmartin (303) 673-4428" <stortek!Paul_Gilmartin@csn.org>
Subject: UNIX utility to convert BinHex 4.0 files

On Wed, 20 Jan 93 13:33:40 -0500 you said:

> I was wondering if there is a UNIX utility to convert BinHex 4.0 files?
> I tried "mcvert", but in addition to converting a file from BinHex
> 4.0, it also converts the file to Macbinary format.  I'd like to just
> convert a file from BinHex 4.0 to whatever it was originally -- e.g., a
> GIF file.

To extract the data fork from a MacBinary GIF file, you can use:

    mcvert -Ud *.GIF.bin

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

Date: Mon, 25 Jan 93 23:13:08 GMT
From: L.H.Wood@lut.ac.uk
Subject: Word 5.0 printing graphics on StyleWriter

I've just had the scariest academic experience of my life - passing a
PostScript file through a multitude of Unix machines, spoolers and laser
printers in an attempt to get something looking vaguely like what I saw
on the Mac in my office/bedsit.

I have succeeded, but it's been a long (12 hour) haul to get my forty
page (not overdue at ALL!) report finished. And I have a perfectly good
StyleWriter sitting back in my bedsit, that I couldn't use.

Why not? I hear you cry.
Because that ***** Word 5.0 prints text beautifully on the StyleWriter,
but dumps graphics at screen-resolution of 72dpi. Ugh. Needless to say,
after preparing a report using Publish/Subscribe between Macdraw Pro and
Word 5.0, this was something of a shock. (P/S is very nice, by the way -
although Word only seems to update drawings 'on the fly' if MacDraw Pro
was launched first - is this normal?)

Of course, MacDraw Pro prints fine on the StyleWriter, so all my proofs
of the drawings were okay.
My questions:
Am I correct in believing that Word 5.0 cannot print graphics at a decent
resolution to the StyleWriter?
Is a fix available? (I tried fiddling with Print2Pict, and with publishing
the Word document to Macdraw Pro and Excel. No success)
Is this problem fixed in Word 5.1?

And, most importantly, WHOSE FAULT IS IT? Microsoft, I assume, but I'd
like to check before I flame flame flame.

Yours exhaustedly

Lloyd Wood
L.H.Wood@lut.ac.uk

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

Date: Mon, 25 Jan 1993 11:05:49 -0700
From: panthony@CC.UTAH.EDU (Philip A. Thompsen)
Subject: Word 5.1 and System 7.1

I too have had problems with Word 5.1 with System 7.1.  In particular, the
grammar checker tends to freeze up, and the spell checker was doing some
weird things.  I called Microsoft tech support, and was told to try
removing the Word preferences file from my system folder (inside the
preferences folder).  I did this, and things seem to be better now.  I
still get an occasional hang, but not nearly as often.  Perhaps the
preferences file gets corrupted somehow in the system/software upgrading
process.  Anyway, try removing the prefs file (and letting Word create a
new one the next time you start it).



Philip A. Thompsen -- Department of Communication, The University of Utah
Philip.A.Thompsen@m.cc.utah.edu, BITNET:Panthony@UTAHCCA, Prodigy:JNFM97A


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

Date: Sun, 24 Jan 93 18:52:28 EST
From: Pete Tamas <GNOME%TEMPLEVM.BITNET@Forsythe.Stanford.EDU>
Subject: WYSIWYG

> WYSISYG (pronounced Wizzy-Wig) stands for What You See Is What You Get.
> What does this mean? What you see on the screen is what your doc will look
> like when you print it (the font won't have different kerning or some other
> funky spacing.
>
Getting back to my comment a few days ago that language changes, I
note that in 1984 when the original Macintosh came out, WYSIWYG
meant that the font you chose was actually on the screen. Back then,
if you had a PC, you could with certain printers tell it which font
you wanted to use. It did not show on the screen, but you could use
it in the printed document. Seeing it on the screen was a dramatic
improvement. And, we had no idea what kerning was.

Pronouncing it Wizzy-Wig never seemed to catch on among hard-core
Mac users I know. Perhaps because that feature was assumed and
natural. Like PC users all being human, no one bothered to point it
out, but when one Mac user is a gorilla (Koko), we occasionally
point THAT out.  ;-)      -Pete Tamas
Gnome@VM.Temple.EDU, Temple Univ, Philadelphia (betw New York & Wash DC)

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

End of Info-Mac Digest
******************************