E
Emily
I have created an image that includes most of the XP components and has the
normal start menu, desktop, etc. (Using explorer shell and standard logon)
After the FBA has run I install a custom VB app (which sets up configuration
information in the registry). I have noticed that with certain images it
does work, and on others it doesn't. On a standard Win2k or XP Pro machine
it always works.
I have included all of the components that appear to deal with the
registry - is there some other setting or component that would potentially
enable/disable external apps writing to the registry? When the app installer
runs, no errors are reported - the entries simply aren't added to the
registry - I can manually enter in the entries just fine, however.
normal start menu, desktop, etc. (Using explorer shell and standard logon)
After the FBA has run I install a custom VB app (which sets up configuration
information in the registry). I have noticed that with certain images it
does work, and on others it doesn't. On a standard Win2k or XP Pro machine
it always works.
I have included all of the components that appear to deal with the
registry - is there some other setting or component that would potentially
enable/disable external apps writing to the registry? When the app installer
runs, no errors are reported - the entries simply aren't added to the
registry - I can manually enter in the entries just fine, however.