Wanted to shed some light on the MediaFire problem/problems, if anyone's interested.
With 99 % certainty, I can tell you that it's not the game/file that's the problem, or even the site itself, if we strictly consider only [
You must be registered to see links
]. They have also made some changes on the site, but I'll get to that later. The main problem occurs when you click to download the file, due to each file having a unique code for every link you click on, when you click 'Download'. It would be somethinlg like: dl163.mediafire.com/file/riyTz3468.html (This is just an example, as I didn't get the chance to copy the actual link, or screenshot it, before the connection was dropped, due to my antivirus and other things I have in place to keep virus or malware from getting in.)
But what matters here in the example, is the 163 in the file link. So when you click on the 'Download' button, it actually gives you the adress, and redirects you to said location and file, in the example given, location 163 and file as described on the first original link, like the one in the first page of this thread. And previously, this was handled by the site redirecting you to that 163 adress, by opening a new tab just for a second, while fetching the link, and closing again, upon which a window would open on your computer, asking you where you would like to store the file, as in normal procedure on your end. But this is where it gets tricky.
When the location 163 is infected, or other issues are present, you will see what people in this thread has experienced, when they tried to download the game. But I can't speak for the rest of them, only they know what their actual error notification said, if they actually read it, that is. Sure, It was the "PR_CONNECT_RESET_ERROR", but if you read further below the main error identifier, some additional info can be found, explaining why the connection was dropped. And what I could read, said that transferred data could not be authenticated, which could mean a couple of things. In the less scary scenario, it just means they forgot to renew the certificate for the 163 location, and therefore our antivurus blocks it, just to be on the safe side. But in the worst case scenario, it means that the 163 location IS infected, with malware, virus, or spyware, and our antivirus was correct to block it.
I recently had a similar experience, when trying to download a game, but I can't remember if it was here, or on the other forum (the 95 one) for games like these. But I think it was here. So I just changed the link a little bit, and voila - everything was fine and no security alerts. But it was a little bit different too, in the sense that in that particular instance, it was the actual OP link, that my antivirus blocked, as it was slightly different at the end of the URL, like .com vs. .co, for example.
And finally, I have to apologize, for two reasons. First because this was a bit long, if you've read this far, lol. Secondly, I noticed the problem with MediaFire about two weeks ago, at least, and I didn't let you guys know about it. I should have made a post about it, so you could have been aware of it, but I didn't, and I'm sorry about that. And lastly, about the changes MediaFire has made, which I became aware of when I tried to download a game, but the OP link had a different ending than what it normally is, as I mentioned in the section above this one. And that WAS on 95, and I remember that very well, as 95 typically has Mega, gofile, pixedrain and several other options to download from, but in that case, only MediaFire other than Mega available.
And since I prefer keeping Mega "open" for bigger games (as it's fast AF - up to 75 Mbit downspeed), I had no choice but to go with MediaFire. But as soon as I got on the page, not only was there all the (new) stuff you had to consent to in order to proceed (which wasn't there in the past), but also on top of that, the antivirus going off when I clicked on the download button. So on 95, if there was the choice of MediaFire or workupload, I would always choose workupload after that. So again, sorry for not telling you guys sooner, but at least now you know.
And a little PS at the end:
I'm no computer expert at all, I know far less than what it may seem in this post, but I learn as I go, and I read error messages very carefully, to see if the problem is on my end or the other, and if it can be fixed. So take it for what it is, just a little heads up, and know that I have stayed away from MediaFire since that time with the 95 forum, and because I think MediaFire was asking too much to consent to, including selling your data to third parties, and they said so openly, when you read their consent form. But do as you like, this is just where I stand when it comes to them.
