![]() ![]() Wine does not support Revelations copyprotection mechanism, you have to override it with a "crack". Be sure that you are in the same terminal where you sourced env.sh, if you closed it already source it again. Here are a few mirrors:Īgain, execute the. The next step is to patch Revelation to version 1.03. ![]() The setup will throw a few error messages at the end, but thats okay. Don't forget to 'source /opt/wine-revelation/env.sh' before calling the setup, you want to use the Revelation-patched Wine!ĭo the setup as you normally would. Mount the image and the second DVD somewhere(eg., ~/revelation/disk1 and ~/revelation/disk2), cd to disk1 and execute 'setup.exe' using Wine. It is /dev/hdX on many distributions, try /dev/hdc or /dev/hdd if you are not sure.ĭD does not show the progress, just wait a moment. So you have to create an image of at least one disk. Wine implements the eject feature for that, but it seems that it does not work well here. Revelation comes on 2 DVDs, so you have to switch the disk in the installation progress. I strongly recommend you to use a new WINEPREFIX for Revelation, see the Wiki for more details. This will only apply for the terminal you typed it in, so if you open a new terminal it will use your normal Wine there. You can now switch to the new Wine using 'source /opt/wine-revelation/env.sh'. Rename the file to 'env.sh', and copy it to /opt/wine-revelation, again as root.ħ. > export LD_LIBRARY_PATH=/opt/wine-revelation/lib:$LD_LIBRARY_PATH > export PATH=/opt/wine-revelation/bin:$PATH Install Wine using 'make prefix=/opt/wine-revelation install' as root.Ħ. configure -prefix=/opt/wine-revelation -with-xĤ. Configure Wine with '-prefix=/opt/wine-revelation', for example: Unpack the Wine tarball, copy the patch in the new Wine folder and apply it using 'patch -p1 -i mystIVstartupfix.patch'ģ. Download the Wine 1.1.1 tarball from here: and the MystIV patch from here: Ģ. If you are able to, please use the package build process for your distribution.+++ġ. +++NOTE: This way, your package manager will know nothing about the new Wine. If you use another distribution, this will be generic instructions that should work on every distribution. It will be installed in /opt/wine-revelation. It will do everything for you, so you just need to wait some time until Wine is compiled. If you use ArchLinux and have 'yaourt' installed, it is as easy as just typing "yaourt -S wine-revelation". The way to go is to place the patched Wine somewhere in /opt, so it will not affect other applications. Revelation will need a little patch to Wine, but it seems that this patcÂh could affect other applications in a bad way. The installation process of Myst IV - Revelation is a bit tricky. ![]() STEP 1: Install a patched version of Wine Ubuntu 6.10 "Edgy" i386 (+ variants like Kubuntu) Ubuntu 7.04 "Feisty" i386 (+ variants like Kubuntu) Ubuntu 8.04 "Hardy" amd64 (+ variants like Kubuntu) Ubuntu 8.04 "Hardy" i386 (+ variants like Kubuntu) Ubuntu 9.04 "Jaunty" amd64 (+ variants like Kubuntu) Ubuntu 7.10 "Gutsy" i386 (+ variants like Kubuntu) Ubuntu 11.04 "Natty" i386 (+ variants like Kubuntu) If you have more than one device you can try to google the Vendor ID and the Product ID (this is the hexdecimal number after "PID_") to narrow it down to the exact device.Ubuntu 12.10 "Quantal" amd64 (+ variants like Kubuntu) If it doesn't, you might have another HID device causing the issue.ī. If you have one product by that manufacture, unplug it and see if Myst IV runs. Google the Vendor ID to see what's causing the issue. This is called the Vendor ID (who made the product).Ĩ. Right after the "VID_" there will be 4 hexdecimal characters (0-9, A-F). You'll see a list starting with "HID\VID_."ħ. Open the Driver's Properties and go to the "Details" tab.ĥ. ![]() Repeat until you find the device that crashes Myst IV.Ĥ. If it still crashes, re-enable that device and disable the next oneģ. Go to "Device Manager" and open "Human Interface Devices."Ģ.ĝisable the first "HID-compliant_"and start Myst IV. I have a Corsair VOID Wireless Headset that caused the issue.ġ. UNPLUG IT! A few people on on GOG (which this version is based on) have found that a wireless headset causes the CTD. These are instructions that someone posted that worked for resolving the issue for a few people The newer the operating system the further away it is from the original system it was built to run on.Ī few people had an issue related to audio on Myst IV that caused crashing. The game was not tested to run on Windows 11, it is likely to cause more trouble for Myst IV. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |