Thanks for the incredibly useful post!. "Many Maple users have a preference of user interface" may be a bit of an understatement. The fact that startup time of the java interface is more than an order of magnitude longer than the classic worksheet makes me wonder why maplesoft is pushing it so hard. The post would however have been slightly more useful if you gave some clue as to what all those mystery libraries were and why either the 32 or 64 bit versions were linked in each case. This might have enabled me to do the same thing for maple 11 in a slightly more intelligent way. The problem of course is that maple 11 has different kernel libraries and so care must be taken to ensure your faux architecture directory bin.X86_64_LINUX_CLASSIC has all the necessary goods. Here's what I did: 1. Create an empty directory in my maple11 root subsequently referred to as $MAPLE_ROOT: # mkdir $MAPLE_ROOT/bin.X86_64_LINUX_CLASSIC 2. Link in everything from the $MAPLE_ROOT/bin.X86_64_LINUX directory: # cd $MAPLE_ROOT/bin.X86_64_LINUX_CLASSIC # ls ../bin.X86_64_LINUX/ | xargs -i ln -s ../bin.X86_64_LINUX/{} 3. Now use the above package to determine which 32bit libraries are needed. Download X86_64_LINUX_CLASSIC.tgz and change to the directory I downloaded it to. 4. # tar xvzf 1_X86_64_LINUX_CLASSIC.tgz && cd bin.X86_64_LINUX_CLASSIC/ 3. Create a list of 32 bit libraries in a file in the classic architecture directory: # ls -l | grep IBM > $MAPLE_ROOT/bin.X86_64_LINUX_CLASSIC/32libs 4. Now use that list to link in the necessary libraries from your 32 bit install clobbering (with the -f switch to ln) the 64 bit links as necessary: # cd $MAPLE_ROOT/bin.X86_64_LINUX_CLASSIC/ # cat 32libs | xargs -i ln -sf {} 5. Modify $MAPLE_ROOT/bin/maple script as described above