1
Help / Re: Unable to register key
« on: April 12, 2007, 05:32:44 PM »
OK, I got it working, but it's a funny, and probably my fault. Let me explain, although it could take a while.
I set the system up with NTFS and non-admin accounts for the kids. I then have an admin account that does not appear on the XP login screen. I get the kids to install and run games using "Run As" on the RH button menu.
This offers a small amount of protection from things the kids run (mainly web and mail) as most of the time they are not running as admin (I'm sure that if they worked it out, they would realise that they can run *ANYTHING* as an admin account) but it stops in-advertent damage.
They installed blockland like this, and the demo worked fine.
However, when trying to register the authorization code when running like this, we get the error originally described. When I actually ran blockland from a logged in real admin account, it worked fine, and once registered, works from the "Run As" account.
I guess there must be something I do not understand about the way XP works. I'm sure that UNIX (my world) inheritance would allow sub-processes to inherit all credentials.
Sorry if I wasted peoples time. I don't know whether it is worth leaving this up, as I'm not sure whether it will be of any use to anyone else. What I wish is that Microsoft's security model worked well enough so that we did not have to run games from administration accounts, so we are not required to use such obscure methods to try to keep our systems safe.
Thank you for all of the advice, especially the personal response from Badspot. My kids are now happy.
I set the system up with NTFS and non-admin accounts for the kids. I then have an admin account that does not appear on the XP login screen. I get the kids to install and run games using "Run As" on the RH button menu.
This offers a small amount of protection from things the kids run (mainly web and mail) as most of the time they are not running as admin (I'm sure that if they worked it out, they would realise that they can run *ANYTHING* as an admin account) but it stops in-advertent damage.
They installed blockland like this, and the demo worked fine.
However, when trying to register the authorization code when running like this, we get the error originally described. When I actually ran blockland from a logged in real admin account, it worked fine, and once registered, works from the "Run As" account.
I guess there must be something I do not understand about the way XP works. I'm sure that UNIX (my world) inheritance would allow sub-processes to inherit all credentials.
Sorry if I wasted peoples time. I don't know whether it is worth leaving this up, as I'm not sure whether it will be of any use to anyone else. What I wish is that Microsoft's security model worked well enough so that we did not have to run games from administration accounts, so we are not required to use such obscure methods to try to keep our systems safe.
Thank you for all of the advice, especially the personal response from Badspot. My kids are now happy.