Group items tagged

PowerShell Integrated Scripting Environment PowerShell scripts are standard text files. With Windows Vista and earlier versions of Windows, the built-in editor was Notepad. While Notepad is perfect for quickly editing text files, and it is sufficient for writing scripts, a more robust editor would enable IT professionals to learn, create, and debug scripts more efficiently. Windows 7 includes the PowerShell Integrated Scripting Environment (ISE), a graphical PowerShell development environment with debugging capabilities and an interactive console, as shown in Figure 1.

PowerShell Cmdlets Cmdlets (pronounced command-lets) are one of the most powerful features of PowerShell. A cmdlet is a task-oriented command that is used in the Windows PowerShell environment. For example, PowerShell includes cmdlets that: Append text to a file Read and write XML files Manage services Manage files and folders PowerShell 2.0 supports over 500 new cmdlets to manage client computers and servers, edit the registry and file system, perform WMI calls, and connect the powerful .NET Framework development environment. You can also extend PowerShell by creating custom cmdlets or use community-developed extensions.

Let me fix it myselfIf you want to test memory on the Windows Server-based computer, you can change the registry to enable Memory Diagnostic. To do this, follow these steps.Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.Log on to the Windows Server-based computer by using administrator credentials.Click Start, click Run, type regedit in the Open box, and then click OK.Expand the following subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Office\Common\OffDiagClick OffDiag, and then locate the DoNotTestMemory entry in the right pane.Right-click DoNotTestMemory, and then click Modify.In the Value data box, delete 1, type 0 (zero), and then click OK.Exit Registry Editor. Note When Memory Diagnostic is enabled, any user on the server can test memory. Did this fix the problem?Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support (http://support.microsoft.com/contactus) .We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me (http://blogs.technet.com/fixit4me/) " blog or send us an email (mailto:fixit4me@microsoft.com?Subject=KB) message.

n general, you'll want to find your copy of Normal.dot (or Normal.dotm) and make sure that it is only you that can make changes to it. Load the file directly in Word, and then make your configuration changes. Save the file again and then—for added protection—get out of Word and make the file read-only.

Of course, the problem may not be in your Normal.dot file at all. It could be that somehow the Registry key used for some of your Word settings has become corrupted. The only solution to this problem is to delete the key, restart Word, and then make your settings again. Follow these steps: Exit Word. Start your favorite Registry editor. Locate the following data key. (This data key, as shown below, is for Word 2003. If you are using Word 97, replace 11.0 with 8.0; for Word 2000 replace it with 9.0; for Word 2002 replace it with 10.0; and for Word 2007 replace it with 12.0.) HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Data Rename the entire key to something else, or simply delete it. Close the Registry editor. Restart Word.

Options

I recommend that if you want this added to Default Programs Editor, you should suggest and upvote it on that application's UserVoice Feedback page. I have it on good authority that the application author pays attention to that feedback when deciding how to spend his development time!