Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!wuarchive!udel!sbcs!ameristar!rick
From: rick@ameristar (Rick Spanbauer)
Newsgroups: comp.sys.amiga
Subject: Re: Raaaaaaaaaaaahhhhhhhhhhhhhhhh!!!!!!!!!!!!!!!!
Message-ID: <1990Aug19.174021.11201@ameristar>
Date: 19 Aug 90 17:40:21 GMT
References: <03896.AA03896@sosaria.imp.com>
Organization: Ameristar Technology, Inc
Lines: 33

In article <03896.AA03896@sosaria.imp.com> wizard@sosaria.imp.com (Chris Brand) writes:
>Swift 170 megs harddisk.  Yes.  Destroyed.

	You have my empathy that your disk went bad.

>the buggy ram expansion did - you can't work seriously one hour without a
>crash):  re-format the drive.  But this time, something was different - I

	This just is not normal.  I've had an assortment of machines, with
	drives from several different manufacturers, that I use for
	professional development (ie it is "serious work").  I have never
	had the sorts of filesystem trouble you describe and in fact the 
	other people in the company have never had such problems.

>I can hardly stay calm and not start to flame around what I think of a
>computer system that is so #*g?*% that it can ruin a harddisk.  And no,
>there were no vibrations that could have caused a head crash, the system is
>rock-steady on my desk - and the drive never ever showed the slightest sign
>of a problem before.

	I would suggest that rather than getting on Usenet and venting, you
	call up whoever sold you the drive, controller, etc and work with
	them to resolve the problem.  Hard disk drives do fail on occasion,
	and perhaps you were sold a bad unit.  Check your software, consider
	that either the disk controller, machine or power supply might be
	marginal or bad.  If you find that the problem still eludes you,
	some peer review (from local user group, dealer, etc) might be
	useful - perhaps that can help you find the problem.

>Chris Brand

					Rick Spanbauer
					Ameristar