[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A few (more) IIgs questions.



In article <37BCCD3B.AFFE6221@swbell.net>, rubywand@swbell.net wrote:
> 
>      1.7S sounds like a good version number. You may even have the 32k cache
> installed-- also nice. For info on speed upgrading see
> http://home.swbell.net/rubywand/Csa2ACCEL.html .
Oh, cool. Now, hopefully it's the computer's faults and not the GS...it
would suck to get such a nice TWGS and have it die before my eyes. There
is a small square board piggybacked onto the card marked 'Cache', I'm
guessing that's what you're referring to? It seems to be fairly well
attached though, so I fear to yank on it...but it seems to be...on top of
the CPU on the card?
> 
>      GS/OS error $0046 is "file not found". This could mean that the file is
> missing. Or, it may indicate a messed up Desktop file in your ICONS/ folder.
> You could try booting from diskette and deleting the Desktop file on the hard
> disk.
Hmm, will try that then. Or if I get really sick of it, a reformat
> 
>      If you are running at below spec voltage and/or getting spikes due to
> overloading, then, you are likely to experience all sorts of errors.
Hmm. Well, maybe I'll pull the PCT. Is it using just as much power if I'm
not using the PCT programs and the slot is set to Mouse or whatever it is
in that slot instead of 'Your Card'? Just wondering...I mean, I'm sure it
is, but still...
 
> _______________
> 
>      GS/OS error $0052 is "unknown volume type".
Hmmm <shudder>
> 
> 
> > Also...if I move the cursor block in the transwarp settings panel (in the
> > control panel) up and down rapidly (by hitting up and down arrow keys)
> > <don't ask me why I was doing it, I think it was idle frustration> the
> > screen will get a scattering of gibberish over it. But then it goes away
> > and things seem to return to 'normal'
> > 
> > Any ideas? I hope that the very TWGS I have quested mightily for is not
> > now dying in front of me.
> 
>      It sounds like your hard disk may be getting beat around a bit. You may
> need to clean up some stuff with ProSel-16 or a similar utility and reinstall
> some files.
<sigh>
> 
>      Try pulling your hard disk and running your system from diskette with
> mainly just the TWGS-- i.e. pull the SCSI interface and any other
power-sucking
> cards. (The idea is to simplify and to eliminate low voltage and glitching.)
> 
>      If everything works okay then many (or all) of your problems could relate
> to not having enough clean juice at the motherboard and Slot cards.
> 
>      Something else to try is cleaning the contacts on your TWGS card.
If there
> are still problems, scootch up and re-socket each socketted IC on the TWGS.
> It's kind of a pain; but, checking the continuity of lines in your TWGS cable
> with an Ohm meter is a good idea, too.
Yeah, I'll try the former and then maybe the latter if I get really
desperate...I hate prying at ICs and stuff, I always end up bending a pin
no matter how hard I try (even if I'm using an IC puller, too). Since I
hardly ever (read as haven't used it yet, was going to start once I got a
HD but never bothered yet) use the PCT, I'll probably pull it if that will
help...

Here's a regular problem with my HD, which leads me to believe that it may
indeed be all the hard drive. I think it is slowly dying. If I turn the
drive on say, 5 minutes before the IIgs, it will not work. It accesses for
a bit, the IIgs looks like it will boot....but then, nope, it moves on to
the disk drives after about 3 minutes of flashing the light on the HD.
Now, if I let it 'warm up' with the IIgs off for about, oh, 20 minutes,
then it starts up without any problems...or at least it did, up until
today. In the event that the HD is indeed dying, would replacing the drive
in it with a newer, bigger one help (I was planning on doing that anyway)
or is part of what's dying sound like it may be on a part of the circuits
built into the enclosure itself rather than the drive. (It has no problem
starting up, mind you, so I don't...think...that it's a PSU problem...it
just won't boot or recognize right away if I don't let it 'warm up')