Thank. That helps enormous. One question though. Why does the memory check program from SuSe does not give an error indication. One thing I saw is that the 76K of the 128 MB memory does not show up as tested. Only from 76K to 128M seem to be tested. Would this be the indication of a malfunction or is the first 76K used for something else? Memory both from the machine and myself is a problem ;-). JF>malloc() is the memory allocator. In a C program, JF>malloc() resides in libc JF>and allocates memory for the application. This JF>particular problem appears JF>to be caused by an I/O error while loading a critical JF>program (possibly JF>/sbin/init). JF>IMHO, your system apprears to have a hardware problem JF>of some sort. JF>I would suggest that you remove your memory (make sure JF>you are grounded), JF>and insert them in a different order. Also, if your JF>memories are of JF>different types the system can fail under some JF>circumstances. In practice, JF>it is best that all memories in a system are of the JF>same type, speed rating JF>and brand (although not imperative). Also, if you are JF>using 133Mhz, try JF>slowing that down to 100 in your bios. JF>Lastly, but not likely, you could possibly have a JF>problem with your disk. JF>Remember virtual memory. Physical memory is broken up JF>into pages. It is JF>possible that there was some swapping going on during JF>the load, and there JF>is some corruption in the swap area. JF>On 30 Aug 2002 at 19:36, Constant Brouerius van Nidek JF>wrote: JF>> _loaderFileToMem() malloc failed JF>> JF>> and some lines lower JF>> JF>> fatal IO error 104 JF>> -- " Every little BYTE helps " NTReader v0.36w(P)/Beta (Registered) in conjunction with Net-Tamer.