SP Debug mode documentation - needs to be better documented?

[curriegrad2004]

I'm referring to this:
http://www.project-imas.com/w/THE_iDOLM%40STER_SP_Debug_Mode

I mean my initial documentation of getting into Debug Mode was somewhat shaky and it doesn't go deep in the functions of debug mode. Can somebody better document this feature for me while retaining the M$ style of documenting software? (Yes, I know, M$'s documentations are sometimes a pain to read, but is really good in the end when you need to fix a broken DC with only one command prompt...)

[Pizzaman]

It's a "cheat" that requires dubious modifications/software/roms etc, so I'm not sure if it's even wiki-worthy...

[BT2]

It's a "cheat" that requires dubious modifications/software/roms etc, so I'm not sure if it's even wiki-worthy...

This.

[Drunken Watermelon]

What about use HEN modes? That doesn't install anything onto the PSP.

[curriegrad2004]

What about use HEN modes? That doesn't install anything onto the PSP.

HEN wouldn't let you use plugins like cwcheat afaik.

[Drunken Watermelon]

Ah okay, thought it did.

[BT2]

^It's possible to use plug-ins on HEN with another piece of software.

Doesn't change the fact that hen fw's aren't sufficient to run iM@S.
5.03 HEN<<5.05
Also, iM@S has an anti-cfw check.


Also doesn't change the fact that running any form of 3rd-party code goes against the user agreement one accepted by purchasing a PSP.
Not like anybody but Sony and game developers care <___<

[Drunken Watermelon]

But if you purchased a used PSP you wouldn't see the user agreement, but let's not go into that derailment.

[curriegrad2004]

And yet nobody does really care if your PSP was hacked or not.

Besides, I feel like we need more documentation in debug mode anyways.

[BT2]

Besides, I feel like we need more documentation in debug mode anyways.

People already gave their opinion and reasons why adding a debug mode page isn't something noteworthy and that it might or might not attract unwanted people.
Now it's your turn to defend your standpoint.


[Flaming alert]
Seriously, I only see you talk about debug mode even though you don't even know how to use most of it, heck you couldn't even start the thing with the aid of a machine translated instruction untill someone explained it.

Also, if I recall correctly you were acting high and mighty to someone who failed to correctly recompile the translation of SP before the forum-reset, even though you can't do it yourself.

Stop thinking that you're so great.
[/Flaming alert]

[curriegrad2004]

[Flaming alert]
Also, if I recall correctly you were acting high and mighty to someone who failed to correctly recompile the translation of SP before the forum-reset, even though you can't do it yourself.

Stop thinking that you're so great.
[/Flaming alert]

That's because I messed my CPU from my previous mod on my laptop! My QL-62 isn't even acting correctly after I tried undervolting it to save on power. Now it's being a total mess on my machine. I had to get my retired Terminal Server to re-compile the rest of the game. And I'm still waiting for the replacement CPU to come from an eBay seller!

And the toolkit for it is just too slow for some reason. Right now I'm attempting to re-build the patcher program under ICL 10.1 to see if GCC was the problem of creating huge latencies on my already messed up QL-62.

[BT2]

Doesn't change the fact that you're not giving a reasonable reason why you think that adding a debug-room page to the wiki is noteworthy and that you don't even know how to use most of it's "features" and/or commands.

[Edit]
You're avoiding the main point.

[curriegrad2004]

Yeah, so?

Don't want to take this further, but I'm locking this. The Debug mode needs to be thoroughly documented. Besides, getting into Debug mode wasn't really that much of fun.