Jewels Support

This section provides product support documentation for the Jewels game.

First Steps

If you haven't already, please read the section on General Product Support, which outlines the steps you should do first before you try to diagnose the problem you are having.

Installation Notes

Update! - July 21, 2002 - Be sure you download the proper version of the application for the system you are trying to download for. The JewelsCE version is for PocketPC devices, while the JewelsWin32 versions are for standard windows desktops (Win98,2000,ME,NT).

Update! - June 6, 2002 - There have been many questions regarding how to properly register the game after it has been purchased. we've created a separate page discussing How to Register Jewels Properly. Click here to read it.

Please read the installation read me file that is included with the product.

Also, be sure that you try to install the proper version for your handheld! There are several different handheld devices available, each with their own microprocessors. Be sure you are trying to install the right one...

Revision History

Nov 08, 2003 - Version 1.04 -

- Released 1.04 for PocketPC devices. Standard Win32 Desktop version is NOT included and remains at version 1.03 at this time.
- Improved performance of the game on slower PocketPC devices.
- No longer overwrite the registration file with the temporary file upon installation/upgrade.
- Fixed performance bug on iPaq 38xx models, and added additional device compatibility (notably Casio models).
- Contains build 1285.

Feb 17, 2003 - Version 1.03 -

- Released 1.03 for PocketPC and Standard Win32 Desktops. Removed license agreement from application and placed it into installation package.
- Contains build 1236.

July 21, 2002 - Version 1.02 -

- Released 1.02 for PocketPC and Standard Win32 Desktops.
- Contains build 1225.

March 5, 2002 - Version 1.01 -

- Released version 1.01 which fixes installation issues and included high-quality sound PAK as standard. Also fixes other minor bugs.
- Contains Build 1100 for ARM processors.

January 25, 2002 - WAD update

- Released high-quality sound pack (JewelsWad.zip).

January 19, 2002 - Version 1.0 -

- Official Release 1.0
- Contains Build 1062 for ARM processors.

Known Issues

None at this time.

Error Log Details

The following sample shows a typical log file sample and the meaning of each of the lines in the file. This sample was taken from a successful run of the software (version 1.01-later versions may appear slightly different). Lines marked with PocketPC indicate that the line will show up in the PocketPC version of the software. The Win32 column indicates that the line will also appear in the standard Windows (desktop) version of the software.:

File Line	Pocket PC?	Win32?	Description
Creating new logfile.	x	x	Indicates that the logfile is being generated.
Parsing command line...	x	x	Any command parameters from the icon are being checked.
Jewels - WindowsCE (PocketPC) Build XXXX	x	x	Shows the platform and the current product build number.
[[ Jewels Version 1.01 - Retail Release ]]	x	x	Shows the version of the product and the version type.
<< Full Licenced version - for updates, visit http://www.baysidestudios.com >>	x	x	This line is displayed after the system reads your license file from disk and checks the code. If you have purchased a license and entered it, but do not receive this message, you may have entered the product number in correctly.
Calling InitApp	x	x	Initialized the application.
Windows Class registered.	x	x	The internal windows are created and registered with the OS.
ShowWindow, Update Window successful.	x	x	The main window is created and displayed. At this point GAPI and the graphics engine libraries are still not yet initialized.
Checking License Agreement Acceptance.	x	x	This indicates that the End-User license agreement window is about to be displayed to the user.
Agreement previously acknowledged.	x	x	If the user had already accepted the agreement in the past, this indicates so, and the dialog box is not displayed again.
Calling InitGame.	x	x	Initialization of the game is about to take place.
=== InitGame() ===	x	x	Entry point into the actual routine.
InitGamePlatform() called.	x	x	Calls any initialization necessary for the given platform. On CE devices, the graphics engine is called. On Win32 systems, the DirectX subsystem is initialized.
LoadGraphics() ...done.	x	x	This line indicates that all necessary graphics resources were loaded successfully from the wad file.
LoadSounds() called...	x	x	This line indicates that the sound subsystem is about to be initialized and the sounds loaded into memory.
Initializing sound subsystem...	x		The sound subsystem for the CE version is being loaded (loading fmodce.dll into memory).
Calling _Init()...done.	x		The sound init function is called... and returns successfully.
LoadSounds() complete.	x	x	This line indicates that all sounds were loaded and that the sound system begins to play (silence). Sound is working properly at this point.
Creating mouse and clipping rects...successful!	x	x	Internal structures are allocated for the graphics routines.
InitGame returned successfully.	x	x	End of game and platform subsystem initializations.
InitApp returned successfully.	x	x	The application window is ready and all required game elements are available.
Beginning the UpdateGame loop:	x	x	This indicates the beginning of the game and the frame render loop.
FiniApp() called...	x	x	The user has requested that the program end, and the system is beginning to shut down the subsystems.
FreeSounds() called...	x	x	The sounds are being freed and the memory is being releaased.
FreeSounds() complete.	x	x	Done!
Calling WinMainCEEnd()...done.	x		Closing the graphics engine and GAPI libraries on the CE device. All temporary memory and data structures are being freed.
FiniApp() complete.	x	x	End of the application, right before returning to the OS.

Other Resources

Please check out the Forums for additional information about out products. These forums provide a gathering place to post messages to other members of the community, who may have experienced (and resolved) your problem.