![]() In the Name field, enter the name that you will call this application in AlwaysUp. In the Arguments field, enter the command line parameters you will use to launch DebugView (see step 2). We have used C:\Apps\DebugView\Dbgview.exe (since we expanded the zip file to C:\Apps\DebugView\ on our Windows Server 2016 system). Look for it where you expanded the zip file you downloaded from Microsoft. In the Application field, enter the full path to the DebugView executable, Dbgview.exe. Select Application > Add to open the Add Application window: v /l C:\DebugViewLogs\debugview-log.txt /g /nĪnd before moving on, make sure that your DebugView command line runs as expected! If it doesn't work now, it won't work under AlwaysUp.ĭownload and install AlwaysUp, if necessary. Since we want to capture global Win32 and kernel output to a new log file every day, we have chosen these options: Next, compose the command line that you will use to run DebugView.įor your reference, the full set of command line options is revealed by running Dbgview.exe /?: We have placed our copy of DebugView in C:\Apps\DebugView so that directory will appear throughout this tutorial. If you don't have DebugView installed, grab the zip file from Sysinternals and extract its contents to a new folder. To run DebugView as a service with AlwaysUp: ![]() ![]() Is a free utility that captures diagnostic output from programs calling theĪlwaysUp will start DebugView whenever your PC reboots, making it possible for you to monitor Windows Services and other applications that are launched before you log in. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |