Digital Workshop

I created a large accessible multimedia show for school (students with severe or profound learning difficulties).
Tested it out last nigtht, played very nicely on this computer (HP pavilion zd7000) published it as a stand alone publication, took it into school this morning, tried it on a school computer (of moderate spec) and some of the transtions were decidedly dodgy, some didn't show at all and some of the timing was out.

I know that saving as a standalone publication means alot of work for some of the glorified textprocessors that we still have in schoool (although I've done my best to get them up to some kind of multimedia spec).
I also notice that some transitions work better than others.

So what I'm asking is if anyone knows the relative processing demands of some of the commmon transitions?
and which ones are definitely to be avoided and which ones should play on more basic systems.

I use sound in mp3 format, I have heard that wav sounds need less decoding and so put less strain on the processor (although the size of the publication will increase dramatically).
Do you think that would help?
What is the best way of optimising the picture files (which format ?).

Would it help if I specified in the publication properties that I was going to publish as a flash file (with a more limited set of transitions) and then at the last moment swap to Direct X?




If you want to look at the multimedia it's on the school website
url: http://atschool.eduweb.co.uk/meldreth/t ... edia2.html
called 'a selection of pirate music' half way down the page in the music in Opus section.
Accessible from mouse, keyboard, touchscreen, One or two direct switches or an intellikeys overlay board


Thanks
Richard Walter