Originally Posted by deank
As far as I know - all games work with multiMAN.
Well that's the major problem. I can't change the PARAM.SFO of multiMAN on the fly for each direct-boot game. The gameID must always correspond to the folder name (i.e. BLES80608 -> /dev_hdd0/game/BLES80608). Even if I change the param.sfo when you launch the game - it won't work, because of the folder name mismatch.
D
|
I think you might have misunderstod me. What I did was I installed the older version of MM, 2.00.01 - and then changed it's Folder Name and the GAMEID in the Param.SFO of MM 2.00.01 to something else (MULTIMAN2). This way, I could then install the latest MM 2.05.05, and have both versions installed concurrently and working - so now I can use the older one for Ghostbusters, and the newest one for everything else.
I didn't change anything with the actual Ghostbusters game Folder/Param.sfo, or it's save file.
All I was asking was that I'd be curious to know what changed in MM about the direct boot option between 2.00.01 and 2.03 that caused it to stop working properly with this game. There was definitely something changed, because as I said before - in 2.00.01 using the direct boot option starts the game IMMEDIATELY. But in the later version (2.03 and up) right when you launch the game there is a pause, and a file copy progress bar pops up before the game starts using direct boot now.