gaasedelen / titan Goto Github PK

Receive the following error when running the command:

python tpatch.py m8plus_16_kernel.img --udma 5

[*] Patching with Titan v1.0 -- by Markus Gaasedelen
Traceback (most recent call last):
File "N:\XBOX\titan_win32\tpatch.py", line 277, in
result = main(len(sys.argv), sys.argv)
File "N:\XBOX\titan_win32\tpatch.py", line 266, in main
patcher = TitanPatcher(udma=args.udma)
File "N:\XBOX\titan_win32\tpatch.py", line 26, in init
assert 2 <= udma <= 5, f"Invalid UDMA mode ({udma})"
TypeError: '<=' not supported between instances of 'int' and 'str'

Seems to need a str to int conversion on the command line args so the compare will work.

My environment is win 11 via command prompt or powershell.
Python version output:
python --version
Python 3.9.10

I'm currently using the X2 5035 True VGA BIOS (Sync on Green & 128MB RAM).
It is possible to add the patch to this BIOS? I need 128MB and good VGA compatibility.

https://assemblergames.org/viewtopic.php?t=60232&sid=ba822c6123f05d9c66c22bcf1bd51660&start=10

https://shmups.system11.org/viewtopic.php?f=6&t=64176&start=30

hi i'm at a loss i have a startech now that has bent pins (stupid no sheilding) i cannot find the RXD629A7-7 board what is the brand and is it discontinued? i have a kingwin now and i can deal with using the stable UDMA 4 patch, can someone point me in the right direction?

Is this normal running latest titan bios?

Can we move to an MBR style partition and scrap the xbpartitioner/ hard coded partitions so We can have coexisting xbox, Linux and ReactOS partitions on the same drive?

Currently the xbpartitioner tables roll-over into mbr space and defining MBR partition overwrites xbpartitioner tables.

It would be nice to use mbr for all or move the xbpartition info to free space after the mbr so they can coexist.

I just want to ask before potentially borking my Xbox.

I know that EVtool allows to remove the logo from the bootup animation, so it looks stock (i prefer it this way) and I also know that applying the --force flag in tpatch.py will patch the img file despite its MD5 not matching (which it wouldn't since I applied the logo removal beforehand), I just want to make sure before I do this: is it safe? can I just disable things like the DVD check and removing the EvoX logo, then saving that BIOS .bin file, and then extracting the IMG, patching it with tpatch, repacking the bin file, flashing that to my aladdin (my tsop's broken), and have a working Xbox? since it's likely to break things, would be great to know beforehand.

Thanks in advance.

Just wondering if you could port a 16Tb patch for the complex 4627 bin file (maybe the others as well) for converted original to dev kits. That way converted kits will use up to 16Tb in theory. Normally kits will only see a 4Gb partition for use which 1 prototype game can take up up to 4Gb. Would like to fit a collection of 427Gb prototypes on 1 system

Issue is that whenever user opens file manager in xbmc4xbox clean install it freezes the xbox when opening file manager from within xbmc4xbox with titan bios. It just gets stuck saying working then becomes unresponsive.

I know the focus at the moment is on maximising the addressable disk space, but I wondered if you could look at adding a patch for 128MB RAM support? The kernel you are patching against (m8+) does not support 128MB RAM out of the box.

Hi - FATXplorer dev here. I was testing Titan support in FATXplorer with a user and ran into a perplexing issue where files/folders added using FATXplorer would not show up on the Xbox. Conversely, files added via a file manager on the Xbox wouldn't show in FATXplorer.

From my experience this is almost always a problem where the partition size is being calculated incorrectly. After reviewing your patches I believe I have located the issue.

The problem lies here. You are calculating the size of the F partition without subtracting the starting offset of the partition (0x1DD156000). As a result, you are creating a partition that goes beyond the end of the disk by ~8 GB.

To verify this, I modified FATXplorer to use the disk size as the F partition size, instead of DiskSize - 0x1DD156000. After doing so, the user's files load correctly.

Fixing and not fixing this bug each has its own problems and will require careful consideration.

-If you fix it, all existing users' F partitions will suddenly break and will need reformatting. The point of these patches is to add large storage, so this could be very inconvenient to users with large amounts of data already on F.

-If you do not fix it, users will see a partition that is 8 GB larger than it actually is, and will run into problems if they actually get into that space. I also believe Matt's FATX project will need updating to "properly" format and mount.

a currently formatted Xbox hard drive?

Do you have to reformat the hard drive to use the Titan BIOS or is it backwards compatible to support extended partition(s) already present on the hard drive formatted by XBPartitioner v1.3 with 64KB clusters.

Edit: I want to enable udma5 support but still use the current F and G partitions on a 2TB hard drive. Or, even F and G on a 1TB hard drive, or F alone on a 1TB hard drive.

Possible to add support for original Xbox debug kits?

I am not sure if I am doing it wrong, or if there is an issue. When I use the command as stated here it does not work. I have visual studio code with python newest. I open a command window and put in python tpatch.py --udma 5 m8plus_kernel.img and when I pack it and try to use it I get error 13, or other random errors 16, etc. however when I drop th e--udma 5 it works fine. Also I only can get the command to work with python not python3 even though my version of python is 3.1 (or whatever is newest) I dont know there also if I just did something wrong or what. It works great without the udma 4 or 5 part though, so I just wanted to find out if I did it wrong, or if there is a bug. I have a version 1.1 xbox running a x3 chip so I can easily flash to bios slot 5-8 without messing up my regular x3 bios. I have a 8tb hard drive and a 3tb hard drive I have been testing with. I used a startech sata to ide and a ultra ide cable. Tried a 4 inch cable, a 18 inch and a 24 inch cable one without dvd