CompuServe Messages

Mason: I'm in **my** biggest project and I get similar results, except that I get an apparrantly bogus memory parity error on frame 2 or 3. Usually, if I hide some of the more complex (but not currently visible) parts of the model, it usually renders OK, but it will sometimes go 24 hours or more before it flakes out. (My swap files gets to about 26-28 MB before it fails.) This is only on my 32MB 486DX2-50 machine at work. Neither my 32MB 486DX2-66 at home or the 16MB P5-66 seem to do it, even on the same model. One thing to be careful of – if your system crashes often you should run CHKDSK after you bring it back up. I had my rendering time go from 18 min per frame to 3 and a half hours per frame on my current model. It turned out that I had 211MB of lost clusters on the swap disk! Every time it flamed out I would lose the 30MB used by the swap file. Chris – Chris Johnston, Written 09-Mar-1995 @ 21:57:09 Using: Windows NavCIS PRO 1.5