Different FireFly Registry Instruction behavour under VISTA

[gian young]

Hi,

I have been using the FireFly Set & Get RegistryString instructions successfully with my software utility for a long time. My utility program developed under Win XP SP 3 works reliably.

By example I use an instruction similar to the following.

FF_SetRegistryString(%HKEY_LOCAL_MACHINE, "SOFTWARE\XX\YY", "Inst1", "Value")

When I use RegEdit to examine the success of this instruction under Win XP I find the Keys XX\YY\Inst1 have been created correctly under %HKEY_LOCAL_MACHINE\SOFTWARE as expected and the value assigned to this key is also correct.

When I run the same unaltered program under VISTA and examine the results using RegEdit I find a completely different result.

I find that the registry string and keys have still been created under VISTA but to an entirely different area.

The same instruction as above:-

FF_SetRegistryString(%HKEY_LOCAL_MACHINE, "SOFTWARE\XX\YY", "Inst1", "Value")

Firstly creates a string under %HKEY_USERS and not %HKEY_LOCAL_MACHINE as instructed and then buries the rest under a flow of sub directories that bear little relationship to the values placed in the command.

Fortunately from my software's ability to function nothing has changed, in fact I was unaware inititially that this had occured when testing under VISTA because the Registry Set and Get instructions were still working Ok.

I don't understand why this behavour happens under VISTA and if anyone can shed some light on the subject it would be appreciated.

Regards

Gian Young Australia

[TechSupport]

Hi Gian,

This link seems to address the problem you are seeing: http://www.vistax64.com/vista-security/49012-app-data-hkey_local_machine.html

[gian young]

Hi Paul,

Thank you for responding to this and the information link provided. I will follow through on this and see if this will fix my problem though I know of no reason my Registry should be corrupt ?? 

I really am NOT a satisfied VISTA owner & user.

Regards

Gian

[David Kenny]

Gian,

The only thing in that link that suggests your registry is corrupt is the advertisements (to sell you something to fix a problem you don't have).  The situation the link is talking about is a little different than yours however.  I think this one is much closer, although there seems to be a difference in the actual registry path.  I think it might be done by Vista to make it transparent to your program.

http://msdn.microsoft.com/en-us/library/aa965884(VS.85).aspx

David

[gian young]

Hi David,

Thank you very much for responding and for this link. You are right on the money with this it is exactly what I am experiencing.

I hope this and the correct interpretation of the behaviour by yourself assists others it certainly has helped me.

Thanks again

Regards

Gian