I have windows 7 64 bit home edition. I have noticed lately that a program fog.exe *32 runs in the background and eats half my cpu! If I kill it, it takes two clicks to start fog. Once will start the fog.exe *32 and the other will launch fog itself. When I exit fog, it leaves open this fog.exe *32.
Could you please give me a reason why this occurs, a fix, something as I shouldn't have to open taskmanager to kill a rogue program.
Thanks
FOG.EXE *32
Moderators: Slitherine Core, FoG PC Moderator, NewRoSoft
-
keithmartinsmith
- Field of Glory Moderator
- Posts: 1557
- Joined: Mon Mar 30, 2009 1:26 pm
I have windows 7 64 bit home edition. I have noticed lately that a program fog.exe *32 runs in the background and eats half my cpu! If I kill it, it takes two clicks to start fog. Once will start the fog.exe *32 and the other will launch fog itself. When I exit fog, it leaves open this fog.exe *32.
Could you please give me a reason why this occurs, a fix, something as I shouldn't have to open taskmanager to kill a rogue program.
>>>
Confused. Is this before or after you play FOG? I think you are saying that after playing FOG an instance of FOG exe remains loaded to RAM. Clicking the FOG icon twice will load FOG twice, like almost any other program. On CPU usuage FOG will only take up any if you are doing something in FOG, such as moving a unit. Otherwise it will use RAM but will not use any CPU. So I have FOG in the background having loaded the largest scenario supplied with the game and FieldofGlory.exe *32 is only loaded once and CPU usage by it is 0%.
I would suggest that you run windows update and make sure your anti-virus program us up to date and then run a full system virus scan. A windows issue could be causing the double load. There is no need for FOG to load twice or to stay in the background after exiting. It could also be you have a virus that attaches itself to large applications such as FOG and that could explain the CPU usage while not actually playing.
Keith
Could you please give me a reason why this occurs, a fix, something as I shouldn't have to open taskmanager to kill a rogue program.
>>>
Confused. Is this before or after you play FOG? I think you are saying that after playing FOG an instance of FOG exe remains loaded to RAM. Clicking the FOG icon twice will load FOG twice, like almost any other program. On CPU usuage FOG will only take up any if you are doing something in FOG, such as moving a unit. Otherwise it will use RAM but will not use any CPU. So I have FOG in the background having loaded the largest scenario supplied with the game and FieldofGlory.exe *32 is only loaded once and CPU usage by it is 0%.
I would suggest that you run windows update and make sure your anti-virus program us up to date and then run a full system virus scan. A windows issue could be causing the double load. There is no need for FOG to load twice or to stay in the background after exiting. It could also be you have a virus that attaches itself to large applications such as FOG and that could explain the CPU usage while not actually playing.
Keith
Ok, I did windows update, nothing but live essentials, which I refuse to download as in optional anyway
spybot, nothing
virus scan, clean
I start FOG, it takes two clicks
First click loads fog.exe *32
second loads fog.exe
close fog and fox.exe is gone, fog.exe*32 remains and eats half my cpu.
Any other suggestions?
PS. I did quick reply 2x and nothing happened, so perhaps you might have a forum bug as well.
spybot, nothing
virus scan, clean
I start FOG, it takes two clicks
First click loads fog.exe *32
second loads fog.exe
close fog and fox.exe is gone, fog.exe*32 remains and eats half my cpu.
Any other suggestions?
PS. I did quick reply 2x and nothing happened, so perhaps you might have a forum bug as well.
Again, I didn't have this problem before with my home 64 bit edition. I don't have it with my 32 bit professional. I am not saying it is a 64 bit issue, I am just trying to lay data out there as I would like this fixed. If someone says scandisk and defrag, I may have to convert myself to binary, travel through the ethernet and strangle them. 
Alternatively, I guess I could just get a voodoo doll. Much cheaper and as likely to work.
Alternatively, I guess I could just get a voodoo doll. Much cheaper and as likely to work.
