INFO-MAC@SUMEX-AIM.STANFORD.EDU (Moderator Dwayne Virnau...) (07/22/87)
INFO-MAC Digest Wednesday, 22 Jul 1987 Volume 5 : Issue 108
Today's Topics:
Re: Suitcase and NFNT resources
FCMT
RE: Super Mouse
MacTerminal and System 4.1
Re: Delphi Mac Digest V3 #33
Re: Delphi Mac Digest V3 #33
Re: macPlus keypad question (V5 #106)
Re: Help on data fork request from Major John Buono
Potential Bug???
Bug?
FKEY problems
"disk insert..." bug
Bug in Fullpaint
Pagemaker 2.0 saving bug?
Can the Macintosh II Power up by itself?
Mac II horrors
Re: V5 #101
mac II video card connector pin assignments?
Re: Mac II Software (V5 #107)
Phosphors
Re: Noise on DataFrame 40 (V5 #103)
fan noise on Mac SE.
Smoked video board
----------------------------------------------------------------------
Date: 21 June 1987, 17:21:32 PST
From: David M. Gelphman 415-854-3300 x2538 DAVEG at
From: SLACVM
Subject: Re: Suitcase and NFNT resources
Sorry if in my excitement about Suitcase I gave any misinformation
regarding the release date or any technical information. Thanks
Steve for providing the needed corrections.
I do have a question regarding NFNT resources. Basically I've been
trying to modify the Adobe screen fonts so that I can install them
into the system file and have only one font name appear in the
fonts menus for each font family. I've been reasonably successful
in some cases and sometimes there are some severe problems.
Basically I did the following to each screen font family: I used
Resedit to remove the 'extra' FOND resources which correspond to
BOLD, ITALIC and bold/italic. I used Fedit to change the FONT resources
for these font families to NFNT resources. I then use ResEdit to
install the resulting FOND resource and NFNT resources into the system
file. Some of these work quite well and others repeatedly cause system
bombs. I'm not sure why this would be the case. In any case, I'm sure
there is something I don't understand here AND it isn't clear to me
WHY the Apple Font/DA Mover doesn't just do the right thing for me
instead of making me bumble out on my own.
For Steve Brecher: assuming that one can resolve the above difficulties
with the NFNT/FOND/Font resources, will SuitCase properly add the NFNT
resources if those are in a Suitcase file.
David Gelphman daveg%slacvm.bitnet@forsythe.stanford.edu
------------------------------
Date: Wed 01 Jul 1987 22:45 CDT
From: N. Gokhale <MMAR013%ECNCDC.BITNET@forsythe.stanford.edu>
Subject: FCMT
Could the "GetInfo..." comments be stored as an FCMT resource inside a
particular file's resource instead of the DeskTop file?
o The comments wouldn't be erased after a desktop is rebuilt
o The Finder will read in disks faster
o The file information is not lost if the file is sent over the network.
o There is no danger of leaving a file's resource fork open since the file
is accessed only the first time a GetInfo is issued.
I know there are work-arounds for all of these, but this new approach could
save a lot of hassle.
thanks for your attention, now you can forget this and go back to what you
were doing.. (attn! apple)
Nihar, Western Illinois University
bitnet MMAR013@ECNCDC
internet MMAR013%ECNCDC.BITNET@WISCVM.WISC.EDU
uucp [wanginst!decvax!cbosgd!] psuvax1!ECNCDC.BITNET!MMAR013
------------------------------
Date: Sat, 20 Jun 87 00:41 EST
From: Paul Christensen <PCHRISTENSEN%rca.com@RELAY.CS.NET>
Subject: RE: Super Mouse
> Has anyone figured out how to use Control Panel 3.x with System 3.2?
> I copied the DA and INIT #30 from System 4.0 in the older system...
Control Panel 3.x works properly under System 3.2, as does Chooser 3.x, the
new KeyCaps (that reads the KeyLayout file), and the other DA's released
with System 4.1 (and 4.0). I've been using them in System 3.2 with no
problems, after using the Font/DA Mover to install them.
However, to install the mouse tracking from System 4.1 (and System 4.0)
you'll need to copy more than just INIT #30. You must copy the following
from System 4.1 (or 4.0) to enable the faster mouse tracking:
INIT #30 Installs mouse tracking code
MMAP #0 New mouse tracking code (if not in ROM)
mcky #0,1,2,3,4 Mouse movement definitions for tracking settings
(^ whoever said that Apple wasn't creative!)
Your mouse should then track properly under System 3.2. Also note that
Easy Access only responds to the new mouse tracking settings...it ignores
the settings from the older control panels.
Paul Christensen
CSNET: PCHRISTENSEN@RCA.COM
------------------------------
Date: Fri, 26 Jun 87 09:54:57 CDT
From: ragan%CDCCentr.BITNET@forsythe.stanford.edu
Subject: MacTerminal and System 4.1
CDC has a product Connect that is based on the source code of MacTerminal
(under license from Apple). Connect was broken under System 4.1 just as
MacTerminal was. We have a patch to fix Connect and it will probably fix
MacTerminal but I have not tried this since I don't have a copy of
MacTerminal handy. However, it might be that someone else out there would
like to try it and let people know if it works. The change is made by
finding the first occurrence of $02B6 in the binary and changing it to
$0A78.
MacTerminal contained some debugging code that stores something into 02B6
which is now used by System 4.1. This code should not have been left in.
------------------------------
Date: Wed, 8 Jul 87 10:42:19 pdt
From: Larry Rosenstein <lsr%apple.csnet@RELAY.CS.NET>
Subject: Re: Delphi Mac Digest V3 #33
In article <8707021845.AA00448@ucbvax.Berkeley.EDU> you write:
>Delphi Mac Digest Thursday, July 2, 1987 Volume 3 : Issue 33
>From: INTECO
>Subject: Mac II Err 28
>Date: 21-JUN 17:42 Programming Techniques
>While porting and adding color to my communications program to te Mac II
>I got a system error ID 28 (Stack runs into heap) from the same code
>that runs ok the Mac+ (Code is from LSP or MPW 2.B1 - same results).
>There are now low level tricks... Any idea?
>The error disappeared when I used NewCDialog for a the central modless
>dialog. Why? Perhaps it uses some UserItems?
Was part of your dialog in color?
If you color part of your dialog window, then you need to make sure you are
using a color grafPort.
Larry
------------------------------
Date: Wed, 8 Jul 87 10:41:14 pdt
From: Larry Rosenstein <lsr%apple.csnet@RELAY.CS.NET>
Subject: Re: Delphi Mac Digest V3 #33
In article <8707021845.AA00448@ucbvax.Berkeley.EDU> you write:
>From: LAMD
>Subject: Mac II Utilities
>Date: 20-JUN 04:11 Hardware & Peripherals
>Anyone know of a good screen blanker for the Mac II? I tried "Macsbug"
>today and it froze on boot. Also, anybody know if there's a version of
You need a special version of Macsbug to run on a Mac II. (In fact there
are different versiosn depending on whether you have 1, 2, 5, or 8 megabytes.)
>From: STANKRUTE
>Subject: debugging as art
>Date: 21-JUN 12:11 Programming Techniques
>I'm back here as an itinerant worker in the valley. Putting together
>some documentation for Jasik's The Debugger. Right now I'm doing a
>section called the Art Of Debugging, and am shamelessly scrounging for
>people's favorite two or three vital Macintosh debugging hints/
First, I would try to avoid bugs by putting in extra code to check for
invalid situations (defensive programming). If the code is under a
compile-time flag it adds nothing to the final result, but will help track
down problems quickly. (We did this in MacApp, and it made a big
difference.)
As far as specific cases go, here are a couple of things that come to mind
right off:
* Be careful about whether thePort is a plain grafPort or a window. You
can't call InvalRect (for example) if thePort is a plain grafPort.
* Be careful about multiplying 2 integers and expecting to get a long (eg,
the size of a handle). In Pascal, for example, you have to force the
compiler to use a longword multiply.
* If you get a system error, the System Error handler stores all the
registers in a fixed memory location. (You can disassemble the start of the
SysError trap to find out where.) This will tell you where the actual call
to the SysError happened. Alternatively, you can set a trap breakpoint on
SysError.
* Read the compatibilty guidelines in the Tech Notes.
Larry Rosenstein
Apple Computer
UUCP: {sun, voder, nsc, mtxinu, dual}!apple!lsr
CSNET: lsr@Apple.com
------------------------------
Date: 13 Jul 87 15:06:02 GMT
From: dartvax!earleh.UUCP@seismo.css.gov (Earle R. Horton)
Subject: Re: macPlus keypad question (V5 #106)
> From: "Collins, Herman" <SYSHERM%UKCC.BITNET@wiscvm.wisc.edu>
> Subject: MacPlus keypad question
> OK, ok, ok. I give up. I've read the books (I'm waiting for the
> movie). I've hacked at the code. How in the heck do I tell the
> difference between the "=/*+" keys on the MacPlus keypad and the cursor
> keys on the main keyboard? This topic has come up several times on this
The "=/*+" keys are SHIFTED, while the cursor keys are not. That is,
the "=/*+" return the shiftKey bit set in the modifier flags. If you
hold down the shift key and type one of the cursor keys, the application
gets the keypad key, every time. Shifted: keypad, unshifted: cursor.
This was done because Apple was in such a rush to release the Mac Plus
that they were willing to ship it with an un-fixable hardware bug that
few people would notice, rather than do the job right. This, to me,
is an unacceptable business practice.
*********************************************************************
*Earle R. Horton, H.B. 8000, Dartmouth College, Hanover, NH 03755 *
*********************************************************************
------------------------------
Date: Fri, 17 Jul 87 13:34:04 CDT
From: BMDP <BMDP@scarecrow.waisman.wisc.edu>
Subject: Re: Help on data fork request from Major John Buono
An application can open its own file just as if it were opening a regular
data file external to the application. The reads and writes then go to
the data fork of the application. My Spelling Champion application keeps
the dictionary in the data fork.
------------------------------
Date: 24 Jun 87 11:21 PDT
From: newman.pasa@Xerox.COM
Subject: Potential Bug???
I think I noticed a bug the other night on my SE, but I'm not sure, and
I wondered if anybody else had noticed it.
When you pull a menu down that has more than the number of menu items
that would fill the screen top to bottom, the menu manager now puts a
little arrow at the bottom of the menu to indicate that you can scroll
down. I pulled a menu down that appeared to have exactly the number of
menu items necessary to fill the screen top to bottom, yet the menu
manager put the arrow in anyway. The arrow took the last space of the
screen, and forced me to scroll to get at that one menu item too many
(which would have fit on the screen had the arrow not been there.
Is this a bug? Has anyone else noticed it? Or am I hallucinating?
Thanks,
>>Dave
------------------------------
Date: Thu, 16 Jul 1987 13:50 PDT
From: GLAURIE%CALSTATE.BITNET@wiscvm.wisc.edu
Subject: Bug?
I have encountered what may be a Mac bug. Using ResEdit I have been "tailoring"
windows to display icons the way I prefer them to be spaced, etc. I also prefer
the windows to display the "small icons".
Using ResEdit I attempted to change my default view in the Finder by
popping into LAYO and changing the display. To my surprise I can change the
display to anything except "small icons", although pulling down the "View" menu
shows that "small icons" should be the current view for the active window.
I would welcome any suggestions. I am using a Macintosh Plus with the latest
version of Finder.
Laurie Takao
------------------------------
Date: Mon Jul 20 16:04:40 1987 EDT
From: TDOWNEY@cc8.bbn.com
Subject: FKEY problems
I have had two problems with FKEYs since upgrading my MacPlus to system
4.1/finder 5.5 and am wondering if anyone else has seen these or knows what
causes them:
1. FKEYs don't seem to work at all when running Excel 1.04. Pressing the keys
causes nothing at all to happen, both for the standard Apple FKEYs and the ones
that I have installed. They work fine in other programs. Is this a bug in
Excel?
2. The Pop-key init causes my Mac to crash during boot. Removing it from the
system folder cures the problem. The init works fine on my MacPlus at home,
but not on my Mac at work. The only obvious difference in my upgrade
procedure is that I used FKEY manager (1.7) on my Mac at work after the
installation of 4.1, but haven't used it on the other Mac yet.
The only non-standard thing that I am currently running is Tempo.
Any ideas or thoughts?
Tom Downey, tdowney@cc8.bbn.com
------------------------------
Date: Tue 21 Jul 1987 12:06 CDT
From: Nihar Gokhale <MMAR013%ECNCDC.BITNET@forsythe.stanford.edu>
Subject: "disk insert..." bug
why are the Cmd-Shift-1/2 fkey's disabled during a "disk insert..."
interrupt??? I spent about half an hour swapping disks in the external
drive while the internal drive sat idle (it had a disk in it of course
but I could not eject it!) This is a really bad flaw in the system obviously
not fixed because most apple techies out there either use one drive or a HD.
so I ask Apple or any hackers out there: could you please provide a patch
to fix this annoying and unnecessary problem?
------------------------------
Date: Mon, 6 Jul 87 00:53 N
From: <AERTS%HLERUL5.BITNET@forsythe.stanford.edu>
Subject: Bug in Fullpaint
Well, mucking about in Fullpaint I ran across another bug...
Try this:
Close all files.
Try to get rid of the menu bar (by a command A) en zap!
You just bombed your mac!
In my case, it was just an accident as I ment to strike the
command Q, and if you can't imagine loosing
data this way, since all the files have to be closed first,
well, I think you are right. Still, never underestimate
the power of a bug. The most innocent bugs cause no
trouble until maximum effect can be reached. (sorry, murphy)
So B-ware!
-John Sinteur-
(aerts@hlerul5.bitnet)
Leiden, the Netherlands, Europe, etc.
Disclaimer: that there is no funny disclaimer under this message
has nothing to do with my ability to think up one.
------------------------------
Date: Fri, 17 Jul 87 19:23 N
From: <AERTS%HLERUL5.BITNET@forsythe.stanford.edu>
Subject: Pagemaker 2.0 saving bug?
I recently ran across something rather annoying in pagemaker 2.0
I had a _very_ large document of two pages :)
Which means, I had some Ilustrator files on my page, and
those tend to get big.
Actually, I had the same page twice, with different layout
so I could make a choice between them after seeing them
as LaserWriter output.
The file was almost 700 K !!!
Well, I copied this to a floppy, had them Laserwritten :)
and then went to a friend, who showed me something I found
extremely fascinating, so I said, make a copy. Well, OK, but
I had to make some free space on my floppy. No problem, enter
pagemaker, get rid of page two, and voila! ehh. nope...
Although I had removed some 350 K from the document, that
didn't show on the floppy. The file was still 700 K..
I borrowed a floppy from my friend:
I had to reenter pagemaker, save as to a different floppy,
diskswapswapswapswapswapswapswapswapping as I went along,
remove the old file, copy the new one, and finally copy the
stuff my friend showed me. Awkward as I'm used to using a HD.
I reread the manual, didn't find anything about it. Did I miss
something? Is this a bug or a feature? Or just odd?
John
AERTS@HLERUL5.bitnet
------------------------------
Date: Thu, 09 Jul 87 14:47:56 SET
From: Alexander Falk <K360950%AEARN.BITNET@forsythe.stanford.edu>
Subject: Can the Macintosh II Power up by itself?
Finally I got my Macintosh II last week. It's simply speaking great|
There are some questions left:
1. Apple's Lisa included an undocumented feature used only by a diagnostic
program, which made it possible to set a time, after which Lisa would
power up again automatically. Is this feature implemented in the Mac II,
too?
2. Why is a memory bank on the MacII Logic Board 4 SIMM's wide? If it were
2 SIMM's wide, one could use the 2-mb upgrade (M2019) together with
the original 1MB and have a 3MB Machine.
3. If one would turn off the 24 Bit Address Mode with SetMMUMode, what
would happen? Would the OS die, or would some Applications simply break?
Any answer would be appreciated.
Alexander
------------------------------
Date: Mon, 13 Jul 87 13:58:29 edt
From: rs4u+@andrew.cmu.edu (Richard Siegel)
Subject: Mac II horrors
This morning, I carried my hard drive from my Mac Plus to a newly acquired
Mac II. I hooked everything up, turned on the disk, waited 10 seconds, and
turned on the Mac II. Whiole the Mac was booting, I moved the keyboard to
a more comfortable position; in the process, the keyboard cable snagged
(not my fault; I've alread shot the installer), and the keyboard got
disconnected. The Mac II stopped dead in its tracks. Screen went dark,
disk stopped running. So I turn everything off, reroute the cables from the
keyboard, and fire everything up. No response from the hard drive. The Mac
II sits there and blinks the question mark, so I stick in a floppy. The
system boots; I get the floppy's icon, then I get the message: "This is not
a Macintosh disk; do you want to initialize it?"
After some sincere curses, I click "Cancel". I fire up the Apple HD SC
Setup (I'm using HD 20SC), and initialize the hard disk. But when I quit to
the Finder, the Hard drive's icon doesn't appear! So I go back intoh HD SC
setup, and it says that my hard disk (SCSI 5) is not a Macintosh-format
hard disk.
So I carry the whole deal back to my Plus, and restore the hard disk
(DiskFit is *wonderful*). Then I go back to the Mac II, hook up everything,
and power on. This time, I get a System Error 33 on startup. I click
Restart, and once again, my hard disk is destroyed!
Why is my hard disk getting ruined?! Here's the background:
Mac II with 1mb memory, one floppy drive.
Apple Extended Keyboard
Apple Hard Disk 20SC (platinum) set to SCSI address 5
Apple 12" monochrome monitor
Apple Video Card
The software:
System 4.1
Finder 5.5
Hard Disk SC Setup version 1.3
I don't have any strange startup software; the only INIT
I have is for LaserSpeed (a LaserWriter print spooler).
I suspect that this INIT *may* have caused the system error,
but why? I've since un-installed it, but
I'm not especially interested in risking the information
on my hard disk
again.
I didn't actually lose anything, since I backed up the hard drive before
moving it, but it is a real inconvenience to restore a hard disk; it takes
a while.
Can anyone offer help? Has anyone had a similar problem? I remember
hearing about problems with early hard disks on the SE; is this possibly
related?
Any assistance would be greatly appreciated.
Rich
------------------------------
Date: Fri, 19 Jun 87 02:00:32 EDT
From: MacTechnics_User_Group@um.cc.umich.edu
Subject: Re: V5 #101
There is currently NO video card for the Mac II that implements hardware
drawing (i.e., they all tax the 68020). Inside Mac V mentions that the
color drawing modes are the same as the TI graphics chip and implies
that hardware drawing would be available at some point.
Some printer spoolers (I've used SuperMac's LaserSpool) allow the use
of CMD-SHIFT-3 to dump the screen directly to the LaserWriter. Very
handy addition...
There was a question about DA's and keyboard stealing a while ago.
It seems to me that the program should steal the keyboard interrupt
(or let the ROM process the interrupt and then call the user routine).
Apple has hooks for the interrupts that make processing them fairly
easy (but interrupt routines are always a little difficult). A DA
without a window might miss out on keystrokes due to confusion about
whether the application should get the key or the DA.
Eric Shapiro
MacTechnics
P.O. Box 4063
Ann Arbor, Mi 48106
(313) 668-1881 (work)
------------------------------
Date: Thu, 25 Jun 87 17:24 EST
From: "RCSDY::YOUNG%gmr.com"@RELAY.CS.NET
Subject: mac II video card connector pin assignments?
We have received our MAC II but the color monitor will not be available for
several months yet. We would like to temporarily try hooling up to the SONY
Trinitron Color TV model KV-1311CR, which has a SONY 34 pin connector for
analog input. Question: Does anyone know the pin assignment on the DB-15
connector which comes out of the MAC II video card? Also, what monitors
have people managed to successfully connect up to the MAC II?
YOUNG@GMR.COM@CSNET-RELAY.CSNET 313-986-1471
p.s. I will post all replies to INFO-MAC.
------------------------------
Date: Tue, 21 Jul 87 01:18:31 pdt
From: palomar!joel%beowulf@sdcsvax.ucsd.edu
Subject: Re: Mac II Software (V5 #107)
There were some questions about a "colour" Mac II by Ralph Martin...
The 256-color (8-bit) is definitely recommended if you plan on doing any
color or gray scale work. It's on the order of $100 from NEC distributors
of the chips, $150 at dealer list, but well worth it for any imaging or
drawing work.
A Mac II is pushing it at 1 Mb and (subjectively) it seems to get slightly
worse with the 256 colors. However, I see no reason to recommend 4 (or 5)
Mb over 2 Mb, short of a large RAM cache. All the software I've seen so
far will fit in 1-1.5 Mb (other than A/UX, which isn't a Macintosh
application.) A 1->2 Mb upgrade can be real cheap if you find a Mac
Plus with 120ns SIMMs (the recent ones do) that have become redundant.
As for the color products from Apple, they will probably be from Claris
(the spin-off software company) as they are many months off. Other color
products will likely be announced at Macworld, August 11-13, although
delivery may be fall or even winter.
Joel West . ihnp4!gould9!palomar!joel
Palomar Software, Inc. joel%palomar.UUCP@beowulf.sdcsvax.edu
P.O. Box 2635, Vista, CA 92083 joel@palomar.cts.com
------------------------------
Date: 22 Jun 87 07:55:00 EST
From: "ERI::SMITH" <smith%eri.decnet@mghccc.harvard.edu>
Subject: Phosphors
Following up on a recent question, I'd like to start a discussion on phosphors
because questions keep coming up on this and nobody has more than scraps of
information.
A number of standard sources have SOME information on characteristics of the
JEDEC P-numbered phosphors. I don't have it at hand, but I think even the
Handbook of Chemistry and Physics has it. The information is always the
same, i.e. they're all getting it from the same place. The reference I
DO have at hand is "Reference Data for Radio Engineers," 6th edition,
copyright 1975, published by Sams. pp 17-34 through 17-36 give spectral
efficiency curves and a table of properties for P1 through P31.
It cites "Optical Characteristics of Cathode Ray Tube Screens," JEDEC
Publication #16, (J6-C3-1), and "Introduction to Luminescence of Solids,"
H. W. Leverenz, Wiley, 1950.
For "P4," it gives the composition as "ZNS:Ag+ZnCdS:Ag". Three variants are
mentioned, "all sulfide," "silicate-sulfide," and "silicate" types. All
have fluorescent color as "white" Persistence is "medium short" for all
sulfide, and "medium" for the others. No numeric data on persistence and
decay is given.
I've been through this unsuccessfully before; unfortunately for visual
physiologists, computer companies consider tubes a commodity and often use
varieties from several vendors. The article in "reference data" warns that
"considerable departure" from the data presented is to be expected in
individual screen samples, i.e. you'd have to open your Mac and REALLY find
out what vendor made the tube and contact them for technical data.
In general, CRT screens show obvious, gross departures from any kind of
simple exponential decay model. At the very least many screens show an
"afterglow." A Mac screen, for example, obviously has some decay on the
order of 1/20 second, but also has an afterglow that lasts for minutes.
Some Lisa screens have an obvious GREEN afterglow. So the spectrum changes
as it decays, i.e. different wavelengths decay at different rates. I
remember one attempt to measure phosphors where they thought their equipment
was drifting; it turned out that with the kind of measurement they were
making, they were able to detect phosphor aging as they watched. (They were
using an unscanned dot; current density was high, but NOT at a level that
would startle any experienced CRT user. There was NO visible burning of
the screen. Just that the output from the dot would slowly, slowly, but
measurably keep s-a-a-a-a-a-g-i-n-g--and whenever they moved the dot slightly
to a fresh place it would recover).
Daniel P. B. Smith ARPA: smith%eri.decnet@mghccc.harvard.edu
Eye Research Institute CompuServe: 74706,661
20 Staniford Street Telephone (voice): 617 742-3140
Boston, MA 02114
"We are in great haste to construct a magnetic telegraph from Maine to
Texas; but Maine and Texas, it may be, have nothing important to
communicate."--Thoreau
------------------------------
Date: 26 Jun 87 20:38:04 GMT
From: kwe@bu-cs.bu.edu (kwe@buit1.bu.edu (Kent W. England))
Subject: Re: Noise on DataFrame 40 (V5 #103)
GFJAK in Alaska recently posted a note about horrible noises in his
DataFrame 40 M drive. I have a year old 20 M DataFrame that was making
screeching noises (it's a noisy drive anyway) and I had to have it
serviced. The noise abated when the weather was humid or rainy and got
worse as it got hotter and drier. The technician said that the problem was
caused by the antistatic arm. He sprayed some antistatic spray on it and
that was it. No loss of data. I couldn't believe that screeching was
caused by static, but it was fixed. The drive is still noisy (about as
noisy as an SE fan). So if you think your screechy drive is humidity
sensitive then maybe it's the antistatic arm. It's possible you may be
able to fix it yourself, but I wouldn't have any idea how.
Hope this helps.
| Kent W. England |
| Network & Systems Engineering Group |
| Boston University |
| Information Technology |
| 111 Cummington Street |
| Boston, MA 02215 |
| (617) 353-2780 |
| kwe@buit1.bu.edu internet |
| itkwe@bostonu BITNET |
------------------------------
Date: Wednesday, 08-July-87 8:10 AM EST
From: J_CERNY%UNHH.BITNET@forsythe.stanford.edu
Subject: fan noise on Mac SE.
We received our first shipment of Mac SEs. Those of us who are switching
from Mac 512's or MAC Plus's are astounded at the fan noise. At first we
even thought the fans might be defective, but realized they were all the
same. What makes them esepcially annoying is that the motor changes in
pitch when power is drawn to disk drives etc. Does anyone know if Apple is
aware of this problem and/or if there are other fixes. It seems that most
of the noise is from the fan motor itself, not from the air being forced
through the air slots. The noise is not as severe as that produced by the
old Zenith Z100's (which sounded like small jet engines), but it is
extremely annoying, especially if you do not have other contributing noise
from a laser printer, hard disk drive, etc.
Jim Cerny
Academic Services Group
University Computing Center -- Univ. N.H.
J_CERNY@UNHH
------------------------------
Date: Tue, 30 Jun 87 17:24 CDT
From: TILLEY%UOFMCC.BITNET@wiscvm.wisc.edu
Subject: Smoked video board
While downloading a large hqx file, my screen narrowed, funny interlacing
and overlapping LARGE characters appeared and smoke poured out the top
left of my 1984 stock fat mac (normally left on).
I removed an obviously burnt capacitor (C1 25V 3.9uF bipolar) and
temporarily tacked in an approximate replacement. Powered on and
screen was perfect. This was too easy.
Powered off, shorted CRT anode to chassis (a bad thing??) and permently
soldered in the replacement. Now screen is unreadable. Illuminated area
too far left, too high, and has 12 white downward sloping lines and
12 paler level lines on it - much different than original symptoms.
Also the replacement gets too hot (perhaps not surprising).
Tried another replacement. Same thing. No other parts look damaged or
get hot. Machine appears to boot OK.
Help. Can anyone debug this from this limited description?
Where is the best place to get a schematic of this board?
Many thanks,
Richard <Tilley%uofmcc.BITNET@wiscvm.arpa>
------------------------------
End of INFO-MAC Digest
**********************