.... I work for a small engineering services company. We are currently using a LLNL Finite element code called Dyna3D to do some analyses on behalf of a client. We have a 1000 MHz PIII at work, running SuSE 8.2, all stock right off the CDROM. We compile the code under the Portland Group FORTRAN 77 compiler, pgf77, since all (!!!!) of the other compilers we have tried either won't compile the code or produce an executable which generates wrong answers, seg faults, or both. Last night I brought home a statically linked version of the Dyna3D executable & some cases to run on my 2400 MHz P4, also running SuSE 8.2, right off the CDROM. I set up a directory to work in & kicked off 10 cases, which should have taken about 30-35 hours to run. This A.M., all were done. 8 of the 10 finished with random seg faults, 1 successfully completed, & 1 had a program error termination (crushed elements, operator error ;-)). I am puzzled by the random seg faults. The P4 has a kernel called '2.4.20-64GB-SMP', while the PIII at work (& mine at home) have one called '2.4.20-4GB'. All 3 installs of SuSE 8.2 (my 933 MHz PIII, the 1000 MHz PIII at work, & my 2400 MHz P4 at home) are completely default, plain vanilla installs right off the CDROM, no recompiled kernels, no shenanighans. The P4 is NOT a multi-processor machine, just 1 CPU. Are there any known problems with this M.O. (compile code on PIII, run it on P4) under SuSE 8.2 ? Is there some problem with using the '...SMP' kernel on a single CPU machine (everything else seems to work fabulously) ? If so, why did the installer install the SMP kernel on my single CPU box ? I can provide any other info anyone wants (except the code, export restricted ;-)). Please advise, & thanks in advance for your time. William A. Mahaffey III Huntsville, Al. USA