A Series of Tubes

I have an intel-based mac, and I am trying to install Myst V on it. Even though the game is Mac compatible, it was never made to run on mac Intel chips, and thus the problems. Ubisoft released a patch, but it really does not work. I have tried almost every method suggested to me so far, and the most useful have been the new patcher, and the following hack. The patcher does basically all this for you, but this is an explaination of it.
(Note- I did not figure this out. It is taken from Luis Carlson’s Technoblog. The specific post can be found here. I have modified it a bit to work better, but other than that it’s all his)

The following information is not to be used by anyone because the EULA might prevent you from doing so. It is for informational purposes only and mainly takes place on the command line within the Terminal.

cd ~
mkdir myst5 && cd myst5
jar xfv /Volumes/Myst\ V\ EOA/setup.jar
cp -r /Volumes/Myst\ V\ EOA/support .

at this point, type ls and look for a long string of letters and numbers. copy this.

cp -r /Volumes/Myst\ V\ EOA/setup/INSERT LONG STRING HERE/md5 INSERT LONG STRING HERE, TOO
curl -O http://www.kpdus.com/jad/macosx/jadap158.zip
unzip jadap158.zip
./jad com/installshield/wizard/service/file/PureJavaFileServiceImpl.class
open -t PureJavaFileServiceImpl.jad

Look for public String[] getPartitionNames(). This is the place that caused the pesky error. What happened is that Intel Macs currently are missing a Java library that will provide the installer with a list of partitions for the computer. All we have to do is hard code that list and we are home free. Change it to look as follows.

public String[] getPartitionNames()
throws ServiceException
{
String as[] = new String[2];
as[0] = “/”;
as[1] = “/Volumes/Myst V EOA”;
return as;
}

Save and close the file. Back to the command line.

mv PureJavaFileServiceImpl.ja{d,va}
javac PureJavaFileServiceImpl.java
cp PureJavaFileServiceImpl.class com/installshield/wizard/service/file/
java run

Now, in the event that it creates a binary which doesn’t work, uninstall myst v (leave the /myst5 directory you made), and just run the installer from the disc. Because we changed something in Java, it should now work correctly. 🙂 Happy Myst’ing!

Eh, screw that. Nevermind, as the above obviously does not work.