Dear Chris (Robison),
Have you tested the original .bat file? I ran into just this issue earlier
today. I had written my .bat file from Visual Studio (11) which started as
a UTF-8 (or -16 not sure) .txt file. Not surprisingly, it had the BOM
appended to the front, which prevented execution.
Respe
Garbage in, garbage out.
Sorry, couldn't resist. Seriously though, I've never heard on Windows
Installer doing this. Do you have any custom actions that updat the file?
Is it possible the file is corrupted during the build process. ( Hence the
GIGO joke. )
Yeah, the UTF-8 suggestion was it. I reencoded the file to ANSI. Thanks so
much.
Chris
2012/4/12 Dirk Räder
> 2012/4/12 Chris Robison :
> > I have a batch file that I'm packaging into an installer and when it gets
> > installed on a machine, the installer seems to be putting garbage text at
> >
2012/4/12 Chris Robison :
> I have a batch file that I'm packaging into an installer and when it gets
> installed on a machine, the installer seems to be putting garbage text at
> the beginning of the file. This is causing execution problems. Any
> suggestions?
>
> Chris
Hi Chris,
usually neither
What is the garbage text? My suspicion is that you may have inadvertently saved
the batch file as a Unicode file and that there is a Unicode byte-order mark
(BOM) at the beginning of the batch file. If so, then open the batch file is
Notepad and then choose Save As and explicitly specify the enc
5 matches
Mail list logo
