All packages quoted below installed from repositories
Mint 16, Wine 1.4, Gecko 1.4, msttcorefonts working fine
Mint 17 RC, Wine 1.6, Gecko 2.2.1, msttcorefonts fails with "Zapf Calligraphic 801 Bold BT fialied to initlalise." blah blah Reboot
Mint 17 RC breaks Everquest II
Re: Mint 17 RC breaks Everquest II
So what exactly is the problem with Everquest II and Wine? All I see in the body of your post is some problem with the msttcorefonts package in Mint 17 RC. That's not a Wine issue--report it to your distro.
-
- Newbie
- Posts: 3
- Joined: Tue May 27, 2014 4:31 am
Re: Mint 17 RC breaks Everquest II
To be a lot clearer:
With the Mint 16 setup, launchpad.exe runs without error and the game runs without error after clicking the Play button.
With the Mint 17 setup, launchpad.exe runs without error and the game fails to launch with an error message that the font fails to load.
So does Wine install the font or does Mint install the font?
With the Mint 16 setup, launchpad.exe runs without error and the game runs without error after clicking the Play button.
With the Mint 17 setup, launchpad.exe runs without error and the game fails to launch with an error message that the font fails to load.
So does Wine install the font or does Mint install the font?
-
- Newbie
- Posts: 3
- Joined: Tue May 27, 2014 4:31 am
Re: Mint 17 RC breaks Everquest II
Some further investigation has shown that the font is supplied by the Everquest II game.
zcal801b.ttf is stored in c:/Games/EverQuest II/UI/fonts
c:/Games/EverQuest II/ will vary dependant a choice made during installation of the game
A screen capture of the pop-up is at https://www.dropbox.com/s/5nivo20xg3fr7pn/ZapfFail.png
zcal801b.ttf is stored in c:/Games/EverQuest II/UI/fonts
c:/Games/EverQuest II/ will vary dependant a choice made during installation of the game
A screen capture of the pop-up is at https://www.dropbox.com/s/5nivo20xg3fr7pn/ZapfFail.png
Re: Mint 17 RC breaks Everquest II
From your original post, it worked in 1.4 but doesn't in 1.6, so it could be a regression. Both versions are old, however, so before you run a regression test, try the current development release; this could be a bug that has already been fixed. If it still doesn't work in 1.7.19, run a regression test and file a bug.