Closed GoogleCodeExporter closed 9 years ago
Basically the Agent cannot be responsible for this as the Agent does not read
or
write the Starcraft's memory at all.
You don't have to start Starcraft with the Agent. All you need to do is run the
Agent
while you play.
The Agent can be started (or closed) at any time. You can login to battle.net
and
start the Agent after that.
One thing I have in mind. Can you start the Agent as Administrator, and then
start
the Starcraft with it?
Original comment by icz...@gmail.com
on 8 Jan 2010 at 12:10
So did the run-as-administrator work for you?
Original comment by icz...@gmail.com
on 8 Jan 2010 at 3:36
If the problem still exists, simply start Starcraft with Starcraft.exe, or
start the
Agent after you logged on to battle.net.
Original comment by icz...@gmail.com
on 4 Mar 2010 at 5:53
Original issue reported on code.google.com by
Hxax...@gmail.com
on 7 Jan 2010 at 11:28