Forwarders not working anymore.

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Using latest build ( 140 )
2.With Rev 502 everything works fine.
3.

What is the expected output? What do you see instead?
Black screen using latest ( 140 ) + desyncing remotes

What version of the emulator are you using (official, SVN revision,...)?

Latest rev 140
Please provide any additional information below (Video settings, Console
region,...)

Forwarders work fine using rev 502.

Original issue reported on code.google.com by hielk...@gmail.com on 2 Nov 2010 at 6:40

[GoogleCodeExporter]

It's a bug with your forwarder, the application does nothing special.

Original comment by ekeeke31@gmail.com on 2 Nov 2010 at 10:17

• Changed state: Invalid

[GoogleCodeExporter]

ok, ANY idea why my forwarder DOES work with rev 502?
Can it be the abproth flag?

Original comment by hielk...@gmail.com on 3 Nov 2010 at 10:20

[GoogleCodeExporter]

the "ahbprot flag" is in the Channel (HBC or Forwarder) header, not the 
application dol

The only thing that might change something is the libogc version you used to 
compile the dol. Old versions (before 1.8.3 I think) did reload IOS 
themeselves. Recent versions expect the loader to do it properly. 1.4.0 has 
obviously been compiled with the most recent one (1.8.5)

How did you compiled rev 502 in the first place ?

Original comment by ekeeke31@gmail.com on 3 Nov 2010 at 10:59

[GoogleCodeExporter]

Actually I was wrong, there WAS a difference in rev 502: the emulator would 
automatically try to reload into IOS58 if AHBPROT was not detected (i.e was not 
set by the loader channel) AND if IOS58 was not already loaded (i.e was not 
reloaded or used by the loader channel already).

However, that still means your forwarder is not loading the application 
properly, probably because it is not shutting and/or reloading down IOS stuff, 
I guess this is not so trivial to do and only "serious" loaders to this 
properly, hence why unofficial forwarders are not supported.

Let's hope that can help fixing the code in your forwarder

Original comment by ekeeke31@gmail.com on 3 Nov 2010 at 11:14