Path: utzoo!attcan!uunet!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga
Subject: Re: ST157N problems
Keywords: Hard Disk
Message-ID: <5624@cbmvax.UUCP>
Date: 4 Jan 89 17:15:41 GMT
References: <8901022054.AA08155@jade.berkeley.edu> <407@oetl1.oetl.UUCP>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 30

In article <407@oetl1.oetl.UUCP> king@oetl.UUCP (Steve King) writes:
>In article <8901022054.AA08155@jade.berkeley.edu> PHILIP@VTVM1.BITNET (Fred Senese) writes:
>>After a few months of fairly trouble-free operation I am having
>>trouble with my hard drive.
>>   2) The drive will run for several hours or days but eventually gives
>>lots of read-write errors (and executables on the drive aren't recognized
>>as object modules.)  A file that is corrupt one day is OK the next.  

	One possibility is heat.  The drive may be fine initially, but after
heavy use or a long time on may overheat.  Or the drive may be failing.  Or it
may have trouble completing seeks.

>		   Amiga 1000
>		   Pal Jr. with ST506 DMA cntlr. 1.0 M RAM
>		   Seagate ST251-1 40M drive /DH0: FFS, 20K Stack, LCyl 0,
>		   HCyl 818
>		   WB1.3
>
>Pal Jr. came with a low level disk test program (plus sketchy doc). At least
>I can block out the crashes.  System worked fast & well under 1.2.  I first
>backed up hd with MRbackup, then configured for 1.3.

	First, I'd recommend trying the latest A2090 driver (34.4) which has
been posted to many places, I think including here.  The Pal hardware is
essentially the same as the 2090.  Double check your mountlist, especially
stack and dostype.  You could try a maxtransfer of 512 (the _old_ driver that
came with the pal may not like large transfers.)

-- 
Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup