Hi,
I think I found a bug that occurs in a very special situation.
I have a OOBE-Script to automatically (and silently) install a couple of programs after the Windows installation.
For one installer I have the additional parameter:
When I save the configuration to a .wccf-File and load it later the string '+SAPGUI' ist replaced by asian (??) letters and all following characters (also in the following lines) are displayed using a different font. The resulting .cmd-file in the WORK-directory of course doesn't have differnt fonts, but the asian (??) letters are replaced by two question marks.
Screenshot of the script inside WinReducer 8.1
Replacing the whole script doesn't change this behavior.
Could you please have a look at it?
Best regards
BiberM
EDIT: WenReducer Details
Version: 2.2.0.0 x64 (started at least in version 2.0.0.0 or a bit earlier)
Used on german Windows 8.1.1 Pro x64 to build a custom Windows 8.1.1 Pro x64
I think I found a bug that occurs in a very special situation.
I have a OOBE-Script to automatically (and silently) install a couple of programs after the Windows installation.
For one installer I have the additional parameter:
Code:
/product:"NWBCGUI+SAPGUI"
When I save the configuration to a .wccf-File and load it later the string '+SAPGUI' ist replaced by asian (??) letters and all following characters (also in the following lines) are displayed using a different font. The resulting .cmd-file in the WORK-directory of course doesn't have differnt fonts, but the asian (??) letters are replaced by two question marks.
Screenshot of the script inside WinReducer 8.1
Replacing the whole script doesn't change this behavior.
Could you please have a look at it?
Best regards
BiberM
EDIT: WenReducer Details
Version: 2.2.0.0 x64 (started at least in version 2.0.0.0 or a bit earlier)
Used on german Windows 8.1.1 Pro x64 to build a custom Windows 8.1.1 Pro x64