I've heard that most networked systems are setup to have local
registrys on local machines or terminals. However, suppose that the network was set up so that the individual computers on the network did not have a local registry. In this case, would the Windows API still be able to access the common registry?
I need to know something as soon as possible please!
When the registry is stored on disk its mostly stored in 2 files - User.Dat and System.Dat.......the former holds info related to the logged on User (HKCU) and the latter holds more "machine related" info (HKLM).
One way that I know of Networks holding remote registry data is for the User.Dat to be held on the server and then it is copied to the local machine at logon, and then loaded into memory with the machine's Sytem.Dat........On logoff....the User.Dat is copied back
As the registry is still maintained locally, the API functions still work AOK.....There may be a remote registry method (I dont know).....but I doubt you would have any APIs that wouldnt work..
Thanks Rob!
Yes, I know the Windows API is functioning, but would there be
anything that would prevent the API from reading and writing to the registry? I know my read and write to the registry functions
are working on my machine, however, I have windows 98 and I'm not networked. I guess I could get 2000 or XP and test with that, and maybe I could go through the trouble of networking to
test as well, but I sure hope I can avoid all that expense and trouble. OK, if the windows API read and write functions are working on my machine (windows98), is there anything on a networked windows 2000 machine that would prevent the API from reading and writing to the registry? Would 2000 have a problem finding the registy (doesn't seem likely)?
I have Win2k and the API functions are fine on that as they were when I had Win98....in fact the only real difference between the APIs is that you have more functions on Win2k that arent implemented in Win98....
