Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!hammen
From: hammen@csd4.milw.wisc.edu (Robert J. Hammen)
Newsgroups: comp.sys.mac
Subject: Re: Color/Non-Color Mac Logo at Start-up - What duz it mean?! *SOLVED!?*
Message-ID: <2356@csd4.milw.wisc.edu>
Date: 3 May 89 04:27:07 GMT
References: <1549@thumper.bellcore.com>
Sender: news@csd4.milw.wisc.edu
Reply-To: hammen@csd4.milw.wisc.edu (Robert J. Hammen)
Organization: Bulfin Printers
Lines: 45

>If you upgraded to 6.0.x using the MINIMAL mac-ii script, it doesn't
>copy in the color icon to the system file to save disk space.  Pasting
>in the cicn resource from another system file, or re-installing
>using the standard mac-ii script should fix the B/W startup icon;
>assuming you monitor is set for color :-)

This might not be the cause of the problem in this case. One of the first
things I noticed when I got my Mac II was that it didn't always display the
color icon, but in the middle of startup it would switch over to the color
mode. This is caused by the Mac's PRAM not matching up with the settings in
the Monitors cdev, as someone mentioned it: simply go to the Control Panel,
turn color off (go to B&W 2-bit), close the Control Panel, and then open it
again and set it back to 256 (or whatever) colors.

>HOWEVER, I still 
>don't know why I'm getting fairly frequent bombs.  There doesn't seem to be 
>any special rhyme or reason to it.  Not always repeatable,
....
>YAP (Yet Another Problem): This probably isn't related (or IS it?!):  I'm
>having a devil of a time copying files from floppy to my HD.  Using the usual
>finder level "select & drag" method results in some files (usually the smallest
>of the bunch) getting copied, but the bigger files die - I get a "Error
>writing file -- (Disk Error)" with a "Continue" or "Cancel" button selection.
>The above verbage is approximate, but should ring a Bell(R) with the Mac gurus
>in the audience. Watching the "meter" (the little 'How much has been copied so 
>far' display - the error occurs at the instant it stops reading the big file and
>before it begins writing it to the HD (or IMMEDIATELY after it TRIES to write 

Judging from the problems you seem to be having, I'd bet one of the following
things is happening: your System is corrupted, and/or your hard disk is
corrupted (judging from the write errors that you're getting trying to copy
files to the disk, I suspect the latter, though you never know. It's amazing
sometimes how the Mac can continue to function somewhat when the System file
is trashed). Call me paranoid, but I don't modify my System file often (thanks
to Suitcase II), so I keep a couple of backups on floppies, and then restore
a "fresh" copy every couple weeks or so.

Robert

///////////////////////////////////////////////////////////////////////////
/ Robert Hammen  | hammen@csd4.milw.wisc.edu | uwmcsd1!uwmcsd4!hammen     /
/ Delphi: HAMMEN | GEnie: R.Hammen | CI$: 70701,2104 | MacNet: HAMMEN     /
/ Bulfin Printers | 1887 N. Water | Milwaukee WI 53202 | (414) 271-1887   /
/ 3839 N. Humboldt #204 | Milwaukee WI 53212 | (414) 961-0715 (h)         /
///////////////////////////////////////////////////////////////////////////