Thanks Randall,
Based on your suggestions I tried a few things - here are the results. hzslice is the name of my script. Starting with a command line "dx -processors 2 -memory 1024 -script" Then "dx>include hzslice" Everything works fine. Starting with a command line "dx -processors 1 -memory 1024 -script hzslice" Everything works fine. Starting with a command line "dx -processors 2 -memory 1024 -script hzslice" It stops before executing the sequencer (found that by using the Describe module as suggested). I get exactly the same behaviour using the sample script "Sequencer" now that I have tried it. Go figure? Runs much quicker with two processor, so if anyone know a fix I'd appreciate it. If not, is this the sought of thing I should stick in a bug report? Also, I have never had a problem with my Bus! Cheers, Cameron > I don't know for sure what's wrong (haven't run your script yet), but > in looking at what you're doing, one possibility jumps to mind: > > On multiprocessor SGIs (Onyx, Octane), I've never had -processors > 1 > work with -script. Try -processors 1. I'd be interested if that > does/doesn't work around your problem. > > Also, try putting Describe modules in your dataflow so you can see > where it's quitting on you. > > Randy > > P.S. Are you saying this works for you if you run it interactively, running > it by typing "include ..."? Unless I use -processors 1, when I "quit", I > see a Bus error.
