TmEE wrote:On my 9x machines I use RetroZilla for the sites that Opera can no longer open due to some security protocols related issue.
Thanks! I didn't knew that program. I thought Opera 10.53 was the newest browser working on win9x, but that's about 8-10 years old. Hmmm, downloading RetroZilla without https seems to be impossible ; ) okay, downloaded it on a laptop, and moved the installer to my PC...
It can access https gbatemp, but with the gbatemp java script adverts, it's endless slow, and the browser seems to have no option for disabling java script for certain webpages (it can only disable it for all
As for other https sites: Sourceforge bugs saying that the webpage is empty. And github uses a "not enabled" https security protocol (I am using the latest RetroZilla version from 2017, which is itself being hosted on github - meaning that RetroZilla is unable to browse to its own homepage).
RetroZilla doesn't seem to be of too much use at the moment : / but thanks for mentioning it! Maybe it'll be useful for some other webpage someday (or maybe it gets updated and works better in next version).
edo9300 wrote:Weirdly enough... The 1,3 stil doesn't work :( at this point i think it's my ds
The only thing not working for you is booting without sd-card inserted (or button A pressed), and then it hangs while displaying the unlaunch version number and attempting to load the original launcher, right?
I would assume that you have somehow lost your launcher ".app" file, or some other important system files. My guess would be about the issue from unlaunch v0.6, which could cause launcher to get deleted when accessing data managment, or dsi shop, or 3ds transfer tool - did you did that back then when v0.6 was out? Or did you try to upgrade/downgrade the firmware at some point after installing unlaunch?
If it's for one of the above reasons, then it could be repaired, and the same issue should also occur when testing in no$gba. Did you really test that, using a backup of your CURRENT emmc/nand, and renaming it to dsi-1.mmc, and using that in no$gba, with dsi mode enabled, and with the entrypoint set to BIOS mode, and then start some random dsi title? If yes, then you should see the unlaunch v1.3 screen, and then see the launcher (or it should hang in the unlaunch screen if the problem occurs in no$gba, too). If you just see the loaded game (without preceeding unlaunch and launcher screens), then you didn't test it properly.
Well, that are quite some steps, I am not sure if you really did all that stuff when testing - or if you had just tested a random game in no$gba, and then figured that "working game" is same as "working firmware image" (which isn't so).
For some general checks, you also dump your emmc, decrypt it with twltool, mount it, and then use scandisk to check for obvious errors, and check the launcher's content folder to see if it still has the .app and .tmd files, and the hwinfo files in other folders (gbatek has a list of files/folders that should be present, see the SD/MMC filesystem chapters).