<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Windows :: Tag :: JP&#39;s Domain</title>
    <link>https://www.jpsdomain.org/tags/windows/index.html</link>
    <description></description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://www.jpsdomain.org/tags/windows/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>POSIX Redirection</title>
      <link>https://www.jpsdomain.org/windows/redirection/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.jpsdomain.org/windows/redirection/index.html</guid>
      <description>Originally written for and copyright by Information Security Magazine, February 2002 &#34; Windows Security Scripting.&#34;&#xA;Note: Under DOS &amp; Win9x/ME some of the simple STDOUT redirection and pipes work, but none of the advanced STDERR or multiple command methods are supported.&#xA;IO Redirection in Windows NT, 2000, XP, UNIX (sh, bash and variants) File Descriptors FD Description 1 STDOUT 2 STDERR 3+ Additional files as opened by the process Redirection Command Description cmd1 | cmd1 Pipe STDOUT of cmd1 into STDIN of cmd2 \&gt; file Direct STDOUT to file, overwriting existing contents \&gt;\&gt; file Direct STDOUT to file, appending to existing contents `&gt; file` 2\&gt; file Direct STDERR to file, overwriting existing contents 2\&gt;\&gt; file Direct STDERR to file, appending to existing contents \&lt; file Get STDIN from file 2\&gt;&amp;1 Direct STDERR to the same place as STDOUT \&gt;&amp; file Direct both STDOUT and STDERR to file 2\&gt;&amp; Duplicate STDOUT to STDERR echo &#39;foo&#39; \&gt;&amp;2 Send output to STDERR instead of STDOUT Notes: Numbered file descriptions above may be used arbitrarily. noclobber is a UNIX setting that prevents overwriting (clobbering) existing files by redirection. UNIX /dev/null is equivalent to Windows NUL. Windows NUL is not case sensitive. ^ is the meta-character escape in DOS/Windows, so it may sometimes be necessary to use ^| (e.g. when using egrep in a batch file). You may use ^^ for a literal ^. Examples: Command Description dir c:\*.* &gt; myls.txt Redirect output of ls into myls.txt, overwriting or creating myls.txt if necessary dir c:\winnt\*.* &gt;&gt; myls.txt Append more output of ls into myls.txt noisy_cmd &gt; NUL Make STDOUT output from noisy_cmd go away noisy_cmd 2&gt; NUL Make STDERR output from noisy_cmd go away noisy_cmd &gt; NUL 2&gt;&amp;1 Make ALL output from noisy_cmd go away noisy_cmd 2&gt; NUL 1&gt;&amp;2 Make ALL output from noisy_cmd go away noisy_cmd | more Pipe noisy_cmd STDOUT into more (or less or whatever) noisy_cmd 2&gt;&amp;1 | more Pipe noisy_cmd STDOUT and STDERR into more (this is great for those “net” commands that scroll off the screen when you try to get help) echo some message 1&gt;&amp;2 Use the echo command to send output to STDERR (it usually goes to STDOUT). Running Multiple Commands in Windows NT, 2000, UNIX (sh, bash and variants) Use parentheses to nest as needed.</description>
    </item>
    <item>
      <title>Windows Voodoo</title>
      <link>https://www.jpsdomain.org/windows/winvoodoo/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.jpsdomain.org/windows/winvoodoo/index.html</guid>
      <description>Obsolete Content This content is obsolete, but I am leaving it here as a historical reference.&#xA;Introduction Does your computer ever do any of the following, “just for the heck of it,” with no rhyme or reason? Does it do it a lot? More than once or twice a day?</description>
    </item>
    <item>
      <title>Favorite Utilities, Tools, Software for Windows</title>
      <link>https://www.jpsdomain.org/windows/win-tools/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.jpsdomain.org/windows/win-tools/index.html</guid>
      <description>Obsolete Content This content is obsolete, but I am leaving it here as a historical reference.&#xA;As far as I know, all of these tools are free unless otherwise noted.&#xA;Use any ZIP program, such as WinZip or InfoZip’s FREE Unzip to extract the ZIP files.&#xA;(Old) Disk &amp; File Utilities BootPart Lets you create DOS and Win95 boot sectors for the NT Loader (NTLdr.exe). IT also lets you fix broken NT boot sectors. Very nice little freeware tool. For more information about NT Boot Sectors, you can check this direct boot page. delpart.exe Old Microsoft utility to delete partitions – ANY partitions. Great for removing NTFS partitions from a bootable DOS floppy, or for those times when FDisk confuses itself and will not let you remove an extended partition because it says there are logical drives, but when you try to delete the logical drives it says there aren’t any… dirmatch.com From PC Magazine, allows you to compare two different directories (see FreeCommander, below). Since this is so old (DIRMATCH 3.1 (c) 1989 Ziff Communications Co.) it doesn’t really work with long filenames. (If you have problems downloading try dirmatch.com.txt and rename it to remove the trailing .txt.) freeCommander A dual-pane file manager for all 32-bit windows platforms (i.e. 95/98/NT/2000). It is a free program, similar to an updated Norton Commander. Nicer and more current than 2xExplorer. 2xExplorer An obsolete dual-pane file manager for all 32-bit windows platforms (i.e. 95/98/NT/2000). It is a free program, similar to an updated Norton Commander. Use the previous one instead. mcopy.exe Copies only newer files. obslt10.zip Deletes files older than the date/time specified. Excellent for purging log and temp files, etc. UNIX Utilities for Windows FREE tools from 3Com Including 3CDaemon an Integrated TFTP/FTP/Syslog Daemon for Windows 95/98/NT. Win32-ports of tools with a GNU or similar open source license These are the “official” GNU Win32 ports. GNU utilities for Win32 Really awesome “native” Win32 ports of some UNIX tools. Native in this context means that no emulation layer (e.g. CygWin) is needed. This avoids a lot a installation complexity. With these native tools, you unzip ’em and run ’em! bc-1.05, bison-1.28, bzip2-1.0.2, diffutils-2.7, fileutils-3.16, findutils-4.1, flex-2.5.4, gawk-3.1.0, grep-2.4.2, gsar110, gzip-1.2.4, indent-2.2.9, jwhois-2.4.1, less-340, m4-1.4, make-3.78.1, patch-2.5, recode-3.6, rman-3.0.7, sed-3.02, shellutils-1.9.4, tar-1.12, textutils-2.1, unrar-3.00, wget-1.8.2, which-2.4. David’s Programs and Source Code UNIX or UNIX-like tools, including cat.exe, bin2bmp.exe, bmpdump.exe, detab.exe, diskuse.exe, ebcdic.exe, entab.exe, fsplit.exe, fstat.exe, gifdump.exe, hdump.exe, head.exe, reboot.com, scram.exe, scram.doc, snow.exe, tcopy.exe, tee.exe, tod.com, unicode.exe, uniq.exe, vdate.exe, vecho.com, vfind.exe, whence.exe, wordc.exe Mountain Math Software’s port of GNU Bash to Windows NT. It it listed as a beta, and for Windows 3.51, but it runs under NT 4. I have not tested it much though. See the Readme.txt or download the archive (~ 1.7 meg). Licensed under GNU (free), and stand alone (i.e. does not need DJGPP or CygWin). tcsh Free GNU, stand alone (i.e. does not need DJGPP or CygWin). Read the Readme.NT. pgrep.com DOS port of a version of the grep command. Can handle “|” under DOS/Windows. DOS2UNIX.COM &amp; UNIX2DOS.COM (from The free Win32 software page at BASTET.COM) Convert CRLF to LF and LF to CRLF respectively. While the programs above are ports of various UNIX tools, the next four items are complete UNIX environments for the PC. DJGPP is older, and has not been updated too much (not that it needs it). DJ Delorie went to work on the Cygwin project after he wrote DJGPP. Both environments are very cool! I don’t know too much about the other two, and have never used them.</description>
    </item>
    <item>
      <title>Windows Shell Scripting</title>
      <link>https://www.jpsdomain.org/windows/winshell/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.jpsdomain.org/windows/winshell/index.html</guid>
      <description>Old Content This content is old! It’s still useful, but it’s old, and there may be bit rot, newer/better tools or ways to do things. Sanity check and do your research.&#xA;This article is translated to Serbo-Croatian by WHGeeks. Thanks!&#xA;I plan to move much of this to https://github.com/vossenjp/ at some point…&#xA;Introduction The term “shell script” comes from UNIX, the DOS term is “batch files.” UNIX shell scripts are very powerful and flexible, they are essentially programming languages unto themselves. Windows or more rightfully DOS batch files are a pale imitation. However, sometimes you need to write something that will just work on any plain old out-of-the-box Windows install someone has–without adding all kinds of other tools.</description>
    </item>
    <item>
      <title>Windows port of Logcheck</title>
      <link>https://www.jpsdomain.org/windows/winlogcheck/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.jpsdomain.org/windows/winlogcheck/index.html</guid>
      <description>Obsolete Content This content is obsolete, but I am leaving it here as a historical reference.&#xA;Introduction Welcome to the Windows port of Logcheck (now called LogSentry), the famous UNIX log processing tool. Psionic was bought by Cisco who has moved the cool Abacus tools, including LogSentry, to http://sourceforge.net/projects/sentrytools/&#xA;As you probably know if you are bothering to read this, LogSentry helps spot problems and security violations in your logfiles automatically and will send the results to you in e-mail. However, it can only work with what it’s given. I personally find the Windows Event Logs to be verbose, yet un-informative. So when you get e-mailed messages with three or 4 lines on arcane gibberish, remember that it’s the same information as you would see in the Event Log, except it’s in a slightly different format, and you are actually SEEING it! (Of course, you would have reviewed the Event Logs anyway, right?) :-)</description>
    </item>
  </channel>
</rss>