Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - pvtgmerpyleusmc

Pages: 1 [2]
16
when I tried to launch FH2 earlier, it refused my connection.  I went into the launcher, showed my user password.  Noted it was correct.  Then when I tried to launch I saw this:

Connecting to GameSpy Server.
An error occurred while verifying "pvtgmerpyleusmc" GameSpy account:

Couldn't connect to bfewaw.com server.    <-- This seems really odd.  What does the bfewaw.com server have to do with FH2 authentication?

I didn't think FH2 still relied on GameSpy.  Why am I seeing this, and why can I no longer play?  Any ideas / assistance would be appreciated.  No internet issues.  Nothing seen from Windows firewall about application blocked.

17
FH2 Help / Support / Windows 10
« on: 02-06-2015, 00:06:52 »
I'm guessing that most folks who are running Windows 7 have noticed an icon on the start bar for the free Windows 10 upgrade.  Has anyone upgraded yet, and if so are they able to run FH2?

Thanks.

18
Last night I ran a virus scan on my machine using McAfee, and it flagged FH2_Toolbox.exe and the 2nd part of the downloaded install executable that was part of the Forgotten_Hope2_v2.2.zip file as containing Trojan Generic!Artemis.

McAfee also removed a registry entry for FH2.

I downloaded the 2.2 update using mu Torrent shortly after it's release. 

Questions:

(1)  Has anyone else seen this with McAfee or some other virus protection like Avast or Trend?

(2)  Is this an erroneous recognition on the part of McAfee, much like one that would previously occur with an older version of AVG where it would quarantine - I think it was the game spy browser portion - of the original BF1942 and make it unplayable.

(3)  Is this an actual Trojan infection that has been noted by others here, and if so, where can I find a clean copy of the FH2.2 client?  My gut feeling after having researched Generic!Artemis is that it's a browser hijacker and I've experienced none of this.  That said, it's possible that it was deployed in such a way as part of it's payload may not have installed and worked as it should've.

Thanks guys.  I really appreciate the assistance. 

Pages: 1 [2]