Return to BSD News archive
Xref: sserve comp.sys.ibm.pc.hardware.misc:17691 comp.os.linux.hardware:1659 comp.os.386bsd.misc:5190 comp.os.os2.misc:123924 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!constellation!bubba.ucc.okstate.edu!news.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!pipex!uunet!utcsri!newsflash.concordia.ca!ishmael From: ishmael@cs.concordia.ca (Ian Ishmael) Newsgroups: io.general,io.computers,comp.sys.ibm.pc.hardware.misc,alt.comp.periphs.mainboard.asus,comp.os.linux.hardware,comp.os.386bsd.misc,comp.os.os2.misc Subject: Re: List of recommended hardware components Date: 31 Jan 1995 20:33:53 GMT Organization: Computer Science, Concordia University, Montreal, Quebec Lines: 29 Message-ID: <3gm6rh$moc@newsflash.concordia.ca> References: <3g890k$cbl@ionews.io.org> <3gjhe1$ced@pentagon.io.com> NNTP-Posting-Host: sunset.cs.concordia.ca NNTP-Posting-User: 11030 In article <3gjhe1$ced@pentagon.io.com>, Der Gestiefelte Kater <janos@pentagon.io.com> wrote: >In article <3g890k$cbl@ionews.io.org>, Brian Tao <taob@io.org> wrote: >> >> I didn't choose the Seagate for any particular reason... what is >>bought in the end could just as well be a Quantum or Micropolis or >>Fujitsu drive. Any names to stay away from in the 500-meg range? >> >Yes : Seagate. I had a Seagate drive that started to have bit rot right >after when the warranty (get this : 12 months) has run out. I've >talked to people with similar problems. Stay away from Seagate. > What about Conner?I've been offered a Conner CFS540A at a pretty good price.Is it a EIDE drive?How much cache is on it? Also, my current hard drive crashed last week,and I had it replaced by the store that I bought my system from.Since then, writing to my hard drive has been very slow.For instance, when playing DOOM the screen freezes and the little blue diskette shows up in the bottom right hand corner, indicating that it is reading or writing from/to my hard drive.Before I had my drive replaced, thisnever happened.Its as though Doom didn't load enough information into RAM when it first loaded the mission.This slowness is also noticable when I'm in OS/2 using the editor.In this case the autosave is very slow(normally it would save the file in the background thus allowing me to continue working without any in -terruption).Does anyone have any idea what might be causing this problem? Any help would be much appreciated. Thanks, ~~Ian