Prev: U++ 2467 released
Next: temporaily set background to colour like RDP
From: Jackie on 10 Jun 2010 09:33
Aah. I understand perfectly now. Thank you.
I like the game a lot.. At least when you don't find 4 snipers on a
rooftop. And maybe a few more hiding somewhere in the bushes.

I saw 4 of them on the same roof maybe in my last game.

Then maybe I can recommend running the game from the limited account,
but running it _as your other account_. Know what I mean?

You have some sort of "Run as user" option in Windows XP but I need to
look for it if you have Windows Vista or 7. I know you can do it with
the task scheduler though in Vista/7.

--
Regards,
Jackie
From: Jackie on 10 Jun 2010 09:36
Well, that doesn't fix the problem you have now though. :(

--
Regards,
Jackie
From: Jackie on 10 Jun 2010 09:44
The same thing is also in Windows 7 at least. Right-click on the
executable while holding down the shift-key. You should have "Run as
different user" there. You'll need to do this every time though and type
in the password as well.. But you can do it in different ways to make it
easier. Maybe via the task scheduler or a command line application.

--
Regards,
Jackie
From: Heck on 10 Jun 2010 11:17
On Thu, 10 Jun 2010 15:44:53 +0200, Jackie <Jackie(a)an.on> wrote:

>The same thing is also in Windows 7 at least. Right-click on the
>executable while holding down the shift-key. You should have "Run as
>different user" there. You'll need to do this every time though and type
>in the password as well.. But you can do it in different ways to make it
>easier. Maybe via the task scheduler or a command line application.

I tried that, too, both on my first installation on XP and on Windows
7. SecuRom was complaining under both OSs it couldn't write to my
users directory tree. So I gave permissions to Everyone for full
control in my user directories, but to no avail. It simply would not
work from my son's account, no matter what I did. That is, no matter
what I could think of, perhaps someone else could have tricked or
fixed it properly. A developer, for sure. Neither EA nor SecuRom
support had a clue how to fix it. After initial conversations, they
had exhausted their scripted help.

Once, I saw my son also had a problem with a persistent sniper. Some
guy was hanging out on the mountainside above (I think) the area he
had to protect. Every time my son spawned, the guy plugged him. I
suggested he run the other way and work his way up onto the
mountainside, above the sniper. He did and surprised him there.
Killed the guy a few times. It was lots of fun. Gratifying. Sticking
up for family, family values, it was wholesome.

My son's almost 14. On this score, I'm not sorry he's been forced to
take a break from the game. Again, I was writing facetiously. It's
not what we'd reasonably call wholesome, BBC2.

I won't allow him to buy Grand Theft Auto. I tell him I don't approve
of it nor of him involving himself with it because it aggrandizes
criminal and destructive behavior and promotes disregard for life and
law. He accepts that, but I feel I can't push this sort of conscience
too far with a kid who just likes to blow things up, so, without much
objection, I allow the war game, which is slightly more idealized.

To be fair, he likes the strategy, too. And, he's good at it. Good
grief, I remember the things I did and was into when I was young. I
try to guide him and support and encourage him, help him develop a
conscience and wholesome responsibility, but not stifle him.
From: Jackie on 10 Jun 2010 11:23
I experimented with using the task scheduler and event logs... Turns out
it works but...

Properties for the task:
-----
When running this task, use the following user account: [ main account ]
[*] Run only when user is logged on
[ ] Run whether user is logged on or not

[ ] Hidden
-----

This works fine. The application launches and is visible to the user..
That's nice but probably not what you want though. You want to launch it
from a different user account, and I think without having to log on your
main account first. Now here's the problem...
-----
When running this task, use the following user account: [ main account ]
[ ] Run only when user is logged on
[*] Run whether user is logged on or not

[ ] Hidden
-----

The application launches but it is invisible! Task manager shows that
the application is indeed running under the specified user. Can you
understand that? I can't.

--
Regards,
Jackie
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: U++ 2467 released
Next: temporaily set background to colour like RDP