Re: Sys 6.0.1 Technical Problems

[nathan@visi.com (Nathan Mates)]

In article <jeremy-0705971203290001@haines-du-08.seaknet-dom.alaska.edu>,
Jeremy Andrews <jeremy@seaknet.alaska.edu> wrote:
>I have an original Woz IIgs with ROM Version 01.  I've been using system
>6.0.1.  On occasion after a crash my computer won't restart, crashing into
>the monitor.  To fix this error I'd have to reinstall the Prodos file, and
>all was well.

   You don't seem to mention what kind of disk media you've got 6.0.1
on.  If it's any from of SCSI, I'd advise you to double-check
termination and the like. In my experience (and I do crash a lot,
especially when developing) disk corrupting crashes are rare for me.

>But if I select shut down, then shut down, then actually turn off the
>computer, I then have about a fifty percent chance that when I turn the
>computer back on I'll crash into the monitor.

   _Really_ sounds like SCSI termination errors if it's behaving
differently from poweron until later operation.

>After file by file weeding things out, I found an error in my
>sys.resources.  Unfortunately, the problem seems to be in all five copies
>I have on various disks...  Copy II plus 9 giving me a $4B error, while
>Copy II plus 8.3 gives me a $4A error.  Finally I was able to get a new
>copy in there, but it didn't seem to help things.

   DO NOT USE COPY ][+ ON SYSTEM 6.* FILES! System 5.0 introduced
'forked' files, which Copy ][+ is UBABLE to copy correctly, and tends
to corrupt your disk partitions while doing so. Seriously, what is
wrong with using the GS System Installer, which is designed to copy
these files, and do a good job at them.

>I also tried replacing the following files in the System folder: Start,
>GS.OS, Start.gs.os, gs.os, error.msg and gs.os.dev.  I also tried
>replacing in the System.Setup folder:  Tool.setup, TS2, TS3, Resource.mgr,
>Sys.Resources.

   And right now, the partition/disk this is on could be pretty
toasted.  I'd advise checking the disk for integrity (and NOT using
Copy ][+ for the integrity check or any future things involving System
6.* files), and repairing any damage. ProSEL is does a great job at
that; it's available from Charlie's Appleseeds.

>Can any one tell me what is wrong here?  Is there any particular file that
>is suspect?  What might have caused this?

   Sounds like possible SCSI flakiness, and use of a program that's
known to frag System 6.* files. 

Nathan Mates
--
<*> Nathan Mates http://www.visi.com/~nathan/      <*>
# What are the facts? Again and again and again-- what are the _facts_?
# Shun wishful thinking, avoid opinion, care not what the neighbors
# think-- what are the facts, and to how many decimal places?  -R.A. Heinlein