QUOTE (clevermax @ Sep 5 2008, 09:43 PM)

I recently installed Google Chrome. Installation was very light, and it took less than a minute to get it installed and working. Wow...
It can run executables from javascript with no prompts whatsoever, not to mention that it (by default) sends your omnibar information back to Google - and that was just the first day, I'm sure there will be many more "fun" things about Chrome to come up as time moves on. I'm hopeful these will be addressed quickly, but one has to wonder - how much security does Chrome actually have if such a simple exploit was included in the release?
I will agree that Chrome is quite zippy on javascript pages (due to compiled js and a very good engine), but more complex (not javascript driven) pages tend to choke it and slow it down immensely, and some pages just don't look quite right when compared to Firefox, Safari, Opera, or IE. Also, Google's applications are inherently in beta status for a long time, leaving some of us wondering how much actual refinement and further development actually goes into their applications once they do release - dev might indeed continue full-scale, but there's no way to know if it never hits "1.0" or "2.0" (in fact, how many Google apps compared to their entire stable are in beta? - I'm actually curious...)
QUOTE (clevermax @ Sep 5 2008, 09:43 PM)

Anyone here faced this problem? I'd appreciate any information as to what went wrong.
The IE installer logs everything. Look for ie8*.log files on your box - the information on why it failed should be in there.