Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!agate!usenet.ins.cwru.edu!po.CWRU.Edu!ptd2 From: ptd2@po.CWRU.Edu (Palmer T. Davis) Newsgroups: comp.unix.bsd Subject: Re: Gateway 2000 problems? Date: 12 Dec 1992 00:51:22 GMT Organization: Case Western Reserve University, Cleveland, OH (USA) Lines: 22 Message-ID: <1gbd2bINN6bh@usenet.INS.CWRU.Edu> References: <1992Dec11.215721.10579@usasoc.soc.mil> Reply-To: ptd2@po.CWRU.Edu (Palmer T. Davis) NNTP-Posting-Host: thor.ins.cwru.edu In a previous article, ted@usasoc.soc.mil (Ted Nolan) says: > >We happened to have a Gateway 2000 486DX-33 sitting in our lab, so I took >the dist-fs floppy from the bootables directory and tried it out: no >dice. I also tried the new dist-fs from the unofficial/terry/new-bootables >area on agate, but that didn't work either. I think the floppy is OK, because >I have tried it on another system here and it booted fine. We have a Gateway 486DX2-50 that I just brought 386bsd up on last night. The problem may be that you didn't turn off the memory caching; if it is enabled, the kernel panics. For what it's worth, the distribution I used was taken from gatekeeper.dec.com. >Does this mean I have to stop considering Gateway. . . ? You don't have to, but you should; Gateway's designs are relatively rude and annoying, and the only reason that I'm using ours is that it was assigned to me. Think of Gateway as the SCO of hardware vendors. 1/2 :-) -- Palmer T. Davis ___ <ptd2@po.cwru.edu> \X/ cthread. cthread_fork(). Fork, thread, fork!