1 hour ago
(This post was last modified: 42 minutes ago by Bowlsnapper.)
Easy XDK Installer V1.4.2
-------------------------------------------------------------
-------------------------------------------------------------
This is an easy way to turn your retail console into a debug kit. There are two main options:
1. Install the XDK dashboard as an "app", meaning that you will have the option to load the dash as an app which will be marked "XDK Launcher" in your apps list. This will boot the dash by booting a Debug version of Cerbios through PBL, which forces the load of the XDK dashboard. This is the safest option, as you have an option in the installer to simply remove this. It is what's recommended for new users who don't know if they even want to run the XDK or are unsure if they want to commit the console they have to it entirely. I foresee a LOT of people using this option.
2 "Standalone mode" turns the console into a full-on, dedicated debug kit. This will wipe your C and E partitions and will end up dedicating the console to this purpose, just like a legitimate MS "Debug Kit". Underneath the XDK Launcher, there is a basic dashboard installed with useful applications and all kinds of goodies which can be accessed through the "Retail" selection (Utilizing Pheonix Bios Loader) in the XDK Launcher. The XDK Launcher will be the default dashboard that you boot up to. The installer also provides the means to flash a debug enabled Cerbios bios through this option at the end of the install. Speaking of that:
Please use common sense when deciding whether to flash the debug bios at the end of the standalone install. If you decide not to flash, you will have a Cerbios Debug ini installed that still directs the bios to boot the XDK Launcher and boot into a debug environment. However, if you do not flash, the Cerbios bios you are using must obviously be hardcoded to read the ini/config file. You will probably know if you have intentionally flashed a bios that specifically ignores the ini, since this is a pretty obscure and rare thing to do, and if you don't know why you did it or that you've done it at all... then damn. If you are unsure what your Cerbios is hardcoded to do, just flash the bios at the end of the standalone install. It will be hardcoded debug, and you will not have any doubts as to what you have flashed. This choice was provided for the same reason that the "Application" and "Standalone" modes were created: Flexibility. If you don't want a hardcoded debug bios for any reason, you will be allowed to keep retail. You have been advised.
The installer menu items are pretty straightforward. Application mode and Standalone mode both are able to install with either the 4627 or 5849 XDK Launcher. Once you make a selection, simply "Install XDK & Setup XDK-Launcher". The rest takes care of itself. Its as easy as pie. I recommend the newest Launcher as this has the most compatibility with the Win XP SDK/XDK toolkit.
This should cover most case uses. However I will add features and modify the installer over time as I receive feedback. I am researching softmods, although installing on a softmod is not an ideal situation, for a few reasons. One of them being memory.
The only real requirements for this install is 128MB of RAM. This will allow you to have the overhead necessary to run the debug environment and still be able to use the full stock 64MB of RAM that most consoles do. This can even be installed on a console with a stock 8GB HDD. MS Debug Kits were equipped with this. If you don't have 128MB of RAM... The XDK launcher will boot, but your experience will be unstable to varying degrees and I do NOT recommend it. If you would like to use a SuperIO serial debugger, I would recommend performing a TSOP flash and keeping the pin header free for the ribbon cable. LPC breakout boards DO exist however, and this may be an option for you to consider so that you can have a modchip AND have a pin header for the SuperIO. I describe how I built my development kit with SuperIO in the thread I linked below. I absolutely encourage you to build one as it is a satisfying project and super cool to say that you did!
Also included is every single piece of software imaginable on the PC side. Everything from Windows XP itself, to Visual Studio 2003, to the MS VS2003 XDK Installer, and of course, the Virtual Machine HDD image is linked below.
The XDK version numbers are a lie. 5849.16 is the latest version of the XDK.
Please remember: The HDD image is in VMDK file format and can be used with either VMware or VirtualBox. If you use VMware, download the VMware Tools ISO. It is version 10.0.0 and is compatible with XP. If you use VirtualBox, use the VirtualBox Additions ISO. These will install the respective drivers for your virtual machine and make the experience much more pleasurable and easy. Generic drivers suck! I recommend VirtualBox as they have a link provided for their software. VMWare isn't exactly free (although a free version can be found if you look hard enough) and they make tracking it down a pain. If somebody would like to locate it for me, please do.
Please do not use vx.dxt (VerifierX) in your "DXT" folder. It serves no purpose and causes some things to not load and to crash, namely anything Cromwell based like PBL or XBlast.
A LOT of this installer was coded by DarkDestiny. Although the collab is no longer a thing, it would feel wrong to not assign credit for this, as it would make it seem like I want people to believe that I was the sole coder of everything that was written. That is not the case and I do not want this to be misrepresented.
"Creating a Development Kit" OGXbox Thread Link: https://www.ogxbox.com/forums/index.php?...ment=67822
Installer Link:
Drive: https://drive.google.com/file/d/1aW9MXog...sp=sharing
Virtual Machine XDK HDD Image Link: https://drive.google.com/file/d/1Du_3Fk0...drive_link
VMWare Tools ISO: https://drive.google.com/file/d/1sQuSOaT...sp=sharing
VirtualBox Additions ISO: https://drive.google.com/file/d/1xXHHs7l...drive_link
--------------------------------------------------------------------------------------------
1.4.2
-Changed and added to all the readmes and further clarified
what everything is and what to be cautious of when using it.
-Cleaned up menu text and made things a little tiny bit neater.
That's pretty much it.
1.4.1
-Changed XML commentary, installer messaging and structure,
as well as finishing readme's for each section and adding further
explanation of operations so that people can have a better
understanding of what is being done and how.
-Added ability to say no to flashing Cerbios at the end of the
Standalone installs. It is a hardcoded debug bios that is flashed.
However, there is a debug ini that is installed anyway, so if you don't
want to flash a hardcoded debug Cerbios for any reason, you will be
given the choice not to flash and the debug ini will still enable you to
boot into the XDK launcher.
-Fixed a bug that copied the incorrect bios to HDD when selecting option
to flash back to retail bios under "Back to Retail" section.
fdrive.rar (Size: 915 bytes / Downloads: 0)
1. Install the XDK dashboard as an "app", meaning that you will have the option to load the dash as an app which will be marked "XDK Launcher" in your apps list. This will boot the dash by booting a Debug version of Cerbios through PBL, which forces the load of the XDK dashboard. This is the safest option, as you have an option in the installer to simply remove this. It is what's recommended for new users who don't know if they even want to run the XDK or are unsure if they want to commit the console they have to it entirely. I foresee a LOT of people using this option.
2 "Standalone mode" turns the console into a full-on, dedicated debug kit. This will wipe your C and E partitions and will end up dedicating the console to this purpose, just like a legitimate MS "Debug Kit". Underneath the XDK Launcher, there is a basic dashboard installed with useful applications and all kinds of goodies which can be accessed through the "Retail" selection (Utilizing Pheonix Bios Loader) in the XDK Launcher. The XDK Launcher will be the default dashboard that you boot up to. The installer also provides the means to flash a debug enabled Cerbios bios through this option at the end of the install. Speaking of that:
Please use common sense when deciding whether to flash the debug bios at the end of the standalone install. If you decide not to flash, you will have a Cerbios Debug ini installed that still directs the bios to boot the XDK Launcher and boot into a debug environment. However, if you do not flash, the Cerbios bios you are using must obviously be hardcoded to read the ini/config file. You will probably know if you have intentionally flashed a bios that specifically ignores the ini, since this is a pretty obscure and rare thing to do, and if you don't know why you did it or that you've done it at all... then damn. If you are unsure what your Cerbios is hardcoded to do, just flash the bios at the end of the standalone install. It will be hardcoded debug, and you will not have any doubts as to what you have flashed. This choice was provided for the same reason that the "Application" and "Standalone" modes were created: Flexibility. If you don't want a hardcoded debug bios for any reason, you will be allowed to keep retail. You have been advised.
The installer menu items are pretty straightforward. Application mode and Standalone mode both are able to install with either the 4627 or 5849 XDK Launcher. Once you make a selection, simply "Install XDK & Setup XDK-Launcher". The rest takes care of itself. Its as easy as pie. I recommend the newest Launcher as this has the most compatibility with the Win XP SDK/XDK toolkit.
This should cover most case uses. However I will add features and modify the installer over time as I receive feedback. I am researching softmods, although installing on a softmod is not an ideal situation, for a few reasons. One of them being memory.
The only real requirements for this install is 128MB of RAM. This will allow you to have the overhead necessary to run the debug environment and still be able to use the full stock 64MB of RAM that most consoles do. This can even be installed on a console with a stock 8GB HDD. MS Debug Kits were equipped with this. If you don't have 128MB of RAM... The XDK launcher will boot, but your experience will be unstable to varying degrees and I do NOT recommend it. If you would like to use a SuperIO serial debugger, I would recommend performing a TSOP flash and keeping the pin header free for the ribbon cable. LPC breakout boards DO exist however, and this may be an option for you to consider so that you can have a modchip AND have a pin header for the SuperIO. I describe how I built my development kit with SuperIO in the thread I linked below. I absolutely encourage you to build one as it is a satisfying project and super cool to say that you did!
Also included is every single piece of software imaginable on the PC side. Everything from Windows XP itself, to Visual Studio 2003, to the MS VS2003 XDK Installer, and of course, the Virtual Machine HDD image is linked below.
The XDK version numbers are a lie. 5849.16 is the latest version of the XDK.
Please remember: The HDD image is in VMDK file format and can be used with either VMware or VirtualBox. If you use VMware, download the VMware Tools ISO. It is version 10.0.0 and is compatible with XP. If you use VirtualBox, use the VirtualBox Additions ISO. These will install the respective drivers for your virtual machine and make the experience much more pleasurable and easy. Generic drivers suck!
I recommend VirtualBox as they have a link provided for their software. VMWare isn't exactly free (although a free version can be found if you look hard enough) and they make tracking it down a pain. If somebody would like to locate it for me, please do.Please do not use vx.dxt (VerifierX) in your "DXT" folder. It serves no purpose and causes some things to not load and to crash, namely anything Cromwell based like PBL or XBlast.
A LOT of this installer was coded by DarkDestiny. Although the collab is no longer a thing, it would feel wrong to not assign credit for this, as it would make it seem like I want people to believe that I was the sole coder of everything that was written. That is not the case and I do not want this to be misrepresented.
"Creating a Development Kit" OGXbox Thread Link: https://www.ogxbox.com/forums/index.php?...ment=67822
Installer Link:
Drive: https://drive.google.com/file/d/1aW9MXog...sp=sharing
VMWare Tools ISO: https://drive.google.com/file/d/1sQuSOaT...sp=sharing
VirtualBox Additions ISO: https://drive.google.com/file/d/1xXHHs7l...drive_link
1.4.2
-Changed and added to all the readmes and further clarified
what everything is and what to be cautious of when using it.
-Cleaned up menu text and made things a little tiny bit neater.
That's pretty much it.
1.4.1
-Changed XML commentary, installer messaging and structure,
as well as finishing readme's for each section and adding further
explanation of operations so that people can have a better
understanding of what is being done and how.
-Added ability to say no to flashing Cerbios at the end of the
Standalone installs. It is a hardcoded debug bios that is flashed.
However, there is a debug ini that is installed anyway, so if you don't
want to flash a hardcoded debug Cerbios for any reason, you will be
given the choice not to flash and the debug ini will still enable you to
boot into the XDK launcher.
-Fixed a bug that copied the incorrect bios to HDD when selecting option
to flash back to retail bios under "Back to Retail" section.
fdrive.rar (Size: 915 bytes / Downloads: 0)