http://www.jannikvogel.de/scratchpad/xbox/launch-chihiro-3.xbe Same as before but also carefully extends the WB region (instead of setting it as fallback) - this should have been done by a debug bios though. So if this helps you should blame the bios authors for not making use of your 128MB properly.. Please upload a log too. //Edit: Source is temporarily available here: http://www.jannikvogel.de/scratchpad/xbox/source/
That doesn't make much sense as it's UMA, the CPU & GPU share the same RAM. When using write back the data will end up in ram, it's just that it goes into the cache first and it might take a while before the writes are flushed. It could be that the code is doing more than the comment suggests.
I thought the GPU would operate on WC buffers? I guess this has to do with the fact that it expects data in bursts? I'm not too sure about the details though. What I do remember is that the GPU won't work unless it's using WC memory for the pushbuffer registers. //Edit: Just checked, what I do is extend the WB region too. Oops! Where does the GPU get it's WC region from though?
OK. I tested the new launcher and found some interesting stuff. I launched it from cold boot so the memory prefetch was set to 64MB as I had the red bar. Game still failed to load. So I went back to dash via IGR and loaded the launcher again. This time the bar was green telling me the prefetch was indeed moved to 128MB. Game still failed to load. Here's the log it generated. Almost forgot. It's this way due to me launching it a second time after the prefetch was changed to 128MB. That's why the first set of limits match the second set. I did follow the instructions on where and how to put everything for the files and folders. My console is a revision 1.4, 128MB, TSOP flashed IND-BIOS 5003, Unleashx dash revision 0.39.0528A build 584, 40GB Seagate HDD, games in the F folder. Game still launches once I fire up MAME and return to dash with IGR or MAME options.
http://www.jannikvogel.de/scratchpad/xbox/launch-chihiro-4.xbe Same thing as before but more debug output and finally a text blitter.. Also allows to launch test mode XBE (Hold A during launch - but I still have to hold Back to actually get into it once I selected it. Probably launchdata check-fail). I also added the MAME hack by holding B - however, it's not the proper way to solve this.. //Edit: Please verify that it shows 128MB RAM [twice!] with 32768 pages.
OK. Tested this out several times several ways. As before it fails to load the game without the "MAME hack" enabled. I checked each time when the default prefetch was set to the factory 64MB and I did indeed get the "128MB RAM [twice!] with 32768 pages." message to show. Shows the RAM, pages, then RAM again so that is working properly. I can launch the test mode too but it doesn't work unless I hold B to get the MAME hack going too. Launching the game from the test mode made it crash for some odd reason. Probably because I changed some settings to see what would happen. Now for the logs. First log is just simply pressing start at the screen: This log seems to be the exact same and this is when I held the B button to enable the MAME hack: Both logs are from cold boots with default 64MB prefetch. I decided to go ahead and include a log from a relaunch with prefetch limit set to 128MB beforehand in case there is something different: Hope this helps.
Had the boolean twisted for the Writeback patch.. http://www.jannikvogel.de/scratchpad/xbox/launch-chihiro-5.xbe Noticed that my bios sets this properly though.. So it's rather surprising that the MAME hack works but the original doesn't.. MTRR 0: 0x00000000 - 0x07FFFFFF (6 = WriteBack) MTRR 1: 0xFFF80000 - 0xFFFFFFFF (5 = WriteProtect) So the Chihiro games must be writing to an address in the range 0x80000000 to 0xFFF7FFFF or paged address which is not in WriteBack mode by default. Can anyone provide a *proper* crashlog from VC3 or possibly the smallest crashing game with MAME disabled? (Stack trace, memory dump, registers, ...?)
No need for a dump or anything. Your fix to this one has it working now. VC3 loaded without needing the "MAME hack" activated. Well done man.
Still interested why other games crash though. It would be nice if someone could set up a table (Google Docs?) or something which lists all games in all possible versions (Revision, 512MB / 1024MB), their title id, what was used to extract them, possibly a good crashdump and detailed notes how to get it working or a detailed explanation of the crash (incuding xbox version, modchip, bios, ... - if known). Would make it a lot easier to compare and look for problems.
What is this Mame hack thing? I never use mame before booting a Chihiro game and Virtual Cop 3, Ghost Squad, and Outrun 2 Beta start fine. I use either ind-bios 5003 with the .cfg file set to use all 128mb of ram or I use X2 5035.
I'm interested in the way you set the .cfg file in IND-BIOS 5003 to use all the RAM. Care to share it? That would get rid of the need to have this boot loader.
This still patches the GPU too (and the filesystem too).. so Ghost Squad hopefully works better now. It's really hard to tell what benefit my launcher gives though. To me, not a single game works (on my 64MB board)
I just played some Ghost Squad. I used the Chihiro loader 5 to get all the RAM and file systems in order. I still had to delete that one texture pack and mission 3 is still unplayable. So the problem with the game has to be in the game files then. The Chihiro loader didn't help Ghost Squad to play better... And you really need to get a 128MB board or mod Jay. Totally worth it for all sorts of stuff.
Dear I am not sure can help bit an old post with some of log from dr watson, about boot from some of game, work o (VC 3, outrun 2 beta) or not: I tried, but I have no enough knowledge for exploit this, my old post about it:
Go to the .cfg file and change this line USEUSEALLMEMORY=0 ;Use 128mb of Ram if Available Default=0 to this USEUSEALLMEMORY=1 ;Use 128mb of Ram if Available Default=0
Correct me if I'm wrong, but I think your videos show you using XBMC as your dash? XBMC does the same thing as the MAME technique discussed above - sets the xbox to correctly use the 128MB of RAM. Edit: I just tried flashing iND-5003 to my 128MB retail box with the "USEUSEALLMEMORY=1" flag in the cfg file. Cold booted iND5003 to UnleashX and tried to launch VC3 and it hung as if it were being run on a 64MB system. So even with iND-5003 and the USEUSEALLMEMORY=1 flag you have to first run MAMEoX128, XBMC, or jayfoxrox's chihiro launcher to properly initialize all the RAM before running a Chihiro game.
Disassembled vc3_t.xbe now and changed my LaunchData. Test mode works reliable for me now. Also added code to patch XboxHardwareInfo to represent ARCADE xbox and also added one undocumented flag which stops vc3_t.xbe from remounting the DVD Drive (Both not shown in GUI yet). I also changed the mounting code so it actually mounts now instead of getting errors That being said, I noticed that I can't remount \Device\CdRom0 because the original device can't be unlinked. I guess I'd have to delete the device object or somehow move the driver. I figured it would be best to use the undocumented flag and mount the D drive myself for now. http://www.jannikvogel.de/scratchpad/xbox/launch-chihiro-6.xbe //Edit: No logs necessary I think - unless this crashes for anyone.
Whatever you did to this version of the launcher it sure makes the games load fast. Used to when I would use the MAME hack it would take around 10 seconds to load a game after the dashboard loading screen went away. Now the game takes half a second or less before going to the warning screen. I also managed to get my IND-BIOS 5003 patched to use the full 128MB from launch and that allowed the games to launch without needing the launcher or the MAME hack to get the full RAM working. But then I derped the config for another change which resulted in a no boot console, installed my Xecuter 2.6CE modchip to fix it, and shorted out the TSOP chip while hooking the D0 line to an alternate point. OOPS... Looks like I'm stuck using the 2.6CE now until I can replace the TSOP. May just forget it and continue on using the Xecuter X2 5035 BIOS and configure it up.
Hi guys, Firstly Awesome work JayFoxRox...your the man!! Had some time so had a go with some of your launcher files etc on a few chihiro dumps. Your latest one (number 6) makes mine no longer need to load mame for the 128mb ram hack and loads VC3, Ghost Squad and Outrun 2 Beta fine but no go on others yet. Loving the progress
