New
#11
Chrome installed fine for me as well. Haven't had any problems with it; it runs great.
I had a couple problems with some apps not installing correctly on 7100, which worked fine in 7077. I tried Vista compatibility and running as administrator, still didn't work. But then I turned off UAC (hadn't had a chance to yet) and bam, it worked fine once I installed the program again with it completely off.
Before when i installed the program UAC would pop up and I would say ok, it would then install what seemed to be normally. Not sure why turning it off would make any difference.
I still have a network issue that I did in 7077 where my wireless won't seemed to connect automatically. May be a driver issue though.
Which version of chrome are you using. I installed and run fine with beta 2. If it is chrome 1 you tried then try with the beta which can be found here. If you still have no luck post back and I tell you what to do.
Google Chrome (BETA)
Hi there
just before doing a new "Clean install" I'm noticing on the old 7100 install that IE8 seems to crash randomly with no particular reason. I never had this on build 7077.
I notice also that uploading a file to the forum just waits until I do ANYTHING else on the computer -- even just look at Outlook Inbox etc -- then the file uploads instantly.
This is NOT a Forum problem -- it's IE8 as I have the same upload problem when file uploading with IE8 to other servers.
Enc screenshot. - I've disabled all accelerators etc.
I'll see again after a new clean install on a "virginal pristine HD" .
Cheers
jimbo
Odd issues jimbo, my IE8 has no problems whatsoever, and actually, it used to crash for me in 7077, never so far in 7100.
7100 works better than 7077 on my rig. A smidge faster, and has yet to crash since I installed it. 7077 was probably the most unstable build for me, although thats not really saying much. No issues whatsoever here. I've run x64 since build 7000 btw.
I have the solution to your problem, had the same issue.
*edit* You have to change the target name of your shortcut to
chrome.exe --in-process -plugins
In other words: you have to add "--in-process -plugins" to the target of your shortcut.
it should look like
C:\Users\your_username\AppData\Local\Google\Chrome\Application\chrome.exe --in-process-plugins on your desktop in the properties of your desktop shortcut
Hope this helps, this did it for me, it's a x64 bug
I'm pretty sure I heard/read that was a really bad idea Stannitje, I thought it opened up lopeholes etc.