Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!newsfeed.internetmci.com!solaris.cc.vt.edu!csugrad.cs.vt.edu!csugrad.cs.vt.edu!not-for-mail From: cremeans@csugrad.cs.vt.edu (Lee Cremeans) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: CMD 640 flawed chip Date: 16 Feb 1996 18:17:35 -0500 Organization: Virginia Tech Computer Science Dept, Blacksburg, VA Lines: 21 Message-ID: <4g33af$lk5@csugrad.cs.vt.edu> References: <4g1d5v$21k@fu-berlin.de> NNTP-Posting-Host: csugrad.cs.vt.edu X-Newsreader: TIN [version 1.2 PL2] Axel Thimm (axl@zedat.fu-berlin.de) wrote: : Hello, : my PC is the proud home of a flawed CMD640-chip. Until now I was working : under DOS, where the buggy chip is not doing much harm (no : multitasking), but I would like to install FreeBSD, and it will do some : harm there, I think. : I read about a way for Linux (turning off multiblock requests?), that : turned the flaws off. It was some line in a startup file (please look : away from my ignorance). : Is there a similar way for FreeBSD? FreeBSD (2.0.5 at least) defaults to not using 32-bit access or multi-block mode. If you use the generic kernel settings, you should be fine. Lee C. at school -- ***********http://csugrad.cs.vt.edu/~cremeans***** *Lee Cremeans * hcremean@vt.edu *CS major--Virginia Tech * cremeans@csugrad.cs.vt.edu (preferred) ***********TeamOS/2--FreeBSD--UNIX--Macintosh*****