Two maps: "Atlas" and "Open Street Map" appear to work just fine. Any other map that I have yet tested does not work. As you can see in the screenshot, the globe behind the dialog is white. The dialog never moves beyond 0%. This is Marble in Windows 7 in VirtualBox, Fedora 20.
Created attachment 88002 [details] Dialog
Same problem on Windows 7 x64 native.
Can you give a pre-release of the Marble 1.9.1 installer (64bit version) a try? I uploaded it to http://nienhueser.de/marble/marble-setup_1.9.1_x64.exe It contains the following patch which might fix the problem: http://quickgit.kde.org/?p=marble.git&a=commit&h=134ab731459a481621600951c678d4dd6519b9f3 Use a local path determined by Qt API as storage location in windows While i cannot reproduce bug #337872 I suspect that the calls to Windows API to determine a local storage are related. Since Qt has API for it let's just use that instead. At the same time the storage location changes from a roaming profile location to a computer local location. If Marble stores several GB in a roaming profile (happens easily for e.g. heavy OSM users), the Windows login time can increase significantly when the roaming profile is synced. Using a local location avoids that (at the cost of having to install additional map themes on each computer in use separately). If that breaks your use case, please open a bug report and I'll introduce a config option to enable storing in roaming profiles again. Old data in a roaming profile, if any, is migrated to the new location on Marble startup if the user chooses so (a dialog asks about it once on startup).
1.9.1 gives the following error: marble-qt.exe - System Error The program can't start because MSVCR120.dll is missing from your computer. Try reinstalling the program to fix this problem.
Right, sorry about that. http://nienhueser.de/marble/marble-setup_1.9.1_x64.exe is updated and should have that fixed along with some other installer improvements.
Git commit 790e3a5186875da472738983cb87eef666d4c300 by Dennis Nienhüser. Committed on 14/09/2014 at 19:51. Pushed by nienhueser into branch 'master'. Use a local path determined by Qt API as storage location in windows While i cannot reproduce bug #337872 I suspect that the calls to Windows API to determine a local storage are related. Since Qt has API for it let's just use that instead. At the same time the storage location changes from a roaming profile location to a computer local location. If Marble stores several GB in a roaming profile (happens easily for e.g. heavy OSM users), the Windows login time can increase significantly when the roaming profile is synced. Using a local location avoids that (at the cost of having to install additional map themes on each computer in use separately). If that breaks your use case, please open a bug report and I'll introduce a config option to enable storing in roaming profiles again. Old data in a roaming profile, if any, is migrated to the new location on Marble startup if the user chooses so (a dialog asks about it once on startup). (cherry picked from commit 134ab731459a481621600951c678d4dd6519b9f3) M +6 -0 src/apps/marble-qt/QtMainWindow.cpp M +2 -1 src/lib/marble/DataMigration.h M +30 -17 src/lib/marble/MarbleDirs.cpp http://commits.kde.org/marble/790e3a5186875da472738983cb87eef666d4c300