Hacking neek2o

  • Thread starter Thread starter obcd
  • Start date Start date
  • Views Views 329,530
  • Replies Replies 1,533
  • Likes Likes 5
Using the boot2 version to detect if Sneek is running sounds stupid. Why not use di ioctl 0x24 (get game count)? Hmm, ok that's only for +DI, but do you care about non +DI?

He changed it to make it undetectable.
He'd have to do a lot more than just returning the correct boot2 version if that was the aim.

But there's no need to add more stuff that makes Sneek detectable.
 
Using the boot2 version to detect if Sneek is running sounds stupid. Why not use di ioctl 0x24 (get game count)? Hmm, ok that's only for +DI, but do you care about non +DI?

As sneek exist, using ioctl 0x24 don't solve the problem. (imho)
 
This works fine, and should be compatible with any (current) versione of sneek/uneek/neek2o

Code:
bool SenseSneek (bool isfsinit)
{
bool ret = true;
char path[ISFS_MAXPATH] ATTRIBUTE_ALIGN(32);

strcpy (path, "/SNEEK/kernel.bin");

if (isfsinit) ISFS_Initialize ();

s32 fd = ISFS_Open(path, ISFS_OPEN_READ);
if (fd < 0)
ret = false;
else
ISFS_Close (fd);

if (isfsinit) ISFS_Deinitialize ();

return ret;
}
 
If you run BC from sneek nand, or BC from real nand, it shouldn't make a difference.
As BC is unpatched, it will get DML Mios from real nand.
Once it's running, it's not using the nand anymore. So, it should work from uneek2o as well. (not only from sneek2o)
The major problem there was creating the diconfig.bin, as the sneek di wasn't having sd access.
 
Like you didn't know :)

Btw, nice fix you found for the SenseSneek. Will need to update the one I added to the uneek_fs library.
 
crediar told some people there's no specific reason he changed the bootmii version back to 4.

For dml support in uneek2o it was not only a problem to read the game info, but also to write the boot.bin file. The uneek2o beta I'll release tomorrow for the test crew has full dml support.
 
Looks like stfour already fixed it for postloader.
Everything besides di can check the sd card games folder and create the boot.bin file on it without problems in uneek2o.


 
Can anyone give me pointers on what I should investigate if I can't get sneek2o+di working? So far, with the same hardware and filesystems, I got working sneek+di, sneek (no di), and uneek2o+di (haven't tried just sneek2o w/o di). No matter what I do, sneek2o+di just sits and never even initializes video output (TV says "No Input"). It does manage to create the "sneek" directory on the USB drive (even if I delete it) and blink the light on the drive a few times. It's hitting the drive and obviously recognizes the filesystem, but nothing ever happens from there. It's like it doesn't load the nand on the SD, but the SD works fine for sneek+di, bootmii, etc. Blue light on the Wii just stays dark.

uneek2o+di and sneek2o+di installs were both built with ModMii. sneek+di that worked was compiled from most recent using the compile quick guide.

Anyone got some pointers here?
 
If you run BC from sneek nand, or BC from real nand, it shouldn't make a difference.
As BC is unpatched, it will get DML Mios from real nand.
Once it's running, it's not using the nand anymore. So, it should work from uneek2o as well. (not only from sneek2o)
The major problem there was creating the diconfig.bin, as the sneek di wasn't having sd access.
Hmm...does this mean that to get DML running in neek2o, you need to install the DML Mios to the real nand?
 
Yep, that's the case. It replaces the normal Mios on real nand the way it is now (from rev. 12 +)
 
Is this only an issue with rev. 70, or also with other rev. of neek2o?
Have you tried it on a U nand? Did it work?
 

Site & Scene News

Popular threads in this forum