for Storage. Executing user applications directly from ROM. Support for the exFAT file system can be added by installing KB955704. Supports VESA display if vendor-specific video driver not installed, or in the safe mode. System administration Windows Script Host 5.6 Windows XP includes Windows Script Host 5.6, a major update to the WSH environment, which includes an improved object model to reduce boilerplate code, stronger security and several other improvements. A new XML-based file format, the Windows Script File format (.WSF) has been introduced besides .VBS and .JS which can store in an XML node in the same file, extra information besides script code, such as digital signature blocks, runtime directives or instructions to import external code. The WSF schema can include jobs wrapped each by a unique <job> tag and an outer <package> tag. Tags in a WSF file allow including external files, importing constants from a TLB, or storing the usage syntax in the <Runtime> element and displaying it using the new ShowUsage method, or when invoked by the /? switch. The WSF format also supports hosting multiple WSH scripting languages, including cross function-calls. The WshShell object now supports a 'CurrentDirectory' read-write method. Scripts can now be digitally signed as well as verified programmatically using the Scripting.Signer object in a script itself, provided a valid certificate is present on the system. Alternatively, the signcode tool from the Platform SDK, which has been extended to support WSH filetypes, may be used at the command line. The VerifyFile method can be used to authenticate the embedded signature's validity and check the script for modifications after signing. WSH can thus decide whether or not to execute the script after verification. Code stored in an in-memory string can also be signed by using the Sign method. The signature block is stored in a commented section in the script file for backward compatibility with older WSH versions. By using Software Restriction Policies supported in Windows XP and later, a system may also be configured to execute only those scripts which have been digitally signed, thus preventing the execution of untrusted scripts. Local scripts can also run on a remote machine with the new WScript.WshController object, which is powered by DCOM. Remote WSH can be enabled through a Group Policy Administrative Template or registry. Remote scripts always run through wscript and are loaded into the remote machine's Server process so they run non-interactively by