> I'd rather suggest storing these values in shell32 resources and have > shell32 create the keys itself; we don't want to have these values > stored in two different places. Then the install program could load > shell32 and ask it to create the keys (maybe we can use DllInstall for > this?). Of course this means we can no longer use a simple shell > script... Yes, this works. It would just have to call SHGetSpecialFolderPath with nFolder = 0 ... nn and the create flag TRUE. DllInstall is not exported from native shell32 but we could use it of course. Some CLSID's and ProgID's in HCR could also created this way. Bye Juergen juergen
- Re: wine configuration issues (long) Martin Pilka
- Re: wine configuration issues (long) Alexandre Julliard
- Re: wine configuration issues (long) Francois Gouget
- Re: wine configuration issues (long) Alexandre Julliard
- Re: wine configuration issues (long) Martin Pilka
- Re: wine configuration issues (long) David Elliott
- Re: wine configuration issues (long) Juergen Schmied
- Re: wine configuration issues (long) Martin Pilka
- Re: wine configuration issues (long) Juergen Schmied
- Re: wine configuration issues (long) Alexandre Julliard
- Re: wine configuration issues (long) Juergen Schmied
- Re: wine configuration issues (long) Ove Kaaven
- Re: wine configuration issues (long) Juergen Schmied
- Re: wine configuration issues (long) David Elliott
- Re: wine configuration issues (long) Francois Gouget