<div>
1&gt;nul is the same as &gt;nul in this context, for example:<br />
<br />
dir &nbsp;1&gt;nul<br />
<br />
1 indicates stdout, whereas 2 indicates stderr:<br />
<br />
dir &nbsp;\\server\share &nbsp;2&gt; err.out<br />
<br />
If the server can't be found, the error message will be sent to err.out
</div>


<div>
[These 1's are wreaking havoc on my scripts]<br />
<br />
How so? &nbsp;What kind of scripts are you referring to?
</div>


<div>
Sorry all.. turns out it was a permissions issue on the share where the script was kept... which was causing the errors. &nbsp;I assumed it was due to the 1's being present in the output... but once the perms were fixed, the 1's didn't matter.<br />
<br />
Again, sorry for the dumb moment.. and thanks for your help.<br />

</div>


<div>
<div class="content wysiwyg-content">
Im making a batch file in DOS and trying to put &gt;NUL or &gt;&gt;(filename) at the end of lines but when I run it and see the output it comes out wrong...<br />
<br />
&gt;NUL becomes 1&gt;NUL and &gt;&gt;(filename) becomes 1&gt;&gt;(filename).<br />
<br />
These 1's are wreaking havoc on my scripts.. anyone know why this is happening?<br />
<br />

</div>
</div>


Im making a batch file in DOS and trying to put >NUL or >>(filename) at the end of lines but when I run it and see the output it comes out wrong...

>NUL becomes 1>NUL and >>(filename) becomes 1>>(filename).

These 1's are wreaking havoc on my scripts.. anyone know why this is happening?



1&amp;gt;nul is the same as &amp;gt;nul in this context, for example:

dir  1&amp;gt;nul

1 indicates stdout, whereas 2 indicates stderr:

dir  \\server\share  2&amp;gt; err.out

If the server can&amp;#39;t be found, the error message will be sent to err.out

[These 1&amp;#39;s are wreaking havoc on my scripts]

How so?  What kind of scripts are you referring to?

Sorry all.. turns out it was a permissions issue on the share where the script was kept... which was causing the errors.  I assumed it was due to the 1&amp;#39;s being present in the output... but once the perms were fixed, the 1&amp;#39;s didn&amp;#39;t matter.

Again, sorry for the dumb moment.. and thanks for your help.


BATCH FILES:  When sending output to a file, &amp;gt;&amp;gt; becomes 1&amp;gt;&amp;gt;.  Why?

Im making a batch file in DOS and trying to put &amp;gt;NUL or &amp;gt;&amp;gt;(filename) at the end of lines but when I run it and see the output it comes out wrong...

&amp;gt;NUL becomes 1&amp;gt;NUL and &amp;gt;&amp;gt;(filename) becomes 1&amp;gt;&amp;gt;(filename).

These 1&amp;#39;s are wreaking havoc on my scripts.. anyone know why this is happening?



BATCH FILES:  When sending output to a file, &gt;&gt; becomes 1&gt;&gt;.  Why?

Most development for the Microsoft platform is done utilizing the technologies supported by the.NET framework. Other development is done using Visual Basic for Applications (VBA) for programs like Access, Excel, Word and Outlook, with PowerShell for scripting, or with SQL for large databases.

Microsoft Development

Batch files are text files containing a script of commands that are executed by the command interpreter on DOS, OS/2 and Windows systems. Most commonly, they are used to perform a series of functions that are repeated -- copying a set of files created daily with one step, for example.

Windows Batch

Microsoft Disk Operating System (MS-DOS) was an operating system for x86-based personal computers, and traces of it are still found in the Windows operating system. DOS is still used in some embedded systems and for certain legacy 16-bit networks.