Entering a registry Value with php??

I need to be able to enter a registry value from a webform after a user
registers at my site and be able to read that value after the user logs in
or attempts to login. We are using php 4.3.4 on fedora core 1 linux server.
I do not want to have to write a windows application for the user to
download to enter these values as I know that php can interact with OTHER
languages and it can interact with a Windows COM object with some careful
programming. So if I can accomplish this with a combination of java script
or any other way, I am open to suggestions....

Help!!

Jim

In article <HeQcd.9773$JS4.717@twister.nyroc.rr.com>,
"Jim G." <jgrago@NO_SPAM-twcny.rr.com> wrote:

> I need to be able to enter a registry value from a webform after a user
> registers at my site and be able to read that value after the user logs in
> or attempts to login. We are using php 4.3.4 on fedora core 1 linux server
.
> I do not want to have to write a windows application for the user to
> download to enter these values as I know that php can interact with OTHER
> languages and it can interact with a Windows COM object with some careful
> programming. So if I can accomplish this with a combination of java script
> or any other way, I am open to suggestions....

I think you'll have to write something--Javascript, Java applet, or a
compiled program to do this on the Windows client.

php runs on your Linux server and not on the Windows client, I don't see
any other way of doing this from the server.

--
DeeDee, don't press that button!  DeeDee!  NO!  Dee...

"Jim G." <jgrago@NO_SPAM-twcny.rr.com> wrote in message
news:HeQcd.9773$JS4.717@twister.nyroc.rr.com...
> I need to be able to enter a registry value from a webform after a user
> registers at my site and be able to read that value after the user logs in
> or attempts to login. We are using php 4.3.4 on fedora core 1 linux
server.
> I do not want to have to write a windows application for the user to
> download to enter these values as I know that php can interact with OTHER
> languages and it can interact with a Windows COM object with some careful
> programming. So if I can accomplish this with a combination of java script
> or any other way, I am open to suggestions....

PHP... on the server. You can't access the client registry via PHP.

But *why* do you want to write a registry entry? Based upon your description
above, I have to wonder why a cookie won't solve your problem.

- Virgil

"Virgil Green" <vjg@DESPAMobsydian.com> wrote in message
news:fqedd.7585$Lk3.5898@newssvr12.news.prodigy.com...
> "Jim G." <jgrago@NO_SPAM-twcny.rr.com> wrote in message
> news:HeQcd.9773$JS4.717@twister.nyroc.rr.com... 
> server. 
>
> PHP... on the server. You can't access the client registry via PHP.
>
> But *why* do you want to write a registry entry? Based upon your
> description
> above, I have to wonder why a cookie won't solve your problem.
>
> - Virgil
>
Hi, We are already using session cookies, but we deal alot with financial
information, and when we find fraud we need a way to permanently "Ban" that
pc where it came from. The registry check is ideal, because you can bury the
key almost anywhere and disguise it so that prying eyes cant find it. If we
just suspend or close the account, they can come back and attempt to
register again if they have other stolen information to try to fraud us
with.

Thanks!

In article <ifOdd.14529$JS4.12180@twister.nyroc.rr.com>, Jim G.
<jgrago@NO_SPAM-twcny.rr.com> wrote:

> "Virgil Green" <vjg@DESPAMobsydian.com> wrote in message
> news:fqedd.7585$Lk3.5898@newssvr12.news.prodigy.com... 
> Hi, We are already using session cookies, but we deal alot with financial
> information, and when we find fraud we need a way to permanently "Ban" tha
t
> pc where it came from. The registry check is ideal, because you can bury t
he
> key almost anywhere and disguise it so that prying eyes cant find it. If w
e
> just suspend or close the account, they can come back and attempt to
> register again if they have other stolen information to try to fraud us
> with.
>
> Thanks!
>
>

But not everyone uses Windoze y'know. Whatever Windoze only methods you
implement to prevent that situation aren't gonna work on Mac or Linux
systems.