You are here

GoogleChromePortable.exe Doesn't Launch chrome.exe

3 posts / 0 new
Last post
kleinfelter
Offline
Last seen: 13 years 6 months ago
Joined: 2006-11-09 08:47
GoogleChromePortable.exe Doesn't Launch chrome.exe

I have to run Google Chrome Portable from a "network" drive. It gets half-way started, but does not proceed.

Looking in Task Manager, I see GoogleChromePortable.exe running, but no chrome.exe processes running. In the Chrome UI, I see a what looks like an "about:blank" page (without "about:blank" actually being in the URL field), but the mouse pointer is a wait-cursor (the hourglass) in the content area.

If I enter an URL in the URL field, it vanishes when I press enter, and the content area still looks like about:blank, with a wait-cursor.

If I start GoogleChromePortable.exe with log-level of 0 or 3, I get an empty chrome_debug.log. If I start it with log-level of 9, chrome_debug.log contains only a message that 9 is an invalid log level.

My employer uses a whole-disk encryption product, which attempts to encrypt NTFS or FAT partitions on USB drives when they're inserted. I'm working around this by running a VM, which is accessing a raw partition on the USB drive. My VM then shares folders on a host-only network.

So to Windows, it looks like Chrome Portable is running from a network drive. I'm the only person who will ever use this 'network' drive.

I'm thinking that GoogleChromePortable.exe is attempting to lock something before it lets things proceed.

Any suggestions as to how to get it to stop waiting for whatever it is waiting for?

John T. Haller
John T. Haller's picture
Online
Last seen: 19 min 2 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Unsupported

Chrome itself can't run from a UNC path at all. It can only run from a proper drive showing up as an actual drive letter.

Sometimes, the impossible can become possible, if you're awesome!

kleinfelter
Offline
Last seen: 13 years 6 months ago
Joined: 2006-11-09 08:47
Mapped Drive

Thank you for your reply. I do have the UNC path mapped to a drive letter.

I did a little more testing and I think that it was a permissions problem caused by not mapping correctly between my Windows user ID and my Linux user ID. (Looks like I'm going to have to learn how to upgrade from SAMBA's smbpasswd database to a passdb user store.)

Log in or register to post comments