F.E.A.R. problem, I updated it, now it wont run

[trodas]

BTW, I found, that blocking these servers:

127.0.0.1 fear.available.gamespy.com
127.0.0.1 motd.gamespy.com

into your hosts file, make the Fear stop complaining that it want get updated to v1.2

[DABhand]

Errrr

127.0.0.1 is the local machine IP address

[TippeX]

i presume he meant editing the hosts.dat file and puting those entries in so they become 127.0.0.1 when resolved and thus cant connect

[trodas]

DABhand - sure And what is your point exactly? I do this, so the FEAR connecting to my machine, instead of the webserver it should connect to. And since no webserver and certainly not one, what offer update to FEAR run on my machine, it effectively kill the message.
That is my point

TippeX - exactly Same way I use for blocking adverts, spy-servers, unwqanted updates, checkc and unwanted traffic in general

[DABhand]

You didnt explain correctly that you put in the local address, so I asked.

[Muji-FightR]

I found this:

1. Create a user account without admin rights, e.g. FEAR
2. Create a PW for this user (important)
3. Block full access to these Registrykeys:
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SCSI\SCSI PORT2 (my DT4)
Do this for all Virtual drives e.g. SCSI PORT3 Alcohol drive
HKEY_LOCAL_MACHINE\SOFTWARE\D-TOOLS
HKEY_LOCAL_MACHINE\SYSTEM\MOUNTEDDEVICE and if available
HKEY_LOCAL_MACHINE\SYSTEM\MOUNTEDDEVICE1

4. Keep logged in as Administrator, mount the FEAR image, either the one from GCW or your own and rightclick on the FEAR shortcut and choose Open as (not sure, or execute as ?), often under open. Enter your PW for the FEAR-user. DADA !

Hope, this helps.