On Mon June 18 2007 13:40:19 Michael Schwendt wrote: > Running w2k successfully on the same machine is no sufficient > test to rule out that the RAM is bad. You would not be the > first person to run into that trap. If it isn't RPM that is > hit hard by hardware instability, it's a different > application that creates a memory usage/load pattern which > exposes the hardware problems. GCC, for example. Many users > have seen spontaneous segmentation faults and believed them to > be bugs in the compiler, even when subsequent runs of Make > continued for a while. > > A lot of problems with RPM are due to hardware problems or > attempts at disturbing RPM at run-time. OK - point taken - I'll run memtest for a few hours after I get home tonight, and see if it picks up anything -- Claude Jones Brunswick, MD, USA
