Jump to content

Recommended Posts

Easy-Build for XBOX Original

What is it?

A tool in testing for compiling xbox code. Easy to Update script.

https://github.com/Empyreal96/easy-build-xbox

spacer.png

How to use:

  • Have easy-build-xinit.cmd on the ROOT of a drive e.g: D:\easy-build-xinit.cmd
  • Open easy-build-xinit.cmd
  • Setup the Xbox trunk in your Drive root as specified in easy-build-xinit (VHD users are already set up)
  • Let the script apply Team Complex patches (These allow the xbox trunk to be built)
  • Once that's done, follow onscreen instructions until Razzle loads
  • Type into razzle: easybuild
  • You can now build from the Easy-Build mainmenu
  • Built binaries will be in %DriveRoot%\xbox\xboxbuilds\fre{dump}

Any issues or suggestions please open an issue ticket so I can look into it

Information

 

  • Windows XP - 10 x86

  • Fixed issues with mstools/idw folders incorrectly being set

  • Basic Options for compiling

  • 'Unofficial' binplace script 'xcopybins.cmd' to place some built files

  • Added 'xmakesamples.cmd' which builds the XDK Sample CD.

  • Added a WIP script to set off the XDK build see XDK below
  • Fixed %_BUILDVER% not being set on razzle-easybuild handover
  • Changed menu colours (I may change back depending on feedback)
  • Small update to some 'dirs' files that adds folders to the build process that can build successfully
  • Separated easybuild.cmd (mainmenu) to public/tools/
  • Actual easybuild.cmd shows correct Razzle Tool Path now, starts xcopybins.cmd as postbuild

XDK Building 

InstallShield Professional 6.2 is required for this: I have included my currently in progress script to try and build the Xbox SDK. Currently it fails compiling the InstallShield specific XDK Setup scripts..

  • To run the script, load Easy-Build, drop to Razzle prompt and type "private\SDK\setup\xsdkbuild.cmd"

If you want to help the development of Easy-Build, have some issues join the Matrix chat!

https://matrix.to/#/!febkSwamiedCsfevDe:matrix.org?via=matrix.org

NOTE: This is VERY early stages.. It is lacking in many features that Easy-Build-NT5 has.. If I get time I will eventually figure out more of the build system, any and all help is greatly welcomed!!

  • Like 3
Link to post
Share on other sites

Theres been a small update, mainly to test the log outputs and placing another thing from the src

• Postbuild scripts now have 'basic' logs in the %_NT386TREE% folder

• Added copying 'HVS Launcher Test' files (not sure what this is)

• Added two more buildable directories in "private\sdktools\factory"

Link to post
Share on other sites

This is awesome work!

I fetched your git tree and vhd last night and attached it to my Win XP vm and had no issues (beyond the warnings you mentioned) doing a clean build.

I'm sure you have looked around too, but to get some info out there, it appears that the installer for IS Pro 6.20 and 6.21 were likely distributed as "InstallShieldProfessional620.exe" and "InstallShieldProfessional621.exe", while 6.22 may have been distributed as "IPSE622.exe". The installer was probably around 95mbs in size. This is all speculation based on archives of warez pages from twenty years ago.

While I still can't find the installer itself, here is some information on how to crack it when you do.

Edited by ShamedSalmon
  • Like 1
Link to post
Share on other sites
7 hours ago, ShamedSalmon said:

This is awesome work!

I fetched your git tree and vhd last night and attached it to my Win XP vm and had no issues (beyond the warnings you mentioned) doing a clean build.

I'm sure you have looked around too, but to get some info out there, it appears that the installer for IS Pro 6.20 and 6.21 were likely distributed as "InstallShieldProfessional620.exe" and "InstallShieldProfessional621.exe", while 6.22 may have been distributed as "IPSE622.exe". The installer was probably around 95mbs in size. This is all speculation based on archives of warez pages from twenty years ago.

While I still can't find the installer itself, here is some information on how to crack it when you do.

Thanks!! I'm glad it runs on XP fine, I only tested it myself on 10 x86 😁

 

Yeah I actually found a copy of InstallShield 6.2 on archive org (I think it was archive .org) it works but it seems the actual IS script we compile is either incomplete or files for the XDK building are missing :( but I plan on messing with Installshield at some point to learn about these 'Language Independant Intel 32 Files' and why they appear to be missing..

 

Let me know if you test any of the xbe's and ISOs created with the tool 😁

  • Like 1
Link to post
Share on other sites
1 hour ago, KaosEngineer said:

Does your InstallShield installation have the Setup.exe [??? template (is it a template don't know 4 sure) ???] file in the Redist\Language Independent\i386\ folder?

I think so yeah, I will double check this weekend as got my new laptop today so I can crack on with this and NT5

 

I think it is like you think though with some template files missing

Link to post
Share on other sites
3 hours ago, KaosEngineer said:

There is a file, IS622PROSTD.zip (google it), out there on the Internet (includes serial number).

Welp, I'm embarrassed for not checking there first, since I had fetched a few other things from that site earlier, lol. Thank you so much for pointing this out! It would appear that this is one and the same as the binary I was searching for in those dead warez archives, down to the matching password and serial number.

I'll pick the installer apart with unshield and some other stuff to see what we've got, but I did just finish installing it in an XP vm. My directory tree sounds a little different from yours though. Below is a tree view of some files that I believe we may be talking about, though I'm not entirely sure yet. I've gotta run now, but when I get home tonight, I'll sit down and start combing over those build warnings. (And of course, deep apologies if I'm not providing any helpful information. If need be, let me know and I will certainly cut this out.)

Folder PATH listing for volume Root

C:\Program Files\InstallShield:

    +---Professional - Standard Edition
    |   +---CABData
    |   +---Dialog Sampler
    |   +---Examples
    |   +---GeneralData
    |   +---GeneralLink
    |   +---Include
    |   +---Objects
    |   +---Program
    |   +---Redistributable
    |   |   +---Compressed Files
    |   |   |   +---0009-English
    |   |   |   |   +---Intel 32
    |   |   |   |   \---OS Independent
    |   |   |   \---Language Independent
    |   |   |       +---Intel 32
    |   |   |       \---OS Independent
    |   |   |           \---Corecomp.ini
    |   |   +---Uncompressed Files
    |   |   |   +---0009-English
    |   |   |   |   +---Intel 32
    |   |   |   |   \---OS Independent
    |   |   |   \---Language Independent
    |   |   |       +---Intel 32
    |   |   |       \---OS Independent
    |   |   \---Web Files
    |   |       \---Language Independent
    |   |           +---Intel 32
    |   |           \---OS Independent
    |   \---Script
    \---Professional - Standard Edition Setup Files
        \---Disk1
            +---Setup.exe
            +---Setup.ini
            \---setup.inx

In short, are you two referring to Setup.ini and binary Setup.inx, or maybe to the Corecomp.ini, or possibly even something else I'm not seeing?

7 hours ago, empyreal96 said:

Let me know if you test any of the xbe's and ISOs created with the tool 😁

Absolutely, I will! I'll get to some testing this weekend.

Thanks everyone!

Edited by ShamedSalmon
Link to post
Share on other sites
3 hours ago, ShamedSalmon said:

Welp, I'm embarrassed for not checking there first, since I had fetched a few other things from that site earlier, lol. Thank you so much for pointing this out! It would appear that this is one and the same as the binary I was searching for in those dead warez archives, down to the matching password and serial number.

I'll pick the installer apart with unshield and some other stuff to see what we've got, but I did just finish installing it in an XP vm. My directory tree sounds a little different from yours though. Below is a tree view of some files that I believe we may be talking about, though I'm not entirely sure yet. I've gotta run now, but when I get home tonight, I'll sit down and start combing over those build warnings. (And of course, deep apologies if I'm not providing any helpful information. If need be, let me know and I will certainly cut this out.)



Folder PATH listing for volume Root

C:\Program Files\InstallShield:

    +---Professional - Standard Edition
    |   +---CABData
    |   +---Dialog Sampler
    |   +---Examples
    |   +---GeneralData
    |   +---GeneralLink
    |   +---Include
    |   +---Objects
    |   +---Program
    |   +---Redistributable
    |   |   +---Compressed Files
    |   |   |   +---0009-English
    |   |   |   |   +---Intel 32
    |   |   |   |   \---OS Independent
    |   |   |   \---Language Independent
    |   |   |       +---Intel 32
    |   |   |       \---OS Independent
    |   |   |           \---Corecomp.ini
    |   |   +---Uncompressed Files
    |   |   |   +---0009-English
    |   |   |   |   +---Intel 32
    |   |   |   |   \---OS Independent
    |   |   |   \---Language Independent
    |   |   |       +---Intel 32
    |   |   |       \---OS Independent
    |   |   \---Web Files
    |   |       \---Language Independent
    |   |           +---Intel 32
    |   |           \---OS Independent
    |   \---Script
    \---Professional - Standard Edition Setup Files
        \---Disk1
            +---Setup.exe
            +---Setup.ini
            \---setup.inx

In short, are you two referring to Setup.ini and binary Setup.inx, or maybe to the Corecomp.ini, or possibly even something else I'm not seeing?

Absolutely, I will! I'll get to some testing this weekend.

Thanks everyone!

No problem! I kept forgetting it existed but  now I rely on it 🤣 

 

Yeah that's the same tree I worked with just installed as was in the source setup, with the different installation path, just modify "xbox\private\SDK\setup\xsdkbuild.bat" 

It has paths set for the "Default" they used with the source so we can change it to where ever if needed 😁

 

And the files I think are in the "xbox\private\SDK" folder somewhere, I think it was called setup.rul or something, that folder has the IS Build script and specific XDK setup libraries and headers

Edited by empyreal96
Missed a section
  • Like 1
Link to post
Share on other sites

For anyone interested I have been looking at the SDK building.. I think it requires a lot of external files.

In "xbox\private\SDK\setup\file groups\" it different lists of files to pull, these look in several places it seems:

- "Binaries.X86FRE" which is related to NT builds (possibly the NT 5 Workstation/Beta 2 codebase)

- "Extras\D3DIM\Tools\Maya25" this at face value seems like a tool for Direct3D (need to look in to it more)

- "3dsmax" it needs source files from 3DSMax

- "DMUSProducer" this a Direct Media Producer? (Need to look into this too)

- "VisualStudio" some binaries and source files/headers from Visual Studio (not sure on version yet)

 

Most look in an "sdkfiles" folder which compared to "private\SDK\sdkfiles" is missing quite a lot.. but it could be reconstructed I imagine

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By empyreal96
      *Disclaimer: No links to file will  be provided, this is for discussion only*
      Not sure if anyone has yet, but I have been running a diff between Barnabus Kernel Repack and the 4400 leak Kernel Tree..
      I've only just started looking through, and I have next to no C++, C and C# coding skills so bear with me lol
       
      They seem somewhat the same, but there are quite a few files with parts of code removed or added, on both branches. But Barnabus is reliant on precompiled objects (obviously as it's a smaller, almost stripped down and made 'easy' release of the full tree)
      There are some comments in Barnabus code that isn't in the full tree + CPXXUPD code, and some are recorded more 'formally'
      (i.e private\ntos\init\init.c line 244 - 254 in both branches)
      One other thing is the 4400 tree is set to have 'complex's' edits definable where possible, which there are a lot..
       
       
      One thing that really interests me, is Barnabus uses BIOSPack to pack: 2bl, remainder and kernel into a 'Working' rom (I use that word loosely).
      The 4400 tree uses rombld, which requires: preloaded, init table, bootloader, kernel and a rom decode file(I think).. this is a drastic difference to BIOSPack.. But the main issue with Rombld is it will not produce a full rom.. by default it will error on the 'preloader' being to big (9008 bytes not 1664 bytes)..
      To get around that, we can either build for XDK Systems.. 
      Or as I discovered today: modify 'private\sdktools\rombld\rombld.cpp' Line 879 from (2 * 1024) to (21 * 512), to allow rombld to accept the 9kb preloader file.. (I haven't tested a bios rom built with this edit yet)
       
      I will post here anything else I discover! 
    • By eustachy1973
      My modest modification.
       

       

       

       
      128MB Ram

       
      New Fan
       

       
       
      Open Xenium Chip with Ryzee119's XEnium Spi2par2019
       

       

       


       

       

       

      To be continued...
       
    • By Dougmeister
      It has literally been over 10 years since I've played it. One of the bootup screens says "Xecutor2" at the bottom, so that tells me that much at least.
      My main question is the three (3) dip switches on the front of the console. Someone else installed it for me, and I forget what each of them does.
      I think that the left-most one controls whether or not the modchip is active; you wanted to toggle that one off if you ever went onto XBox Live, I think.
      Can anyone help?

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.