Hacking Nintendont

  • Thread starter Thread starter sabykos
  • Start date Start date
  • Views Views 10,168,736
  • Replies Replies 42,894
  • Likes Likes 194
I'm sorry if this game has been brought up a lot but I was just wondering if anyone else had this problem, super smash bro. melee just shuts my wii off when i try to load it with v1.45 and just tried it with 1.46 same thing and loading from sdhc card fat32 64k

Edit: sorry I forgot about having cache.txt in the folder, it was causing the problem
mine used to shuts off my Wii U having cache.txt on 32k HDD and SD(HC) card fat32 default cluster.
 
ppl you should get ride of the caches since that seems to be causing alot of problems atleast until they are more stable i guess.
 
My bad. i can confirm the wave bird is working on R1.45 it wasnt working for me on earlier revisions.

I use a HDD to load games. Fat32. 32kb cluster. And rev1.45 and it worked.
 
more out of idle curiosity than anything else but i wanted to ask why when loading from USB on a Wii U the controller is restricted to the lower back port but when loading from SD its fine in the front ones ?

i have a extender cable but it does make needing a Y cable for the hdd a small pain
 
more out of idle curiosity than anything else but i wanted to ask why when loading from USB on a Wii U the controller is restricted to the lower back port but when loading from SD its fine in the front ones ?

i have a extender cable but it does make needing a Y cable for the hdd a small pain


I could be mistaken, but I thought it was part of the kernel (USB kernel versus SD kernel); nevertheless, I hope one of these days it can be implemented, it would make Y-cable usage smoother.
 
  • Like
Reactions: VinsCool
I could be mistaken, but I thought it was part of the kernel (USB kernel versus SD kernel); nevertheless, I hope one of these days it can be implemented, it would make Y-cable usage smoother.

yes it would be alot better plus it would stop the need for people to buy another cable but its only a minor issue the work being done on compatibility is much more important
 
I was testing def jam fight for ny and I looked in ndebug.log and at the top it says Nintendont IOS55 v22.31 I thought it used ios 58 sorry for the stupid question i was just curious
 
we
I was testing def jam fight for ny and I looked in ndebug.log and at the top it says Nintendont IOS55 v22.31 I thought it used ios 58 sorry for the stupid question i was just curious
well, the kernel is a patched IOS58 kernel which I set to IOS0 v13.37, our modules are from IOS55 so thats why it shows that.
 

Site & Scene News

Popular threads in this forum