CMD Home | Subscribe | Index | 1997 Index | CM Trading Post

Table of Contents for this issue:
Re: Broken Mac Classic
Re: Old ImageWriter II
SE/30 shrinking screen
Re: Pseud040
IIcx power supply replacement
Re: SE/30 problems
*.sit.hqx?
AE Accelerator question
Opening Macs


Date: Sat, 4 Oct 1997 17:49:25 +0100
To: Classic Posts
From: Rebecca and Rowland
Subject: Re: Broken Mac Classic

Date: Wed, 1 Oct 1997 05:34:31 +0100
From: Christopher Adams
Subject: Re: Broken Mac Classic

Emma wrote:

On bootup all I get is the sad mac with a top
error string of 0000005 and a lower one of 00EF00FF, with occasional
0000001's with and different errors underneath.

This is from MacSecrets (tho' it misses out code 0005!):

According to the article I've appended to this message, $0005 is a RAM
problem as well.

In Mac IIs and SEs:

$0005 The RAM External addressing test failed. The Z field indicates a
failed address line.

[snip]

Do any UK users know where I might get a torx screwdriver that will get the
case off if need be?

Alas, no. I tried and failed :-(

The usual mail-order companies may still have 'Mac Cracker' kits, even
though they don't put them in the catalogue any more. It's a very long
3/16" allen (hex) wrench, otherwise known as a Torx T-15.

Erm, 3/16 inch allen keys are compeletely different to Torx T-15 bits. You
need a Torx T-15 bit.

Somebody here once suggested trying to find a screwdriver/bit set that has both a long
shank and an extension, or an extension and very long bits. Maplin?
Halfords?

I got myself a set of Torx (and other driver) bits of the sort you plug
into a handle. This came with an extension bar.

I found two problems using this combination to open my Mac Plus:

1) The extension bar was too wide to fit down the hole - the socket part
of it that the bit plugged into jammed in the hole so I couldn't engage the
bit with the head of the fastener (a self-tapping screw).

2) The extension bar was too short - the handle of the driver wasn't clear
of the case, so I couldn't have turned it even if I had been able to engage
the bit with the fastener.

What I did in the end was get my little screwdriver - 3mm wide flat bit,
103mm shank, handle < 1in wide at the broadest point. I found I could
engage this with the T-15 head and unscrew it.

This might not work well if the Mac's not been opened recently as mine had
(the bloke I bought it off fitted it with 4MB RAM just before I bought it),
because it's difficult to apply an significant amount of torque to the
screwdriver. But it got the thing undone, so that's alright.

Hope this helps
Rowland.

I found this in Apple's Technical Information Library (under MacPlus, I think):

Article Number: 7748
Article Created: 7/2/91
Last Modified: 26/09/96

Subject: Macintosh: "Sad Mac" Error Code Meaning (11/95)

TOPIC

When I turn on my Macintosh, I get a black screen with a "sad Macintosh"
face and the numbers 020016. There is no listing for this error code in any
of my manuals. What does it mean?

DISCUSSION

The particular error code that appears with the "sad Macintosh" is not as
important as WHEN it occurs. If the Macintosh can start up from a different
system diskette, then the problem is probably with the system software on
the other disk. System problems are usually identified when you get a "happy
Macintosh" face and the "Welcome to Macintosh" screen before the "sad
Macintosh."

If the "sad Macintosh" face appears immediately at power up, that usually
suggests an issue with the logic board or memory. Try starting up from a
floppy disk before assuming it's a hardware problem.

Sad Mac Error Codes Description

===============================
On the Original ROMs (Macintosh 128k, 512k, 512ke, Plus):

When you press the interrupt button on the side of your Macintosh when
starting up, you should get a sad Mac icon with '0F000D' and some bits
cycling under the icon indicating it is performing a memory test.

This numeric code is in two parts:

The first two characters are the class code. The class code tells what
part of the diagnostic program found the error.

The second four are the sub code. The sub class code tells what the error
was. In the case of a bad RAM chip, the sub class identifies the bad chip
(this was very helpful to homegrown upgraders).

Begin_Table

Class Code Sub Code

1 = ROM test failed Meaningless
2 = Memory test - bus subtest identifies bad chips
3 = Memory test - byte write identifies bad chips
4 = Memory test - Mod3 test identifies bad chips
5 = Memory test - address uniqueness identifies bad chips

Single Chip Identification

Data Bit Location Sub Code Bits
-------- -------- -------------
0 F5 0001
1 F6 0002
2 F7 0004
3 F8 0008
4 F9 0010
5 F10 0020
6 F11 0040
7 F12 0080
8 G5 0100
9 G6 0200
10 G7 0400
11 G8 0800
12 G9 1000
13 G10 2000
14 G11 4000
15 G12 8000

Class Code Sub Code
---------- --------
F = Exception 0001 Bus error
0002 Address error
0003 Illegal instruction
0004 Zero divide
0005 Check instruction
0006 Traps instruction
0007 Privilege violation
0008 Trace
0009 Line 1010
000A Line 1111
000B Other exception
000C Nothing
000D NMI (normal indication)
0064 Couldnt Read System File into Memory

Macintosh SE & Macintosh II ROMs:
---------------------------------

The Sad Mac error codes have been changed to incorporate additional power
for testing and to support the 32-bit world. Generally, the same codes are
used for 68000 exceptions as the Macintosh, however they are displayed
differently.

The traditional Macintosh error codes are displayed like this:

0F0003

Where F indicates an exception occurred, and 3 indicates an illegal
instruction occurred. On the Macintosh SE and II, the display would appear:

0000000F
00000003
*Please note that 00000003 is a hex number.*

The new poweron error codes have the following format:

XXXXYYYY
ZZZZZZZZ

Where XXXX is internal test manager state information (ignore this), YYYY
contains codes that indicate either an exception code, or the test number
for a power on test failure. The ZZZZZZZZ code contains additional failure
information to help track down the problem.

YYYY Error Codes:
-----------------
$0001 The ROM checksum test failed. Ignore the Z field.
$0002 The first small chunk of RAM to be tested failed. The Z field
indicates which RAM Bit(s) failed. This small chunk of RAM is
always in Bank B.

Example: $AABBCCDD

AA=8 bit mask for bits 31-24
BB=8 bit mask for bits 23-16
CC=8 bit mask for bits 15-8
DD=8 bit mask for bits 7-0

$0003 The RAM test failed while testing bank B, after passing the chunk
tested for code $0002. The Z field indicates which bits failed as
in code $0002.

$0004 The RAM test failed while testing bank A. The Z field indicates
which bits failed as in code $0002.

$0005 The RAM External addressing test failed. The Z field indicates a
failed address line.

$0006 Unable to properly address the VIA1 chip. The Z field is not
applicable.

$0007 Unable to properly address the VIA2 chip (Macintosh II only). The Z
field is not applicable.

$0008 Unable to properly access the Front Desk Bus. The Z field is not
applicable.

$0009 Unable to properly access the MMU. The Z field is not applicable.

$000A Unable to properly access NuBus. The Z field is not applicable.

$000B Unable to properly access the SCSI Chip. The Z field is not applicable.

$000C Unable to properly access the IWM chip. The Z field is not applicable.

$000D Unable to properly access the SCC Chip. The Z field is not applicable.

$000E Failed Data Bus test. The Z field indicated the bad bit(s) as a
32-bit mask for bits 0-31. This may indicate either a bad SIMM or
data bus failure.

$000F Reserved for Macintosh compatibility.

$FFxx A 680xx exception occurred during power on testing.
The xx indicates the exception:

$01 Bus Error
$02 Address Error
$03 Illegal Instruction Error
$04 Zero Divide
$05 Check Instruction
$06 cpTrapCC, Trap CC, Trap V
$07 Privilege violation
$08 Trace
$09 Line A
$0A Line F
$0B unassigned
$0C CP protocol violation
$0D Format exception
$0E Spurious interrupt
$0F Trap 015 exception
$10 Interrupt Level 1
$11 Interrupt Level 2
$12 Interrupt Level 3
$13 Interrupt Level 4
$14 Interrupt Level 5
$15 Interrupt Level 6
$16 Interrupt Level 7
$17 FPCP bra or set on unordered condition
$18 FPCP inexact result
$19 FPCP divide by zero
$1A FPCP underflow
$1B FPCP operand error
$1C FPCP overflow
$1D FPCP signalling NAN
$1E PMMU configuration
$1F PMMU illegal operation
$20 PMMU access level violation

Macintosh Portable ROMs:
------------------------

The bootup code in the Macintosh Portable contains a series of startup tests
that are run to ensure that the fundamental operations of the machine are
working properly. If any of those tests fail, a Sad Mac icon appears on the
screen with a code below that describes what failure occurred. Here is a
typical example of a Sad Mac display with an error code below it:

SAD MAC CODE
05460203 = (D7.L)
000OB6DB = (D6.L)

The two codes are actually the contents of the two CPU data registers D6 and
D7. The upper word (upper 4 hex digits, in this case 0546) of D7 contains
miscellaneous flags that are used by the start-up test routines and are
unimportant to just about everybody except a few test engineers within
Apple. The lower word of D7 is the major error code. The major error code
identifies the general area the test routines were in when a failure
occurred. D6 is the minor error and usually contains additional information
about the failure, something like a failed bit mask.

SAD MAC CODE BROKEN DOWN

Test Flags Major Error
---------- -----------
0546 0203

Minor Error Minor Error
----------- -----------
0000 B6DB

The major error is further broken into the upper byte that contains the
number of any 68000 exception that occurred ($00 meaning that no exception
occurred), and the lower byte that usually contains the test that was being
run at the time of failure. If an unexpected exception occurred during a
particular test, then the exception number is logically ORed into the major
error code. This way both the exception that occurred as well as the test
that was running can be decoded from the major error code:

SAD MAC CODE FURTHER BROKEN DOWN
68000 Exception Test Code
--------------- -----------
02 03
In this example, the code says that an address error exception ($0200)
occurred during the RAM test for Bank A ($03); $0200 ORed with $03 = $0203.

Major Error Codes
-----------------

Below is a brief description of the various test codes that might appear in
the major error code:

**Warning**: Some of these codes may mean slightly different things in
Macintosh models other than the Macintosh Portable. These descriptions
describe specifically how they are used in the Macintosh Portable.

$01 - ROM test failed. Minor error code is $FFFF, means nothing.
$02 - RAM test failed. Minor error code indicates which RAM bits failed.
$05 - RAM external addressing test failed. Minor error code indicates a
failed address line.
$06 - Unable to properly access the VIA 1 chip during VIA
initialization. Minor error code not applicable.
$08 - Data bus test at location eight bytes off of top of memory failed.
Minor error code indicates the bad bits as a 16bit mask for bits
1500.

This may indicate either a bad RAM chip or data bus failure.

$0B - Unable to properly access the SCSI chip. Minor error code not applicable.
$0C - Unable to properly access the IWM (or SWIM) chip. Minor error code not applicable.
$0D - Not applicable to Macintosh Portable. Unable to properly access the SCC chip. Minor error code not applicable.

$0E - Data bus test at location $0 failed. Minor error code indicates
the bad bits as a 16bit mask for bits 1500. This may indicate
either a bad RAM chip or data bus failure.

$10 - Video RAM test failed. Minor error code indicates which RAM bits failed.
$11 - Video RAM addressing test failed. Minor error code contains the
following: upper word = failed address (16-bit) msb of lower word = data written
lsb of lower word = data read

Data value written also indicates which address line is being
actively tested.

$12 - Deleted
$13 - Deleted

$14 - Power Manager processor was unable to turn on all the power to the
board. This may have been due to a communication problem with the
Power Manager. If so, the minor error code contains a Power Manager
error code, explained in the next section.

$15 - Power Manager failed its self-test. Minor error code contains the
following: msw = error status of transmission to power manager.

lsw = Power Manager self-test results (0 means it passed, non-zero means it failed)

$16 - A failure occurred while trying to size and configure the RAM.
Minor error code not applicable.

Minor error codesPower Manager Processor Failures
--------------------------------------------------

If a communication problem occurs during communication with the Power
Manager, the following error codes will appear somewhere in the minor error
code (usually in the lower half of the code, but not always):

$CD38 Power Manager was never ready to start handshake.
$CD37 Timed out waiting for reply to initial handshake.
$CD36 During a send, Power Manager did not start a handshake.
$CD35 During a send, Power Manager did not finish a handshake.
$CD34 During a receive, Power Manager did not start a handshake.
$CD33 During a receive, Power Manager did not finish a handshake.

Diagnostic Code Summary
-----------------------

Below is a summarized version of the Sad Mac error codes:

Test Codes
$01 ROM checksum test.
$02 RAM test.
$05 RAM addressing test.
$06 VIA 1 chip access.
$08 Data bus test at top of memory.
$0B SCSI chip access.
$0C IWM (or SWIM) chip access.
$0D Not applicable to Macintosh Portable. SCC chip access.
$0E Data bus test at location $0.
$10 Video RAM test.
$11 Video RAM addressing test.
$14 Power Manager board power on.
$15 Power Manager self-test.
$16 RAM sizing.

Power Manager Communication Error Codes
---------------------------------------

$CD38 Initial handshake.
$CD37 No reply to initial handshake.
$CD36 During send, no start of a handshake.
$CD35 During a send, no finish of a handshake.
$CD34 During a receive, no start of a handshake.
$CD33 During a receive, no finish of a handshake.

CPU Exception Codes (as used by the startup tests)
--------------------------------------------------

$0100 Bus error exception code
$0200 Address error exception code
$0300 Illegal error exception code
$0400 Zero divide error exception code
$0500 Check inst error exception code
$0600 cpTrapcc,Trapcc,TrapV exception code
$0700 Privilege violation exception code
$0800 Trace exception code
$0900 Line A exception code
$0A00 Line F exception code
$0B00 Unassigned exception code
$0C00 CP protocol violation
$0D00 Format exception
$0E00 Spurious interrupt exception code
$0F00 Trap inst exception code
$1000 Interrupt level 1
$1100 Interrupt level 2
$1200 Interrupt level 3
$1300 Interrupt level 4
$1400 Interrupt level 5
$1500 Interrupt level 6
$1600 Interrupt level 7

End_Table

Article Change History
----------------------
20 Nov 1995 - Added new keyword and reviewed article for technical accuracy.
14 Aug 1995 - Added Internet table formatting convention.
01 Aug 1994 - Converted enclosed binary file to text and added to article.
20 May 1992 - Reviewed for technical accuracy.

Support Information Services
Copyright 1991- ed, Apple Computer Inc., All Rights Reserved
There have been 130769 total articles read in this database since June23rd
1997.


Date: Sun, 05 Oct 1997 10:48:17 -0600
From: EL
To: Classic Posts
Subject: Re: Old ImageWriter II

Does anyone know of a worthy charity (or individual) who needs and would
accept an ImageWriter II printer? It hasn't been used in over a year since
I picked up a used LaserWriter. The ImageWriter II still works fine, but I
don't need it and it is taking up space I do need. I don't consider its
market value to be high enough to be worth selling with higher resolution
printers so cheep theses days. But I consider it far to valuable to throw
in the trash.

Thanks
Dan Kelly

Many schools would be thrilled to have your printer. I just sold my
imagewriter II to a teacher to use in her classroom with an LC III. The
class cheered when I delivered it, and the teacher cheered when it
worked as soon as I plugged it in.

Even though the school recieved a large hardware grant, the red tape has
delayed delivery for over 6 months. So the teacher was really happy to
have the imagewriter.

Eric Lyons
Buda, Texas
http://www.web-brothers.com/gallery.html is served by a IIsi....


Date: Sun, 05 Oct 1997 14:29:12 -0400
From: V Martin Brennan
To: Classic Posts
Subject: SE/30 shrinking screen

It's the incredible shrinking SE/30! What started out to be a nine-inch
display has now shrunk to about a seven-inch display. No other problems
with the unit... it runs great and does everything that we want it to,
but our eyes are getting tired out by the shrinkies. Any suggestions
will be gratefully received.

(SE/30 with 20MB ram, doubled, 7.5.3 OS.)

Vince Brennan


To: Classic Posts
Subject: Pseud040
From: Kevin Jordan
Date: Mon, 6 Oct 1997 11:01:28 +1000

Date: 10/3/97
To: Classic Posts
From: michael
Subject: More notes from the new moderator

You may have noticed that messages are now separated by
hyphen lines instead of underscores. Hopefully, this will not
present a problem to anyone. This is to help someone who really
likes hyphens.

I received a lot of mail about the Pseud040 program. Here's
the latest news.

1. Someone says it won't let you install OS8 because the
installer looks in ROM to find the CPU type. Well, this may be
true, but I'd like for someone to try it anyway.

2. It will be distributed soon. I am trying to work out last
minute buggy behaviors. Payment will be $20 via Kagi. (Do you guys
think that's too much?

Michael Connolly

I certainly don't think it is too much. Looking forward to seeing it.
Kevin Jordan


Date: Sun, 05 Oct 1997 20:59:05 -0700
From: Fred Mindlin
To: Classic Posts
Subject: IIcx power supply replacement

I have a IIcx with Daystar 040 card and Radius full page display card,
with a bad power supply. I have another IIcx with a good power supply
and without the cards. Am I better off moving the cards to the one with
the good power supply, or trying to replace the power supply on the
machine with the cards? Either way, what are the cautions or special
procedures I need to follow?

Thanks for any help...
Cheers, Fred

Fred Mindlin , 3rd/4th grade bilingual immersion teacher
Alianza School,
408.761.6118
school homepage: http://www.alianza.santacruz.k12.ca.us/


From: "W.F. Gaasendam"
To: Classic Posts
Date: Mon, 6 Oct 1997 10:00:31 +0000
Subject: Re: SE/30 problems

After sending 3 fonts from my Performa to the SE/30 via Eudora attachment,
I attempted to retrieve the fonts from the attachments folder but when I
clicked "Check Mail", I was asked for my password which was correctly given
but I was immediately cut off line. My ISP I thought. Later in the day I
could not only access my mail box, I was unable to access my ISP without a
password which, when given, I was immediately rejected. In my following
attempts to get on line I was not even allowed the access of the modem. It
refused to dial up. Instead I was shown two windows. The first, "MacPPP
Status": "Terminal Mode". The second window was titled "PPP terminal
session". There is a blank enclosure below that, then at the very bottom,
the usual cancel and ok buttons.

At least there's something wrong with your settings. The terminal
window only appears when it is checked in the menu of Config PPP.
BTW, in this window you can manually dial to your provider. So you
type in ATDT <phone number>, login name, etc, like you are using a
simple modem application like Zterm. Normally a provider puts these
commands in a connect script. You can edit your connect script under
the button 'Config'.

First thing you should do is check whether 'terminal window' is
active or not. It should not be active. Then check the connect
script. When the fields are empty, you have to type in the right
modem commands (ask your provider).

Still, this doesn't solve the problem. The first versions of MacTCP
are rather buggy, and known to have problems with other applications.
E.g. I use MacTCP 1.1.1 with MacPPP 2.0. This doesn't work with
software for CD-Rom. Since you are using an SE 30 instead of SE, the
problem should have something to do with this. Perhaps you're using
another system, or virtual memory?

I would be remiss at this time not to offer my appreciation to our new
moderator, Michael Connally, for the splendid job he has been doing with
the Classic Post. I surely missed it while it was on hiatus and I am sure
most of us look forward to every informative issue.

Goes for me too.

Fred Gaasendam


From: "Gordon L. Harlan"
To: Classic Posts
Subject: *.sit.hqx?
Date: Mon, 6 Oct 1997 06:47:31 -0500

Ok, again, I'm a PC dweeb, I assumed these were similar to .ZIP files, but
they do not appear to function in a way I can relate to, I dbl-click on a
file, or pull it into the stuffit app and nothing happens. I tried to find
a newer version of stuffit, but it comes in an archived file, which
requires me to already have it (kinda catch-22 type of thing).

This is on an old Mac SE with only ONE meg of RAM. Is there a URL to
explain it all to me, I looked at alladinsys.com and there wasn't much help
there, that was the place that had the catch-22 archived archiver. They
ought to put it into a .sea file. At least that's what *I* think.

thanks
gordon

[MODEARATOR]

.sit is a stuffed file, so that's analagous to a ZIP file. Those are
uncompressed with StuffIt.

.hqx is BinHex, which is analagous to UUEncoding in making a file
transmissible via email by making all data printable. The easiest way I
used to decode these on my Mac Plus was the option built into Compact Pro,
the "other" compression utility. You can find that floating around.

If you had system 7, you could use Stuffit Expander to take care of
both encodings. But 7 won't run on your low-memory machine.

[END MODERATOR]


Date: Mon, 06 Oct 1997 08:13:10 -0500
From: Paul Vreugdenhil
To: Classic Posts
Subject: AE Accelerator question

I just purchased a used Applied Engineering accelerator (with no
documentation) for my Classic. I would like to here from anyone who can
help with jumper settings and any other helpful information to get this
accelerator working properly on my Classic. The only helpful numbers I
could find on the board are TW2325. TIA

I would also like to here from anyone who might have documentation for a
Levco accelerator (020) for an SE. TIA

In addition, I don't know if this is proper for this list, I have some
IIcx parts for sale. If interested contact me.

Paul
http://sapphire.surgery.wisc.edu/paul.html
Truth Ignored Is Still Truth


From: Simon Storey
To: Classic Posts
Date: Mon, 06 Oct 1997 16:42:29 +0100
Subject: Opening Macs

Re the torx 15 screwdriver in the UK- I found that a standard long handled
(8"?) 3mm blade flat screwdriver does a nice job of opening up Torx 15
screws.

I bought mine from Farnell - 0113 263 6311, or www.farnellcomponents.com;
they mainly do industry supplies, but take credit card orders of more than a
tenner. First class post is free. They have a huge range of tools - I got
the smaller torx drivers for powerbooks there too, at a very reasonable 2.51
ea + VAT. Try order code 281-244 for the 200x3 screwdriver. That's 1.99
+VAT! Ask a local tv repair shop/school or college lab tech etc to have a
look at the catalogue, or they may send you one if you ask them nicely. And
they're all northerners, too; lovely. I have no connection with them,
they're just good people to know about.

While I'm at it, CPC are a good source of cheap Mac leads & imagwriter
ribbons - account only, but ask a tv repair place and they may be willing to
help.

Simon Storey


CMD Home | Subscribe | Index | 1997 Index | CM Trading Post