Hacking Priiloader Public BETA

  • Thread starter Thread starter Daco
  • Start date Start date
  • Views Views 151,376
  • Replies Replies 728
preloader doesnt do anything to IOS (at least this version).

It replace and moves the original system menu and usually is used to autoboot it with hacks such as region free.

You can use it together with cioscorp if u like, but they are entirely different things.
 
BBking83 said:
What is the difference between this and cIOSCORP?? I was told that Preloader region frees the Wii's Disc Channel.

Is it the same, in that it replaces most genuine IOSes with cIOS or modified IOSes? I was going to say "rips the guts out" but I have never used this (nor cIOSCORP) and that might be a bit harsh.

Basically, it want to try and region free the Disc Channel. I had this mad idea of getting IOS70, trucha signing it and region freeing it with ww_packer and then installing it. Even though I have a NAND backup of my current system, I'm too much of a pussy to try it.
tongue.gif

Preloader is just an app that moves the System Menu, and in its place allow you to boot into HBC (just in case you install a banner-bricked WAD, or if you're lazy), or install homebrew to NAND and autorun it (eg. Wii Home, Crazy Intro), and also apply System Menu patches, or 'hacks' on the fly (eg. Skip health screen, Reigon-free games and channels, Remove NoCopy protection, etc.). You can also choose what IOS you want the System Menu to run under. That's basically it.
 
xzxero said:
0ld8oy said:
Is anybody having any luck with this? i've done a complete uninstall and nand clean. still a no go.

i've reinstalled rev4 and it's working fine

***edit***
also, i've got BootMii as boot2 so i'm willing to test anything you put out.
code dumps on the system menu hacks as well.

got boot2 and am willing to test as well.

rev4 continues to work fine

+1
 
Jacobeian said:
WiiPower said:
Well brkirch, the guy behind the latest Gecko OS, noticed some error and uses the old libogc for Gecko OS because of that. When i compiled Gecko OS with the latest libogc, some games(retail games, no patched IOS) were not working.

Also i have that great issue: When i compiled BlueDump with the new libogc, it created a wad file on sd card, my pc could not read(!). And yes, i could reproduce it and with old libogc i could read the file.


The bug is not in libogc but in the way application access (read/write) files.
I've read on #wiidev that, in devkitPPC r18, I/O access aren't buffered anymore, which means you can't do that anymore:
QUOTEfread(buffer,1,VERY_BIG_SIZE,fp)
fwrite(buffer,1,VERY_BIG_SIZE,fp)



but rather use buffered chunks of smaller size and a read (write) loop
then do point out where we use very big sizes. from what i can tell we rarely/never do :/

edit : and why nothing crashes on my wii( which is irritating the fuck out of me) but does on some other wii's (which is why this is beta, i knew about the bug thx to FGOD )


EDIT2 : thx to oldboy & help of #gui-usbloader-chat the problem should be solved. had to do with the default cache size fatmountSimple uses :/

(and i need a usbgecko damnit)
 
Oh, I see. Thanks for your help an answers!!
biggrin.gif


So, it's kinda like Waninkoko's Menu Patcher? In that you can change which IOS the SM runs off?

I might give this a try.
wink.gif
 
BBking83 said:
Oh, I see. Thanks for your help an answers!!
biggrin.gif


So, it's kinda like Waninkoko's Menu Patcher? In that you can change which IOS the SM runs off?

I might give this a try.
wink.gif
lolno

lookup preloader before posting here

also, currently the beta does not support running different ios for system menu (i have it done but im still killing bugs that keep popping up. i almost bricked myself deu to a bug popping out of nowhere)
 
hi, just installed it.
code dumps on pretty much all options except for hbc boot, sys. menu boot and settings.
 
This release is compiled with devkitpro r18 which contains a very bugged libfat that can produce write errors. Since this app writes to the NAND, I'd advise against installing it at this point unless you can compile it yourself using devkitpro r17.

Not a knock at all on Daco. We spent much of the day testing yesterday and I'm sure it will be ready for a stable release soon.
 
0ld8oy said:
This release is compiled with devkitpro r18 which contains a very bugged libfat that can produce write errors. Since this app writes to the NAND, I'd advise against installing it at this point unless you can compile it yourself using devkitpro r17.
So you use libfat to write to the NAND? libfat is used for SD and USB devices and not the NAND AFAIK.
 
mousex said:
0ld8oy said:
This release is compiled with devkitpro r18 which contains a very bugged libfat that can produce write errors. Since this app writes to the NAND, I'd advise against installing it at this point unless you can compile it yourself using devkitpro r17.
So you use libfat to write to the NAND? libfat is used for SD and USB devices and not the NAND AFAIK.

I wouldn't recommend installing at this point because devkitpro r18 is bugged and the app writes to the NAND. Not necessarily because of libfat itself, but that is one of the major bugs that we are aware of and one of the main goals of this mod of preloader is reading/loading from both SD and USB.

I wouldn't install anything to my NAND (without bootmii/boot2) that was compiled from a bugged compiler. Period.
 
0ld8oy said:
This release is compiled with devkitpro r18 which contains a very bugged libfat that can produce write errors. Since this app writes to the NAND, I'd advise against installing it at this point unless you can compile it yourself using devkitpro r17.

Not a knock at all on Daco. We spent much of the day testing yesterday and I'm sure it will be ready for a stable release soon.
soon, asa i kill this very irritating (and possible bricking) bug in a memalign >_> (prob another crash deu to memory restrictions )
 
A bug in memalign? I only know a bug in ISFS_Read that messes up if the buffer size was not rounded up to a size that can be divided by 32. Or better, when i use memalign(32, (size+31)&(~31) ); for all buffers that read/write files from nand, i don't get problems. With just regular memalign i got lots code dumps.(and that was even with the old libogc)
 
WiiPower said:
A bug in memalign? I only know a bug in ISFS_Read that messes up if the buffer size was not rounded up to a size that can be divided by 32. Or better, when i use memalign(32, (size+31)&(~31) ); for all buffers that read/write files from nand, i don't get problems. With just regular memalign i got lots code dumps.(and that was even with the old libogc)
its the memalign itself. state.cpp , getbootstate() . that memalign almost bricked me (the bug came out of nowhere and therefor almost bricked me)

( StateFlags *sf = (StateFlags *)memalign( 32, sizeof(StateFlags) ); )

im guessing i have a huge memory issue
tongue.gif
(and that on startup of priiloader >_> )
 
If there was a "latest release" worthy of release, Daco would have it in the first post on this thread. If you look at Daco's comment on his source list he says it's "far from stable".

Be patient, this isn't an app that you want to install an unstable version of.
 

Site & Scene News

Popular threads in this forum