How to change this program.
	Needed tools:
		<ul><li>Microsoft Xbox (Software) Development Kit (XDK) (a software package)
		</li><li>What the XDK requires
			<ul><li>Windows 2000 or Windows XP. Windows 98 Second Edition WILL NOT WORK.
			</li><li>Microsoft Visual Studio (It is not known by the author of this document how well Visual C++ without the rest of Visual Studio.)
The version of Visual C++ needed depends on what version
				of the XDK you have.

				<ul><li>XDK version 4361 requires Visual Studio Service Pack 4 or 5 (not 6)
					<ul><li>Note that any version of Visual Studio 6 prior to SP 4 should work since you should be able to <A HREF="http://msdn.microsoft.com/vstudio/downloads/updates/sp/vs6/sp5/">download Visual Studio 6.0 Service Pack 5</A>.
						Note: XDK version 4361's install file said it needed SP4 or SP5.  The Readme said it needed SP5 and Win2K. It did work in Windows XP. It did not install when Visual Studio .NET was installed.
					</li><li><A HREF="msdn.microsoft.com/vstudio/sp/vs6sp5/vcfixes.asp">VC Fixes</A>
					</li><li>The freely-downloadable
The <A HREF="http://msdn.microsoft.com/vstudio/downloads/tools/ppack/default.aspx">Visual Studio Processor pack</A>.  Note that it has been said <A HREF="http://blogs.msdn.com/brianjo/archive/2004/04/04/107365.aspx">&quot;</A>
There is no processor pack for SP6 nor will there be. If you need the processor pack features you need to continue using SP5, or upgrade to VC7/7.1 which integrates the processor pack features directly.<A HREF="http://blogs.msdn.com/brianjo/archive/2004/04/04/107365.aspx">&quot;</A>  Therefore, it seems that VS 6.0 SP 6 (as downloaded from the web) will not work.
<p>
Straight from Microsoft: <A HREF="http://msdn.microsoft.com/vstudio/downloads/tools/ppack/default.aspx">&quot;
<b>Each individual download is compatible only with the specific referenced Visual Studio 6.0 Service Pack. Future releases of the Visual C++ 6.0 Processor Pack will be integrated into and shipped with corresponding versions of the Visual Studio 6.0 Service Pack CDs. The Visual C++ 6.0 Processor Pack is not included in the current versions of the Visual Studio 6.0 Service Packs downloadable from the web.</b>&quot;</A>  Hmm, that makes it sound like the VS 6.0 SP 6 CD would have the processor pack.  However later on the page, Microsoft says the processor pack is mutually exclusive with SP 6 (each one will cause the other to no longer function).
</p>
					<A HREF="http://msdn.microsoft.com/vstudio/downloads/tools/ppack/default.aspx">&quot;Users must also be running Windows 98, Windows NT 4.0, or Windows 2000.&quot;</A>  (Not XP?!?)
				</li></ul>
			</li><li>Some versions (such as v5558 - June 2003) will require Visual Studio .NET or .NET 2003 (not just Visual Studio 6).
		</li></ul>
	</li><li>An Xbox to run unsigned code, needed solely for testing
	</li></ul>
	</li><li>The source code for this program
	</li><li><A HREF="http://bcl.sf.net">Basic Compression Library</A> (BCL 1.0.6 has been used and tested.)
</li></ul>




	Step 1: Creating an XBE file
	Step 2: Creating a decently small XBE file
	Step 3: Modifying the code

<h1>Step One: Creating an XBE File</h1>
		

I found the Visual C++ project files useless. Visual C++ 6.0 couldn't load
the project. Visual C++ .NET 2003 (Visual C++ 7.10) had to convert the files
from an old version. When they did, the project was converted partially into
a Windows program, and to make a long story short, it didn't work.

<ul><li>
	New Xbox Project
		<ul><li>
			Make new Xbox Game:
			<ul><li>Visual Studio .NET 2003:
                        File, New, Project. Xbox Project, (give path and name), OK.
                        The overview screen said I was making an Xbox Game. Finish.
                        </li><li>Visual Studio 6.0: File, New, Project. Xbox Game.
			</li></ul>
		</li></ul>
	</li><li>
		Add all source files from the archive and the XDK
		<ul><li>Visual Studio .NET 2003:
			<ul><li>
				Copy the files from the collection of source code, into the project's
        	                directory. This should overwrite stdafx.cpp and .h, and XSelector.cpp.
				DO NOT OVERWRITE XSelector.vcproj or XSelector.sln!
			</li><li>
				Project, Add Existing Item...
			</li><li>
				Using Visual C++ .NET 2003, I fid the following:
				<ul><li>Unzipped the source code (from XSelector 0.6).
				</li><li>
				Added the following source files:
					<ul><li>Menu.cpp
						</li><li>Tahoma_14.cpp
						</li><li>XSelector.cpp
						</li><li>stdafx.cpp
						</li><li>utils.cpp
						</li><li>xbfont5.cpp
						</li><li>xbfont_mxm.cpp
						</li><li>xbresource_mxm.cpp
						</li></ul>
        	                </li><li>Header Files:
       	        	                <ul><li>Menu.h
						</li><li>StdString.h
						</li><li>Tahoma_14.h
						</li><li>XSelector.h
						</li><li>stdafx.h
						</li><li>utils.h
						</li><li>xbfont5.h
						</li><li>xbfont_mxm.h
						</li><li>xbresource_mxm.h
						</li><li>xntdll.h
						</li><li>(did not import XKExports.h)
                	                </li></ul>
				</li><li>
	                                View, Solution Explorer. Right click on the "XSelector" (2nd item). Add New
        	                        Folder. Name it "Common Items". Right click the new folder. Add, Existing
					items:
					<ul><li>\Program&nbsp;Files\ Microsoft&nbsp;Xbox&nbsp;SDK\ Samples\Xbox\Common\Src\xbinput.cpp
						</li><li>\Program&nbsp;Files\ Microsoft&nbsp;Xbox&nbsp;SDK\Samples\Xbox\Common\Src\xbutil.cpp
					</li></ul>
				</li></ul>		
			</li></ul>
	
		</li><li>Visual Studio 6.0:
			<ul><li>
                                Project, Add To Project, Files. Put all files in source code package into
                                the project's directory. Highlight all of them in Visual C++ except for XKExports.h.
				Select OK to add.
			</li><li>Add \Program&nbsp;Files\ Microsoft&nbsp;Xbox&nbsp;SDK\ Samples\Xbox\Common\Src\xbinput.cpp and xbutil.cpp
			</li></ul>
                Double click on "stdafx.h". Make sure it includes eight files, not just one.
Otherwise, the wrong stdafx.h file is being looked at: Fix this somehow
(it should be in the same Relative Path as stdafx.h)
		</li></ul>
	</li><li>Add files from <A HREF="http://bcl.sf.net">Basic Compression Library</A> 1.0.6

	</li><li>

	Include files:
		<ul><li>
			VS .NET 2003:
	                <ul><li>Tools, Options, Projects, VC++ Directories. Platform: Xbox. Show Directories
for: Include Files. New Line (Ctrl-Insert, the "New Folder" icon),
\Program&nbsp;Files\ Microsoft&nbsp;Xbox&nbsp;SDK\ Samples\Xbox\Common\Include
				<ul><li>OK
				</li></ul>
	                </li></ul>
		</li><li>VS 6:
			<ul><li>
			Tools, Options, Directories, Xbox, Include Files, click on the "New" icon,
			\Program&nbsp;Files\Microsoft&nbsp;Xbox&nbsp;SDK\Samples\Xbox\Common\Include
			</li></ul>
		</li></ul>
	</li><li>
	Pre-Compiled Headers off
		<ul><li>Visual Studio .NET
			<ul><li>Project, XSelector Properties.
			</li><li>Configuration: Make it say "All Configuration" (not "Debug").
			</li><li>Configuration Properties, C/C++, Precompiled Headers.
			</li><li>Change Create/Use Precompiled Header to Not Using
				Precompiled Headers
        	        </li></ul>
		</li><li>
		Visual Studio 6
			<ul><li>Project, Settings.
			</li><li>Settings for: All Configuration
                        </li><li>Post-Build Setup: ftp -s:textfile (have text file be an FTP script). (This has
				nothing to do with Pre-Compiled Headers)
			</li></ul>
		</li></ul>
	</li><li>Ensure all went okay so far.
		<ul><li>Build, Build XSelector
		</li></ul>
	</li><li>You should have this compile perfectly, although in VS Studio .NET 2003 the Link stage may give two
errors (and an error summary):
			<ul><li>error LNK2019: unresolved external symbol "class CStdStr<char> __cdecl operator+(class CStdStr<char> const &,class CStdStr<char> const &)" (??H@YA?AV?$CStdStr@D@@ABV0@0@Z) referenced in function "class CStdStr<char> __cdecl MakeFullDirPath(char const *,char const *,int)" (?MakeFullDirPath@@YA?AV?$CStdStr@D@@PBD0H@Z)
			</li><li>error LNK2019: unresolved external symbol "class CStdStr<char> __cdecl operator+(char const *,class CStdStr<char> const &)" (??H@YA?AV?$CStdStr@D@@PBDABV0@@Z) referenced in function "unsigned long __cdecl LaunchTitle(char const *,char const *,struct _LAUNCH_DATA *)" (?LaunchTitle@@YAKPBD0PAU_LAUNCH_DATA@@@Z)
			</li><li>fatal error LNK1120: 2 unresolved externals
			</li></ul>
		Resolution:
			<ul><li>To resolve this, define __SUNPRO_CC_COMPATright
                                <ul><li>click on the "Header Files" folder. Select
Add, Add New Item. Click on the "Header File (.h)" icon, and name the file
CStdString.h. Copy and paste the contents of StdString.h into OlStdString.h
and save.
				</li><li>Once you have the contents saved in OlStdSring.h, delete all of
the contents of StdString.h and then put in the following two lines:
					<ul><li>#define __SUNPRO_CC_COMPAT
					</li><li>#include "OlStdString.h"
					</li></ul>
				</li><li>Save the file with just those two lines.
				</li></ul>
			</li></ul>
		</li></li>
		Update
			<ul><li>
				Although I found SUNPRO_CC_COMPAT was not required in VC++ 6,
					it did help make the executable smaller. As such, I
					have modified other files, so this shouldn't even be
					an issue anymore.
			</li></ul>
		</li></ul>
	</li><li>Build, Build XSelector.
	</li><li>Now when you build, you should get "error X1001: Could not connect to Xbox".
		<ul><li>Select Project, XSelector Properties.
		</li><li>Configuration: Make it say "All Configuration" (not "Debug").
		</li><li>Configuration Properties, Debugging, Remote Settings, Skip Deployment, Yes.
		</li></ul>
		In Visual Studio 6.0, this will appear as
			<ul><li>"Transferring file to Xbox...xe:\Dirctory\Filename.xbe
			</li><li>error M1001: No address for Xbox has been set"
			</li></ul>
		To solve:
			<ul><li>Visual Studio .NET
				<ul><li>Project, Settings, Debug, General, Remove executable path and file name:
					Set to something that doesn't start with xe:\.
        	                </li><li>That didn't work.  SDK documentation says to run:
					cmd.exe, then xbdir -x name xe:\ (where "name" can be an IP address)
					(Bad Suggestion: try the name of 127.0.0.1)
				</li><li>If you are connected to an Xbox running Evolution-X RemoteX 3935, VS 6
        	                        won't report any errors, won't report any problems. However, it does
                	                not successfully transfer the X.XBE file. If, on the other hand, you
					use xbdir on an IP address that doesn't have an Xbox running Evo-X
					RemoteX (like if you refer to your own machine using the common
					loopback address of 127.0.0.1), the X.XBE file will still be created
					but VS6 will show an error about connecting to the Xbox.
					(Either way, the X.XBE file is created on your local hard drive, and
					that's what matters.)
				</li></ul>
			</li><li>Visual Studio 6
				<ul><li>No workaround for this was found. The XBE file is
					created on the local system, though. Adaption was
					made to the reality that there would be an error in
					the build process every time. It was just hoped, with
					each build, that the error would be an error
					connecting to the Xbox rather than some other error.
				</li></ul>
			</li></ul>
	</li><li>Build, Build Selector.
	</li><li>Now you should see the following three lines (with some other information as well):
		<ul><li>Creating Xbox Image...
		</li><li>---------------------- Done ----------------------
		</li><li>    Build: 1 succeeded, 0 failed, 0 skipped
		</li></ul>
	</li><li>Enjoy the 1,822,720 bytes big XSelector.XBE.
	</li></ul>





<h1>Step Two: Creating A Decently Small XBE File</h1>

<ul><li>Set configuration mode to be release, not debug.
        <ul><li>VS .NET 2003: Project, XSelector Properties. Configuration Manager. Active Solution Configuration. Change from Debug to Release.
	</li><li>VS 6.0: Build, Set Active Configuration
	</li><li>
        This may change some of the other Project Properties. Hopefully earlier
you did select "All Configurations" so that "Skip Deployment" and
"Use Pre-Compiled Headers" are set correctly.
Project, Properties, Release. Xbox Image. Include Debug Info: No.

	</li></ul>

</lio><li>Rebuild
	<ul><li>VS .NET 2003:
                <ul><li>Select Build, Clean XSelector. Then Build, Build XSelector.
		</li><li>Or just do Build, Rebuild XSelector.
		</li><li>
		</li></ul>
	</li></ul>
Enjoy a 319,488 bytes big XSelector.XBE in the RELEASE (not the DEBUG) directory.
(Note: I also did this:)
Select Project, XSelector Properties. Configuration. Release (not Debug).
</li></ul>



<h1>Step Three: Making a better XBE file</h1>

<ul><li>
        Create a *.XBE designed for a retail Xbox, not a Debug Xbox. This won't matter much
		for XBE's run under mod chips, but this will affect XBE's run using the retail
		BIOS (such as those that get run from a saved game exploit).
	<ul><li>
                Run XBEPatch.EXE file.xbe. This modifies file.xbe (doesn't make a new copy of the file).
	</li></ul>
</li><li>
        Make an executable that xbedump.exe will like. (Note: Skip this part if you intend to use xbepack!)
	(Note: Skip this part even if you don't intend to use XBEPack. This does make the
	XBE un-XBEPackable, and XBEDump's tests aren't worth worrying about. VC++ seemed to
	do better at making XBE's that passed XBEDump's tests even without CXBE needed.)
	<ul>
		<li>Download <A HREF="http://dwl.xbox-scene.net/~xbox/xbox-scene/tools/development/cxbe-0.2.0.zip">CXBE Relinker</A> (as named on <A HREF="http://www.caustik.com/xbox/news.htm">the author's home page</A>, but he says he for some reason likes that the program has the same number of letters as cxbx, and this program is sometimes just called <A HREF="http://www.xbox-scene.com/tools/tools.php?page=development#newsitemEpFAAEAEuEBoLJDptb">CXBE</A>)
		</li><li>Make sure you can get an EXE version of your program
		<ul><li>In my experience, Visual C++ makes this automatically
			</li><li>It seems there's a program called <A HREF="http://dwl.xbox-scene.net/~xbox/xbox-scene/tools/development/XbeTool.zip">XbeTool</A> (<A HREF="http://www.loser-console.org/">homepage</A>) which, 
			<A HREF="http://www.xbox-scene.com/tools/tools.php?page=development#newsitemEpFVEupEkkRAqOHogh">according to Xbox-Scene.com</A>, can convert *.XBE files to *.EXE files
		</li></ul>
	</li><li>Run CXBE on the *.EXE file
	</li><li>The resulting *.XBE file passes XBEDump's header size test
	</li></ul>

</li><li>
	Sign the code using XBEDump.EXE
		<ul><li>Users of any font-based hack may want the executable signed with the font hack key.
		</li><li>Users of any audio hack may want the executable signed with an audio hack key.
		</li><li>Users of game exploits may want the executable signed with a game exploit ("habibi") key.
			It seems that the habibi keys and audio hack keys may be at least somewhat interchangable (I think
                        some audio hack used the habibi key). Or maybe that's just because I have used them so
			often that I just forget when I use what.
		</li></ul>
        Note: Don't worry about XBEDump complaining about failing XBE file integrity. XBEDump runs numerous
		tests on the XBE file, and there are times when it may see something that it doesn't expect
                and so XBEDump will call the file invalid. In reality, XBEDump's tests are imperfect.
</li><li>
        Run XBEPack. Note that this may make the XBE less compatible.
</li></ul>


<h1>Creating A Really Small XBE File</h1>


<ul><li>Download <A HREF="http://www.xbox-scene.com/tools/tools.php?page=development#newsitemEpyuklVEppBjXOeexP">XBEPack</A>, version <A HREF="http://dwl.xbox-scene.net/~xbox/xbox-scene/tools/development/xbepack-0.2.tgz">0.2</A> (latest). The <A HREF="http://dwl.xbox-scene.net/~xbox/xbox-scene/tools/development/xbepack-0.2-win32.rar">Win32 port</A> seems to crash on Windows 98 Second Edition.
</li><li>I'm hoping that XBEPack will be able to work with this now.
</li></ul>