Source code of Windows XP (NT5)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

25 lines
2.2 KiB

  1. {\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}
  2. {\colortbl ;\red0\green0\blue0;}
  3. \viewkind4\uc1\pard\fi-1800\li1800\tx1800\cf1\b\f0\fs20 From:\b0\tab John Delo (Exchange)\par
  4. \b Sent:\b0\tab Tuesday, November 16, 1999 8:30 PM\par
  5. \b To:\b0\tab Alex Armanasu (Exchange)\par
  6. \b Cc:\b0\tab NTW Migration Services Team; Chris Steck (Exchange); Michele Freed (Exchange); Murthy Srinivas (Exchange)\par
  7. \b Subject:\b0\tab RE: Odyssey DSM Next Steps Mtg Mins.\par
  8. \pard\cf0 I put updated tools and setmgr.msi on \\\\jdelo3\\public\\state, fixing minor bugs, incorrect schema file reference (should be SmSchema.xml), INI file handling, and a decompiler that regenerates the XML manifest (useful after merging multiple XML pieces).\par
  9. \par
  10. What isn't obvious is that you don't need to register the compiled manifest - just specify it's name on the command line of settings.vbs (the default extension is .wsc). Registration isn't supported in settings.vbs anyway, and this special provision will likely become permanent - I will make that clearer in the command-line help.\par
  11. \par
  12. So the procedure would be, given your manifest named foo:\par
  13. 1. Generate and refine the manifest foo.wsm\par
  14. 2. Compile using \b WsmComp foo \b0 (same as WsmComp foo.wsm foo.wsc), fixing any errors\par
  15. 3. Check the settings by using \b Settings foo\b0 or you may also specify individual settings as the 2nd arg, and updated values as the 3rd arg\par
  16. 4. Backup the settings using \b Settings foo /a foo.wsb \b0 (default extension for the archive file will be fixed in a future release)\par
  17. 5. Transfer the archive file and either the original or compiled manifest to another machine\par
  18. 6. Compile the manifest if necessary, and restore using \b Settings foo /a /r foo.wsb\b0\par
  19. 7. Check the settings using the tool or peeking the registry.\par
  20. \par
  21. Currently the state store is also XML, but with a different schema, not terribly efficient, but very useful during development and testing. SInce the archive file is generated using MSXML.DLL, it comes out as a single line. You can view it formatted nicely using the tool \b ShowXml.vbs\par
  22. \par
  23. \par
  24. \pard\fi-1800\li1800\tx1800\cf1\b0\par
  25. }