Team-Resurgent/Repackinator

Split/Multipart CCI don't start

Closed this issue · 7 comments

Hi,

am currently experiencing an issue with two games converted to CCI (with TrimScrub option enabled; didn't try without that option though), in that they don't start (black screen when run from XBMC, console appears to hang and requires power-cycle).

The games/ISOs in question are

and are stored at F/Games/.

CCIs were created from these redump images. The resulting CCI files are (with SHA256 sums)

a909c2bcd44ae6d171843f3de028c760b84dbdb9aadec9fe751829fae3eda47f  Conker - Live & Reloaded (USA).1.cci ; around 4GB
3517c109096f854e0c287cbbdefd3eebc4043135f35fb53c8e90b343a77b9d24  Conker - Live & Reloaded (USA).2.cci ; around 400MB
20ea337df9b02ae721b036c82768d9d01f5a74e39d5d59ea0c7678c1daafcb80  T.C Splinter Cell - C.T (GLO).1.cci ; around 4GB
1ed7c3956f1e423193cc8d6b864cb16c9640c97d8340a878ba94acf306b41ffb  T.C Splinter Cell - C.T (GLO).2.cci ; around 1GB

This is on a Xbox 1.6 64MB with latest CerBios 2.2.0 BETA. Other CCI-converted games work fine so far, though I only tested a handful since I just flashed CerBios and just started playing with CCI and got curious about "bigger" games.

Is this a known problem (i.e. related to the BETA tag of the CerBios version)? Or something related to Repackinator?

EDIT: Forgot to mention: Repackinator used is version 1.2.6.

Thanks!

How did you transfer the files to the HDD?

There are Xbox FTP servers that will not completely transfer the first file and create the same condition. Make sure your first file cci size on your Xbox matches original file size on your computer.

Thanks for the response! In fact, I just had a very brief look and indeed noticed that on the Xbox HDD the filesize for ie. "Conker.1.cci" is different (smaller)

The file on the box has 4257135632 bytes while it should be 4290690064 bytes (while the second looks correct, and "smaller" CCIs from other games also appear fine, didn't download and SHA-check the files yet), so yeah that obviously is pretty wrong. Any recommendation for a "proper" FTP server that doesn't have such issues?

To answer the question: Used FileZilla/Linux and the XBMC (3.6-DEV-r33032) FTP server to transfer the files over.

If you are using XBMC FTP Etc its is known to cut off parts of the transfer, way to test that would be to transfer the first part across again but instead of overwriting existing part select resume option on your ftp and see if it transfer the remaining last bits.

Otherwise it is highly recommended that you connect your unlocked xbox hdd to your pc and transferring files across using fatxplorer.

Thank you guys for your advice regarding FTP and broken files.

I first tried the resume variant to "complete" the transfer, though I decided to double-check and downloaded the file and checked the SHA256, it was broken anyway. So I then started the old EvoX dashboard and FTPed the CCIs (only the first one since the second one was alright in both cases) again. While the file sizes are shown completely wrong with EvoX FTP (it pretends the files are only a handful megabytes), they were alright with the XBMC FTP server. Downloaded and verified them (I somehow had a feeling it'd be a good thing to store the checksums alongside the games) from the console and they were ok then.

Obviously, the two games in question are working now (went only a few meters into each one), so, no issue with either CerBios nor Repackinator. Gotta verify everything I uploaded so far then, meh.

Nasty thing...

Thank you for the help! Not sure if you'd like to keep this open for anyone else running into such issues ;)

Good to hear it worked! That is the reason we only recommend direct connection at this time. While it is not the only way, it is the fastest, and only way we have thoroughly tested so far.

We will add a note about known FTP issues with XBMC based dashboards to the read me to hopefully help prevent this with others in the future.

If we get time, we will try to do some testing on various FTPs. If there are any that standout as proficient, they will get added as recommended transfer methods to the read me in the future.

A bit offtopic: One thing I noticed with the EvoX FTP server regarding the mentioned file size thing: The file size seems to be reported as "signed 32bit integer" - starting at 2GB, the reported size will get lesser... A 2.3GB CCI was/is shown as 1.7GB and a 3.6GB CCI was/is shown as 0.4GB 😆

We have added this to the "known issues" section of the read me. We also added our recommend method of transfer, as well as your report of EvolutionX FTP successfully transferring. Thank you again for the feedback!