I'm trying to evaluate which is the fastest method for generating thousands of files for my fractal animations. I've been playing with partobat, FA100, FAE, Batcher etc.. which generate long BAT files with call statments and also calling Fractint *.par files. I'm also comparing that method with Fractint's internal Autokey scripting feature. I'd like to hear opinions which method might work best for generating thousands of images without "slowing down".. Just for the record I'm running the Fractint and the batch files from within a Win98 Dos Box. Here's a typical line from one of my bat files: FRACTINT @e:\fract\par\5sp001.par/Step0 BATCH=Y I've noticed on the long runs there's been a gradual "slowing down" of the Fractint processing speed. Is that due to "memory leaks" caused by the constant loading and unloading of Fractint from within a Win98 DOS box? Are there any Fractint or Win98 Dos Box settings or tweaks that might solve that problem? Does either Fractint or command.com need EMS to run the batch files? If that problem can't be solved, I'm looking at using the Fractint Autokey scripting as an alternative. Say I were to run a similar Fractint Autokey file to generate thousands of images, using a long Fractint Autokey file, would Fractint's processing speed remain constant, or would there also be this phenomenon of Fractint "slowing down"? The idea is to use the Autokey script to instruct Fractint to load a *.par file, parse the pars and then generate and save images. It seems to work OK for the few files that I ran. Will it work OK if I try to run an Autokey script to generate say 4,000 images? Heres my sample autokey file: ;; CALCWAIT "2" CALCWAIT F6 CALCWAIT ;; 5sp001.par "5sp001.par" ENTER ;; steps.key ;; ;; step0 "step0" ENTER CALCWAIT "s" CALCWAIT ;; step1 "@" "step1" ENTER CALCWAIT "s" CALCWAIT ;; step2 "@" "step2" ENTER CALCWAIT "s" CALCWAIT