I'm glad it might be usefull to someone (I have used sucessfuly it in the past). Have a look at (googling around will lead you here): http://badmem.sourceforge.net/docu/BadMEM-HOWTO.html
It does not waste resources as what it does os just install itself as a resident kernel module (not swapable) into those specific locations, so it locks them but will never be used. The only thing to accomplish is to try to put the good module(s) first to guarantee that lilo, the loader, etc get executed properly just upto the "module" load. El lun, 06-10-2003 a las 19:42, Lawson, Jim escribi�: > I agree it really was great info. > > -----Original Message----- > From: Wolfgang Bornath [mailto:[EMAIL PROTECTED] > Sent: Monday, October 06, 2003 1:36 PM > To: [EMAIL PROTECTED] > Subject: Re: [expert] Do these messages explain why my system hung? > > > diego schrieb am 06 Oct 2003 19:02:06 +0200: > > > Hummmm... and if that's the case (a module is corrupted), you can have > > a look at badmem: > > it will lock bytes reported as wrong by memtest86 so you would > > be able to still spend 0$ and use much of that module ;-)) > > Now this IS a great advice! I have a module here in my desk that memtest > reported has some bad bytes (only a few). If I could get that to work > with locked bad bytes it would increase my desktop's memory up to > 1GByte! > > If this works then this advice may be one of the most important advices > I received this year. > > wobo > > > ---- > > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com -- Diego Dominguez __/\__ | | Andalucia / \ Spain \ / |__ __| \/
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
