Quick check on hekate_ipl.ini file

  • Thread starter Thread starter Psd99
  • Start date Start date
  • Views Views 13,593
  • Replies Replies 9

Psd99

Well-Known Member
Member
Joined
Oct 1, 2021
Messages
534
Reaction score
88
Trophies
1
Age
125
XP
1,251
Country
United Kingdom
Hi,

I just wanted to get your opnion on my hekate_ipl.ini file as it looks like this:

[config]
autoboot=0
autoboot_list=0
bootwait=0
autohosoff=0
autonogc=1
updater2p=1
backlight=100

[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp


Does that look right to you as when I go into the SysMMC, CFW SysMMC I end up with a yellow screen and the console hangs. Emu MMC is fine for now...

so I suspect the entries are incorrect

I don't suppose you would be able to share your own version of this file?


p.s is the correct file the console uses in the /bootloader folder or is it in /bootloader/bootloader?
 
Similar question

Until 18.1 I have this file. only Emummc and Stock

Code:
[config]
autoboot=0
autoboot_list=0
bootwait=0
backlight=220
autohosoff=0
autonogc=1
updater2p=0
{updater2p=1 payload always hekane}

{--- Custom Firmware ---}
[Atmosphere (Emummc)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/Atmoslogo.bmp
usb3force=1
{-------- Stock -------}
[Stock]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp
usb3force=1

In 19.0.1 I find this new file with sysMMC, emuMMC and Stock
Is it sysMMC necessary, I guess I don't use sysMMC, not knowing the exact difference with Stock

Code:
[config]
autoboot=0
autoboot_list=0
bootwait=0
autohosoff=0
autonogc=1
updater2p=0
{updater2p=1 payload always hekane}
backlight=100

[CFW - sysMMC]
fss0=atmosphere/package3
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

[CFW - emuMMC]
fss0=atmosphere/package3
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp
usb3force=1

[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp
usb3force=1
 
for now I don’t need to use sysnans
I use emunand and stock system

So better if I erase sysnand lines in the file?
 
for now I don’t need to use sysnans
I use emunand and stock system

So better if I erase sysnand lines in the file?

Feel free to remove this portion if you have no intentions of ever using cfw/Atmosphere on sysMMC.

[CFW - sysMMC]
fss0=atmosphere/package3
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp
 
Ok. Thinki ha Boix that maybe the reís a posibilite of need it in one situation. If i need copy savegames from stock side to emu side

I round a tutorial starting in Hekate, disable emupattition and use “payload” from Hekate, launch Systems with atmosphere, enter in JKSV backup savegames, back to Hekate and entable emuMMC partirion

Mayor its better to mantain this option in ini file. Is it? What happen if it doesnt exist?
 
Ok. Thinki ha Boix that maybe the reís a posibilite of need it in one situation. If i need copy savegames from stock side to emu side

I round a tutorial starting in Hekate, disable emupattition and use “payload” from Hekate, launch Systems with atmosphere, enter in JKSV backup savegames, back to Hekate and entable emuMMC partirion

Mayor its better to mantain this option in ini file. Is it? What happen if it doesnt exist?

What you trying to do, don't understand what you wrote.
 
What you trying to do, don't understand what you wrote.
make a backup of save games of stock mode for use in emu and mode and viceversa

For now I only boot switch on that two modes. Emu and stock but sometimes I could need to swap the save games depending where I advance more

For that kind of think I watch a tutorial that disable emu partition in Hecate and boot using a payload in hekafe. So in this action I would be booting as SysMMC isn’t it?
 

Site & Scene News

Popular threads in this forum