Update translations

This commit is contained in:
Pk11 2021-12-19 13:34:46 -06:00
parent a708451b2c
commit 126855a266
23 changed files with 117 additions and 127 deletions

View File

@ -22,7 +22,7 @@ These are the builds that are present for all three lines of systems.
### Master
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build.
All other branches than this one are considered expmerimental and not stable enough to be included into the Master.
All other branches than this one are considered experimental and not stable enough to be included into the Master.
The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
### Wi-Fi-Link

View File

@ -21,7 +21,7 @@ These are the builds that are present for all three lines of systems.
### Master
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered expmerimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered experimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
### Wi-Fi-Link

View File

@ -3,7 +3,7 @@ lang: fr-FR
layout: wiki
section: ds-index
category: guides
title: DS Game Forwarders
title: Forwarders de jeu DS
description: How to use DS game forwarders on hiyaCFW or 3DS HOME menu
tabs:
-
@ -14,34 +14,25 @@ tabs:
Forwarders are shortcuts for games that you can install to your home menu or hiyaCFW menu. You can load DS games from the SD card (using nds-bootstrap) or from a compatible flashcard (via its respective kernel) using forwarders installed to your menu of choice. <!--- I feel like this still needs a bit of work. Still better than what was there before. -->
Les jeux de DS doivent être dumpés au format `.nds<code>. You can dump your DS cartridges using <a href="https://3ds.hacks.guide/dumping-titles-and-game-cartridges#dumping-a-game-cartridge">GodMode9</a> on 3DS, or <a href="https://dsi.cfw.guide/dumping-game-cards">GodMode9i</a> on DSi.
</p>
Les jeux de DS doivent être dumpés au format `.nds`. You can dump your DS cartridges using [GodMode9](https://3ds.hacks.guide/dumping-titles-and-game-cartridges#dumping-a-game-cartridge) on 3DS, or [GodMode9i](https://dsi.cfw.guide/dumping-game-cards) on DSi.
{:.alert .alert-info}
<p spaces-before="0">{:.alert .alert-info}</p>
Si vous rencontrez un problème, consultez la FAQ sur le [site GBAtemp](https://gbatemp.net/threads/nds-forwarder-cias-for-your-home-menu.426174/).
{:.alert .alert-warning}
<p spaces-before="0">If you have any issues, check the FAQs on the <a href="https://gbatemp.net/threads/nds-forwarder-cias-for-your-home-menu.426174/">GBAtemp thread</a>.
</p>
Choisissez l'un des éléments suivant à ajouter au menu Home :
<p spaces-before="0">{:.alert .alert-warning}</p>
{% capture tab-3ds-sd-card %}
<p spaces-before="0">Choose one of the following to add to the HOME menu:</p>
Cette page considère que vous possédez un CFW tel que celui utilisé dans le [guide](https://3ds.hacks.guide).
{:.alert .alert-warning}
<p spaces-before="0">{% capture tab-3ds-sd-card %}</p>
### Étape 1: Récupérer les fichiers nécessaires
<p spaces-before="0">This page assumes you are running a modern CFW environment from <a href="https://3ds.hacks.guide">3ds.hacks.guide</a>.
</p>
Si vous avez déjà Universal Updater installé sur votre console, vous pouvez passer à l'étape 3.
{:.alert .alert-info}
<p spaces-before="0">{:.alert .alert-warning}</p>
<h3 spaces-before="0">Étape 1: Récupérer les fichiers nécessaires</h3>
<p spaces-before="0">If you already have Universal Updater installed on your console, you can skip to step 3.
</p>
<p spaces-before="0">{:.alert .alert-info}</p>
<ol start="1">
<li>Ouvrez FBI, allez dans <code>Remote Install<code>, puis sélectionnez <code>Scan QR Code<code></li>
1. Ouvrez FBI, allez dans `Remote Install<code>, puis sélectionnez <code>Scan QR Code<code></li>
<li><p spaces-before="0">Scannez ce QR code pour installer la dernière version de <a href="https://github.com/Universal-Team/Universal-Updater">Universal Updater</a><br>
<img src="https://db.universal-team.net/assets/images/qr/universal-updater-cia.png" alt="Universal-Updater QR code" /></p></li>
<li><p spaces-before="0">Ouvrez Universal Updater depuis le menu Home</p></li>
@ -55,11 +46,10 @@ Les jeux de DS doivent être dumpés au format `.nds<code>. You can dump your DS
<li>Lancez l'Homebrew Launcher</li>
<li>Dans l'Homebrew Launcher, ouvrez <code>NDS Forwarder Generator<code></li>
<li>Naviguez à l'emplacement de votre jeu et appuyez sur <kbd class="face">A</kbd></li>
<li>Confirmez l'installation en choisissant <code>Yes`</li>
1
Une fois installé, votre jeu apparaîtra sous forme d'icône sur le menu Home
<li>Confirmez l'installation en choisissant <code>Yes`
1. Une fois installé, votre jeu apparaîtra sous forme d'icône sur le menu Home
{% endcapture %}
{% assign tab-3ds-sd-card = tab-3ds-sd-card | split: "////////" %}</ol>
{% assign tab-3ds-sd-card = tab-3ds-sd-card | split: "////////" %}
{% capture tab-dsi-sd-card %}

View File

@ -21,7 +21,7 @@ These are the builds that are present for all three lines of systems.
### Master
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered expmerimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered experimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
### Wi-Fi-Link

View File

@ -21,7 +21,7 @@ These are the builds that are present for all three lines of systems.
### Master
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered expmerimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered experimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
### Wi-Fi-Link

View File

@ -1,5 +1,5 @@
---
lang: en-US
lang: hu-HU
layout: wiki
section: gbarunner2
title: GBARunner2 build-ek
@ -21,29 +21,29 @@ Ezek azok a build-ek amik mindhárom rendszeren jelen vannak.
### Master
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered expmerimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
A Master buildek vagy "fő" buildek a GBARunner2 megfelelő kiadásai. Általában ez a legstabilabb build. Az összes többi ág ezen kívül kísérleti ágnak és nem elég stabilnak tekintett ahhoz, hogy bekerüljön a Master-be. A Master buildek a DS, a DSi és a 3DS számára készült különböző build-ekre oszlanak. Mindegyiknek a fájlneve végére hozzá lett illesztve a hozzá tartozó rendszer neve.
### Wi-Fi-Link
The Wi-Fi-Link branch adds the possibility to link up two systems wirelessly. Note that this does not go over the Internet, and this will never be possible. Currently your mileage will vary, and the only sure-fire game that will be able to keep a stable connection is Advance Guardian Heroes, and that is provided that you follow very specific instructions. Needless to say, consider this branch in its current state a novelty and a proof of concept, and not something to actually use. A few other games are able to connect, but they are very dependent on external factors like interference from other Wi-Fi signals, among many other things.
A Wi-Fi-Link ág lehetővé teszi két rendszer vezeték nélküli összekapcsolását. Fontos megjegyezni, hogy nem az Interneten keresztül és az nem is lesz soha lehetséges. A jelenlegi előrehaladás változó és az egyetlen biztosan stabil kapcsolatot tartani tudó az Advance Guardian Heroes és az is csak akkor, ha követed a nagyon speciális utasításokat. Mondani sem kell, hogy ezt az ág jelenlegi állapotában újdonságnak tekinthető és egy koncepció, nem olyannak, amit ténylegesen használni kell. Néhány más játék képes csatlakozni, de ezek nagyon függenek a külső tényezőktől, például más Wi-Fi jelek interferenciájától, sok más dolog mellett.
## DS-specifikus build-ek
### ARM7DLDI vs ARM9DLDI
**Normally use the ARM9DLDI**, and if that does not work then try the ARM7DLDI. Some flashcards need either the ARM7DLDI or the ARM9DLDI, and some might work with both. There is no list of which flashcards work with which builds, but if you are running into issues getting GBARunner2 to run then you might want to try the other one.
**Általában az ARM9DLDI-t használd**, és ha ez nem működik, akkor az ARM7DLDI-vel próbálkozz. Néhány flashcard-hoz vagy az ARM7DLDI vagy az ARM9DLDI szükséges, néhány pedig mindkettővel működhet. Nincs lista arról, hogy melyik flashcard melyik build-del működik, de ha problémáid vannak a GBARunner2 futtatásával, akkor érdemes a másikat kipróbálni.
There are no feature or performance differences between the two so there is no use in testing both to see if a game runs better or has less issues on the other.
A kettő között nincsenek funkció- vagy teljesítménybeli különbségek, így nincs értelme mindkettőt tesztelni, hogy kiderüljön, egy játék jobban fut-e vagy kevesebb problémája van-e a másikon.
See further down to find out what build you are currently using.
Lásd lejjebb az információkat, hogy megtudhasd, milyen buildet használsz jelenleg.
### ROM3M
If you are using TWiLightMenu++ then you are already using this feature in the GBARunner2 build that comes with it.
Ha TWiLightMenu++-t használod, akkor már használod ezt a szolgáltatást azzal a GBARunner2 build-del, ami vele érkezik.
This branch might help if trying to run ROMs that are a bit larger on the DS, but there is a limit due to the limited amount of RAM present in the DS. This is basically the Pokémon Emerald branch for the DS.
Ez az ág segíthet, ha olyan ROM-okat próbálsz futtatni a DS-en, amik nagyobbak, de van egy korlát a DS található korlátozott mennyiségű RAM miatt. Ez lényegében a Pokémon Emerald ág a DS-re.
Void Star made [a fork of GBARunner2](https://github.com/unresolvedsymbol/GBARunner2-DSL-Enhanced/releases) that combines this ROM3M branch with some other neat features, and this is the build that comes with TWiLightMenu++ if you are using a DS.
Void Star készített egy [a GBARunner2 ágat](https://github.com/unresolvedsymbol/GBARunner2-DSL-Enhanced/releases), amely egyesíti ezt a ROM3M ágat néhány más hasznos funkcióval, és ez az a build, amelyet a TWiLightMenu++ tartalmaz, ha DS-t használsz.
## DSi- és 3DS-specifikus build-ek

View File

@ -33,4 +33,4 @@ Manuálisan is megadhatod az SD-kártyán lévő bármely fordítási fájl elé
#### Hogyan módosítom a betűkészletet?
A GodMode9i betűtípusát úgy változtathatod meg, hogy kiválasztasz egy `.frf` betűtípus fájlt, majd a `Betűtípus betöltése`lehetőséget. Egy másik betűtípus alapértelmezettként való beállításához vagy helyezd el a `sd:/gm9i/font.frf` helyen, vagy szerkeszd a config fájlt (`sd:/gm9i/config.ini`), hogy a `FONT_PATH` oda mutasson, ahol a betűtípus fájl található.
You can find a few pre-converted fonts in the [resources folder](https://github.com/DS-Homebrew/GodMode9i/tree/master/resources/fonts) of the GitHub repository and you can convert your own from a PBM image and TXT file containing the Unicode mappings using GodMode9's [fontriff.py](https://github.com/d0k3/GodMode9/blob/master/utils/fontriff.py) script.
A GitHub repository [resources](https://github.com/DS-Homebrew/GodMode9i/tree/master/resources/fonts) mappájában találsz néhány előre konvertált betűtípust, és a sajátodat is konvertálhatod a PBM képből és az Unicode leképezéseket tartalmazó TXT fájlból a GodMode9 [fontriff.py](https://github.com/d0k3/GodMode9/blob/master/utils/fontriff.py) szkript segítségével.

View File

@ -7,12 +7,12 @@ long_title: nds-bootstrap GYIK & helyreállítás
description: GYIK & hibaelhárítás az nds-bootstrap-hez
---
#### I'm having issues with my ROM(s), what should I do?
#### Problémáim vannak a ROM(ok)-mal, mit tegyek?
- Make sure that you are on the latest release of [nds-bootstrap](https://github.com/DS-Homebrew/nds-bootstrap/releases/latest) and [TWiLight Menu++](https://github.com/DS-Homebrew/TWiLightMenu/releases/latest) if you are using it (update instructions are provided in each release page)
- Check the [the nds-bootstrap compatibility list](https://docs.google.com/spreadsheets/d/1LRTkXOUXraTMjg1eedz_f7b5jiuyMv2x6e_jY_nyHSc/htmlview#gid=0) to see if this is a known issue on the latest nds-bootstrap
- Try with all cheats disabled for that game as some cheats are not compatible with nds-bootstrap at the moment, pressing <kbd class="l">L</kbd> in the game's cheats menu on TWiLight Menu++ will disable all cheats for it
- Ha korábban működött, töröld a `fatTable` és a `patchOffsetCache` mappát az `sd:/_nds/nds-bootstrap/` könyvtárból
- Run the game with different settings, this includes ARM9 CPU Speed, Async card read, DS/DSi Mode, sound quality, Card read DMA, etc
- Futtasd a játékokat más beállításokkal beleértve az ARM9 CPU sebességet, DS/DSi módot, hang minőséget, aszink kártya olvasást, kártya DMA-t, stb.
- Using TWiLight Menu++, change all the per-game settings to `Default`
- If there is a specific per-game setting that causes your issue, please report this to the [GitHub](https://github.com/DS-Homebrew/nds-bootstrap/issues)
- If you have followed all the above steps, ask in the [Discord server](https://discord.gg/yD3spjv)

View File

@ -7,37 +7,37 @@ description: Fogalomjegyzék az nds-bootstrap-hez
---
## Beállítások
These can be found within TWiLight Menu++'s per-game settings. Some of these options can also be changed in nds-bootstrap's in-game menu
Ezek a TWiLight Menu++ játékonkénti beállításai között találhatók. Néhány opciót az nds-bootstrap játékon belüli menüjében is meg lehet változtatni
### SDK ver
The version of the Software Development Kit (SDK) that was used to compile the ROM. ROMs that require Donor ROMs must have the same SDK version as the Donor ROM.
A szoftverfejlesztő készlet (SDK) verziója, amelyet a ROM lefordításához használtak. A donor ROM-okat igénylő ROM-oknak ugyanazzal az SDK-verzióval kell rendelkezniük, mint a donor ROM-nak.
### Mentés szám
The save file for the game will have the `.savX` file extension where X is the given save number if the save number is not 0. This allows for up to 10 save files for the same ROM.
A játék mentési fájljának a `.savX` fájlkiterjesztés lesz, ahol X az adott mentési szám, ha a mentési szám nem 0. Ez akár 10 mentési fájlt is lehetővé tesz ugyanahhoz a ROM-hoz.
### Run in
The Mode which the ROM should be run. This affects the ARM9 CPU Speed and VRAM Mode options. Setting to DSi Mode for ROMs that do not support will likely have no effect.
### Futtatás mód
A mód amiben a ROM-nak futnia kell. Ez az ARM9 CPU sebesség és a VRAM mód beállításait érinti. A DSi Mode beállítása olyan ROM-ok esetében, amelyek nem támogatják az, valószínűleg hatás nélküli.
### ARM9 CPU sebesség
Changes the speed at which the ARM9 CPU runs. ROMs ran in DS Mode will use 67 Mhz (NTR) by default. This can be changed to 133 Mhz (TWL) to reduce slowdowns, but may also cause issues. ROMs ran in DSi Mode can only be set at 133 Mhz (TWL).
Módosítja az ARM9 CPU futási sebességét. A DS módban futtatott ROM-ok alapértelmezés szerint 67 Mhz-et (NTR) használnak. Ez 133 Mhz-re (TWL) módosítható a lassulások csökkentése érdekében, de ez is okozhat problémákat. A DSi módban futtatott ROM-ok csak 133 Mhz-re (TWL) állíthatók be.
### VRAM mód
Changes the mode of the Video Random Access Memory (VRAM) of the system. ROMs ran in DS Mode will use the DS VRAM Mode by default. This can be changed to DSi VRAM Mode but does not do anything and may cause visual issues. ROMs ran in DSi Mode can only be set at DSi VRAM Mode.
Módosítja a rendszer Video Random Access Memory (VRAM) üzemmódját. A DS módban futtatott ROM-ok alapértelmezés szerint a DS VRAM módot használják. Ez megváltoztatható DSi VRAM módra, de ez nem csinál semmit, és vizuális problémákat okozhat. A DSi módban futtatott ROM-ok csak DSi VRAM módra állíthatók be.
### Kártya olvasás DMA
Enables the uses of Direct Memory Access (DMA) for card reads. Having this setting on can speed up ROMs but may cause issues. More technical info can be found on the [DS Index](https://wiki.ds-homebrew.com/ds-index/retail-roms#card-read-dma).
Engedélyezi a közvetlen memória-hozzáférés (DMA) használatát a kártya olvasáshoz. Ennek a beállításnak a bekapcsolása felgyorsíthatja a ROM-okat, de problémákat okozhat. További technikai információk a [DS Index](https://wiki.ds-homebrew.com/ds-index/retail-roms#card-read-dma) oldalon találhatók.
### SWI Halt-ra csatlakozás
Changes whether Halt Software Interrupts (SWI) are Hooked or not. Having it set to On can speed up loading times, but might cause issues. Keeping it Off may reduce slowdowns as well.
Megváltoztatja, hogy a Halt Software Interrupts (SWI) csatlakoztatva vannak-e vagy sem. Ha bekapcsolva van, az felgyorsíthatja a betöltési időt, de problémákat okozhat. A kikapcsolt állapotban tartás a lassulásokat is csökkentheti.
### Ex. ROM space in RAM
If a game is small enough, it can be loaded into the system's RAM to speed up loading times. Turning this option on will increase the size limit for ROMs, but might break some.
### ROM bővítés RAM-ban
Ha egy játék elég kicsi, akkor a betöltési idő felgyorsítása érdekében a rendszer RAM memóriájába tölthető. Az opciót bekapcsolása, megnöveli a ROM-ok méretkorlátot, de néhány hibás lehet.
### Közvetlen boot
Appears only for homebrew ROMs. Setting this to On will not use nds-bootstrap when launching the ROM. This is useful for homebrew ROMs that do not need or work with nds-bootstrap.
Csak a homebrew ROM-ok esetében jelenik meg. Ha ezt a beállítást bekapcsolt nem használja az nds-bootstrap-et a ROM indításakor. Ez olyan homebrew ROM-ok esetében hasznos, amelyeknek nincs szükségük az nds-bootstrap-re, vagy nem működnek vele.
### Bootstrap
Change whether to run the ROM with either the Release or Nightly build of nds-bootstrap. Information on Nightly builds can be found on the [nds-bootstrap FAQ](https://wiki.ds-homebrew.com/nds-bootstrap/faq?faq=what-is-a-nightly-and-where-do-i-get-it)
Módosíthatod, hogy a ROM az nds-bootstrap Kiadás (Release) vagy Esti fordítás (Nightly) build-jével fusson-e. Az Esti (Nightly) buildek-kel kapcsolatos információk a [nds-bootstrap GYIK](https://wiki.ds-homebrew.com/nds-bootstrap/faq?faq=what-is-a-nightly-and-where-do-i-get-it) oldalon találhatók
### Képernyő arány
3DS esetén a képernyő képaránya 4:3 (alapértelmezett a DS/DSi esetében) helyett 16:10-re változtatható. Csak akkor működik, ha a [széles képernyő engedélyezett](https://wiki.ds-homebrew.com/twilightmenu/playing-in-widescreen).

View File

@ -7,30 +7,30 @@ description: Kompatibilitási lista és tippek a ROM-ok teszteléséhez
---
### Kompatibilitási lista
A tesztelt ROM-ok megtekintéséhez nyisd meg a [kompatibilitás listát](https://docs.google.com/spreadsheets/d/1LRTkXOUXraTMjg1eedz_f7b5jiuyMv2x6e_jY_nyHSc/). Ha szeretnél közreműködni, nyomj a `View only`-ra majd a `Request edit access`-re. Make sure to add entries to the proper sheet according to the tabs on the bottom of the page.
A tesztelt ROM-ok megtekintéséhez nyisd meg a [kompatibilitás listát](https://docs.google.com/spreadsheets/d/1LRTkXOUXraTMjg1eedz_f7b5jiuyMv2x6e_jY_nyHSc/). Ha szeretnél közreműködni, nyomj a `View only`-ra majd a `Request edit access`-re. Győződj meg róla, hogy a bejegyzéseket a megfelelő laphoz adod hozzá az oldal alján található füleknek megfelelően.
To view ROMs with known issues, check the [issues page](https://github.com/DS-Homebrew/nds-bootstrap/issues) on Github. If you want to create a [new issue](https://github.com/DS-Homebrew/nds-bootstrap/issues/new), please properly follow the issue template.
Az ismert problémákkal rendelkező ROM-ok megtekintéséhez nézd meg az [issues oldalt](https://github.com/DS-Homebrew/nds-bootstrap/issues) a Githubon. Ha egy [új hibát (issue)](https://github.com/DS-Homebrew/nds-bootstrap/issues/new) szeretnél létrehozni, kérjük, kövesd megfelelően az issue template-et.
### Tippek a ROM-ok teszteléséhez
- In general, look through the [nds-bootstrap FAQ](https://wiki.ds-homebrew.com/nds-bootstrap/faq) and [glossary](https://wiki.ds-homebrew.com/nds-bootstrap/glossary) to make sure that you understand how to troubleshoot issues
- Általánosságban nézd át az [nds-bootstrap GYIK](https://wiki.ds-homebrew.com/nds-bootstrap/faq) és a [fogalomjegyzék](https://wiki.ds-homebrew.com/nds-bootstrap/glossary) oldalakat, hogy biztos legyél abban, hogy érted, hogyan kell a problémákat elhárítani
#### If testing for a specific reported bug
- Replicate the steps as close as possible
- If there are any differences (such as nds-bootstrap version, system used, or settings changed), make sure to include that in your report
- Feel free to ask the original reporter for more details (such as uploading a save file or any missing information) if possible
- If there is no solution, make sure to update the compatibility list
#### Ha egy konkrét bejelentett hibát tesztelsz
- Ismételd meg a lépéseket, amilyen pontosan csak lehet
- Ha bármilyen eltérés van (például az nds-bootstrap verziója, a használt rendszer vagy módosított beállítások), ezt mindenképpen írd bele a jelentésedbe
- Nyugodtan kérj az eredeti bejelentőtől további részleteket (például mentési fájl feltöltését vagy bármilyen hiányzó információt), ha lehetséges
- Ha nincs megoldás, frissítsd a kompatibilitási listát
#### If a ROM has an issue after updating nds-bootstrap
- Find which specific version first introduced this issue
- You can downgrade nds-bootstrap by downloading a [past release](https://github.com/DS-Homebrew/nds-bootstrap/releases) and following the update instructions
- Downgrading to a past release of [TWiLight Menu++](https://github.com/DS-Homebrew/TWiLightMenu/releases) might be needed as well
#### Ha egy ROM-nak problémája van az nds-bootstrap frissítése után
- Keresd meg, melyik verziótól jelent meg először ez a probléma
- Az nds-bootstrap downgrade-je egy [korábbi](https://github.com/DS-Homebrew/nds-bootstrap/releases) kiadás letöltésével és a frissítési utasítások követésével elvégezhető
- A [TWiLight Menu++](https://github.com/DS-Homebrew/TWiLightMenu/releases) korábbi kiadására való visszaváltás is szükséges lehet
#### If testing for a ROM that has no known issues or has not been tested before
- Be thorough with testing the ROM, going through anything that other users might see
- Make sure to add the appropriate information on the compatibility list on the correct sheet
- Also make sure to remove games that have been tested off of the Testing Queue sheet
#### Ha olyan ROM-ot tesztelsz, amelynek nincsenek ismert problémái, vagy amelyet korábban még nem teszteltek
- Legyél alapos a ROM tesztelése során, és nézz át mindent, amit más felhasználók esetleg látnak
- Add hozzá a megfelelő információkat kompatibilitási listához a megfelelő lapon
- Ne felejtsd el eltávolítani a tesztelt játékokat a tesztelési várólistáról (Testing Queue)
#### If testing to update blacklists
- Change only the blacklisted options, these being: 133 MHz (TWL) CPU Speed, Card Read DMA, Asynch Card Read, and SWI Halt Hook
- To enable blacklisted options in the per-game settings, go to `sd:/_nds/TWiLightMenu/settings.ini` and set `IGNORE_BLACKLISTS` to `1`
- If there are any issues caused when turning on these settings, please report them on the Github issues page
#### Ha a feketelisták frissítése miatt tesztelsz
- Csak a feketelistán szereplő opciókat változtasd meg, ezek a következők: 133 MHz (TWL) CPU sebesség, Kártya olvasás DMA, Aszink kártya olvasás és SWI Halt kapcsolódás
- A feketelistás opciók engedélyezéséhez a játékonkénti beállításokban menj a `sd:/_nds/TWiLightMenu/settings.ini` fájlba, és állítsd az `IGNORE_BLACKLISTS` opciót `1`értékre
- Ha bármilyen probléma merül fel ezen beállítások bekapcsolása során, kérjük, jelentsd a Github issues oldalon

View File

@ -21,7 +21,7 @@ crwdns28367:0crwdne28367:0
### crwdns28369:0crwdne28369:0
crwdns28371:0crwdne28371:0 crwdns28373:0crwdne28373:0 crwdns28375:0crwdne28375:0 crwdns28377:0crwdne28377:0 crwdns28379:0crwdne28379:0
crwdns28371:0crwdne28371:0 crwdns28373:0crwdne28373:0 crwdns28531:0crwdne28531:0 crwdns28377:0crwdne28377:0 crwdns28379:0crwdne28379:0
### crwdns28381:0crwdne28381:0

View File

@ -1,55 +1,55 @@
---
lang: en-US
lang: id-ID
layout: wiki
section: ds-index
category: guides
title: Hardmod
description: How to hardmod a Nintendo DSi
title: Modifikasi Keras (Hardmod)
description: Cara meng-hardmod Nintendo DSi
tabs:
-
windows: Windows
other: macOS/Linux
---
Hardmodding is when you physically solder the motherboard of the Nintendo DSi to an SD card adapter in order to be read on a computer. This is useful for restoring NAND backups, viewing NAND on your PC, etc...
Memodifikasi keras (Hardmod) adalah ketika Anda mematri lunak fisik papan induk konsol Nintendo DSi ke adaptor kartu SD agar terbaca di komputer. Ini berguna untuk memulihkan cadangan NAND, melihat NAND di komputer, dll...
### Nintendo DS
[![Original DS motherboard with touch-points labeled](/assets/images/ds-hardmod/mobo_pinout.png)](/assets/images/ds-hardmod/mobo_pinout.png)
[![Papan induk DS Original dengan titik sentuh berlabel](/assets/images/ds-hardmod/mobo_pinout.png)](/assets/images/ds-hardmod/mobo_pinout.png)
### Nintendo DSi
To hardmod a Nintendo DSi/DSi XL (LL) you will need:
Untuk memodifikasi keras Nintendo DSi/DSi XL (LL) dibutuhkan:
- [Pencil tipped soldering iron](https://www.amazon.com/dp/B01N4571Q6)
- [Very fine wire](https://www.amazon.com/dp/B01MXGNTA4), 28AWG or smaller, preferably 30AWG+
- SD to microSD adapter
- An SD card reader able to read eMMC chips running in single data-line mode. [Here's a known working one](https://www.amazon.com/dp/B006T9B6R2)
- [Win32DiskImager](https://sourceforge.net/projects/win32diskimager/) and [HxD](https://mh-nexus.de/en/downloads.php?product=HxD20) if on Windows
- Adaptor SD ke microSD
- Pembaca (reader) kartu SD yang mampu membaca cip eMMC berjalan di mode single data-line. [Ini yang dikenal bisa](https://www.amazon.com/dp/B006T9B6R2)
- [Win32DiskImager](https://sourceforge.net/projects/win32diskimager/) dan [HxD](https://mh-nexus.de/en/downloads.php?product=HxD20) jika di Windows
- A valid NAND backup of the DSi you are hardmodding
- To be comfortable soldering to pads that are as small as 0.5mm in diameter
#### DSi side A pinouts
#### Pin-out DSi sisi A
[![DSi side A pinouts](/assets/images/dsi-hardmod/side_a.jpg)](/assets/images/dsi-hardmod/side_a.jpg)
#### DSi side B pinouts
#### Pin-out DSi sisi B
[![DSi side B pinouts](/assets/images/dsi-hardmod/side_b.png)](/assets/images/dsi-hardmod/side_b.png)
#### DSi XL side B pinouts
#### Pin-out DSi XL sisi B
[![DSi XL side B pinouts](/assets/images/dsi-hardmod/dsi_xl_side_b.png)](/assets/images/dsi-hardmod/dsi_xl_side_b.png)
- You will need to solder the points on the motherboard to the microSD card adapter
- CMD to pin 2
- GND to pins 3 and 6
- CLK to pin 5
- DAT0 to pin 7
- Anda perlu mematri titik (point) pada papan induk ke adapter kartu microSD
- CMD ke pin 2
- GND ke pin 3 dan 6
- CLK ke pin 5
- DAT0 ke pin 7
#### Soldered microSD adapter example
#### Contoh adaptor microSD terpatri lunak
[![microSD example](/assets/images/dsi-hardmod/sd.jpg)](/assets/images/dsi-hardmod/sd.jpg)
- Insert the microSD card adapter into your computer
- **WARNING** - Windows will ask you to format it: **DO NOT** format it - this might cause irrepairable damage
- Sisipkan adaptor kartu microSD ke komputer Anda
- **PERINGATAN** - Jika Windows meminta memformat: **JANGAN diformat** - bisa terjadi kerusakan tak bisa diperbaiki
#### Removing the no$gba footer
You will first need to remove the NOCASH footer from the backup you are flashing to the DSi. This can be done using the [hiyaCFW helper](https://github.com/mondul/HiyaCFW-Helper/releases/latest).
#### Membuang footer no$gba
You will first need to remove the NOCASH footer from the backup you are flashing to the DSi. Caranya bisa dengan [hiyaCFW helper](https://github.com/mondul/HiyaCFW-Helper/releases/latest).
1. Download the version for the operating system you are using
1. Unduh versi aplikasi untuk sistem operasi yang Anda gunakan
1. Run the script, selecting the NAND backup you wish to flash to your DSi
1. Switch to NAND mode with the button to the left of the file path
1. Click `Start` to create the NAND backup without the no$gba footer
@ -58,7 +58,7 @@ You will first need to remove the NOCASH footer from the backup you are flashing
- Use this file as the NAND image you flash onto the DSi
{% capture tab-windows %}
1. Open Win32DiskImager
1. Buka Win32DiskImager
1. Click the folder icon and browse to your desktop. In the text box, write `NAND_0.bin`. When selecting type, choose `All types *.*`
1. Choose the device that is the DSi and click read
1. Once it is done, click the folder icon, change the name to `NAND_1.bin` and read again
@ -68,7 +68,7 @@ You will first need to remove the NOCASH footer from the backup you are flashing
- If it doesn't say that, and both NANDs aren't around 240 MB, dump NAND_1/NAND_0 again
1. Open Win32DiskImager, click the folder icon and choose your existing NAND backup you created before
1. Flash it with the `Write` button
1. Unplug the SD card adapter and attempt to turn on the DSi
1. Cabut adaptor kartu SD dan coba hidupkan konsol DSi
{% endcapture tab-windows %}
{% assign tab-windows = tab-windows | split: "////////" %}
@ -109,7 +109,7 @@ You will first need to remove the NOCASH footer from the backup you are flashing
1. Flash NAND
1. Locate the NAND backup you created before on the console
1. Run the following command:
1. Jalankan perintah berikut:
- `cat {existing-nand-backup} > {device-name}`
- Replace `{existing-nand-backup}` with the location and name of your old NAND backup
- Replace `{device-name}` with the mount point of the SD card

View File

@ -1,27 +1,27 @@
---
lang: en-US
lang: id-ID
layout: wiki
section: gbarunner2
title: GBARunner2 Builds
description: Information on the various GBARunner2 Builds and their uses
title: Binaan (Build) GBARunner2
description: Informasi tentang beragam Build GBARunner2 dan kegunaannya
---
There are a number of different GBARunner2 releases or "builds" which one can use. They come from different branches and forks of GBARunner2 and have different features targeting either different GBA games or some different functions. **For most users** using the build that comes with TWiLightMenu++ is enough.
Ada sejumlah lepasan (release) atau "build" GBARunner2 berbeda yang dapat digunakan. Asalnya dari cabang (branch) dan fork GBARunner2 yang juga mempunyai fitur berbeda baik untuk permainan GBA lain atau beberapa kegunaan lain. **Bagi kebanyakan pengguna**, menggunakan build yang disertakan di TWiLightMenu++ sudah cukup.
## DS vs DSi vs 3DS Builds
## Build DS vs DSi vs 3DS
GBARunner2 has had builds made that makes use of the extra hardware found inside the DSi and 3DS. Naturally, these DSi- and 3DS-specific builds will not work on a DS. However, they also will not work if you are running GBARunner2 from a flashcard on any of the systems, DSi and 3DS included. The details about this will not be covered here.
This means that you can use builds for the DS on both DSi and 3DS, but not vice-versa.
Ini artinya Anda dapat menggunakan build untuk DS di konsol DSi dan 3DS, tapi tidak sebaliknya.
## Shared Builds Between the DS, DSi and 3DS
## Build yang sebagi antara DS, DSi dan 3DS
These are the builds that are present for all three lines of systems.
Berikut adalah build yang terdapat pada ketiga deret sistem.
### Master
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered expmerimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. Semua cabang selain yang ini dianggap dicoba-coba dan tidak cukup stabil untuk dimasukkan ke bentuk Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
### Wi-Fi-Link
@ -65,12 +65,12 @@ This branch makes use of the internal accelerometer in the 3DS so that GBA games
There is no consistency in what type of 3DS has what chip, at least as far as anyone knows.
## Finding the Build Info
## Memeriksa Info Build
GBARunner2 has an menu you can open by touching the touch screen and pressing the right shoulder button. Within this you can find the about menu which tells you what build you are on. However, the builds that come with TWiLightMenu++ do not report a build version because they are based on forks by other people. This means that if your About page shows blank for build, you are most likely using one of these.
GBARunner2 mempunyai menu yang dapat dibuka dengan menyentuh layar bawah dan menekan tombol R. Dengan ini Anda dapat mencari menu About yang menjelaskan ada di build berapa. Namun, build yang disertakan di TWiLightMenu++ tidak menulis versi build karena sudah didasarkan pada fork dari orang lain. Ini artinya jika di halaman About hanya kosong saja tentang build, kemungkinan Anda menggunakan yang sudah disertakan.
This tells you if you are using an ARM7DLDI or ARM9DLDI build
Ini agar tahu jika yang digunakan build ARM7DLDI atau ARM9DLDI
Knowing what build to use is useful when checking the official compatibility list in case you are having issues with running a game.
Mengetahui build yang digunakan dapat berguna ketika memeriksa daftar kesesuaian (compatibility list) resmi jika saja mengalami isu menjalankan permainan.
The release ID can be seen on the release page of the GBARunner2's github repository, where the last seven alphanumeric symbols represent the version. For example, the current latest Master release is "v20200812-131430_6e4ce45" and "6e4ce45" is used to represent its version.
Bilangan ID lepasan (release) dapat dilihat pada laman release repository github GBARunner2, tulisan versinya terdiri dari tujuh alfanumerik. Contohnya, lepasan Master terbaru saat ini "v20200812-131430_6e4ce45" dan "6e4ce45" yang mewakili bilangan versinya.

View File

@ -12,7 +12,7 @@ Jika Anda belum punya cara menjalankan homebrew di DSi, ikuti [dsi.cfw.guide](ht
{:.alert .alert-info}
### Pemasangan (Installing)
1. Unduh (download) [`TWiLightMenu-DSi.7z`](https://github.com/DS-Homebrew/TWiLightMenu/releases/latest/download/TWiLightMenu-DSi.7z) versi terbaru
1. Unduh [`TWiLightMenu-DSi.7z`](https://github.com/DS-Homebrew/TWiLightMenu/releases/latest/download/TWiLightMenu-DSi.7z) versi terbaru
1. Ekstrak `TWiLightMenu-DSi.7z`
1. Salin folder `_nds` ke root kartu SD
1. Salin berkas `BOOT.NDS` ke root kartu SD

View File

@ -9,7 +9,7 @@ description: Cara memasang TWiLight Menu++ pada flashcard Nintendo DS
---
### Pemasangan (Installing)
1. Unduh (download) [`TWiLightMenu-Flashcard.7z`](https://github.com/DS-Homebrew/TWiLightMenu/releases/latest/download/TWiLightMenu-Flashcard.7z) versi terbaru
1. Unduh [`TWiLightMenu-Flashcard.7z`](https://github.com/DS-Homebrew/TWiLightMenu/releases/latest/download/TWiLightMenu-Flashcard.7z) versi terbaru
1. Ekstrak `TWiLightMenu-Flashcard.7z`
1. Salin folder `_nds` ke root kartu microSD flashcard
1. Salin berkas `BOOT.NDS` ke root kartu microSD flashcard
@ -44,7 +44,7 @@ Mohon diingat tidak semua flashcard dapat memainkan permainan dengan cara ini. J
- M3i Zero (non-GMP-Z003 model)
- DSONE SDHC & DSONEi
Install [RetroGameFan's YSMenu](https://gbatemp.net/threads/retrogamefan-updates-releases.267243/).
Pasang [YSMenu-nya RetroGameFan](https://gbatemp.net/threads/retrogamefan-updates-releases.267243/).
- Make sure you have `YSMenu.nds` (renamed from `TTMenu.dat` if there isn't one) and the `TTMenu` folder on the flashcard microSD root
1. Ubah `Gunakan nds-bootstrap` ke `Tak`, agar yang digunakan bukan nds-bootstrap tetapi firmware flashcard

View File

@ -15,7 +15,7 @@ Jika memperbarui dari versi yang lebih tua dari v21.0.0, mohon pindahkan dulu be
{:.alert .alert-info}
### Pemerbaruan (Updating)
1. Unduh (download) [`TWiLightMenu-DSi.7z`](https://github.com/DS-Homebrew/TWiLightMenu/releases/latest/download/TWiLightMenu-DSi.7z) versi terbaru
1. Unduh [`TWiLightMenu-DSi.7z`](https://github.com/DS-Homebrew/TWiLightMenu/releases/latest/download/TWiLightMenu-DSi.7z) versi terbaru
1. Ekstrak `TWiLightMenu-DSi.7z`
1. Salin folder `_nds` ke root kartu SD
1. Salin berkas `BOOT.NDS` ke root kartu SD

View File

@ -21,7 +21,7 @@ These are the builds that are present for all three lines of systems.
### Master
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered expmerimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered experimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
### Wi-Fi-Link

View File

@ -21,7 +21,7 @@ These are the builds that are present for all three lines of systems.
### Master
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered expmerimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered experimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
### Wi-Fi-Link

View File

@ -21,7 +21,7 @@ These are the builds that are present for all three lines of systems.
### Master
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered expmerimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered experimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
### Wi-Fi-Link

View File

@ -21,7 +21,7 @@ These are the builds that are present for all three lines of systems.
### Master
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered expmerimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered experimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
### Wi-Fi-Link

View File

@ -21,7 +21,7 @@ These are the builds that are present for all three lines of systems.
### Master
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered expmerimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered experimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
### Wi-Fi-Link

View File

@ -21,7 +21,7 @@ These are the builds that are present for all three lines of systems.
### Master
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered expmerimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered experimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
### Wi-Fi-Link

View File

@ -21,7 +21,7 @@ These are the builds that are present for all three lines of systems.
### Master
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered expmerimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build. All other branches than this one are considered experimental and not stable enough to be included into the Master. The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
### Wi-Fi-Link