KaosEngineer
-
Posts
5,063 -
Joined
-
Last visited
-
Days Won
479
Everything posted by KaosEngineer
-
Not a donation - a membership. Donations do not gain immediate download access or other perks of either level of paid membership.
-
Go straight into Chimp 261812, not sure what this 5 minute wait's all about. The new version doesn't use linuxboot.cfg. All the files are self contained in the subfolder where it is installed: Changes.txt (not actually required to run Chimp 261812) config.cfg default.xbe initrd.gz linux267 Chimp 261812 must be installed on the E drive (e.g., in E:\Apps\Chimp or E:\Chimp). Edit: here's the entire list of locations it can run from: E:\applications\chimp E:\applications\chimp loader E:\apps\chimp E:\apps\chimp loader E:\chimp E:\chimp loader
-
The new version of Chimp prompts you when to connect the new hard drive (SLAVE device) after you start it.
-
The latest version of Chimp does not require linuxboot.cfg to be installed to E:\ and the rest of the app in a subfolder of E. Download Chimp 261812 and use it instead of the older version you are trying to run. https://github.com/Rocky5/Chimp261812/
-
yeah, other modchips allow flashing a newer BIOS. There's probably a way to wire a flash programmer to the Xecuter 1 but no information was ever released to do so. You could unsolder the flash chip and program it with an external programmer then solder it back.
-
24" (60cm) high-speed 80-wire 40-pin IDE cable. ChimericSystems.com sells some that may even be spaced correctly for the Xbox: https://www.chimericsystems.com/product/24-ide-cable
-
How did you burn/write the dot ISO file to a DVD-R disc? If you load the disc into a PC, do you see a directory listing or get an error accessing the disc?
-
You will have to use an installer disc (boots a replacement dashboard so you can have access to the Xbox's hard drive). An Installer disc is just a bootable customized version of either Evoxdash or UnleashX that automates the process of installing a replacement dashboard to the Xbox's hard drive. HeXEn is one of the more popular most-hated installer disc as it changes and installs items to the hard drive you didn't ask for. Slayer's Evox Installer disc is another popular but older installer disc. You could make your own as well by placing a properly configured version of UnleashX or Evoxdash (depends how you want an IP addres to be assigned - statically (manual) or via DHCP. Adding some filler files and creating an XISO disc image then burning that disc image to DVD-R media. Boot the disc when the modchip is activated then copy the files from the disc to the xbox's hard drive or FTP them over to the Xbox. Which modchip do you have? Which modified xbox BIOS is it booting? in the MS dashboard when the modchip is activated, check the Settings > System Info menu option for the Kernel value displayed at the end of the copyright scroller. K: 1.00.KKKK.DD <-- what value do you see?
-
Best solution would be to copy via FTP to the E drive all of the Xbox Softmodding Tool saves, uninstall the xecuter 1 modchip from the motherboard, softmod the console using one of the 4 exploitable original game discs then flashing the TSOP on the motherboard with one of the latest BIOS versions: Evo-X M8plus F and G (.67) iND-BiOS 5003.67 iND-BiOS Beta Feb-11-05 (aka 5004.67) X2 5035
-
The Xecuter 1 modchip that he has installed cannot be reflashed (at least by normal methods of using Evoxdash Xbox. And, IIRC, the BIOS is scrambled iin the flash chip and is descrambled by the CPLD device on the modchip when it is loaded across the LPC bus on boot up. There is a program to scramble a BIOS for the Xecuter 1 but I'm not sure how you go about writing it to the flash chiip without an external programming device.
-
It's the BIOS that the Xecuter 1 has. It does not support LBA48 and larger cluster allocations. You will be limited to a maximum of 137GB and 16KB clusters. When Hexen boots, it loads a different BIOS into memory that does have LBA48 support so you see all the space and files you uploaded. But once you reboot, the hard drive access is once again limited to the original LBA28 137GBs accessible by the ancient Xecuter 1 BIOS. Update: The Xecuter1 BIOS doesn't know how to interpret the data stored at the location of the extended partition 6 that's using LBA48 access and larger cluster allocations. The directory is stored in a foreign language to it Therefore, since it does not recognize the F partition/drive's format, it shows 0 free space or the size of 0.
-
Go for the Blue no reason to spend anymore money on the hard drive than necessary. Get a good adapter: Startech IDE2SAT2 or DeLock 62510 and a 24" long 80-wire 40-pin high-speed IDE cable. If you do buy the cheap IDE-to-SATA adapters, buy at least 2 so hopefully you get at least one that works!
-
What's wrong with the web page that I posted in a reply of this thread to download it? Gamebrew.com's download link still works. https://www.gamebrew.org/wiki/Quake3_XBOX
-
I saw that post at assemblergames.com however the poster never elaborated on how to do so. I found this thread, [DIY tutorial] Matrix SPI nand flasher upgrade to CPLD (coolrunner/glitch chip) programmer @ se7ensins.com, maybe there's some info posted there that can help. Not using a NAND-X though.
-
I believe they are trying to reprogram the CPLD, Lattice LC4032V, on an Aladdin XT plus 2 with new code using the JTAG pads, not flashing the XBlast OS BIOS to a new SST49LF080 (1MB) flash memory chip.
-
You don't have to erase the old hard drive. First, softmod the console with the original drive then clone it to a new larger HDD using Chimp 261812.
-
There are no tools to resize an Xbox partition once it has been created. The BIOS has fixed sizes and locations for the C, E, X, Y and Z partitions used on the Xbox - the kernel - and possibly applications (games) expect them to be there. Making changes to the basic partitions is not guaranteed to work! Configuration area - No drive letter assigned (hidden) - Size: 512 KB - Starting Sector Offset: 0 Cache 1 - X drive - 750 MBs - 1,024 Cache 2 - Y drive - 750 MBs - 1,537,024 Cache 3 - Z drive - 750 MBs - 3,073,024 System Files (MS Dashboard) - C drive - 500 MBs - 4,609,024 Data: Game Saves, Soundtrack files, DLC - E drive - 4,895 MBs - 5,633,024 F starts right after the last sector of E, and G starts after the last sector of F. Max usable HDD space is ~2.2TB (2,199,023,255,040 bytes) . Limitation of the size of the counters fixed in the Xbox's BIOS/Kernel. Before the LBA48 patches were added to modify the Xbox's BIOS, the maximum hard drive size was limited to 137GBs - LBA28. The LBA48 patches are more like LBA32 since the counters used to hold the cluster address are limited to 32-bits, not 48.
-
Auto Installer Installer v4.53 | Full & Lite
KaosEngineer replied to dispunko's topic in Installation Disks
Try these two links to download the files from MEGA: Auto-Installer.Deluxe.v4.53.Xbox-Hq.7z.001 (1.66GB): https://mega.nz/folder/5SpQhSiK#HdyKDJ0KQjDu-krCYKgYaQ/file/VWgCgKLD Auto-Installer.Deluxe.v4.53.Xbox-Hq.7z.002 (300.5MB): https://mega.nz/folder/5SpQhSiK#HdyKDJ0KQjDu-krCYKgYaQ/file/dfpXHCTL Edit: Weird MEGA's so strange. When I click on either link it still goes to the folder and shows both files. why don't their links just start downloading each individual file as they should? Crazy! -
You use XPR Express. https://github.com/Rocky5/XBMC-Emustation/raw/master/Other/Tools/XPR Express.zip If that link doesn't work, it is available in the XBMC-Emustation repository under Other / Tools: https://github.com/Rocky5/XBMC-Emustation
-
No, there's too much DLC to fit on the limited space allocated for storing them on the Xbox hard drive - E drive/partition.
-
Looked up the Xecuter 1 BIOS info. It doesn't do much other than allow unsigned code to run. https://web.archive.org/web/20031002221543/http://www.xbox-scene.com/bios10.php It does not support any change of the boot file name - so it only starts xboxdash.xbe. Rename the original MS dashboard to something other than xboxdash.xbe and rename the replacement dashboard to xboxdash.xbe. Any installer disc's change replacement dashboard operation is not going to work correctly with this ancient BIOS.
-
I think the BIOS on that modchip (Xecuter 1.1) which is meant only for a v1.0 Xbox and cannot be upgraded (reflashed) has no BIOS boot order list like later modified BIOS versions have. I believe the Xecuter 1.1 BIOS only starts xboxdash.xbe. Newer BIOSes have a boot order list that they would attempt to run evoxdash.xbe, nexgen.xbe then avalaunch.xbe (I'm not sure if all of these names are correct - especially the latter two - I've not double checked them). If all of those files are not found on the hard drive, the stock MS dashboard, xboxdash.xbe, will be executed. HeXEn install disc expects this type of boot up operation to switch the replacement dashboard. For your Xecuter 1.1's BIOS, I think you need to rename the current xboxdash.xbe file to yboxdash.xbe (most any other name will do too) and change the name of the replacement dashboard, evoxdash.xbe, to xboxdash.xbe.
-
It's the original the red ones are the newer clones
-
The dot CLF file has strings for many languages in it: Turkce Nederlands Deutsch Dansk Français Italiano Svenska Norsk Suomi Espanol Português but, how the program finds the offset to the location of each language's strings in the file has yet to be determined.
-
Found Old Avalaunch Team Files Online
KaosEngineer replied to DobaMuffin's topic in General Xbox Discussion
http://www.crusaders.no/~joker/old_web/avalaunch/index.htm Just shows information about AvaLaunch's features. At least, that is all I have found.
Board Life Status
Board startup date: April 23, 2017 12:45:48