FiveTech Software tech support forums

Under Windows XP I stored values ( server path, etc ) in the registry using the following:

To read the value:

oReg := TReg32():Create( HKEY_LOCAL_MACHINE, "SOFTWARE\Masterlink\Setup" )
cPath := oReg:Get( "Path", cPath )

Or to set the value if none was found:

oReg:Set( "Path", cPath )

Trying to run the program in Vista, if it is not found, the call is to cGetDir32( ) to display the directory and select the path.

On my first try, 1) the path was not in the registry so it wasn't found, 2) there was no popup for cGetDir32( ), and no value was written to the registry.

Whats different in Vista ?

Thanks.

Tim,

Have you tried it logged in as administrator ? First you have to activate the administrator account

Hello!

Whats different in Vista ?

File and Registry Virtualization – the good, the bad, and the ugly
http://windowsconnected.com/blogs/jerry ... 19/86.aspx

The same type of magic is used with certain parts of the registry. For example, if an application writes to “HKLM\Software\PoorlyBehavedApp\2.0\Settings”, windows will send that write operation to “HKCR\VirtualStore\Machine\Software\PoorlyBehavedApp\2.0\Settings”.

To help combat this, Microsoft has built some API’s that will allow developers to specify certain folders and registry keys to never virtualize.

Regards, Roman

I guess we will get used to it.

First, I was logged in as administrator. Essentially the whole system began to degrade so I went back to ground zero. Instead of an update, I told it to give me a clean install ... which was supposed to erase all the files. Well, some of the files were erased, and some folders remained ... very strange ... so I'm not sure what is "good, bad, and ugly" but I find that some software works, other software packages dont .... but when I did a brand new install of my package it seemed to go ok and initially it works .... but for how long I don't know.

I think Vista will be a topic for much discussion as we see our clients buy new computers with this OS.