Table of Contents
WHDLoad Advanced FAQs
What are the components of a WHDLoad install?
- WHDLoad - the tool itself. This is a command, which usually resides in the C directory.
- Slave - compiled 68000 assembler code. This has been written specifically for a certain game and can call functions provided by WHDLoad.
- Disk image/files - actual game files. Either one or more disk images (default filenames are disk.1, disk.2 etc.) or game files copied from the disks (in a 'data' dir).
- Icon - although not necessary, an icon is an easy way to call WHDLoad with a tooltype which will specify the slave.
- Installer - standard Workbench installer. Automates the process of setting the game up on the hard disk, ready to run.
- Readme - explains features of the install etc.
What is the difference between disk images and data files?
If the original game is non-DOS, then a complete dump of the disk will be used in the form of a disk image. If the game is DOS, then the files will be placed in a subdirectory, usually called 'data'. However, for some non-DOS disks, the patcher of the game will extract the files to hard disk, knowing that they are stored in a custom format on the original disk.
What is the process of installing and running a game with WHDLoad?
Make sure that the standard 'installer' tool - download it from: http://www.guildserver.co.uk/files/Installer44.10.zip
Decompress with unzip: unzip "Installer44.10.zip" Ram: and copy installer to the C: drawer/directory in sys: (your boot partition): Copy Ram:Installer C:
Download the actual WHDLoad archive from the homepage. Extract the LZX/LHA archive and run the installer, which will place all the WHDLoad files in relevant directories.
Download the specific patch for your game from the homepage and extract the LHA archive. Run the patch installer.
Follow the on-screen instructions, specify where the game is to be installed and insert the original disks when prompted.
Navigate to the directory when you installed the game and double-click the icon to run the game.
Why are the game files not available on the WHDLoad website?
Putting copyrighted games on the website would endanger WHDLoad itself. It is primarily designed for use by owners of original games.
Can I use cracked games with WHDLoad?
Many crack images will work, although it is not guaranteed. Patchers like Codetapper design their installs to work with cracks sometimes.
Why don't the WHDLoad patchers fix the games which don't work with emulators?
WHDLoad is designed to work on real Amigas and the patchers don't have time to work around emulator bugs, which may be fixed in a future emulator version. Often the compatibility of game with an emulator is improved, due to the fixing of non-standard features of the game or the removal of a badly-coded disk routine.
What is JST?
JST is a similar system to WHDLoad, but has now been discontinued (see the old homepage at: http://jffabre.free.fr/amiga/patches.html). The author, Jean-François Fabre now writes WHDLoad patches.
I got an error 'DOS-Error #205 (object not found) on reading "devs:kickstarts/kick34005.a500"' when running a game under WHDLoad.
The specific game uses KickEmu and requires an A500 kickstart image and an associated .rtb file. The kickstart image must be located in the directory "Devs:Kickstarts" and must be named "kick34005.A500". The image can be extracted from an A500 with tools like "GrabKick" or similar which can be found on Aminet. If the image is the wrong version or altered in any way, WHDLoad will quit with an appropriate error message.
Additionally the file "kick34005.A500.RTB" must be installed in the same directory as the kickstart image. It can be found in the archive "http://www.aminet.net/util/boot/skick346.lha" on Aminet.
I got an error 'DOS-Error #205 (object not found) on reading "devs:kickstart/kick40068.a1200"' when running a game under WHDLoad.
The specific game uses KickEmu and requires an A1200 kickstart image and an associated .rtb file. The kickstart image must be located in the directory "Devs:Kickstarts" and must be named "kick40068.A1200". The image can be extracted from an A1200 with tools like "GrabKick" or similar which can be found on Aminet. If the image is the wrong version or altered in any way, WHDLoad will quit with an appropriate error message.
Additionally the file "kick40068.A1200.RTB" must be installed in the same directory as the kickstart image. It can be found in the archive "http://www.aminet.net/util/boot/skick346.lha" on Aminet.
What is KickEmu?
Some games use a lot of operating system calls to the Amiga ROM, which can't be accessed directly within WHDLoad. A patcher can emulate the calls in the slave, or else use KickEmu and WHDLoad functions which allow access to a ROM image in FAST RAM (and therefore requires 512K more RAM to run the slave).
The game disk images are big. Can they be compressed?
Yes, install the user version of the tool XPK and compress the images (for example, using the MASH compression algorithm).
What is CAPS / SPS?
SPS - The Software Preservation Society - http://www.softpres.org/ (Previously known as CAPS - Classic Amiga Preservation Society - http://www.caps-project.org/) aims to rescue Amiga games in a different way than WHDLoad. SPS/CAPS dumps original disks for preservation as they are, including protection, while WHDLoad removes protection and aims to run the games off a hard disk.
How to make WHDload install with .IPF?
N.B you will need RawDIC 4.0 for this so, first make sure you have the latest version of Whdload installed and then download:
- TrackWarp from: http://www.whdload.de/whdload/TrackWarp14.lha
- ipflib_amigaos-m68k.lha from: http://www.softpres.org/?id=download
Copy capsimage.device to Devs:
Copy trackwarp.library to Libs:
Proceed as if you were going to install from disk.
When RawDIC appears and asks for disk 1, click the Select file button in the middle.
Select the first .IPF file.
Repeat the above operation if/when asked for the next disk. Done
Using "uae-configuration" and "Tool Types" or "whdload.prefs" to disable JIT in WinUAE
In WinUAE you may find that you have some timing and GFX problems when having JIT enabled. So to save you having to disable JIT each time you run a WHDLoad installed game, you can do this automatically via "uae-configuration" from WinUAE's Amiga programs folder and by adding two lines to "whdload.prefs" or "Tool Types" within Icon Information.
For more information please see: http://guide.abime.net/wb3.1/miscwhd.htm