DATE: August 19, 1994 BETA Version for Galileo, version 1.00 Build4 Galileo is a Windows Control Panel Applet which is used to configure the following : 1) S3 Windows Driver Screen Resolution. 2) S3 Windows Driver Color Depth. 3) The refresh rate of the card installed. 4) S3 Windows Driver Switches. Galileo can also be used to read the current configuration of the card and update the current S3 Windows' Driver. Galileo was only written to work on the 864/964 and Trio boards. NOTE: There are some known problems trying to navigate using the keyboard. We are addressing them. In the interim, we strongly suggest you use the mouse when using Galileo. ú Installation procedures for GALILEO. The following files are needed to run Galileo: 1) GALILEO.CPL 2) CTL3D.DLL 3) MODEPARM.DAT 4) GALILEO.INI 5) A 256 Windows bitmap in RLE format. The name of this file is defined in GALILEO.INI. 6) A 16 Windows bitmap in RLE Format. The name of this file is defines in GALILEO.INI. 7) A 32x32 bitmap to be used as an icon in the ABOUT box. The name of this file is defines in GALILEO.INI. To Install Galileo: 1) Copy GALILEO.CPL and CTL3D.DLL to your Window's system directory. 2) Copy MODEPARM.DAT and GALILEO.INI to your Window's directory. 3) Copy all bitmap images into your Window's system directory. *********************************************************** NOTE: GALILEO.INI is where the OEM can configure their company and board name when GALILEO brings up the "ABOUT" dialog box. This is also where you define which bitmap to load to use for the background and ABOUT dialog box ICON. *********************************************************** 4) To run GALILEO, run CONTROL PANEL in your Window's MAIN program group. You should see the GALILEO icon there. When running GALILEO for the first time, it is assume that Windows is configured for a S3 640x480 256 color mode. This can be done through the DOS Window's setup program. ú Format of GALILEO.INI Galileo.ini makes it possible of OEM vendors to customize a string for GALILEO without having to modify the source code. The format of this file follows the similar format used in Windows INI files. [vendor_info] board_vendor = Name of the OEM board vendor. For example, board_vendor = P.A.W. Inc. copyright_msg = Copyright message to use in Galileo. For example, copyright_msg = Copyright 1994. 16color_background_bmp = RLE bitmap to use when GALILEO is running in 16 color modes. For example, 16color_background_bmp = happy.bmp 256color_background_bmp = RLE bitmap to use when GALILEO is running is 256 color modes or higher. For example, 256color_background_bmp = frame.bmp about_bmp_icon = Bitmap file to be used as an icon in the ABOUT dialog box For example, about_bmp_icon = Galileo.bmp [switches] These switches allow the OEM to configure which drivers switches the user can configure in system.ini in the [display] section. The format of this data is as follows: switch = , , , , , The following example shows how an OEM can configure GALILEO to allow the use of the MMIO setting while not allowing them to modify polygon-support. switch1= mmio,off ,on,Memory Mapped I/O , on switch2= polygon-support, off, on, Polygon-Support: ,off Known bugs with Galileo V1.00 Build 4 Known Problems: 1) When Galileo is dragged around the screen, control dialog box goes gray. Control dialog box can be restored if the dialog control button is clicked. 2) Run the 1 Meg mode, 640x480 16.7(1Mb), in 2 Meg board configuration, Galielo will display incorrect current refresh rate for that mode. i.e. scope shows 60Hz but Galieo displays 75Hz. 3) Refresh rate for 1600x1200 may not display correctly in the Vision 864 because Galileo cannot detect different DAC. -Vision 864 SDAC supports Interlaced refresh rate only. -Vision 864AT&T supports 60Hz refresh rate only. User has to edit the MODEPARM.DAT to change by themselves. Galileo limitation To avoid Galileo or Windows hangs , user must use S3 Installation utility program to copy all driver files to the Windows System and Window directories before using the Galileo utility to UPDATE CURRENT DRIVER. Because the Galielo always reads file information from OEMSETUP.INF at the Window 's system directory, not the one in the updated drivers diskette.