Obviously it is not a HDD formatting issue so that is very good news.
Problem is now finding where the problem is in the game and why it should apparently repeat for what you'd think must be different downloads which are unlikely all to be suffering the same fault, if that is what it is.
Sorry I should or may have asked this earlier or not but what version Xbox and video encoder (Conexant, Focus, Xcalibur) are you using? I can test the game easily on another, softmodded, Xbox with Contexant and somewhere in storage I have a Focus softmodded machine too.
I suppose I should also ask what BIOS your TSOP is using too but if there is any possibility of that causing this niche issue I have no idea but the info might be helpful for others.
Have you tried burning the Jurasic Park OG ISO to disc (DVD-R using ImgBurn), test playing that from the disc then and then installing it using DVD2Xbox similar to what was done for Halo 2?
There's no reason to think this will work because the download I tested worked fine without any DVD2Xbox ACL (Access Control List) or other patching although, of course, I have no idea what was done to the original files provided. Anyway this problem is not like any ACL issue I've ever encountered; in my experience the game either plays or does not display correctly on boot.
However we have to test all possibilities: so before wasting any blank media you could try DVD2Xbox patching the installed game just to check this. Launch DVD2Xbox > File Manager > the specific game's folder. Highlight that folder and then press the controller's White button to bring up the context menu. Select "Process ACL" and when you press the (A) button it should show an ACL processing message. Once done check the game's folder. You should now have a "default.xbe" which is the newly ACL patched one and the old unpatched one "default.xbe_org".
Reboot and from the XBMC file manager launch the game from that "default.xbe". If it was an ACL issue then the game should display without the text problem.
BTW I have been testing this on a Xecuter 2.6 chipped v1.6 (BIOS probably Evox M8plus_16) with the Xcalibur video encoder at 480p using the MS Xbox Component cable. So if anyone else here might be thinking of suggesting it may be a Xcalibur display issue that is pretty good evidence it is not.
Short of trying one of the same download(s) you used which would either eliminate or confirm that as the source of the problem (
NB. the forum/mods will not allow links to be posted) I'm not sure how we can identify what
may be either missing or corrupted.
There are 10 folders with sub-folders too which contain most of the 4000+ individual files that make up the game. Unless someone can help identify the particular .INI or other file that controls the in-game menus text display it is like hunting for a needle in a haystack.
RE: Other Questions
1). XBMC will unZIP and unRAR(?) files via the file manager. I'm not 100% sure about .rar as I do not often unpack stuff using XBMC (prefer UnleashX) but it definitely unpacks .zip. No Xbox dash will unpack the popular .7z format though. There is a lot of Xbox stuff archived with 7Zip using its .7z rather than .zip format (which, of course 7Zip also supports). I've read plenty of cases where people have made the mistake of copying .7z folders to their Xbox and then complaining about not being able to open them.
If you click on a compressed archive it will usually display the contents. Select all those contents and copy them to a new folder and it unpacks them as part of the copying process. This is a bit crude compared to UnleashX's file manager's unpacking options. I've had stuff which UnleashX refused to unpack due to FATX character/file path matters which XBMC unpacked without issue because it can rename
some troublesome files on the fly.
UnleashX will also ZIP archive files/folders but not RAR them as that is a copywrited process. I've never tried zipping with XBMC but even if the reverse process works there are no menu options. You would have to have a previously zipped folder to add the files too. Again, UnleashX is the preferable tool.
2). E:\ is a bit low. The recommendation is to leave 10% free but at least 100MB. You have more than that so should be OK.
Additional game files are usually written to the X, Y and Z drive which are not displayed in the XBMC file manager by default. Low E:\drive space and cache issues certainly cause problems but not, that I've read about, anything like this.
You could always try deleting or moving some stuff on E:\ to test that. If you have any games in "games" or apps that are taking up a lot of space on E:\ then those are the obvious things. HexIns needs to be left on the root of the E:\ drive as unfortunately it was written to be used just from there.
3). No idea what that CACHEGSRV is but unless it contains something clearly related to JPOG then I wouldn't worry about it. It is probably from an Emulator or Homebrew game some of which write stuff to the root of the E:\ drive no matter where they were installed.