Game Explorer Categories что это за программа и как ее удалить?
Добрый день друзья Говорим сегодня мы о Game Explorer Categories, что это за программа, что за дичь, сегодня все узнаем! Да уж ребята, инфы нет вообще, вот обломаха, но я ищу!
В связи с тем что инфы по поводу Game Explorer Categories вроде как нет, пришлось подключить свои телепатические возможности. Лично я думаю что эта программа является или игрой или набором игр или же это оболочка-доступ к играм. Не удивлюсь если программа работает только при наличии подключения к интернету.
Значит я также узнал, что программа может сидеть в компе вот по такому адресу:
C:\Program Files (x86)\TOSHIBA Games\Game Explorer Categories — genres\
И работает прога под процессом provider.exe. Кстати, видите в пути есть слово TOSHIBA? У меня есть подозрение что программа эта фирменная, то есть например вы купили ноутбук, а там уже была установлена прога Game Explorer Categories
Также нашел инфу, что может прога и тут сидеть:
C:\Program Files (x86)\WildTangent Games\App\
И работать может под процессом GamesAppService.exe. WildTangent это как я понимаю компания. В принципе все понятно, дело в том что эта компания пилит игры, можно зайти на ее сайт wildtangent.com и убедиться в этом
Ищу дальше хоть какую-то информацию.. На одном форуме нашел такую строчку:
C:\Program Files (x86)\Acer Games\Game Explorer Categories — touch\Uninstall.exe
Эта строчка говорит вот о чем. У вас в папке Program Files (x86) или просто в Program Files где-то должна быть папка Game Explorer Categories, внутри должен быть файл Uninstall.exe или uninst.exe, этот файл является деинсталлятором, то есть если его запустить о начнется процесс удаления проги.
Кстати, получается что эта прога может быть и на ноутах компании Acer. Короче я думаю что и на ноутах других фирм она тоже может быть. Все верно, на ноутах HP тоже может быть эта прога, вот подлянка..
В общем как можно удалить Game Explorer Categories? Вот как, смотрите. Можно отыскать папку с прогой и оттуда запустить модуль деинсталляции. Но есть еще один способ. Зажимаете кнопки Win + R, далее выскочит оконце Выполнить, вы туда кидаете эту команду:
Потом запустится окно со списком всех установленных приложений, тут вам нужно найти Game Explorer Categories, вот оно как может выглядеть (походу еще и несколько экземпляров может быть):
Необходимо нажать правой кнопкой по проге и там выбрать Удалить (Uninstall) и далее следовать инструкциям, скорее всего нужно будет просто нажимать Далее или Next. Таким образом вы удалите приложение
Если удалить не получилось или даже если получилось, я вам честное слово советую все равно проверить комп утилитой AdwCleaner, вот как она выглядит:
Плюсы: реально простая, бесплатная, и имеет прилично хорошую репутацию. Я даже писал о ней уже вот здесь, советую к прочтению:
На этом все, удачи вам и чтобы не было у вас никогда левых прог на ПК!
Windows Games Explorer for Game Developers
Windows Vista improves the user experience of gaming on Windows by including Games Explorer. Games Explorer is exposed in the Windows Vista Start Menu as the Games folder and provides a central location for accessing games.
Starting with the March 2009 release of the DirectX SDK, a new game definition file (GDF) schema is used to support features in Windows 7, Game Provider and RSS feed, and IGameExplorer2. IGameExplorer2 is a new interface on Windows 7 that simplifies the process of integrating a game with Games Explorer.
This article outlines the process of registering a game with Games Explorer and parental controls on Windows Vista and Windows 7 by using the new GDF schema.
Game Explorer is unavailable in Windows 10, version 1803, and later.
- Prerequisites
- Integrating with an Installer
- Integration Process
- Games Explorer Tasks
- Integrating into InstallScript
- Integrating into an MSI Package
- Debugging Tips
- Test with sample code
- Make sure that your game was removed properly
- Be sure to sign using Authenticode
- Be sure that parental controls are available
- Verify that tasks are of the correct type
- Verify the data in GDF binary
Prerequisites
Before you can integrate a game into Games Explorer, you must create a game definition file (GDF). A GDF is an XML file that contains metadata that describes the game. In the March 2009 release of the DirectX SDK, a section for game provider, RSS feed, and game task has been added to the GDF schema. To use the instructions in this article, you must use this new GDF format to create your GDF file.
Microsoft provides a tool for authoring GDFs in the DirectX SDK, Game Definition File Editor, to make this creation process easier. This tool also helps you create localized versions of a GDF.
Once a GDF has been authored and localized, it must be encapsulated within a resource section of a binary file (either an executable or DLL), along with the game’s thumbnail and icon. The GDF contains all of the metadata associated with the game, including the game’s rating. Windows Parental Controls use the game’s rating to allow parents to control access to the game. The binary file which contains the GDF must be digitally signed with a valid Authenticode certificate; otherwise, Games Explorer and the parental control system ignores the game’s rating, because the rating information cannot be trusted without certification. For more details about signing code with Authenticode, see Authenticode Signing for Game Developers.
Integrating with an Installer
To simplify Games Explorer integration, the GameUXInstallHelper sample provides a common API that can be called on Windows XP, Windows Vista, and Windows 7. It is designed to work with scripts for InstallShield and Wise Installation System, as well as MSI custom actions and custom installation tools. Detection of the operating system is handled inside this sample DLL, so the caller does not need to worry whether the client is running Windows XP, Windows Vista, or Windows 7.
The functions exported by this DLL are the following:
GameExplorerInstallW
Registers a game with Games Explorer, given a path to the GDF binary, a full path to the folder where the game is installed, and the installation scope.
GameExplorerInstallA
Registers a game with Games Explorer; ANSI version of GameExplorerInstallW.
GameExplorerUninstallW
Removes a game from registration with Games Explorer, given a path to the GDF binary.
GameExplorerUninstallA
Removes a game from registration with Games Explorer; ANSI version of GameExplorerUninstallW.
GameExplorerSetMSIProperties
Configures the CustomActionData properties for the actions of an MSI deferred custom installation. Usage of this function is described in detail later in this article.
GameExplorerInstallUsingMSI
Adds a game to Games Explorer; for use during an MSI custom action installation.
GameExplorerUninstallUsingMSI
Remove a game from Games Explorer; for use during an MSI custom action installation.
These functions are further explained in the GameUXInstallHelper.h header.
Integration Process
Once the GDF and related files have been added to a binary resource, it is then possible to integrate the game with Games Explorer. Using GameUXInstallHelper will simplify the integration process. To register the game with Games Explorer, call the GameExplorerInstall with a path to the GDF binary, a full path to the folder where the game is installed, and the installation scope. To remove the game’s registration, call GameExplorerUninstall with a path to the GDF binary.
Note that the removal process only removes one unique installation. If a game has been installed multiple times, this process must be repeated for each unique installation.
Games Explorer Tasks
Games Explorer tasks will appear in the context menu of an item in Games Explorer. Tasks are divided into play tasks and support tasks. Play tasks launch a game into a particular mode, while support tasks serve any other purpose, including linking to web sites.
In Windows Vista, tasks are simply shortcuts that are located in specific folders. Play tasks and support tasks are stored in folders with the corresponding names PlayTasks and SupportTasks. GameUXInstallHelper can read the game’s task information from the GDF binary file and create all of the shortcuts automatically.
In Windows 7, the shortcuts to the tasks are not needed, because Games Explorer obtains all of the task information directly from the GDF binary file.
Integrating into InstallScript
Calling Games Explorer APIs from InstallShield’s InstallScript is made easy by using the GameUXInstallHelper sample. The steps required to integrate with InstallShield are as follows:
- Open an InstallScript project in the InstallShield editor.
- Add GameUXInstallHelper.dll to the project to be installed to the target directory. To add GameUXInstallHelper.dll to an InstallScript project:
- On the Installation Designer tab, click Application Data in the navigation pane on the left.
- Click Files and Folders and browse in Source computer’s folders to locate GameUXInstallerHelper.dll in Source computer’s files. The default location for GameUXInstallerHelper.dll is DirectX SDK root\Samples\C++\Misc\Bin\x86.
- Under Destination computer’s folders, click Application Target Folder.
- Drag GameUXInstallerHelper.dll from Source computer’s files to Destination computer’s files.
typedef GUID begin LONG Data1; SHORT Data2; SHORT Data3; CHAR Data4(8); end; prototype LONG GameUXInstallHelper.GameExplorerInstallW(WSTRING, WSTRING, NUMBER); prototype LONG GameUXInstallHelper.GameExplorerUninstallW(WSTRING); function OnMoved() WSTRING gdfbin[256]; WSTRING path[256]; NUMBER scope; begin if !MAINTENANCE then UseDLL( TARGETDIR ^ "GameUXInstallHelper.dll" ); UseDLL( WINSYSDIR ^ "OLE32.dll" ); path = TARGETDIR; gdfbin = TARGETDIR ^ "bin\\ExampleGame.exe"; // TODO: Change this to point to binary containing the GDF if ALLUSERS == 1 then scope = 3; else scope = 2; endif; GameUXInstallHelper.GameExplorerInstallW( gdfbin, path, scope); UnUseDLL( TARGETDIR ^ "GameUXInstallHelper.dll" ); UnUseDLL( WINSYSDIR ^ "OLE32.dll" ); endif; end; function OnMoving() WSTRING gdfbin[256]; begin if MAINTENANCE && UNINST != "" then UseDLL( TARGETDIR ^ "GameUXInstallHelper.dll" ); UseDLL( WINSYSDIR ^ "OLE32.dll" ); gdfbin = path ^ "bin\\ExampleGame.exe"; // TODO: Change this to point to binary containing the GDF GameUXInstallHelper.GameExplorerUninstallW(gdfbin); UnUseDLL( TARGETDIR ^ "GameUXInstallHelper.dll" ); UnUseDLL( WINSYSDIR ^ "OLE32.dll" ); endif; end;Integrating into an MSI Package
The following is a high-level description of the steps required to call the Games Explorer APIs using MSI custom actions:
- Add a property to the MSI Property table called «RelativePathToGDF» containing the relative path to the GDF binary.
- After the CostFinalize action, call the GameUXInstallHelper DLL function SetMSIGameExplorerProperties in an immediate custom action to set the appropriate MSI properties for the other custom actions.
- Upon installation, trigger a deferred custom action after the InstallFiles action that calls the GameUXInstallHelper DLL function AddToGameExplorerUsingMSI. If the installation is for all users, then the custom action must set the flag msidbCustomActionTypeNoImpersonate; otherwise, it must not set this flag. Therefore, two nearly identical custom actions are defined: GameUXAddAsAdmin and GameUXAddAsCurUser.
- Upon removal of the installation, trigger a deferred custom action before the RemoveFiles action that calls the GameUXInstallHelper DLL function RemoveFromGameExplorerUsingMSI. If the installation was for all users, then the custom action must set the flag msidbCustomActionTypeNoImpersonate; otherwise, it must not set this flag. Therefore, two nearly identical custom actions are defined: GameUXRemoveAsAdmin and GameUXRemoveAsCurUser.
- Define rollback custom actions to handle the case where the user cancels installing or removing after one of these custom actions has already happened. This results in an additional 4 custom actions: GameUXRollBackAddAsAdmin, GameUXRollBackAddAsCurUser, GameUXRollBackRemoveAsAdmin, and GameUXRollBackRemoveAsCurUser.
This procedure is described in detail in the following instructions, which describe a process that can be done using an MSI editor, such as the Orca editor found in the Platform SDK. Some MSI editors have wizards which simplify some of these configuration steps.
To configure an MSI package for integration with Games Explorer
- Open the MSI package in Orca.
- Add the row shown in the following table to the Binary table in the MSI package.
Name Data GAMEUX file path to the DLL\GameUXInstallHelper.dll Note This file will be embedded in the MSI package, so you must do this step every time you recompile GameUXInstallHelper.dll.
Action Type Source Target GameUXSetMSIProperties msidbCustomActionTypeDll + msidbCustomActionTypeBinaryData + msidbCustomActionTypeContinue = 65 GAMEUX SetMSIGameExplorerProperties GameUXAddAsAdmin msidbCustomActionTypeDll + msidbCustomActionTypeBinaryData + msidbCustomActionTypeContinue + msidbCustomActionTypeInScript + msidbCustomActionTypeNoImpersonate = 3137 GAMEUX AddToGameExplorerUsingMSI GameUXAddAsCurUser msidbCustomActionTypeDll + msidbCustomActionTypeBinaryData + msidbCustomActionTypeContinue + msidbCustomActionTypeInScript = 1089 GAMEUX AddToGameExplorerUsingMSI GameUXRollBackAddAsAdmin msidbCustomActionTypeDll + msidbCustomActionTypeBinaryData + msidbCustomActionTypeContinue + msidbCustomActionTypeRollback + msidbCustomActionTypeInScript + msidbCustomActionTypeNoImpersonate = 3393 GAMEUX RemoveFromGameExplorerUsingMSI GameUXRollBackAddAsCurUser msidbCustomActionTypeDll + msidbCustomActionTypeBinaryData + msidbCustomActionTypeContinue + msidbCustomActionTypeRollback + msidbCustomActionTypeInScript = 1345 GAMEUX RemoveFromGameExplorerUsingMSI GameUXRemoveAsAdmin msidbCustomActionTypeDll + msidbCustomActionTypeBinaryData + msidbCustomActionTypeContinue + msidbCustomActionTypeInScript + msidbCustomActionTypeNoImpersonate = 3137 GAMEUX RemoveFromGameExplorerUsingMSI GameUXRemoveAsCurUser msidbCustomActionTypeDll + msidbCustomActionTypeBinaryData + msidbCustomActionTypeContinue + msidbCustomActionTypeInScript = 1089 GAMEUX RemoveFromGameExplorerUsingMSI GameUXRollBackRemoveAsAdmin msidbCustomActionTypeDll + msidbCustomActionTypeBinaryData + msidbCustomActionTypeContinue + msidbCustomActionTypeRollback + msidbCustomActionTypeInScript + msidbCustomActionTypeNoImpersonate = 3393 GAMEUX AddToGameExplorerUsingMSI GameUXRollBackRemoveAsCurUser msidbCustomActionTypeDll + msidbCustomActionTypeBinaryData + msidbCustomActionTypeContinue + msidbCustomActionTypeRollback + msidbCustomActionTypeInScript = 1345 GAMEUX AddToGameExplorerUsingMSI Action Condition Sequence Notes GameUXSetMSIProperties 1015 The sequence number places the action soon after CostFinalize. GameUXAddAsAdmin NOT Installed AND ALLUSERS 4003 This custom action will only happen during a fresh installation for all users. The sequence number places the action after InstallFiles and after the rollbacks. GameUXAddAsCurUser NOT Installed AND NOT ALLUSERS 4004 This custom action will only happen during a fresh installation for the current user only. The sequence number places the action after InstallFiles and after the rollbacks. GameUXRollBackAddAsAdmin NOT Installed AND ALLUSERS 4001 This custom action will only happen when a fresh installation for all users is cancelled. The sequence number places the action after InstallFiles and before the Add custom action. GameUXRollBackAddAsCurUser NOT Installed AND NOT ALLUSERS 4002 This custom action will only happen when a fresh installation for the current user only is cancelled. The sequence number places the action after InstallFiles and before the Add custom action. GameUXRemoveAsAdmin REMOVE~=»ALL» AND ALLUSERS 3452 This custom action will only happen during removal for all users. The sequence number places the action directly before RemoveFiles and after the rollbacks. GameUXRemoveAsCurUser REMOVE~=»ALL» AND NOT ALLUSERS 3453 This custom action will only happen during removal for the current user. The sequence number places the action directly before RemoveFiles and after the rollbacks. GameUXRollBackRemoveAsAdmin REMOVE~=»ALL» AND ALLUSERS 3450 This custom action will only happen when removal for all users is cancelled. The sequence number places the action directly before RemoveFiles and before the Remove custom action. GameUXRollBackRemoveAsCurUser REMOVE~=»ALL» AND NOT ALLUSERS 3451 This custom action will only happen when removal for the current user is cancelled. The sequence number places the action directly before RemoveFiles and before the Remove custom action. Property Value RelativePathToGDF relative file path\name of binary file that contains the GDF Note The location specified by the path is relative to the location specified by the installation path. For example, bin\GDF.dll.
For more detailed information about MSI packages and Windows Installer, see Windows Installer.
Debugging Tips
The following are some tips to help debug issues when calling Games Explorer APIs:
Test with sample code
Building the GameUXInstallHelper sample solution will create a GameUXInstallHelper.dll and a GDFInstall.exe. The GDFInstall.exe is a sample application that uses GameUXInstallHelper.dll. Running GDFInstall.exe will prompt if you want install or remove a GDF binary from game explorer. You can test your GDF binary file by passing it in as the first command line arg to GDFInstall.exe.
If you don’t have a GDF binary or yours fails to install, try using the sample GDF in the DirectX SDK. The GDFExampleBinary sample is found in the DirectX SDK and is just a DLL that only contains a GDF file. Also included in the source is its GDFMaker project. You can build it and test it using GDFInstall.exe. You can also compare its XML to yours to pinpoint exactly where the issue is.
Make sure that your game was removed properly
If the game is already installed in Games Explorer, then subsequent calls to IGameExplorer::AddGame will return E_FAIL so make sure your game isn’t installed before testing. This also applies if you install the GDF for only the current user and then try to install the GDF for all users. You must first remove the game from the current users before IGameExplorer::AddGame will succeed.
If you run GDFInstall.exe enum, the sample application will enter a different mode which will enumerate all of the installed Games Explorer games and prompt you to remove them. You can also browse and search the registry in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\GameUX to make sure that your game isn’t installed for another user on the system. However, do not alter these registry settings for any other purpose, as they are not guaranteed to remain compatible in future versions of the operating system.
Be sure to sign using Authenticode
If you have provided a rating, but are not seeing it in Games Explorer, make sure that you have used Authenticode to sign the executable or DLL file that contains the rating. Games Explorer ignores ratings information in unsigned files. For more information about Authenticode, see Authenticode Signing for Game Developers.
Be sure that parental controls are available
Ensure that you are testing parental controls on an edition of Windows Vista that provides parental controls: Home Basic, Home Premium, or Ultimate. Windows Vista Business and Windows Vista Enterprise do not provide parental controls however if you are testing on Windows Vista Ultimate, and the test computer is joined to a domain, you must change a group policy setting make parental controls visible. To do this, see Getting Started with Games Explorer.
Verify that tasks are of the correct type
If you have specified support tasks that do not appear in Games Explorer, verify that they are all Web links. Any other shortcut tasks must be created as play tasks. Tasks are covered earlier in this article in Games Explorer Tasks.
Verify the data in GDF binary
GDFTrace.exe is a tool found in the DirectX SDK. You can run GDFTrace.exe on your GDF binary and it will output all the GDF metadata contained in the binary for every supported language for quick validation. It also displays any warnings about missing or outdated information.
Summary
Games Explorer in Windows Vista provides an easy, customizable way to present your game to users of Windows Vista, but it also requires you to register the game with the system during the installation process. The GameUXInstallHelper sample greatly simplifies this process for developers.
Getting Started with Games Explorer
Windows Games Explorer provides game developers with a secure and attractive way to present their games to users of the Windows platform (starting with Vista). This document details how to add a game to Games Explorer.
What is Games Explorer?
Windows Games Explorer is a custom folder for the Windows shell that provides a rich presence for games. It is accessed on the Start by clicking Games.
Games Explorer provides:
- Display of game title, description, version, release date, publisher, and developer information
- Display of general or region-specific game box art
- Display of minimum and recommended system performance ratings
- Display of game content ratings and descriptors
- Restriction of game play based on parental control settings
- Customizable context menus when a game is right-clicked
- Unique settings for multiple installations on the same system
- Display of game statistics
- Display of game notifications
- Display of game providers with optional news feeds
Using Games Explorer
To enable your game to use Games Explorer, you must create the data files that Games Explorer relies on, and add your game to Games Explorer.
- Creating Games Explorer Data Files
- Adding a Game to Games Explorer
- Enabling Games Explorer on a Domain
Creating Games Explorer Data Files
The first part to adding a game to Games Explorer is to create and properly include a set of data that is consumed by Games Explorer. Doing this consists of the following steps.
Step 1. Create GDFs
Games Explorer displays a variety of data about each game. This data is stored in an XML-based document called a game definition file (GDF). For your information to be shown, you must author at least one GDF; if you want your game information to be localized for different world regions, you must author several GDFs, one for each region.
The GDF format is defined by a schema, which requires only a minimal set of information; many of the fields are optional. In creating your GDF, you can choose the level of detail that you want to supply to Games Explorer.
To see examples of minimal and full GDF files, and to understand the schema for GDF files, see The Game-Definition-File (GDF) Schema.
Step 2. Create Bitmaps
Games Explorer displays artwork for every game that provides it. The artwork provided is shown in a small format in the list of games, and in a large format when a game is selected by the user. Create an image file that will represent your game in Games Explorer.
The image should be in PNG format, as this allows for transparency features to give your artwork a clean look in the Games Explorer. Other formats are also available. For a list of formats, see GDF Delivery and Localization
Step 3. Embed GDFs and Bitmaps
The GDF files and bitmap files that are used by Games Explorer cannot be independent files that are simply installed in a game’s directory along with the rest of the game files. They must be embedded as resources, either into an executable file or a DLL.
The Games Explorer header (GameUx.h) contains defined constants that you must use in the resource script to identify your GDF and bitmap file so that Games Explorer can find them. By separating the resource script into sections with #ifdef for multiple languages, you can instruct Games Explorer to search for localized versions of GDF files and bitmaps.
Adding a Game to Games Explorer
The second step to adding a game to Games Explorer is performed by the game’s installer. The installer’s code must identify the location of the game data for Games Explorer. Because Games Explorer is only available on Windows starting with Vista, a different set of steps must be taken for an installation on a computer running Windows XP as opposed to on one running a more recent version of Windows. Games that do not use an installer can perform these tasks at launch time, if necessary.
- Adding a Game to Recent Versions of Windows
- Adding a Game to Windows Vista, Windows 7, or Windows 8 Desktop
- Adding the Game to Windows XP
Adding a Game to Recent Versions of Windows
If a game is installed on a recent version of Windows (Windows 7 or later), see the Windows Games Explorer for Game Developers technical article for instructions on how to add your game.
Adding a Game to Windows Vista, Windows 7, or Windows 8 Desktop
If a game is installed on Windows Vista, Windows 7, or Windows 8 Desktop, it can be added to Game Explorer, and this is the most straightforward scenario.
Step 1. Install Game Files
The first step in adding your game to the Games Explorer is to have your game files installed on the hard drive. It is important that all game files be installed by this step; once the game is added to Games Explorer in step 4, the parental controls of Windows Family Safety might prevent your installation process from accessing the game’s base directory to add or change files.
Step 2. Create IGameExplorer COM Object
The next step is to create the IGameExplorer COM object that you will use to add your game information to Games Explorer.
Step 3. Call IGameExplorer::VerifyAccess
To check whether the game has permission to run on the current user’s account, call VerifyAccess. Note that doing so also adds the game to the «Parental Controls Activity Viewer» log. Additionally, you must call this function prior to logging into the parental controls activity viewer. The VerifyAccess method takes as a parameter the path to your game’s GDF. It checks parental control rating in the GDF against the current user’s parental control settings and determines whether the current user has the necessary permission to run the game.
You might choose to inform the user of their lack of permission to run the game, since if VerifyAccess returns FALSE, the user will not be allowed to run the game.
Step 4. Call IGameExplorer::AddGame
To identify your game to Games Explorer, you must call AddGame with the path to your GDF resource, the path to your base installation, the installation scope, and optionally, an InstanceID (a GUID). You can either provide an InstanceID for the pguidInstanceID parameter using a GUID that you generate, or, by setting pguidInstanceID to GUID_NULL, one will be generated for you. The InstanceID uniquely identifies the instance of your game added to Games Explorer, and you must persist it in the next step.
Note that after calling AddGame, restriction by parental control settings might prevent the game’s installation directory from being accessed by the current user.
Step 5. Make the Game InstanceID Persistent
Store the InstanceID that you retrieved from or passed into AddGame, using either a file or the registry. Alternatively you can look up your InstanceID at runtime using WMI. See the various samples for more information on how to do this.
Step 6. Create Game Task Folders
Tasks are the actions that a user can perform on your game in Games Explorer. Actions such as playing the game, updating the game, or visiting the game’s website are examples of tasks. You must create a directory structure that represents the tasks that you wish to support for your game, even if you only want to support the default task, which runs when the user double-clicks on the game in Games Explorer. See Games Explorer Tasks.
Adding the Game to Windows XP
You can install your game on a computer running Windows XP and store extra information so that your game will show up in Games Explorer if the user upgrades the system to a more recent version of Windows.
Step 1. Install Game Files
As in the scenario for more recent versions of Windows, the first step will be to install all of your game files to the user’s system.
Step 2. Generate Your Own InstanceID
Because the Games Explorer APIs are not available in Windows XP, the system cannot generate an InstanceID for your game. Therefore, you must create your own InstanceID, which you should persist in a file or the registry.
Step 3. Create Game Task Folders
As in the scenario for installation with more recent versions of Windows, you can prepare tasks — commonly-used actions — for your user. Because the user is currently running Windows XP, the tasks will not be available for use immediately, but they will be automatically added to the game in Games Explorer when the user upgrades to a newer version of Windows, such as Windows Vista or Windows 7. See Games Explorer Tasks as well as Supporting an Upgrade from Windows XP.
Step 4. Install Registry Values
So that a more recent version of Windows will add your game automatically upon installation of the operating system, you must create some values in the registry; for more information, see Creating Custom Registry Values.
Enabling Games Explorer on a Domain
To use parental controls on a Windows system joined to a domain, you must change a group policy setting to make parental controls visible:
- Run gpedit.msc
- Navigate to Local Computer Policy | Computer Configuration | Administrative Templates | Windows Components | Parental Controls.
- Set «Parental Controls control panel visible on a Domain» to enabled.
- Log off and parental controls will be visible.
Related Topics
- The Game-Definition-File (GDF) Schema
The topics provided here provide a detailed explanation of the XML-based GDF schema and how to best use the fields to represent your game. - Games Explorer Tasks
The topics provided here provide a detailed explanation of the Games Explorer task system, including how you can create your own custom tasks. - Game Definition File Editor
The topics provided here provide a detailed explanation of the Game Definition File Editor, which is a graphical utility designed for creating localized game definition files (GDFs). as well as the necessary resource compiler scripts to compile game-definition files.
Что такое категории Game Explorer?
Категории Game Explorer — жанры программное обеспечение, разработанное WildTangent. Самая распространенная версия — 11.0. 0.7, при этом более 98% всех установок в настоящее время используют эту версию. Пакет установки обычно устанавливает около 6 файлов и обычно имеет размер около 13,04 МБ (13 675 102 байта).
Могу ли я удалить категории Game Explorer?
Вы можете удалить Game Explorer Categories — main со своего компьютера, выполнив следующие действия. с помощью функции «Добавить / удалить программу» на панели управления Windows.. Когда вы найдете программу Game Explorer Categories — main, щелкните ее и выполните одно из следующих действий: Windows Vista / 7/8/10: нажмите «Удалить».
Что такое Game Explorer?
Что такое Games Explorer? Windows Games Explorer — это настраиваемая папка для оболочки Windows, обеспечивающая богатый доступ к играм. Доступ к нему можно получить в меню «Пуск», нажав «Игры». Обозреватель игр обеспечивает: Отображение названия игры, описания, версии, даты выпуска, информации об издателе и разработчике.
Как удалить программу вручную?
- Откройте меню «Пуск».
- Щелкните Настройки.
- Щелкните «Приложения».
- В меню слева выберите «Приложения и функции».
- Выберите программу или приложение, которое вы хотите удалить, из появившегося списка.
- Нажмите кнопку удаления, которая отображается под выбранной программой или приложением.
Как удалить Windows7?
- Чтобы удалить приложение, используйте программу удаления, входящую в состав Windows 7. .
- На правой панели нажмите Панель управления.
- В разделе «Программы» выберите пункт «Удалить программу».
- Затем Windows перечисляет все программы, которые были установлены с помощью установщика Windows. .
- Нажмите вверху на Удалить / Изменить.
Как использовать Game Explorer?
Чтобы использовать Game Explorer, просто Делайте ходы на доске и смотрите, как таблица справа обновляется с играми и ходы, сделанные в аналогичных позициях другими шахматистами. Это отличный способ изучить общие открытия, и вы можете увидеть названия открытий, связанных с текущей позицией, чуть ниже доски.
Где хранятся игры для Windows 10?
- На рабочем столе одновременно нажмите клавиши Windows + R — запустится «Выполнить».
- На экране запуска введите «shell: games» и нажмите Enter.
- Теперь у вас должна быть папка «Игры» — легко, правда?
- На панели задач щелкните правой кнопкой мыши папку с играми и выберите «Закрепить эту программу на панели задач».
Как избавиться от приложения, которое не удаляется?
- На телефоне Android откройте «Настройки».
- Перейдите в «Приложения» или «Управление приложениями» и выберите «Все приложения» (может отличаться в зависимости от марки и модели вашего телефона).
- Теперь найдите приложения, которые хотите удалить. Не можете найти? .
- Коснитесь имени приложения и нажмите Отключить. Подтвердите при появлении запроса.
Как удалить программу, которая не деинсталлируется?
- Откройте меню «Пуск».
- Выполните поиск по запросу «добавить или удалить программы».
- Нажмите на результаты поиска с заголовком «Добавить или удалить программы».
- Найдите конкретное программное обеспечение, которое вы хотите удалить, и выберите его.
- Нажмите кнопку «Удалить».
- После этого просто следуйте инструкциям на экране.
Как я могу удалить приложение, которое не удаляется?
- Нажмите и удерживайте приложение в списке приложений.
- Коснитесь информации о приложении. Это приведет вас к экрану, на котором отображается информация о приложении.
- Параметр удаления может быть неактивен. Выберите отключить.