timbojones
09-21-2006, 12:08 PM
Yesterday I was running a command line compile of our large project while testing some improvements in a testbed project called empty.sb5. It seems that SetupBuilder got confused by this, accessed some shared memory or something. The resulting .exe was named as expected, contained all the web install files I expected, but when we ran a test, it had the fullscreen background like I was testing in empty.sb5, and:
- Doing an upgrade, it finished immediately having not copied anything
- After it finished, I had a dialog titled #UNINST_HEADIN with text on|046|1|136|37 and OK as my only option
- Clicking OK just brought up that dialog again. I only clicked it about 10x before killing the process in Task Manager.
- Same for installing new to an empty folder.
- The default path to install to is “C:\Program Files\Flying Lab Software\empty”
I am currently rebuilding the installer with no other instances of sbuilder.exe running.
Update: rebuilding with no other instances worked without issue, as it usually does.
- Doing an upgrade, it finished immediately having not copied anything
- After it finished, I had a dialog titled #UNINST_HEADIN with text on|046|1|136|37 and OK as my only option
- Clicking OK just brought up that dialog again. I only clicked it about 10x before killing the process in Task Manager.
- Same for installing new to an empty folder.
- The default path to install to is “C:\Program Files\Flying Lab Software\empty”
I am currently rebuilding the installer with no other instances of sbuilder.exe running.
Update: rebuilding with no other instances worked without issue, as it usually does.