While you may be able to install some of our software from a normal Windows account, it is generally recommended that you install it while logged in as an administrator. This will help to avoid any permission issues you may encounter during installation.
This problem is the result of an incomplete download. The simple solution is to try downloading it again. See additional things to try listed under the next installation issue.
This error can occur if you have a “bad download”. When Setup is run, it checks the integrity of the Setup file itself. This error is generated if it is determined that the Setup file has missing or corrupted data. To fix the problem, you simply need to try downloading again.nFollowing the steps below should increase your chances of being successful on your next download attempt:n n
- n
- Delete the Setup file that contains the error.
- Empty your Temporary Internet Files folder. See the help that is included with your browser to see how to do this.
- Try downloading the file again.
- Try to refrain from downloading too many other things at the same time.
n
n
n
n
The system files required by the software were not installed correctly, are missing, or have become corrupted. Please re-install the software. This can sometimes occur after “un-installing” another application. When given the option, it is recommended to not allow an un-installer to remove DLL or OCX files from your ‘System’ folder.
The system files required by the software were not installed correctly, are missing, or have become corrupted. Please re-install the software. This can sometimes occur after “un-installing” another application. When given the option, it is recommended to not allow an un-installer to remove DLL or OCX files from your ‘System’ folder.
Automation errors have no specific cause, but are generally due to a driver problem or problem with DirectX. Try the following to fix this error:n
- n
- Be sure you are running the latest version of DirectX
- Click Start>Run then type dxdiag into the box and click OK. Once this app starts, click on each tab at the top of the window to examine each part of DirectX. At the bottom of the window for each tab, you will see a list of problems found (if any). Fixing any problems listed in this app is a good place to start! Often the errors listed can be fixed by doing the next suggestion.
- Be sure you are using the latest drivers for your sound and graphics cards. You can usually find driver updates by going to the website of the company who makes the card (or sometimes the company who makes the processor that the card uses). If you are unsure of their website, try doing a search on the name of your card.
n
n
n
This is more likely to occur in a newer operating system (such as Vista or 7). The problem is a missing CODEC and can usually be fixed by installing the Intel Indio CODEC.n Click here to download an installer. You may need to restart your computer after installation.
No. All of my software and installers are created to ensure that no uninstalling is necessary in order to upgrade from an older version or demo. If for some reason there is a circumstance where uninstalling a previous version IS necessary, it will be made clear to everyone.
Occurs in a game I downloaded:nPlease ensure that the game was unzipped properly. Games created with InterAx have sub-folders within the main (root) folder. This sub-folder information is stored in the zip file. After unzipping, if the game’s main (root) folder contains many files and has no sub-folders in it, then the following will solve your problem: In WinZip, be sure that the “Use folder names” option is checked before you unzip the file. This option is visible in the window that appears after you click on the ‘Extract’ button. When unzipped properly, there should be a “Resource” folder under the game’s main folder. Within the “Resource” folder, there should be two more folders: “Gfx” and “MMedia”. This error occurs when either the Editor or Player tries to access a file in one of these sub-folders, but it doesn’t exist.n nOccurs in a new project I created:n If you receive this error while running a new project you created in the Player, the most likely cause is that no image was chosen for Scene 1’s ‘Scene Image’ property.
This error occurs if the InterAx code get’s stuck in an infinite loop, and is the result of a flag problem. The problem occurs if a flag change causes one or more other flag changes which comes back to a previous flag change in that series of flag changes. Sounds a bit confusing, yes. Here is a basic example of what can cause this:nA responder is set to trigger when Flag 1 = 2. The responder is set to change flag 1 to 2 when triggered. When flag 1 = 2, the responder takes action. When the action calls for changing flag 1 to 2, the responder is triggered again. This repeats itself until the error occurs.nNote that the above example is basic, in that the problem lies solely in one object. Many times the problem is the result of several flag changes in several objects that ultimately come back to a previous flag change in that series of flag changes. The flag changes could be something like: Flag 1 = 3, which changes Flag 10 to 12. This causes Flag 17 to change to 8, which changes Flag 1 to 3 (note that we are back to the beginning of the series of flag changes).nThe best way to figure out the cause is to:n
- n
- Keep the ‘Debugging/Notify Window’ turned on, which lists all flag changes as the game is played.
- Examine the properties of all objects in the scene in which the error occurs. Pay close attention to any flag properties (setting or checking of flags), and look for a situation that can cause a looping condition.
- If you can’t find the problem just by looking at the properties, go through each property with a flag and UN-CHECK the governing checkbox, thus disabling the flag check or change. Do this for all flag checks or changes in the scene except for one. Run the game and check for errors. If none occur, go back to the editor and one by one, re-enable the flag properties until the error occurs. This should at least narrow the problem down to a particular flag.
n
n
n
nIn versions 3.1 and higher of the InterAx Player, this error will have a better description and hopefully make it clearer as to exactly which flag caused it.