Trying to create a .bat file for windows using fwrite( [message #183658] |
Thu, 07 November 2013 00:07 |
scasti1
Messages: 2 Registered: November 2013
Karma: 0
|
Junior Member |
|
|
I can create the .bat file, but the resulting file does not have the same new line
characters as another file that executes and looks the same except for this
the working file seems to have the type of newline characters
you would see in a word document (select it and you see a little
blank character area)
will using PHP_EOL solve my problem?
both files end up being properly recognized by the system as
batch files and both look the same in terms of content except for
the new line (i created my new line by using /r/n
Its not the same.
Thanks for any help.
|
|
|
Re: Trying to create a .bat file for windows using fwrite( [message #183659 is a reply to message #183658] |
Thu, 07 November 2013 00:29 |
Thomas 'PointedEars'
Messages: 701 Registered: October 2010
Karma: 0
|
Senior Member |
|
|
scasti1(at)yahoo(dot)com wrote:
^^^^^^^^^^^^^^^^^
Please fix.
> I can create the .bat file, but the resulting file does not have the same
> new line characters as another file that executes and looks the same
> except for this
>
> the working file seems to have the type of newline characters
> you would see in a word document (select it and you see a little
> blank character area)
The newline character sequence in WinDOS is <CR><LF>. It is therefore
natural that .bat files for Windows require this character sequence as they
are executed by a WinDOS program, COMMAND.COM or CMD.EXE.
> will using PHP_EOL solve my problem?
Only if it is PHP on Windows.
> both files end up being properly recognized by the system as
> batch files and both look the same in terms of content except for
> the new line (i created my new line by using /r/n
> Its not the same.
The proper escape sequence is "\r\n" (in double-quotes).
PointedEars
--
When all you know is jQuery, every problem looks $(olvable).
|
|
|
Re: Trying to create a .bat file for windows using fwrite( [message #183662 is a reply to message #183658] |
Thu, 07 November 2013 04:49 |
Richard Damon
Messages: 58 Registered: August 2011
Karma: 0
|
Member |
|
|
On 11/6/13, 7:07 PM, scasti1(at)yahoo(dot)com wrote:
> I can create the .bat file, but the resulting file does not have the same new line
> characters as another file that executes and looks the same except for this
>
> the working file seems to have the type of newline characters
> you would see in a word document (select it and you see a little
> blank character area)
>
> will using PHP_EOL solve my problem?
>
> both files end up being properly recognized by the system as
> batch files and both look the same in terms of content except for
> the new line (i created my new line by using /r/n
> Its not the same.
>
> Thanks for any help.
>
When you create text based files for your local machine, you should make
sure that you open them in "text" mode, which will cause the library to
convert \n to whatever is needed for the local machine as a line ending.
|
|
|
Re: Trying to create a .bat file for windows using fwrite( [message #183666 is a reply to message #183658] |
Thu, 07 November 2013 20:00 |
scasti1
Messages: 2 Registered: November 2013
Karma: 0
|
Junior Member |
|
|
On Wednesday, November 6, 2013 5:07:33 PM UTC-7, sca...@yahoo.com wrote:
> I can create the .bat file, but the resulting file does not have the same new line
>
> characters as another file that executes and looks the same except for this
>
>
>
> the working file seems to have the type of newline characters
>
> you would see in a word document (select it and you see a little
>
> blank character area)
>
>
>
> will using PHP_EOL solve my problem?
>
>
>
> both files end up being properly recognized by the system as
>
> batch files and both look the same in terms of content except for
>
> the new line (i created my new line by using /r/n
>
> Its not the same.
>
>
>
> Thanks for any help.
My solution was to do a more normal set of batch commands rather a funky set that worked for some reason some time in the past and still did but could not be replicated with new iterations of creation for some reason. Since it wasn't working initially, I thought something else may be wrong. I did still use PHP_EOL but /r/n would have worked too I'm sure. Thanks for the help.
|
|
|