H o m e  |  F e a t u r e   D e t a i l s  |  S c r e e n s h o t s D o w n l o a d s  |  S u p p o r t

 
[Click Here] to email the author for suggestions or to report a bug or issue.

Minimum System Requirements:

Celeron 566Mhz or higher (Pentium 4 Recommended)
Windows 2000 or higher (Window XP Recommended)
16 Bit Sound Card or higher (32 bit recommended)
Requires Windows Media Player 9.0 or higher installed
Video card capable of decoding DVD and DVD CD reader for using the DVD Module (no 3rd party player required)
*Note-> For Split Screen Mode a 2nd Video Card is required
with Windows XP running Windows Extended Desktop.


Known Issues:

These issues are not bugs. They are issues that the author of this program has either run into in his own experience or has foreseen to be potential irresolvable problems.

1. Issue: Screen appears to be scrambled and pictures and center logo are not lining up
Description: This occurs when the DPI is set to Large Size 120 dpi.
Resolution: Open display properties and click on the settings tab. Click on the advanced button, click on the general tab, change the dpi back to the default of Normal Size (96pdi). Apply the changes and restart the program.

2. Issue: User gets a blank screen after clicking on a rom file in the emulator module.
Description: The program is not installed to the default path of C:\Program Files\Mobile Impact
Resolution: Uninstall the program, then reinstall it to the default path C:\Program Files\Mobile Impact. The program is hard coded to look in this path for the emulator programs.

3. Issue: iGuidance not embedding properly
Description: with iGuidance installed and selected in the settings, when starting the program and opening the GPS module, iGuidance shows the warning dialog to where the user has to click ok, or iGuidance does not embed.
Resolution: This is caused by a program running in the background, often it is a touch screen monitoring program or this is also caused by the Logitech webcam and scanner software. Uninstall this software or remove any unnecessary programs from starting up.

4. Issue: Visualizations not going to full screen
Description: When user clicks on the visualization window in the media player module, the visualization either goes to full screen and then back to regular automatically or it does nothing. This is caused by the right version of Windows Media Player being missing.
Resolution: Install Windows Media Player, version 10 from Microsoft.com

5. Tview Monitor conflict
Issue: Conflict with Tview touch-screen monitor;
Description: Touchkit software will not allow media player visualizations to run full screen.
When user touches the visualization box it goes to a full black screen, then goes back to the normal video screen.
Resolution: Remove the Touch Monitor from startup.

6. Runtime Error 481 - Invalid Picture
Issue: Error message when starting program.
Description: When starting the software, the user receives a Runtime Error 481 - Invalid Picture.
This is caused by the skin directory being moved, changed or deleted without a new skin directory being selected in the skin chooser, or by an entry in the config.ini file under the skins section to be either removed, or the config.ini file is missing completely.
Resolution: Open the config.ini file in notepad or other text editor and under the [Skin] section of the file make it show the following: SKINPATH=Default. If the config.ini file is missing, then reinstall the program.

7. Emulator Settings
Issue: When the user clicks on any of the file menus and clicks on an option or setting, the Nintendo 64 emulator locks up and the only way to close it, is to use the Mobile Impact mini menu bar.
Description: When the user starts the Nintendo 64 module from within Mobile Impact and tries to configure any of the plug-ins or set the rom home directory by clicking on any of the file menu items, it seems like the program locks up. The design of Mobile Impact doesn't allow the file menu items to be selected.
Resolution: Close Mobile Impact and start the Nintendo 64 emulator on its own and then configure all of the settings.

8. Issue: Runtime Error - flash.ocx missing
Description: The user gets this error when starting the program and it shows a blank white box where the logo should be.
Resolution: This is caused by Flash Player not being installed or flash player is damaged. Uninstall flash player, manually delete any flash.ocx files found in C:\Windows\System32,. Go to Adobe.com and download and install a fresh copy of Flash Player.

9. Issue: Super Nintendo emulator playing a very small screen
Description: When the user selects a super nintendo rom, the program shows a small window in the middle of the screen and the game shows very small. With the small window showing, Click on the show menus button, then select Options, then Display configuration from the file menu. Place a check on stretch image, click Ok.