Are you trying to say "instead of"?r201 compiled Uneek + DI
same error
game region: UNK
instead
game region:EUR
and does not see the games
r201 compiled Uneek + DI
same error
game region: UNK
instead
game region:EUR
and does not see the games
I think your problem is something to do with the Wii game format under usb:\games.
"UNK" is the default if there is no games found under usb:\games folder.
Pls try to use Wii backup manager to convert/install your Wii games.
(don't use DiscEX to convert your ISO because it's not the correct format for uneek/di)
kernel_usb_di.bin airline38
di.bin R198
Ok
If my kernel.bin is OK, then it's nothing to do with the game format.
I didn't do anything special except I used the SMenu.c which is modified
myself.(esmodule) You may try to use my SMenu.c to compile then
see what happen.
same error
incorrect patch version in EUR
I don't know how to update the linker script, which is necessary if you want to build it with the latest devkitARM.
I just use a batch script to quickly swap between versions. Save this to Swap.bat in your devkitPro folder. Download https://sneek.googlecode.com/svn/devkitARM_r32.rar and extract it to devkitARM_Old. You can then double-click Swap.bat whenever you need to change versions.
No, they can't be compatible with new and old.nice work, thx . that'll make it a lil less tedious.
got another question ... updating to new devkit isn't just for the newest revisions is it ? ... if the repository says updated to use new devkit(or whatever) then all older revisions will compile with the new devkit too ?
(i wasn't thinking one revision could be built with either devkit...BUT)No, they can't be compatible with new and old.
No, r202 would need devkitARM r33 or above, but r197 would need devkitARM r32 or below.(i wasn't thinking one revision could be built with either devkit...BUT)
lets see if i understand ...so lets say *neek got updated to build with the newest devkit , then revision 197 would then need the newest devkit to build it as well , just as rev202 would?
(i am not sure why but i was thinking that when i project was changed to build with a new devkit that the older revisions still needed the old devkit)