https://bugs.winehq.org/show_bug.cgi?id=52710
Eric Pouech eric.pouech@orange.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eric.pouech@orange.fr
--- Comment #6 from Eric Pouech eric.pouech@orange.fr --- confirming (partially)
---- installation notes
installation of version 5.5.9 non unicode version - same version as in #0, from https://files.jrsoftware.org/is/5/ - picking up non unicode version (for the record)
side note: - installation is done in Program Files (x86), while report in #0 gets installation in Program Files (for the record)
run the whole stuff from Inno Setup 5 directory (for simplicity) (all paths below are in this directory)
need a couple of more files (than attachments #1 and #2) - touch EULA.rtf - touch Setup.bmp - touch SetupSmall.bmp - cp <whatever ico you want>.ico icon.ico
---- running notes
confirming that now ANSI escape sequences appear in output but that doesn't impact expect (given the way the expect script has been written - ie no sync on beginning or end of line)
<[[output]]> Copyright (C) 1997-2016 Jordan Russell. All rights reserved. Portions Copyright (C) 2000-2016 Martijn Laan Inno Setup Preprocessor Copyright (C) 2001-2004 Alex Yackimoff. All rights reserved.
Compiler engine version: Inno Setup 5.5.9 (a)
[ISPP] Preprocessing. [ISPP] Preprocessed.
Parsing [Setup] section, line 32 --snip--- Parsing [Setup] section, line 70 Reading file (LicenseFile) Reading file (WizardImageFile) File: C:\Program Files (x86)\Inno Setup 5\Setup.bmp Reading file (WizardSmallImageFile) File: C:\Program Files (x86)\Inno Setup 5\SetupSmall.bmp Preparing Setup program executable Updating icons (SETUP.E32) Using existing signed uninstaller file: C:\Program Files (x86)\Inno Setup 5\TheOutDir\uninst-5.5.9 (a)-983e611017.e32 Error in C:\Program Files (x86)\Inno Setup 5\testFile.iss: Signed uninstaller mode is enabled. Using an external code-signing tool, please attach your digital signature to the following executable file:
C:\Program Files (x86)\Inno Setup 5\TheOutDir\uninst-5.5.9 (a)-983e611017.e32
and compile again.
saw uninstaller signing failure <[[output]]>
--- and now? that leaves the interleave (pleas\r\r\ne from #0) as the potential culprit for the issue I checked (from the example) that iscc.exe doesn't spawn new processes
that leaves several options:
a) iscc.exe behaves differently between #0 and my testings
b) it's a FIXME debug info from wine running iscc.exe. you can try to turn them off (export WINEDEBUG=fixme-all,err-all could help)
c) it's another wine's session program outputing in // of ISCC a possible work around would be: - in the runInExpect.sh script, **before** running expect, to do something like: wine notepad - having the wine session launched before the expect will ensure all the other regular programs run in the session will not get attached to the expect pty - (I won't comment terminating notepad, it can be more complicated)
d) it's a crossover thingie maybe quirk from c) could help too; maybe not
e) some other things?
in all cases, having the full log of the wine session output (through exp_internal or exp_log if it works) could help