Hi,

I got this classic error Extractor failed on mac m1 running ventura. I am not sure how to fix this problem

fix_ndsheader.py currently requires python2. It would be nice to have this updated to Python 3 or so.

The version of this script that TWiLight Menu++ uses does use python3, but it seems to have some issues as hiyaCFW won't load when using it (white screens after the splash), unless I just set it up wrong.

Can you pretty please guide me on exactly how to do it as I just finished trying to do it but when I finished following the guide I realised it never once said to extract the: hiyaCFW.7z so I don't think I did it right my DSixl still works though thankfully

It only happens when I launch the game using HiyaCFW forwarder (not sure if this is a edo3900 Forwarder Maker Problem), but it works fine when I launch it using twilight menu ++.

Tested on v1.4.0, only happens with this flashcard. Game cards are fine.

Here's what I discovered:
Changing settings while inside hiyaCFW causes the SysNand versions of Download Play and Pictochat to use the updated settings, even though they should be separate.

I'll provide an example:
Let's say that my sysNand username is "foo" and my sysNand color is blue.
When changing my sdNand username to "bar" and my sdNand color to red, the sysNand system apps, such as Pictochat and Download play, do reflect the change, but the sysNand Launcher does not.
This effectively results in the sysNand Launcher saying I'm "foo", but sysNand Pictochat saying I'm "bar".

Is this intended behavior?

I discovered this while using Yoti's hiyalang to change the sdNand's region to EU, this software modifies only the SD card, as it is ran on the computer.
Through the sdNand System Settings app, I changed the language of sdNand to English.
This, however, also changed the language of the sysNand's Pictochat and Download Play apps to English as well.
These changes persisted even after removing the SD card that has hiyaCFW installed on it, and booting to the stock Launcher without any sd card.
After this, I suspected that this is not intended behavior, and I did a test with usernames and colors, which should not involve hiyalang.
These tests showed the same behavior, causing mismatches between the sysNand Launcher and its apps.

For this reason, it has not been installed hiyaCFW

I do n’t know if I support it now

can anyone tell me how to fix this

If my understanding is correct, if you update the system menu with hiyaCFW, it'll replace the modified 1.4 Launcher with the unpatched 1.4.5 (or 1.4.6) Launcher, making hiyaCFW unusable.

So, I think a good way to mitigate this issue would be to check if Launcher's header CRC is equal to that of any of the 1.4.5 Launchers (as opposed to checking if it matches the modified 1.4 Launcher, so that I and no one else people can use customized Launchers as if wish) and display an error if this is the case.

When posting a new version on GitHub, the version number is not displayed in the hiyaCFW configuration menu. It only appears when building locally.

So I started pokemon soulsilver 2 days ago and from the first 15 minutes of playing i froze. I dont want to accidentally lose progress anymore as ive already froze 4-5 times. Ive tried everything i could find about. I tried every kind of diffrent rom, even the anti piracy patch but im still freezing.

After Hiya's splash screen, it gets stuck on white screen.

This is the sole issue preventing a new release.

Touch screen does not work on all system apps and dsiware except TWiLightMenuPP and the System Menu.

The statement says it all as the information relating to proper boot and setup of console
As relating to hiya custom firmware helper. Proper install of the boot 9 binaries as related to
God mode 9 and DSI to 3ds setup. - (basically what one should do is put these in the bootloader setup folder.)

I use HiyaCFW on a nightly basis for Sleep Clock, as it's an easy and cheap way to track sleep using just a DSi.
However, I always have to make sure the write protect notch is up. If it isn't, my tracked sleep doesn't save.
I would prefer if the app tested for write protection on startup, and prompted the user to disable it if the check fails.