Re: Problems running Basic.system on hard drive

[rubywand@swbell.net]

David de Sosa writes ...
> .... 
> I just finished re-initializing my hard disk because my directory
> had gotten corrupted recently and I wasn't able to write to the drive 
> anymore.
> ....
> I reloaded GS/OS 6.01 using the Installer, then added the Ramfast 
> driver, ZipGS Init and other ZipGS files (CDA, CDEV).  I've always had 
> this problem trying to use Basic.System off the hard drive since day 
> one. I really think it has something to do with using the ZipGS or 
> Ramfast drivers because everything else loaded is identical to what's 
> on the system disk ....

     Maybe; first, it does no harm to unplug and securely replug the SCSI 
cable to your hard disk.

     Zip's CDEV is known to be buggy. Also, it is unclear why you would 
have Zip.init installed on a hard disk. Normally, Zip.init is used only 
on diskettes to make changes in Zip's settings to accommodate diskette 
boots. It may be a good idea to wipe both the Zip CDEV and the Zip init.

     If the above does not help, then, before doing hardware-related 
checks, you may want to retry BASIC.SYSTEM after wiping the 'usual 
suspects': AppleTalk (drivers, inits), CloseView Init, ICONS/Desktop, 
screen savers, any other weird inits, NDA's, etc..

     Other tries focus upon the hard disk and related hardware. You can 
try renaming BASIC.SYSTEM to BASIC.BOMB and, then, copy BASIC.SYSTEM from 
the system diskette to the hard disk. See if this new BASIC.SYSTEM works 
any better.

     The idea behind this test is that disks sometimes develop weak areas 
which accept and verify writes but screw up upon later reads. If your 
installs and re-installs have ended up placing BASIC.SYSTEM onto the same 
weak spot (or, unluckily, another weak spot), then you would tend to have 
problems with BASIC.SYSTEM.

     A related check is to have Copy II+ verify each file on your boot 
volume.

     If the new BASIC.SYSTEM works okay or Copy II+ Verify Files turns up 
a number of errors, you may have a hard disk on its last legs and/or some 
problem with termination on your SCSI chain. A glitching SCSI interface 
and a bad SCSI cable are other possibilities you can check by swapping-in 
known-good units.


Rubywand