Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

64-bit Win 7 builds not running #612

Closed
komoku opened this issue Dec 23, 2014 · 8 comments
Closed

64-bit Win 7 builds not running #612

komoku opened this issue Dec 23, 2014 · 8 comments

Comments

@komoku
Copy link

komoku commented Dec 23, 2014

64-bit builds of Otter do not run in my machines (two different machines) with 64-bit Win 7. They just fail silently, without any error message at all. In contrast, 32-bit builds run normally.

@bajasoft bajasoft self-assigned this Dec 23, 2014
@ghost
Copy link

ghost commented Dec 23, 2014

Same here, 64 bit not starting, just tray icon appears and hides when hovering with mouse

@ghost
Copy link

ghost commented Dec 31, 2014

#52 says "There Is No Disk in the Drive. Please Insert a Disk into Drive \Device\harddisk\Dr1"

@bajasoft
Copy link
Member

Part "\Device\harddisk\Dr1" means Device Removable 1 (It can be USB, CD/DVD drive or card reader)
Try this approach if error still occurs:
http://community.spiceworks.com/how_to/show/1986-there-is-no-disk-in-the-drive-error-message

@ghost
Copy link

ghost commented Jan 3, 2015

beta 4 still same issue

@komoku
Copy link
Author

komoku commented Jan 3, 2015

I have a machine where previous versions had this issue, and Beta 4 seems to work fine (note: not the same machine where I installed the VC++ redistributable the other day). So at least I can confirm it's fixed in some configurations...

@bajasoft
Copy link
Member

bajasoft commented Jan 3, 2015

@JustinTimberland, please try this version and let me know, if it works:
https://www.dropbox.com/s/sv4qzpz5az9gfti/otter-browser-win64-beta4-v2.zip?dl=0

@ghost
Copy link

ghost commented Jan 3, 2015

Yes, this one works

@bajasoft
Copy link
Member

bajasoft commented Jan 4, 2015

The problem was in OpenSSL libraries where is hardcoded path to config file - it leads to drive where were this libraries installed on develop PC (G drive in all previous versions). It cause system exception in case there is drive with this letter, but it is inaccessible (like DVD drive without DVD).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants