Hardware writing to causing forceful crash

[elmoreas]

I am new to USB Gecko but not to hacking games I have experience on the PC. I spoke to Link and he said   "Artmoney will try to write to software based addresses (meaning: you tell it to write to address XYZ, the operating system checks if the software has that address in use and translates it to a hardware address) that Gecko debuggers write to hardware addresses.. meaning: 80450334 is not some software simulated address it is the indeed hardware address - thus there are no checks if you write to valid addresses, if you leave the availible memory then the system will forcefully crash."  What I am confused on is what he meant by leaving available memory? And second this forceful crash, is it a bricking crash or just a needs to be reset and start over crash? I know this is probably a dumb question but I need to know. Thanks in advance to those who help.

Sincerely,
Elmoreas

[Link]

Simple as that:
-If you use ArtMoney.. then you attach to a Windows process.. and request the dynamic memory mapping Windows performed for this applicatin.. every EXE file on Windows for example has a start address of 00400000 for its assembly (stack and such can be in memory below 00400000) - however: those are no true hardware addresses, Windows internally manages memory for each application.. thus if a game for example does not have the memory range of 11000000 to 14000000 and you try to edit a value at address 13000000 Windows will tell Artmoney that this edit failed as the virtual memory map of the application does not contain these addresses.. other than that nothing will happen.

-On the Wii though, Gecko OS doesn't attach to any process technically.. it hooks itself into the game cycle so that it gets executed alongside the game, however there is no Operating System in between managing hardware addresses (okay, technically there is but in a much much lower meaning). So most Wii games use the Wii memory range of 80000000 to 81800000 for MEM1 (24 MB of memory) as well as 90000000 to 94000000 (64 MB of memory - 8 to 12 MB are usually lost meaning most games will only be able to use up to 93400000). These addresses are always availible, so if you work in these memory areas nothing will happen. NOrmally WiiRd and Gecko dotNET will disallow the use of any other memory address.. however, if you forcefully disable the memory protection then you could try reading for example address 12345678 - if this address is unavailible (which it'll most likely be) then you'll forcefully crash the Wii system.. all you can do is: reboot! There is normally no way to recover your Wii!

[elmoreas]

So what are the safe areas to work in, and what are the useful area to work in, and are they one in the same? I ask becuase I dont want to crash my Wii but I want to feel safe using my USB Gecko working on addresses to develop codes for games. For example you said certain memory areas were usually available but nothing would happen so why would I work in those areas? Wouldn't I want to work in the areas where addresses are available but my changes would make a difference so I could tell through trial and error if I had hit upon a code that would work for the game? Or am I going down the completely wrong path? If so could you steer me in the right direction? Thanks so much. Have a happy holidays.

Sincerely,
Elmoreas

[Romaap]

No, its not like a freeze will harm your wii, my Wii froze hundreds of times during hacking.
You can just search with WiiRD or Gecko dotNET because they are set to search between 80000000 and 81800000, 90000000 and 93400000 automatically.

[elmoreas]

Seriously? Link said that it would make your wii unrecoverable. Are you just messing with the new guy trying to get him to look dumb by asking this question? Second was I going down the right path? With Artmoney on the PC you use trial and error on different addresses to see what happens in game to make cheats, is that how hacking on USB Gecko is done, or am I completely wrong? If so, could someone tell me that, and tell me what direction I should be going in, I can figure it out from there. So no need to give me a detailed step by step, just a general this is how its done. I know these are stupid newb questions and I appreciate you guys taking the time to answer me. But I promise your time isnt going to waste, once I learn something I give back to the community and help others as well as provide, in this case codes, back to the community as well. One last question, what memory ranges should I be working in, on Wii/WiiWare/VC games? Thanks in advance for your help. Have a Merry Christmas.

Sincerely,
Elmoreas