<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Batch scripting - zaur.it</title>
	<atom:link href="https://zaur.it/tag/batch-scripting/feed/" rel="self" type="application/rss+xml" />
	<link>https://zaur.it</link>
	<description>Practical tools and guides for system administrators</description>
	<lastBuildDate>Sat, 03 Oct 2026 09:45:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://zaur.it/wp-content/uploads/2025/04/cropped-LogoZaurIt-e1745511455393-1-32x32.png</url>
	<title>Batch scripting - zaur.it</title>
	<link>https://zaur.it</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>where and Get-Command in Windows: find which binary actually runs</title>
		<link>https://zaur.it/where-get-command-windows/</link>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Fri, 18 Sep 2026 11:36:18 +0000</pubDate>
				<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[Batch scripting]]></category>
		<category><![CDATA[Guide]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=2826</guid>

					<description><![CDATA[where answers one question: when I type this command, which file on disk actually runs? On a machine that has been in service for a while that is rarely obvious. A tool can sit in System32, again under a vendor's install directory, and a third time as a store alias in WindowsApps, and the copy [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>findstr and find in Windows: the regex dialect, the traps and which one to use</title>
		<link>https://zaur.it/findstr-find-windows/</link>
					<comments>https://zaur.it/findstr-find-windows/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Fri, 11 Sep 2026 10:53:35 +0000</pubDate>
				<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[Batch scripting]]></category>
		<category><![CDATA[Guide]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=2665</guid>

					<description><![CDATA[Every CMD one-liner that filters output ends in one of two commands. find looks for a literal string. findstr looks for a pattern. They are not the same tool with different names, they do not take the same switches, and choosing the wrong one is how a filter that looks right returns the wrong lines. [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/findstr-find-windows/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Windows Command Aliases: DOSKEY Macros in CMD and Aliases in PowerShell</title>
		<link>https://zaur.it/windows-command-aliases-doskey-powershell/</link>
					<comments>https://zaur.it/windows-command-aliases-doskey-powershell/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Mon, 11 May 2026 06:54:00 +0000</pubDate>
				<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[Batch scripting]]></category>
		<category><![CDATA[Guide]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=2155</guid>

					<description><![CDATA[If you come from Linux, you expect aliases to just work - type alias ll='ls -la', press Enter, done. Windows has the same concept, but it lives in two separate places depending on which shell you are in: CMD has DOSKEY macros, PowerShell has its own alias system built into the language. Neither persists across [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/windows-command-aliases-doskey-powershell/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to customize colors in Windows Terminal</title>
		<link>https://zaur.it/windows-terminal-colors/</link>
					<comments>https://zaur.it/windows-terminal-colors/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Sun, 29 Mar 2026 09:43:50 +0000</pubDate>
				<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[Batch scripting]]></category>
		<category><![CDATA[Guide]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=1485</guid>

					<description><![CDATA[Windows Terminal lets you define color schemes once in settings.json and apply them to any profile. For administrators who spend hours reading PowerShell output, event logs, and SSH sessions, a well-configured scheme is not cosmetic - it directly affects how fast you spot warnings, errors, and status changes. This guide explains how color schemes work [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/windows-terminal-colors/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>pushd and popd: CMD Directory Stack Explained</title>
		<link>https://zaur.it/pushd-popd-cmd-directory-stack/</link>
					<comments>https://zaur.it/pushd-popd-cmd-directory-stack/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Sun, 27 Apr 2025 13:31:18 +0000</pubDate>
				<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[Batch scripting]]></category>
		<category><![CDATA[Guide]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=358</guid>

					<description><![CDATA[pushd and popd are two CMD built-in commands that let you save your current directory to a stack, navigate elsewhere, and return to the saved path with a single command. They are especially useful in batch scripts where you need to change directories temporarily and return cleanly afterward. Quick Reference Command What it does pushd [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/pushd-popd-cmd-directory-stack/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>TITLE command in Windows: label your terminals and track script progress</title>
		<link>https://zaur.it/title-command-windows/</link>
					<comments>https://zaur.it/title-command-windows/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Thu, 17 Apr 2025 22:49:55 +0000</pubDate>
				<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[Batch scripting]]></category>
		<category><![CDATA[Guide]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=345</guid>

					<description><![CDATA[The TITLE command changes the title bar text of a Command Prompt window. You probably already know that. But there is more to it - dynamic status updates during script execution, multi-window orchestration with START, and a few non-obvious behaviors worth knowing before you use it in production scripts. Quick answer What TITLE does TITLE [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/title-command-windows/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Windows dir Command: Syntax, Switches, and Practical Examples</title>
		<link>https://zaur.it/windows-dir-command/</link>
					<comments>https://zaur.it/windows-dir-command/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Wed, 16 Apr 2025 20:24:37 +0000</pubDate>
				<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[Batch scripting]]></category>
		<category><![CDATA[Reference]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=343</guid>

					<description><![CDATA[The dir command lists files and directories in a given path. It is available on every Windows system, works without additional tools or modules, and is reliable in scripts, remote sessions, and recovery environments. For system administrators, it is often the first command used when inspecting an unfamiliar system or building a file inventory. This [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/windows-dir-command/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>ren command in Windows: rename files and folders from CMD</title>
		<link>https://zaur.it/mastering-the-ren-command-in-windows/</link>
					<comments>https://zaur.it/mastering-the-ren-command-in-windows/#respond</comments>
		
		<dc:creator><![CDATA[Zaur Bahramov]]></dc:creator>
		<pubDate>Wed, 16 Apr 2025 10:57:07 +0000</pubDate>
				<category><![CDATA[Windows command line]]></category>
		<category><![CDATA[Batch scripting]]></category>
		<category><![CDATA[Guide]]></category>
		<guid isPermaLink="false">https://zaur.it/?p=332</guid>

					<description><![CDATA[ren renames a file or a folder from the command line. It has existed since MS-DOS, it takes no switches, and it is still the fastest way to rename a batch of files by pattern without opening Explorer or writing a script. The whole command is two arguments, which is exactly why the edge cases [&#8230;]]]></description>
		
					<wfw:commentRss>https://zaur.it/mastering-the-ren-command-in-windows/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
