This content has been marked as final. Show 5 replies
Mabe you had a conflict with some other running software. Close and disable things like virus protection etc...
Just some thoughts
for your hint - but I already tried that, I think that's not the problem.
My machine's system is even freshly set up (3 days ago), so there shouldn't be problems with faultily uninstalled software or the like.
Maybe my notebook is too weak for Flex Builder..?
I wonder if there's a way to use the CLI to call the installer with all parameters neccessary for installation, so that the GUI mode, which the installer obviously can't load, won't load at all?
Good news, in the meantime I got it installed.
There seems to be a problem with "FlexBuilder2_B3_05-08.exe"; after it unpacks itself, it seems it can't find the path to the installer files and therefore aborts. Maybe the problem is that my user name contains an exclamation mark and brackets? Here's why I assume this:
FlexBuilder2_B3_05-08.exe unpacks itself to the folder
%system_root%\Documents and Settings\%user_name%\Local Settings\temp
It creates a folder named "I" plus a 10-digit number. The "FlexBuilder2_Installer.exe" is located in the subfolder "Windows".
Calling the file from this folder resulted in the same splash screen and abort message. Then I copied the whole stuff to another location - and this time I was able to select the setup method.
I selected "Plugin", and the installer told me it had to unpack some more files. After unpacking - the same procedure: splash screen - "Unable to load and to prepare the installer in GUI mode". Again, a look in the temp folder helped:
I copied the just unpacked folder "Downloaded Installations" to another folder and ran
\Downloaded Installations\Adobe Flex Builder 2.0 Beta 3 Installer\subinstallers\Plugin\Windows\FlexBuilder2_EclipsePlugins.exe
, which finally did the job.
I do not know what exactly the problem is but I am posting this because it might be of interest for ppl with the same problem or maybe even Adobe staff.
Thanks for posting your workaround to this problem. I'll keep this issue in mind for future versions of the Flex Builder installer, with the aim of avoiding it entirely.
Flex Builder Team