Direct. X Installation for Game Developers WindowsThis article is intended to address some of the common questions about the Direct.X runtime, and using Direct.Setup to install Direct.X. Direct. X Runtime.Based on the fact that the Office 2010 FixIt files are the same for Windows 10 and all other Windows versions, I am going to assume that the same is true for Office.The following are the best practices for adding installation of DirectX to a games installer.The Direct. X runtime consists of core components and optional components.The core components, such as Direct.D and Direct. Input, are considered part of the operating system.The core components for Direct.X 9. 0c have not changed since the Direct.X SDK Summer 2. 00.Insert preformatted AutoText in your document or configure Word to end words, phrases, or sentences automatically when you type just a few characters.Afo0HnmS' alt='Microsoft Office 2003 Cab Files Download' title='Microsoft Office 2003 Cab Files Download' />Update, and they match what was released with Microsoft Windows XP SP2, Windows XP Pro x.Edition, and Windows Server 2.SP1. Windows Vista includes Direct.Microsoft Office 2003 Cab Files Download' title='Microsoft Office 2003 Cab Files Download' />X 1.Windows Display Driver Model WDDM and Direct.D 1. 0. x. Windows 7 and Windows Vista see KB9.Direct. X 1. 1, which supports Direct.D 1. 1, Direct. 2D, Direct.Write, the WARP1.See Graphics APIs in Windows for more details.The optional components are released in updates of Direct.X SDK, and they include D3.DX, XACT, XAudio.XINPUT, Managed Direct.X, and other such components.Many of the optional components are regularly updated to integrate customer feedback and expose new features.Direct. X Version Number.The Direct. X version number, such as 9.Direct. 3D, Direct.Input, or Direct.Sound. This number does not cover the versions of the various optional components that are released in the Direct.X SDK, such as D3.DX, XACT, XINPUT, and so on.Generally speaking, the Direct.X version number is not meaningful except as a quick reference to the core run time bits.This number should not be used to check if the correct Direct.X runtime is already installed, because it doesnt take into account the optional Direct.X components. Direct.X Libraries. In the past, the optional components of the Direct.X SDK, including D3.DX, were released as static libraries.However, these are now released as dynamic like libraries DLL because of the increased demand for better security practices.DLLs allow servicing of previously released code.If these components were deployed as static libraries, there would be no way for Microsoft to address security issues found after release.As features are added or changed to the optional components, the names of the corresponding DLLs are also changed to ensure that no regressions are caused to existing games that are using released components.The DLLs for each component live side by side, and game developers can choose exactly which DLL version that the game uses by linking to the corresponding import library.While ensuring that DLLs are installed on a system isnt as easy as simply linking to static libraries, some changes have been made to the Direct.X SDK to address the pain of the DLL model.The Direct. X redistributable can be configured to contain only those components that your application requires to minimize distribution and media sizes.The redistributable folder, Program FilesDirect.X SDKRedist, now contains a cabinet.SDK to find them.Installing the SDK itself installs every possible optional component.A Direct. X redistributable that contains all the optional components is available as both a Web based installer and as a downloadable package see the Direct.X Developer Center Direct.X for more information.Installation of Direct.X by the Games Installer.The following are the best practices for adding installation of Direct.X to a games installer.Term. Description.Install the redistributable components every time.A games installation process should install the Direct.X redistributable components during every single installation without allowing users to opt out of it.If you allow opting out, then some users will guess that they dont need it, and if they actually do, the game will not run.Let the Direct. X installer check for optional components.Do not assume that the latest optional components are already installed on a system, because Windows Update and Service Packs do not provide any of Direct.Xs optional components.You must install the Direct.X runtime either by running dxsetup.Direct. Setup. Set up silently.Launch setup in silent mode so that users do not accidentally skip updating the Direct.X runtime. You can do this by launching dxsetup.Direct. Setup and not showing any UI.Combine EULA acceptances.If you prompt the user to accept a EULA, then combine that with prompting for acceptance of the Direct.X EULA when installing in silent mode so that prompting for acceptance of EULAs happens just once.Prompting should happen before you install anything so that if user doesnt accept, you dont end up with a failed and partial installation.Just run dxsetup or call Direct.Setup. Because the Direct.X version number doesnt refer to anything except the core Direct.X components, do not check an installed version before running dxsetup.Direct. Setup. Also, do not check for a files existence to test if an optional component is already installed, since this usually will not correctly determine when a component exists but needs updating.However, the Direct.X setup package will quickly determine this, and perform the right action.Small Installation Packages.You can create smaller installation packages for Direct.X by stripping the contents of the Direct.X redistributable folder down to the minimal set of files required to make the installer work, and retaining any additional components that your game uses.Depending on your minimum specifications, you might not even need to include the core Direct.X 9. 0c cabinet files in the redistributable folder of your installation media.A large majority of Windows XP installations have Service Pack 2, which includes the core Direct.X 9. 0c components, so the Direct.X setup operation will be very fast, and will not require a reboot.The smallest package that can be created is about 3 MB, and it can be compressed to about half that size.A package like this contains one version of the D3.DX DLL, and it requires that Direct.X 9. 0c be already present.The minimal set of files that are required to build a redistributable package are the following files, located in the Direct.X SDK Redist folder Program FilesDirect.X SDKRedist. Add to these the cabinet files for the components that you want to install.If you require the users of your application to already have Direct.X 9. 0c, then you do not need to include Direct.X. cab or dxnt. cab, which make up most of the space requirement.Direct. X. cab is only needed for Windows 9.Windows ME dxnt. Windows 2.Windows XP, and Windows XP SP1 and dxdllregx.Windows 2. 00. 0, Windows XP RTM, Windows XP SP1, and Windows Server 2.RTM. Also, if you do not make use of Direct.Show, or you assume that it is already installed, you can omit BDA.BDANT. cab, and BDAXP.Note You can assume that users of your application already have Direct.X 9. 0c if it was installed by a previous version of your application, you force users to manually update via the Web Installer, or you assume that they have Windows XP SP2 or later.Continuing with this example, if you are using only the 3.D3. DX for April 2.Apr. 20. 06d. 3dx.If you are using the 3.August 2. 00. 6 3.XINPUT, you add Aug.If you have a native 6.However, if you have a 3.OS, the 3. 2 bit versions of the DLLs will work.You can then distribute this package of files and launch Direct.Setup in silent mode or run dxsetup.Remember not to guard this package by any version checking of files, and make sure that your users cannot opt out of running the Direct.X setup. Either of these events creates a fallible installation process.Internal Deployment of the Debug Direct.X Runtime. The debug runtimes of the Direct.X components are installed when the Direct.X SDK is installed, but installing the SDK on every test computer can be painful.You need to design your setup process to copy the debug runtime DLLs from Program FilesMicrosoft Direct.X SDKDeveloper Runtimearchitecture to Windowssystem.However, we strongly recommend that you do not simply copy the released run time DLLs because it is easy to forget to remove them for the final product.Instead, put the Direct.X setup files in a shared folder and run the setup silently from the shared folder.Driver for the Xbox 3.Controller for Windows.The user is expected to obtain the XInput driver for Xbox 3.Windows Update or from the controller packaging.The XInput driver is included with Windows Vista.Removing Old Versions Deployment Mad Scientist.For the last few weeks, weve been building application packages to serve as prerequisites for Office 2.Today, well tackle one last preparatory issue before actually constructing the Office 2.Application in Configuration Manager.As well see next week, Office 2.One of these options instructs the Office Setup program to uninstall previous versions of Office before beginning the installation process.This is great because having multiple versions of Office installed just doesnt work in several combinations, and in others, it is supported but not recommended.See Install and use different versions of Office on the same PC for links to additional details. Ibm Spss Statistics V21 Winning on this page. Unfortunately, this fantastic feature of the Office setup program doesnt actually workDuring setup, if the currently installed old version of Office contains a program e.Share. Point Designer 2.Also, if the existing installation is damaged in some way, it may not be able to be uninstalled reliably.Therefore, if we want a clean upgrade experience for existing installations, we have to find another method to remove previous versions of Office.The Office Deployment Support Team Blog provides the answer.In the post, How to uninstall Office 2.Office 2. 01. 3 Click to Run or Volume License, the author writes Utilizing Offscrub is the best method of removing a previous version of Office.It will call setup.MSIExec to remove the bits.It is best equipped to deal with machine or software corruption and completely removes Office app shortcuts for the previous version.We recommend using Offscrub in almost every situation of moving from Office 2.Office 2. 01. 3. What is this Off.Scrub program Off.Scrub is the underlying VBScript program that runs when you download and run a Microsoft Fix.It program to remove Office.Were going to follow the Office Deployment Support Blogs suggestion and use this technology to reliably remove all previous versions of Office back to Office 2.Office 2. 01. 6. Lets get started.Acquiring the Script Files.I am going to walk through all of the steps below, but you may want to take a moment to go read How to obtain and use Offscrub to automate the uninstallation of Office products from the Office Deployment Support Blog.That is a major source for this post.Download the Fix.It Programs. Let me save you some time.I downloaded seven separate Fix.It files for various versions of Office and Windows.For each version of Office, one package is available for Windows 7 and lower, and another package is available for Windows 8 and higher.It turns out that the Off.Scrub. vbs file is the same in both packages.There is one exception The Windows 7 Offscrub.Office 2. 00. 3 is missing one of the subroutines that it callsa bugbut the subroutine exists in the Windows 8 version.Therefore, you will only have to download four Fix.It files. Well use the Windows 8 versions because they are easier to extract and dont have the bug mentioned above.Browse to the Microsoft Support article, How to uninstall Office 2.Office 2. 00. 7 or Office 2.Control Panel. Download each of the Fix.It programs available on that page for Windows 8.Save them in folders named for the year of the Office version followed by a hyphen and the applicable OS platforms.Win. 82. 00. 7 Win.Win. 8Note There is a Fix.It listed separately for Office 2.Windows 1. 0 in the Office Support article, Uninstall or remove Office 2.As with the Windows 7 version, this Fix.It is the same as the one listed here for Windows 8.Browse to Uninstall Office 2.Office 2. 01. 6, or Office 3.Windows computer.Download the easy fix tool into a folder named 2.O3. 65 Win. I wanted to show you where all of the files came from, but for reference, here are direct links to all of them Based on the fact that the Office 2.Fix. It files are the same for Windows 1.Windows versions, I am going to assume that the same is true for Office 2.Extract the Off. Scrub Scripts.Now we must depart a bit from our instructions, which predate the release of Windows 8.The Fix. It programs we downloaded are packaged in DIAGCAB files.DIAGCAB files work with the Windows Troubleshooting Platform, but architecturally, they are just CAB files, so we can extract their contents with the expand command.On your application staging file share wherever you put application source files for Configuration Manager to find, create a folder structure for the Off.Scrub scripts. Mine will be fileserversoftwareMicrosoftOff.Scrub with a subfolder for each Office version.Make the appropriate changes for your environment in the commands below, and then run them.Change the path to match the parent of all of the folders created earlier.This can also be a network path, like servershareOff.Scrub. Downloads.OFFSCRUBSOURCEE Off.Scrub. Downloads.OFC2. 00. 3WIN8OFFSCRUBSOURCE2.Win. 8. set OFC2.WIN8OFFSCRUBSOURCE2.Win. 8. set OFC2.WIN8OFFSCRUBSOURCE2.Win. 8. set OFC2.OFFSCRUBSOURCE2. O3.Win. rem Change the path to match your Configuration Manager application source location.OFFSCRUBDESTINATIONfileserversoftwareMicrosoftOff.Scrub. md OFFSCRUBDESTINATION2.OFFSCRUBDESTINATION2.OFFSCRUBDESTINATION2.OFFSCRUBDESTINATION2.OFFSCRUBDESTINATION2.OFFSCRUBDESTINATIONC2.R. rem Use the EXPAND command to extract the Off.Scrub files f from the DIAGCAB files, which are really just CAB files with specialized contents, and disregard internal folder structure i.OFC2. 00. 3WIN8Microsoft.Fixit. 20. 05. 4.Off. Scrub vbs OFFSCRUBDESTINATION2.OFC2. 00. 7WIN8Microsoft.Fixit. 20. 05. 2.Off. Scrub vbs OFFSCRUBDESTINATION2.OFC2. 01. 0WIN8Microsoft.Fixit. 20. 05. 5.Off. Scrub vbs OFFSCRUBDESTINATION2.OFC2. 01. 32. 01.O1. 5CTRRemove. diagcab f Off.Scrub vbs OFFSCRUBDESTINATION2.OFFSCRUBDESTINATION2.Off. ScrubO1. 6msi.OFFSCRUBDESTINATION2.OFFSCRUBDESTINATION2.Off. Scrubc. 2r. vbs OFFSCRUBDESTINATIONC2.RThe expand commands above extract just the VBS files that we need from the DIAGCAB files.Update from 2. 01.Subsequent to this blog posts initial publication, testing showed that while all of the extracted scripts work correctly when run manually, they fail on 6.Windows when run from inside a Configuration Manager Package.It turns out that even in Configuration Manager v.Windows. That means that calls to cscript.Windows will use the Sys.WOW6. 4 version of cscript.This prevents the scripts from adequately searching through the entire system and effectively removing Office programs.I added the following section to deal with this issue.Overriding the File System Redirector.In order to work properly, the Offscrub scripts must all run in the native bitness of the platform.On 6. 4 bit Windows, that means we must directly call the native cscript.Configuration Manager Package.In order to keep the package programs platform neutral, I wrote a small script to use in place of cscript.I am indebted to Andrew Lukaszewski, whose generic script to overcome this issue inspired the more specific script below.Copy the following into a plain ANSI text file and save it as CScript.Native. cmd in the root of the Offscrub folder structure.Mine is fileserversoftwareMicrosoftOff.ScrubCScript. Native.CScript. Native. cmd.Author Jay Michaud www.Date 2. 01. 6 0. Source http www.Acknowledgement Inspired by Andrew Lukaszewskis blog at https madluka.Description Use this command script in place of cscript.This is useful when deploying a script as a package program in Microsoft System Center Configuration Manager, where the engine that runs the package program is a 3.Windows. rem Example Instead of.B No. Logo serversharepathtomy script.Native. CScript B No.Logo serversharepathtomy script.On 3. 2 bit Windows, the PROCESSORARCHITEW6.On 6. 4 bit Windows, the PROCESSORARCHITEW6.On 6. 4 bit Windows, the PROCESSORARCHITEW6.AMD6. 4 without quotation marks.PROCESSORARCHITEW6.AMD6. 4. rem Currently running as 3.Windows Sys. WOW6.Launch CScript through Sysnative.System. RootSysnativecscript.System. RootSystem.If the script detects that it is running in a 3.Windows, it calls the 6.File System Redirector, by calling System.RootSysnativecscript.Otherwise, it calls the native cscript.System. 32 folder.Building the Configuration Manager Package.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |