Hi
I have a project where I need a lot of space for backgound images. It seems that nitroFS are the rigth choice. But . . .
It does not work on a real NDS. I have tried the example that comes with devkitarm. Compiles easily, and when trying the NDS file with desmume (but only with folder name set up in GBA-slot/compact flash) it seems OK.
On a real NDS the answer is always "nitroFSInit failure: terminating"
Does the example still works? There has been a lot of updates of devkitarm the last months, so it could be broken.
kvleonhardt
nitrofs - fails to initialize on real NDS
-
- Posts: 10
- Joined: Mon Jun 14, 2010 7:31 am
-
- Site Admin
- Posts: 2003
- Joined: Tue Aug 09, 2005 3:21 am
- Location: UK
- Contact:
Re: nitrofs - fails to initialize on real NDS
It still works, it just requires a launcher which sets argv. See http://devkitpro.org/wiki/Homebrew_Menu for some cards which do & the reference homebrew menu which supports both argv and exit to menu.
-
- Posts: 10
- Joined: Mon Jun 14, 2010 7:31 am
Re: nitrofs - fails to initialize on real NDS
OK. I will place the files on the SD card instead. The users of my application will proberbly not change the menu, and many has the DSTT card which seem unsupported.
I just cannot understand why it shuld be more diffecult to run homebrews than game copies.
kvleonhardt
I just cannot understand why it shuld be more diffecult to run homebrews than game copies.
kvleonhardt
-
- Site Admin
- Posts: 2003
- Joined: Tue Aug 09, 2005 3:21 am
- Location: UK
- Contact:
Re: nitrofs - fails to initialize on real NDS
It's more difficult to run homebrew for two main reasons :-
1. The cards are primarily designed for running "backups" with homebrew as an afterthought.
2. Homebrew authors insist on assuming things about their users and decide not to use features designed to make running homebrew easier.
The cards which currently do support argv do so because several users of those cards requested the feature from the card manufacturer. These users were encouraged to do so by homebrew authors who made use of the nitro filesystem.
If you're not part of the solution, you're part of the problem.
1. The cards are primarily designed for running "backups" with homebrew as an afterthought.
2. Homebrew authors insist on assuming things about their users and decide not to use features designed to make running homebrew easier.
The cards which currently do support argv do so because several users of those cards requested the feature from the card manufacturer. These users were encouraged to do so by homebrew authors who made use of the nitro filesystem.
If you're not part of the solution, you're part of the problem.
Who is online
Users browsing this forum: No registered users and 0 guests