. Someone asked, so... The fractint PAR for the buddhabrot is: Buddhabrot { reset=2004 type=mandelcloud passes=1 center-mag=-0.300522/-4.44089e-016/0.8079007/1/-90/-1.23373533611470521e-014 params=751 float=y maxiter=751 fillcolor=0 inside=0 outside=summ sound=off colors=200A84<20>oiPqjQslR<3>zsW<25>CB6A95874653442220000400<23>o00q00s00<3>z00<25>C00A00800<3>000<2>554776998BBACCB<18>\ iihjjillk<3>ssr<25>BBA998776<2>221000011<24>0bn0cp0er<3>0ky<25>09B089067<2>021000210<2>863 } The colors were saved out as a map, and referenced in sstools.ini. Thus it is simpler: Buddhabrot_ { reset=2004 type=mandelcloud passes=1 center-mag=-0.300522/-4.44089e-016/0.8079007/1/-90/-1.23373533611470521e-014 params=751 float=y maxiter=751 fillcolor=0 inside=0 outside=summ sound=off } A BASIC script prints out the whole thing as a literal string, but the params and maxiter numbers are variables; a simple loop varies them from 2->751 and prints out all the PAR entries to one file, along with a BAT file which runs fractint and references the entries sequentially. XFRACTINT? I tried it a few years ago when I was investigating linux. It didn't seem to be as fast or as versatile as DOS fractint so I shelved it. I'm still waiting for 64 bit Fractint ... In the mean time, I've finally got ultrafractal to read some of my fractint pars, like for the universe sequences, but I have to hack them up a bit. Maybe I can re-render the U3 viddie in 32 bit color if I can get it right. But I don't know if current systems can be run 24/7/365; they are not as robust as older systems and tend to overheat. I can fix that, but the rendering time should be much quicker since a windows app can take advantage of the full proc capabilities and 32 bit memory addressing, but they actually render slower than fractint. Don't know why that is ... JoTz .