Monday, November 16, 2015

Few important Windows Resource Kit tools


Following are some tools from the Windows Resource Kit, which I think are very important.

You can download the Windows Resource Kit from here.

These will work at any location of the command prompt when copied to "c:\windows\system32"
  • consume
          From this you can run a simple stress test on your PC's memory, CPU and disks.

          This is similar to the Linux "stress" command.

          CAUTION !!! use with care if you are going run this in a production server.

          C:\Users\lahiru>consume /?
          Universal Resource Consumer - Just an innocent stress program, v 0.1.0
          Copyright (c) 1998, 1999, Microsoft Corporation

          consume RESOURCE [-time SECONDS]

          RESOURCE can be one of the following:

          -physical-memory
          -page-file
          -disk-space
          -cpu-time
          -kernel-pool


  • createfil
          Use this command if you need to create a big dummy file, which is equal to Linux "dd" command.

          C:\Users\lahiru>creatfil /?
 

          Usage: creatfil FileName [FileSize]
       

          -? :  This message
          -FileName -- name of the new file
          -FileSize -- size of file in KBytes, default is 1024 KBytes


  • tail
        Simple tail command which is similar to Linux "tail" command.

          C:\Users\lahiru>tail /?

          usage: TAIL [switches] [filename]*
          switches: [-?] display this message
          [-n] display last n lines of each file (default 10)
          [-f filename] keep checking filename for new lines 

        
  • robocopy
        This is more like Linux "rsync'.

          Refer "robocopy /?" or "robocopy.doc" for command usage/parameters.

  • qgrep
          This command is useful if you need to find a string from set of files.

  • PortQry 
        portqry.exe does not come in resource kit. You can download it from here.
        
        portqry is useful if you want to test a port status and use it in a batch file. Because telnet can't be used to get port status to a script.

           

No comments:

Post a Comment