On Tuesday 23 October 2001 21:57, you wrote:
At a theoretical level, Linux can map bad blocks of memory out of the way and use good blocks. I remember reading about a set of kernel patches that were written by someone who was exploring the idea of selling 'faulty' RAM (which is a lot cheaper) and mapping out the bad bits.
Since RAM has come down in price so much over the last 2 years, I suspect that this idea has been dropped.
Richard
I'm thinking that, as Rick van Rein's site ( http://home.zonnet.nl/vanrein/badram/ ) states, memtest would let a person use RAM that became faulty due to manufacturer defects AND damaged due to static discharge. The average linux guy can use this to actually make the bad RAM effective rather than spend more money on functional RAM. For instance, about 2 years ago, I bought RAM over the internet and when I received it and put it in my machine it kept faulting. The retailer wouldn't accept a return so I was stuck with bad RAM that I hadn't even had the chance to use! Using memtest, I can now map out the bad parts of the RAM and get it to work with my machine. This is cool but I'm thinking it will work only with Linux unless the bad parts can be locked out physically (can this be done?) so it can work with Windows or other OSs. The thing I don't understand about the above site is that the author is trying to sell an idea: selling faulty' RAM (which is a lot cheaper) and mapping out the bad bits. That's not bad in itself, but how is he going to map out bad bits of RAM to work with a system other than Linux? By what I read, the mapping will be done with Linux-specific software. What if this idea of his is implemented and someone with a dualboot Linux/W98 system wants to use this "cheaper" RAM? They probably won't be able to. The RAM would have to be labeled "Linux compatible only" OR his memory mapping software would have to be ported to Windows. He stated that he's not going to attempt it because Windows isn't open-source and isn't an efficient OS to begin with. I'm no programmer. I've attempted very rudimentary coding and that $hit is hard. I'll give him props for his cool ideas and his memory mapping. He's entitled to his own opinions and can do whatever he likes with whatever OS he wants. I liked his info on his site but once I read about his Windows philosophy, I pretty much stopped reading. There's no need to adopt the same attitude as Microsoft's lackeys in regards to programming. The thing I hate most of the Linux movement is that most are so into this open-source kick that they crap on other OSs for the simple fact that closed-source programming is more difficult. The same thing happened with winmodems and the Linux community and only now are you seeing progress with winmodems...not because hardware developers are finally releasing the code bue because some programmers are putting their spiteful attitudes aside. I've lost count of the number of 'net conversations that state, "my modem won't work with Linux/you have a winmodem -- get a REAL modem." It's funny...hackers will hack almost anything that's hackable but a winmodem, for simple philosophical reasons. Almost everything about Linux was hacked by Unix/Linux programmers...if everyone one of them had the same attitude that many have about winmodems, there would be no Linux (or, Linux would be a real POS). Sure, Linux is open-source but adopting bad attitudes like the above amounts to closed source...it limits the Linux OS as a whole. I'm just putting out my thoughts on the memory test issue and my take on the Linux movement. Keep in mind, all of what you just read is meant to be related. I'm probably missing some things that others, with their vast knowledge of coding and experience with Linux, will want to add. The above isn't meant as a flame. I'm just putting out my opinion and willing to see other points-of-view. Regards. -- Ron Sinclair @ http://www.wigglit.com