On Wed, May 16, 2012 at 7:43 AM, Robert Jackson wrote:
> We dynamically build up a %PATH% location and store into a variable.
I'm still not quite sure what you mean there. :-) I'm getting the
feeling there's a larger problem wrapped around this one which may be
relevant and/or solved a better
Powershell -nologo -file c:\scripts\stripcrlf.ps1 %VARIABLE%
-Original Message-
From: Robert Jackson [mailto:r...@walkermartyn.co.uk]
Sent: Wednesday, May 16, 2012 7:44 AM
To: NT System Admin Issues
Subject: RE: MakeTxt.exe or Equivalent
Hi Ben,
Many thanks for the reply. We dynam
]
Sent: 16 May 2012 12:44
To: NT System Admin Issues
Subject: RE: MakeTxt.exe or Equivalent
Hi Ben,
Many thanks for the reply. We dynamically build up a %PATH% location and store
into a variable. At this point the content of that variable is a string that
occupies a number of lines. The contents
of the %PATH% location expressed as a single line of text..
-Original Message-
From: Ben Scott [mailto:mailvor...@gmail.com]
Sent: Wednesday 16 May 2012 12:28
To: NT System Admin Issues
Subject: r...@walkermartyn.co.uk - Re: MakeTxt.exe or Equivalent -
Bayesian Filter detected spam
On Wed
On Wed, May 16, 2012 at 7:03 AM, Robert Jackson wrote:
> We are using a program MakeTxt.exe to strip out CR/LF’s from
> a path string we build up.
Can you please give some context for that. I don't really get
what's going on.
The "FOR" built-in command can be used to read lines from a file
We are using a program MakeTxt.exe to strip out CR/LF's from a path
string we build up. This command works fine up to Windows 2003. I am in
the process of now building a Windows 2008 R2 server and find that I
cannot use the program as it is not compatible with 64bit. As far as I
can see, I cannot s
