SysCheck ModMii Edition v2.5.0 Released!

XFlak

Wiitired but still kicking
OP
Member
Joined
Sep 12, 2009
Messages
13,818
Trophies
3
Age
38
Location
Cyprus, originally from Toronto
Website
modmii.github.io
XP
9,808
Country
Cyprus
SysCheck ModMii Edition v2.5.0

SysCheck ModMii Edition (aka SysCheckME) v2.5.0 Changelog:
  • Can be compiled with devkitPPC r41
  • Reports can be saved to USB storage
  • The console ID is masked when uploaded
  • All of the assets have been optimised
  • Added GitHub continuous integration
Major thanks to @blackb0x for helping me make this dream a reality!

Download from the Release Page or using ModMii.
 
Last edited by XFlak,

ukigh4ie

Well-Known Member
Member
Joined
Aug 27, 2020
Messages
155
Trophies
0
XP
562
Country
Germany
I use an emuNAND , which I created from the sysNAND. Both with d2x-v11beta1 in Slot 249[56].

SysCheckME correctly detects IOS249[56] (rev 21011, Info: d2x-v11beta1) in Slot 249 in sysNAND.
In emuNAND run via neek2o it says IOS249[56] (rev 21011, Info: d2x-v10beta53-alt).

What could be the reason?
 

ukigh4ie

Well-Known Member
Member
Joined
Aug 27, 2020
Messages
155
Trophies
0
XP
562
Country
Germany
Did u maybe install a dif cios to emunand?
It looks like the d2x-installer installs a new cIOS but leaves behind old artefacts that SysCheck uses to draw wrong conclusions.
Explicit uninstallation before installing a cIOS fixes the problem.
 
  • Love
Reactions: impeeza

XFlak

Wiitired but still kicking
OP
Member
Joined
Sep 12, 2009
Messages
13,818
Trophies
3
Age
38
Location
Cyprus, originally from Toronto
Website
modmii.github.io
XP
9,808
Country
Cyprus
More likely the ciosmaps.xml you used to install the cios was not configured properly, or user error

The d2x cios installer can be configured to install many cios's, so it's not inconceivable that u selected beta53 by mistake

If u can reliably reproduce the issue then I'll believe your claims
 

VictoriousWolf

Member
Newcomer
Joined
Jul 31, 2023
Messages
6
Trophies
0
Age
19
XP
7
Country
Antarctica
I have a previously modded wii (came with hbc and uloader) which give me errors when I try to load anything from any USB device. I think uloader and whatever they installed previously is causing this problem...
Would you suggest I run syscheck to identify the problem or "virginize" my system to start from scratch?
 

impeeza

¡Kabito!
Member
Joined
Apr 5, 2011
Messages
6,362
Trophies
3
Age
46
Location
At my chair.
XP
18,729
Country
Colombia
SysCheck ModMii Edition v2.5.0

SysCheck ModMii Edition (aka SysCheckME) v2.5.0 Changelog:
  • Can be compiled with devkitPPC r41
  • Reports can be saved to USB storage
  • The console ID is masked when uploaded
  • All of the assets have been optimised
  • Added GitHub continuous integration
Major thanks to @blackb0x for helping me make this dream a reality!

Download from the Release Page or using ModMii.
Nice see the Wii Scene still alive on 2023!!!
Post automatically merged:

Hello there, I just try to build it using MSYS2 on windows, with latest packages the devKitPPC is 43-3 but the process abort with the error:

1690823333619.png


I did install the packages:
  • git-2.41.0-1
  • make-4.4.1-1
  • devkitPPC-r43-3
  • libfat-ogc-1.2.0-1
  • libogc-2.4.1-1
  • gamecube-tools-1.0.4-1
Am I missing any other package?


Thanks for your help.
 
Last edited by impeeza,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    linuxares @ linuxares: Brazil?