Help! Sick //gs!

[nandu@anest4.anest.ufl.edu (Nandu S. Shah)]

My //gs has been acting strangely ever since I replaced my GS-RAM (1.5 M) 
with a 4M Q-RAM card (it no longer works properly with the old RAM card, 
either).  First I thought it was a power supply problem, so I bought a new 
one (and the problems disappeared).  Then, files on my HD started getting 
corrupted & their names started arbitrarily changing, sometimes to ILLEGAL 
names.  So I got Salvation-Deliverance & did what I could, but the hard 
drive problems persisted.  System 6.0 seemed to be working just fine from my 
floppies, though, so for the time being I disconnected my HD *and* my SCSI 
card, reducing my system to the following: ROM 01, 4M, TransWarp GS, and 
two 3.5" drives).  My system has been inactive for about the last month, due 
to a move to a new apt., and when I turned it on today, I thought it'd be 
nice to boot Sys 6 from a RAM disk to save me disk-swapping.  Here's where I 
got REALLY scared:

First, while I was copying my system disk to /RAM5, the Finder gave me an 
error to the effect of "Cannot complete this operation.  Directory not 
existent."  So I checked, and sure enough, the RAM5/System/System.Setup 
directory was now .../Systgm.Setup (the analogous dir on floppy was fine).   
Also, the file Error.Msgs was now Grror.Msgs (once again, the original was 
fine).  Thinking that something might be wrong with my system disk (it's not 
the original-- it's a custom setup), I tried using Installer to set up my 
RAM disk.  Halfway through the process, Installer told me to "insert the 
disk /RAM5"!!!  Being a bit on the obstinate side, I tried again & 
everything seemed to work okay.  When I tried to boot /RAM5, I got the old 
sliding apple...  So I booted my system disk & found all the necessary files 
in /RAM5 (although upon closer inspection, I found that some of the 
filenames had changed again)...  Finally, I renamed the bad filenames & 
did Salvation-Deliverance on /RAM5, which came up with a couple of errors 
(no bad blocks), including a damaged volume bitmap, and then claimed to have 
repaired them.  So I tried booting the RAM disk again, and once again got 
the sliding apple.  This time, when I tried to boot my sys disk, I got an 
error msg saying "The disk SYSTEM6 is damaged..."

I just realized that I didn't do a self-test today, but the last time I did 
one (back when I was getting pretty much these same error messages with my 
hard drive), my //gs passed the test(System Good).

Can anyone help me?  I would greatly appreciate ANY help or suggestions.
Please reply via email.

Thank you,
Nandu


Nandu Shah                                          nandu@anest4.anest.ufl.edu

         Please feel free to disregard completely this and any other
                          suggestion that I exist.