You *could* use the all_runs dataset, but it is better to use the pb06(?) *.scale datasets, so that 3dDeconvolve knows there are 2 runs and where the run breaks are. Look at the proc script that was currently run, and start with that 3dDeconolve command.
Or generate a new proc script locally and do not even run it, just get the 3dDeconvolve command.
And if that works, you could go with the -write_3dD_script/_prefix options, too.
- rick