Homebrew postLoader4

[JoostinOnline]

ModMii uses a custom version. That may be the problem.

 

[EffortLess]

What version of Priiloader were you using?

I'm using priiloader v0.7 (r142)... how do I call the forwarder channel directly from priiloader. It's not listed anywhere?

My problem when loading from priibooter_gui or postinstaller is if I install it and load from installed file in priiloader, attempting to refresh cache for channels (real nand) says "postloader was unable to patch ISFS permission. Cannot continue". The only workaround I have is to load homebrew channel and load it from there or from system menu... it also works if I press 1 to load file under install/delete file in priiloader (which is weird because if I do install it then boot that way, it doesn't work).

Hope that wasn't too confusing.. thanks for the help!

 

[JoostinOnline]

I'm using priiloader v0.7 (r142)

Did you get that from ModMii?

Anyway, this is just another reason not to update past 4.1. There are absolutely no benefits to it.

 

[EffortLess]

Did you get that from ModMii?

Anyway, this is just another reason not to update past 4.1. There are absolutely no benefits to it.

I did get it from ModMII, but I just updated to 0.8 beta 7 and it's still doing the same thing.. what version are you guys using?

.... n/m. actually now it's working with the 0.8 beta 7. installed priibootgui as file and booted from that in priiloader and it worked! Thanks for your help!!

 

[JoostinOnline]

Then it is a coding error in Priiloader.

I just use 4.1 because it doesn't have all the limitations of 4.2+ and has no downsides.

 

[stfour]

I'm using priiloader v0.7 (r142)... how do I call the forwarder channel directly from priiloader. It's not listed anywhere?

My problem when loading from priibooter_gui or postinstaller is if I install it and load from installed file in priiloader, attempting to refresh cache for channels (real nand) says "postloader was unable to patch ISFS permission. Cannot continue". The only workaround I have is to load homebrew channel and load it from there or from system menu... it also works if I press 1 to load file under install/delete file in priiloader (which is weird because if I do install it then boot that way, it doesn't work).

Hope that wasn't too confusing.. thanks for the help!

When pribooter_gui start... press any key on the wiimote, the select the second option: "postLoader (channel)". Obviusly you need to install the official channel (or an equivalent with AHBPROT disabled).

 

[stfour]

.... n/m. actually now it's working with the 0.8 beta 7. installed priibootgui as file and booted from that in priiloader and it worked! Thanks for your help!!

nice to known!

 

[JoostinOnline]

I've sent XFlak a PM for the custom Priiloader source so I might be able to spot the issue.

 

[JoostinOnline]

What I'd like to know is if this still happens on something other than 4.3 when using the custom version. I'll see if I can install it tonight (but honestly, I'll probably forget).

 

[AbdallahTerro]

Sup stfour,
any news on more plugins/better arguments yet?

 

[Maxternal]

What I'd like to know is if this still happens on something other than 4.3 when using the custom version. I'll see if I can install it tonight (but honestly, I'll probably forget).

I thought it wasn't a custom version as much as a custom installer that uses IOS236 ... but then again I also thought that no version of PriiLoader was able to disable AHBPROT so I could be wrong with that, too.

 

[JoostinOnline]

I thought it wasn't a custom version as much as a custom installer that uses IOS236 ... but then again I also thought that no version of PriiLoader was able to disable AHBPROT so I could be wrong with that, too.

Yeah, and I found the problem. It's got (almost) nothing to do with the System Menu version. It's that AHB access is enabled on the System Menu IOS, but lost when reloading a different IOS for installed homebrew (i.e. homebrew you set to autoboot), because meta.xml arguments were not passed on for the installed homebrew. It still worked if you just launched an app from the menu.

This was fixed with rev145, which came out after Priiloader v0.7.

 

[stfour]

Sup stfour,
any news on more plugins/better arguments yet?

If you refer to scummvm, I will not implement it. I've checked how it works and requires too much work and quite heavy changes. And I'm not so interested on it

Currently I'm working on on-the-fly switch of dm, dml, qf in real nand.

 

[AbdallahTerro]

Dosbox?

 

[stfour]

Dosbox?

What does it need ? It was not working ?

 

[AbdallahTerro]

argument with "|" support

 

[Etheboss]

Sup stfour,
any news on more plugins/better arguments yet?

Currently I'm working on on-the-fly switch of dm, dml, qf in real nand.

Forget the arguments...on the fly switching sounds muuuuch better.

 

[stfour]

argument with "|" support

You should just use '$' instead of '|'... postloader will replace '$' with '|' before starting the plugin. Doesn't it works ?

 

[AbdallahTerro]

last time I checked it was the other way around (| was replaced by $)
Anyway I'll double check tonight

 

[stfour]

postLoader 4.4.8 (only as update)

* gameBrowser: Automatic DM(L)/QuadForce wad installation (please, read notes carefully !!!). Thx to waninkoko WadManager 1.7 source codes.
* gameBrowser: Fixed a bug on reading/writing configuration information
* Increased mp3 buffer size (less disc i/o)
* little fixes

========================================
DM(L),QUADFORCE automatic mode:
========================================

When this option is enabled (press [home] while in gamecube mode, then "GameCube mode = DM Auto"), postLoader will choose and install the correct wad file to execute the selected gc/qf game.
To use this feature, you must create a wads folder in your <dev>/ploader folder, for example usb://ploader/wads if your postloader data folder is in the usb device.
Then rename the dm(l)/qadforce wads as follow

DIOSMIOS_2.10.wad -> dm.wad
DIOSMIOSLite_2.10.wad -> dml.wad
quadforce_4.1.wad -> qfusb.wad
quadforce_4.0.wad -> qfsd.wad

so you will end with the following files

<dev>://ploader/wads/dm.wad
<dev>://ploader/wads/dml.wad
<dev>://ploader/wads/qfusb.wad
<dev>://ploader/wads/qfsd.wad

Use only tested wads, from well known source. Installing these wads should be a safe operation, anyway it is a your choice. No warranty provided, no responsibility on me if you brick anything!