- Joined
- Nov 24, 2018
- Messages
- 151
- Trophies
- 0
- Age
- 47
- Location
- U.S.A.
- Website
- www.beyondwindows10.com
- XP
- 682
- Country
FYI, fake cards can be found on ebay and amazon. I found out that 2 of my 200gb cards are definitely fake. Also there is the program called H2TEST that will test several details about the card you own.
Personally, I would recommend you look into my claims. You will benefit more than just getting answers to your questions.
Remember that latest Atmosphere has changed the entry names in the emummc ini file. For example, It is no more "emummc_enabled", but just "enabled".
oh lol this fixed long ago im drafting a new release 2.0.0
its mater of seconds now ...
--------------------- MERGED ---------------------------
2.0.0 is ready , check the OP
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 45
- Location
- Engine room, learning
- XP
- 15,648
- Country
Thank you for that tool.
I have a general question, doesn't atmosphere allow emuMMC path to be outside of "emuMMC" folder? can you choose your own folder name? (just to make it less easier to detect by nintendo
)
I have a general question, doesn't atmosphere allow emuMMC path to be outside of "emuMMC" folder? can you choose your own folder name? (just to make it less easier to detect by nintendo
)
path is hardcoded in ams, https://github.com/Atmosphere-NX/At...91273/fusee/fusee-secondary/src/nxboot.c#L236Thank you for that tool.
I have a general question, doesn't atmosphere allow emuMMC path to be outside of "emuMMC" folder? can you choose your own folder name? (just to make it less easier to detect by nintendo
It has various bugs. It truncates the "sector" entry of the ini file, damaging it. This happens also if enabled is at the bottom of the ini, "far away" from the "sector" entry,
If the ini is in UTF8 with BOM, the parser does not read the ini file properly.
If the ini is in UTF8 with BOM, the parser does not read the ini file properly.
Last edited by ::Phoenix::,
make sure your ini layout is set like this and youll have no problems next, "my ini" (just like NYX set it up)
[emummc]
enabled = 0
sector=0xaf9c000
path=emuMMC/RAW1
id=0x0000
nintendo_path=emuMMC/RAW1/Nintendo
well i have incountered this bug only ones and after fixing/replacing the ini . it never accured again, so im not sure.
please check it out
Last edited by KuranKu,
I believe your ini parser assumes CRLF as the new line in the file. I am not sure about that, but after adding some emtpy new lines between the different entries, it started working.
im sure its weird behaviour and i never couldnt replicate it again after the time it happened and as i said i have fixed sector entry manualy and this bug never happened again so im not even sure atm.
I just checked. The problem is the way the new line is encoded in the ini file. If it is linux style (known as LF, which is one byte), the tool truncates what comes after "enabled", this because it assumes Windows style new line instead (known as CRLF, which is two bytes instead).
If you want to replicate the bug, just open the ini with visual studio code, and at the bottom right select LF instead of CRLF, and save.
I believe Hekate creates the emummc.ini file using LF new lines, then your tool cannot be used after creating emuMMC with Hekate, unless you manually fix it first. This might prevent many users on using your tool in the first place.
Last edited by ::Phoenix::,
Similar threads
-
- Article
-
The Real Jdbye
*is birb* -
Veho
-
Psionic Roshambo
-
@
Psionic Roshambo:
If your not getting your pills from Psi's discount drugs who knows what your swallowing!+1
-
@
Psionic Roshambo:
Shawnita used to get her pills from some other street pharmacist and after switching to The Psi Discount plan she now only has to swallow two things a day!+1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
The Real Jdbye:
i have that stupid connector on my gpu luckily it's only a 300w gpu so i should(?) be fine since all the issues are with the quad 8pin->12pin and mine is only dual 8pin
-
-
-
@
The Real Jdbye:
quite a tight bend on that 8pin->12pin adapter in my case, which is the worst case scenario, but i made sure it was fully seated after plugging everything in and bending the cable so it shouldn't come unseated by itself since i pre-stressed the cable
@
The Real Jdbye:
quite a tight bend on that 8pin->12pin adapter in my case, which is the worst case scenario, but...