removing samyak/oriya fonts for wine
when installing the dotnet packages in wine, i got this error -
user@darkstar:~/.wine$ ./winetricks dotnet11
Executing w_do_call dotnet11
Executing load_dotnet11
Executing w_do_call fontfix
Executing load_fontfix
-misc-samyak-medium-r-normal--0-0-0-0-p-0-iso10646-1
-misc-samyak-medium-r-normal--0-0-0-0-p-0-iso10646-1
------------------------------------------------------
Please uninstall the Samyak/Oriya font, e.g. 'sudo dpkg -r ttf-oriya-fonts', then log out and log in again. That font causes strange crashes in .net programs.
------------------------------------------------------
to remove the font package
# its a part of the ttf-indic-fonts package, so we need to remove it
removepkg ttf-indic-fonts-0.4.7.4-noarch-1.txz
# there are other references to them – using a handy sed command you can find them and then edit the file to remove.
# i ran the following commands in the /usr/share/fonts directory
grep -nr samy . | sed 's@\(Samyak\)@@'
grep -nr oriy . | sed 's@\(Oriya\)@@'
after the oriya and samyak fonts and all mentions of them are removed, log out and log back in and you should be all set to move forward with the dotnet11 install
installing wine 1.3.1 in slackware 13.1
here is how to install and configure wine 1.3.1 from source with additional configurations for nVidia card owners.
download the source here.
open up the tarball:
tar -jvxf wine-1.3.1.tar.bz2
cd into the newly created directory:
cd wine-1.3.0
configure and make dependencies:
./configure --with-x && make depend && make
install wine you may need to sudo this one
make install
create the .wine directory in your home folder:
winecfg
install winetricks for additional .dll’s:
cd .wine/
wget http://www.kegel.com/wine/winetricks
make winetricks executable:
sudo chmod +x ./winetricks
install additional .dll’s using winetricks:
./winetricks d3dx9 droid winxp sound=alsa volnum vcrun2008 dotnet20 ie6 corefonts
recommended for nvidia card users: for the physx gaming engine – make sure your card is supported
./winetricks physx
now, after you have done all this, there is still more to do in order to properly configure wine:
configure the wine registry for windows gaming:
wine regedit
browse to HK_CURRENT_USER/Software/Wine/ and add a new key named Direct3D. then add the following strings and values:
| string | value |
| DirectDrawRenderer | opengl |
| Nonpower2Mode | repack |
| OffscreenRenderingMode | fbo |
| RenderTargetLockMode | auto |
| UseGLSL | readtex |
| VertexShaderMode | hardware |
| VideoDescription | NVIDIA GeForce GT 220 |
| VideoDriver | nv4_disp.dll |
| VideoMemorySize | 1024 |
you can add it manually as shown above, or, copy and paste the following to a graphics.reg file and import it to wines registry.
REGEDIT4
[HKEY_CURRENT_USERSoftwareWineDirect3D]
"DirectDrawRenderer"="opengl"
"Nonpower2Mode"="repack"
"OffscreenRenderingMode"="fbo"
"RenderTargetLockMode"="auto"
"UseGLSL"="readtex"
"VertexShaderMode"="hardware"
"VideoDescription"="NVIDIA GeForce GT 220"
"VideoDriver"="nv4_disp.dll"
"VideoMemorySize"="1024"
enable support for misc binaries:
edit /etc/rc.d/rc.modules and uncomment the following line:
/sbin/modprobe binfmt_misc
then add the following to /etc/fstab:
none /proc/sys/fs/binfmt_misc binfmt_misc defaults 0 0
now add the following to /etc/rc.d/rc.local”:
echo ':windows:M::MZ::/path/to/wine:' > /proc/sys/fs/binfmt_misc/register
echo ':windowsPE:M::PE::/path/to/wine:' > /proc/sys/fs/binfmt_misc/register
now reboot the machine
wow 4.x in wines top 10 gold list
this has probably been around for awhile, however, i just noticed it today. wow 4.x made the top 10 gold games list in the appdb.winehq.org.
i cant really say from my experience it has been flawless as far as wow goes, but, that has yet to deter me from continually finding new workarounds toi get the game running even better on my custom slackware system.
adobe with wine in slackware
i already had flash and photoshop installed on a windows vm and i wanted to see how it ran using wine in slackware. (i was getting sick of the marginal delay using vnc)
1) copy adobe over to linux
-
Program FilesAdobeinto$HOME/.wine/drive_c/Program Files Documents and SettingsAll UsersApplication DataAdobeinto$HOME/.wine/drive_c/users/Public/Application Data
2) export the adobe registry branch from HKEY_LOCAL_MACHINE/SOFTWARE/Adobe
3) install additional windows libraries using winetricks – sh winetricks vcrun2008 msxml3 atmlib gdiplus
4) import the registry file into wines registry
i managed to get photoshop working this way and i am having difficulty with flash. i will post more once i solve the problem.
patch 4.0.1 issues
** update 7:38pm 10/16/2010 **
got it working. i ended up having my younger brother come over and i copied his entire wow directory over to my netbook. it worked flawlessly. now i am in the process of pushing the working 4.0 copy of wow to the server so i can download it to my slack box and still have a viable copy.
it may have worked if i wanted to wait the 16 hours it was telling me it would take to download. however, the downloader kept constantly informing me of a firewall in place. which was definitely not the case. i had all the ports open on the untangle router, the untangle firewall, windows firewall exceptions in place as well. hell, i even went into my ddwrt router and setup port forwarding on that as well. even when i shut off the firewall on untangle, shut off the av on untangle and had the ports wide open to the pc, the blizzard downloader still told me i was behind a firewall. thats when i gave up and called my brother.
** end update **
** update 12:40pm 10/16/2010 **
still absolutely no progress. i even deleted wow entirely, removed all instances in the registry, removed all the temp files, hell even the icons. i then downloaded the actual installer from battle.net. it failed at 20%. it fails at 20% every time i try to install the game. both on windows xp and on slackware.
as usual the wow forums are borderline useless. the wine forums have yet to yield anything i can use either.
** end update **
** update 8:35am 10/16/2010 **
i downloaded the patch in its entirety last night. i tried to install it on a 3.3.5 copy of wow that i had on my vm. still now luck. i get a fatal error and wine crashes and it produces the same error as before
i saw here at the wine bug forums that a new ~/.wine would fix the problem. that still didnt work.
i have now removed wine-1.1.42 and built from source wine-1.3.0. i even removed the ~/.wine and have had no success in installing the new patch.
even in windows the patch fails to install. i am copying the entire wow directory from my slack install with the new patch over to my windows xp machine and am going to see how that pans out.
if all else fails i will have my older or younger brother bring one of their pcs over to my place and i will copy their currently working version of wow (which, they both used my 3.3.5 copy from my server to install on)
** end update **
** update 7:49am **
nothing has worked so far. when i ran the
repair.exe it halted and told me it was unable to repair wow and i had to reinstall. this happened on both my slackware box and my xp box. so i deleted wow entirely on both machines and now i am copying my working backup of my vm server to both machines. i will post more if i get anything to work.
once again, thank you blizzard. 12,000,000 * $15.00 = $180,000,000. with this kind of money monthly you would think the patch and update process would be smooth as hell. but no. every single patch results in some kind of issue. (as you can see they brag about 12 million players here)
** end update **
** update 7:35am **
https://us.battle.net/account/downloads/WoW-4.0.0-WOW-enUS-Installer.exe
failed as well. i am going to try a couple different options in wine as well. i saw on the ubuntu forums that some people had to upgrade wine in order to get the new patch to work. i refuse to change my version of wine again. i already had to regress my kernel and version of wine and i have no interest in doing so again.
** end update ***
here is what i have tried so far.
downloaded the patch via wine in slackware. attempted to install the patch and it failed. i ran the repair via wine and then ran the installer again and still no luck.
downloaded the patch via windows xp. attempted to install the patch and it too failed. i ran the repair and then ran the installer again. still nothing.
i have even tried installing the patch inside of windows 7. still epic fail. (thank you blizzard for not even attempting to release a stable patch).
now i have gone over to https://us.battle.net/account/downloads/WoW-4.0.0-WOW-enUS-Installer.exe
to download the patch installer. hope this works.
one would think that with the $15 per account and the 12 million users, blizzard would be producing flawless patches with guaranteed streaming downloads. but no. we are stuck with the p2p downloads at a whopping 250-350kbps. pure awesome.
patch 4.0.1 issues in wine
i downloaded the patch overnight last night. the download went flawlessly. the downloader checks the patch with no errors and begins the installation then gets to about 2% and fails with the following error.
in the past i have had to download the patch on my windows machine and then copy it over to my slack box. this time i tried to copy the patch i downloaded on my slack box over to windows and the patch still failed to install.
here is the error.
wine 1.3.2 released
wine 1.3.2 has been released. you can get all the info for bug fixes and download it here
wow 3.3.5 log in issues using wine cont.
- update -
i regressed my kernel to 2.6.31.14 and my version of wine to 1.1.42 and now wow works flawlessly. i am not to impressed with having to regress my kernel, however, i was able to use my previous .config. recompiling again also gave me another chance to trim more out of my kernel as well.
for more information regarding this issue, see the kernel bug report and the wine bug report.
originally posted on 8/22/2010
i am currently using wine 1.3 with slackware 13.1
mike@darkstar:~$ uname -a
Linux quotidian 2.6.33.4-map-8-6-2010 #7 SMP Fri Aug 6 22:09:44 EDT 2010 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ AuthenticAMD GNU/Linux
i have used winetricks and installed vcrun2005 and switched to direct3d and was unable to login.
i also changed wldap32.dll to native, builtin and still unable to log in.
i have read that using wine 1.1.44 or later with kernels 2.6.33 or later causes this issue. here is the bug report
i suppose i will have to play on my netbook in windows. thankfully it is hooked up to a 36″ flat screen so its not all bad.
wine 1.3.0
wine 1.3.0 was release 07/30/2010. you can get it here.
go here for a quick how-to on installing one from source.
the shortlog is here
a quick summary of whats new in 1.3.0:
- beginnings of a user interface for the builtin internet explorer.
- support for cross-process ole drag & drop.
- new builtin wscript.exe (windows script host) program.
- open/save dialogs remember the last used directory.
- translation updates.
- various bug fixes.
wow patch 3.3.5 log in issues using wine
– update –
i saw on this wow forum a blizzard tech support member said that a 3.3.5a patch should be out in the near future. hopefully this fixes the connectivity issues.
originally posted on 7/5/2010
with the release of the new patch there has been a host of issues with logging onto world of warcraft using wine.
here is some brief system specs for my work pc:
mike@darkstar:~$ uname -a
Linux darkstar 2.6.33.3-smp #2 SMP Sat May 1 00:26:54 CDT 2010 i686 Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz GenuineIntel GNU/Linux
mike@darkstar:~$ wine --version
wine-1.1.38
here is some brief system specs for my home pc:
mike@darkstar:~$ uname -a
Linux darkstar 2.6.32.7-map-03-2010 #2 SMP Tue Mar 16 12:15:50 EDT 2010 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ AuthenticAMD GNU/Linux
mike@darkstar:~$ wine --version
wine-1.1.38
on my home pc, i do not have as many issues logging into wow as my work pc, the primary difference being the kernel version. i had read on several forums that the issue could be related to network stacking in the 2.6.33 kernel. on some of the forums linked above, they suggested either regressing wine or regressing the kernel to an earlier version that 2.6.33 kernel. i am not terribly interested in regressing my kernel and i have tried upgrading wine. the next thing is to try an older version of wine and see how that goes. i will try this when i get into work tomorrow or on wednesday. i also found several good ideas here and will have to try them tomorrow when i go into work.