Warning wine cmd exe c echo appdata returned empty string error message

Не могу запустить wine

Установлен wine64 version 5.0.4 при помощи pkg install wine

При запуске exe файла вылетает с ошибками в консоли:

not supported on this system

что дальше? на haiku или на kolibrios игоры запускать будете?

То есть мне нужно искать какие-то нативные чтобы запустилось?

Под 6.0.1-вайном они же запускаются, я проверял

wine64 version 5.0.4 при помощи pkg install wine

такое нужно самому компилять из портов

Компилять нужно только mesa и всё что связано с видео, wine и i386-wine — совершенно необязательно.

bambie , я не знаю что ты хочешь запустить, но ты уверен что оно именно PE32+ (x86-64), запуская его через wine (amd64)?

а что, у вас там есть уже собранный wine с esync патчем?

ты уверен что оно именно PE32+ (x86-64), запуская его через wine (amd64)?

Я могу в этом убедиться только запустив его с 32битным wine:

mesa и всё что связано с видео

mesa не компиляю — только видеодрайвера

С помощью file можно посмотреть:

Был не прав, оно действительно было PE32

Kron4ek , спасибо большое.

как удалить старое ядро? было у меня оно одно, но подвезли новый drm-kmod который со старым ядром отказался работать, пришлось собрать новое ядро и установить в него новый drm-kmod — теперь у меня два ядра, но старое не нужно — как его удалить? может есть какое нибудь remove-old-kernels или что то типа такого?

А что, из портов можно собрать wine с esync? (%

Еще вопрос. Могу ли я установить второй вайн, собрав его с другим PREXIF? Если да, то как?

с другим PREFIX

Я могу в этом убедиться только запустив его с 32битным wine

file -b /path/to/file.exe

Сам понимаешь, телепаты в отпуске. (%

Был не прав, оно действительно было PE32

FreeBSD хранит только два ядра — последнее и предыдущее, каждый make installkernel перемещает /boot/kernel в /boot/kernel.old (и удаляет старый /boot/kernel.old , если он существует), затем ставит новое в /boot/kernel .

А вот что происходит с /boot/modules я не помню, при обновлении GENERIC на следующий релиз оно вайпает чуть ли не всю систему.

Тебе не обязательно собирать wine с другим PREFIX, достаточно распаковать куда угодно и написать обёртку со всеми нужными переменными окружения.

Могу поделиться скриптом, но он во-первых нифига не документирован (могу на пальцах объяснить что как, но никакой поддержки не обещаю, об этом дальше), а во-вторых не работает с wine >=6.0 (там что-то с окружением, гуглить сейчас лень, фиксить не планирую, ибо проще переписать скрипт с нуля, там костылей за два года быстроправок скопилось).

а что, у вас там есть уже собранный wine с esync патчем?

А что, на фряхе появился eventfd?

UPD: Фигасе, The eventfd() system call first appeared in FreeBSD 13.0.

Все, фря готова для гейминга

Есть же всякие гуи вроде PlayOnLinux, они не умеют рулить несколькими версиями вайна?

Есть форк — PlayOnFreeBSD, но я никогда его не тыкал. А вот Lutris на FreeBSD судя по всему вообще не работает (нет никаких упоминаний на официальном сайте, никаких упоминаний на официальном форуме FreeBSD и на сабреддите).

Мне проще накидать скрипт на двадцать пять килобайт и пару лет не париться по этому поводу. Причём в эти двадцать пять килобайт бонусом влезла поддержка dosbox, renpy, gzdoom, pcsxr и dolphin-emu как для amd64, так и для i386.

…достаточно распаковать куда угодно и написать обёртку со всеми нужными переменными окружения.

Хочу узнать об этом поподробнее. Как это сделать?

Могу поделиться скриптом, но он во-первых нифига не документирован (могу на пальцах объяснить что как, но никакой поддержки не обещаю, об этом дальше), а во-вторых не работает с wine >=6.0 (там что-то с окружением, гуглить сейчас лень, фиксить не планирую, ибо проще переписать скрипт с нуля, там костылей за два года быстроправок скопилось).

Пожалуй, давай, это лишним не будет. В инете информации по этому поводу мало, а этот вопрос может быть интересен не только мне. Ну и если проще переписать, может быть кто-то подскажет, кому будет не лень? А так я не против в этом разобраться.

Есть же всякие гуи вроде PlayOnLinux

https://www.freshports.org/emulators/playonbsd Если это оно, то он удален, написано в прошлом году. Но всё равно это было просто обёрткой для wine

Мне проще накидать скрипт на двадцать пять килобайт и пару лет не париться по этому поводу.

Еще проще — установить games/homura.

…достаточно распаковать куда угодно и написать обёртку со всеми нужными переменными окружения.

Хочу узнать об этом поподробнее. Как это сделать?

Нужно понимать как устроено окружение и что нужно конкретному приложению для полноценной работы.

Если раскуришь скрипты многоуважаемого Kron4ek , многое поймёшь конкретно про Wine. Мой скрипт местами переусложнён и/или сильно несовершенен, но он никогда не пилился для публичного использования, потому он такой какой он есть.

Пожалуй, давай, это лишним не будет.

Ссылка в конце комментария.

В инете информации по этому поводу мало, а этот вопрос может быть интересен не только мне. Ну и если проще переписать, может быть кто-то подскажет, кому будет не лень? А так я не против в этом разобраться.

Ну, FreeBSD никогда не позиционировалась как игровая платформа, потому готовых решений до сих пор нет, а все попытки быстро загибаются.

Я не особо геймер, потому не пытался сделать что-то с планами на будущее.

Внутри быстро накиданный README, наверняка с кучей очепяток и ошибок, но в общих чертах должно быть понятно. А если нет — задавай свои ответы, завтра (если повезёт) гляну.

Источник

Error While installing: warning: wine cmd.exe /c echo ‘%AppData%’ returned empty string, error message «» #226

I’m fairly new to github and linux in general, apologies in advance.

**Description: **
After running ‘lutris -i Downloads/modorganizer2.yml’, installation does not complete. The full log is here, https://pastebin.com/QYVjkuCr; below I have copied the most recent messages. I was able to install mod organizer twice before, but I uninstalled MO2 trying to get the dialogue in Skyrim SE to work, and have not been able to reinstall. For what it’s worth, I haven’t run into the issues described in #61 this time around.

System Info:
OS: Drauger OS (Ubuntu 20.04 focal)
Wine Version: wine-6.0.1
Winetricks Version: 20210206-next — sha256sum: 75730c54ef76da9109f48a064bc53c61bb7301d690ab74fd3c23c719d1683de9

Terminal Output:
warning: wine cmd.exe /c echo ‘%AppData%’ returned empty string, error message «»
———
Monitored process exited.
Initial process has exited (return code: 256)
All children have exited.
Exit with returncode 256
2021-06-17 22:04:16,669: I can’t move /home/kyle/.cache/lutris/installer/mod-organizer-2/successful-prefix-preparation, it does not exist
None
2021-06-17 22:04:16,669: Error while completing task >: I can’t move /home/kyle/.cache/lutris/installer/mod-organizer-2/successful-prefix-preparation, it does not exist
None
File «/usr/lib/python3/dist-packages/lutris/util/jobs.py», line 34, in target
result = self.function(*args, **kwargs)
File «/usr/lib/python3/dist-packages/lutris/installer/commands.py», line 283, in move
raise ScriptingError(«I can’t move %s, it does not exist» % src)
2021-06-17 22:05:04,901: Cancelling installation of Mod Organizer 2

The text was updated successfully, but these errors were encountered:

Источник

Warning wine cmd exe c echo appdata returned empty string error message

Post by jstromsoe » Mon Apr 04, 2022 11:42 pm

Having some issues building Wine (stable branch, cloned from c7c729c0db7c3e246182a890de4c606f3e394d0e).

Distributor ID: Ubuntu
Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04
Codename: jammy

I’m building Wine from scratch because as of this writing there is no build for jammy (it’s brand new).

I’m able to successfully build for 64 bit Wine using:
«`
cd

/wine-dirs/wine64-build/
../wine-source/configure —enable-win64
make
«`
When I try to build for 32 bit (2nd part of instructions)
«`
cd

/wine-dirs/wine32-build/
PKG_CONFIG_PATH=/usr/lib32 ../wine-source/configure —with-wine64=../wine64-build
make
«`

I make it pretty far into the compile but it errors out on :
«`
gcc -m32 -o dlls/capi2032/capi2032.so -shared -Wl,-Bsymbolic -Wl,-soname,capi2032.so -Wl,-z,defs dlls/capi2032/unixlib.o dlls/ntdll/ntdll.so
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_isinstalled’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:117: undefined reference to `capi20_isinstalled’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_get_profile’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:112: undefined reference to `capi20_get_profile’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_get_serial_number’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:105: undefined reference to `capi20_get_serial_number’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_get_version’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:93: undefined reference to `capi20_get_version’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_get_manufacturer’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:85: undefined reference to `capi20_get_manufacturer’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_waitformessage’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:78: undefined reference to `capi20_waitformessage’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_get_message’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:71: undefined reference to `capi20_get_message’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_put_message’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:63: undefined reference to `capi20_put_message’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_release’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:56: undefined reference to `capi20_release’
/usr/bin/ld: dlls/capi2032/unixlib.o: in function `capi_register’:
/home/jstromsoe/wine-dirs/wine-build-32/../wine-source/dlls/capi2032/unixlib.c:48: undefined reference to `capi20_register’
collect2: error: ld returned 1 exit status
«`

Anyone have any ideas ? Any help super appreciated.

Re: Wine Build on Ubuntu 22.04

Post by jkfloris » Tue Apr 05, 2022 6:13 pm

A few things you can try:
— Build without PKG_CONFIG_PATH=/usr/lib32
I believe the gstreamer problem is solved in newer versions.

— Build without CAPI (Do you need ISDN support?)

Re: Wine Build on Ubuntu 22.04

Post by jstromsoe » Tue Apr 05, 2022 10:32 pm

Sooo close. I ran again with —without-capi and that got much further into the compile. I believe per the instructions you NEED to specify PKG_CONFIG to a 32 bit set of libraries or none of what’s being attempted with WoW (32 bit support win apps) would be accomplished. So I left that as you can see, but got another compiler error. Do I need to go install a 32 bit gstreamer version? If so, which and what dependencies? Thanks in advance!

Источник

Warning wine cmd exe c echo appdata returned empty string error message

Post by dE_logics » Thu Nov 10, 2011 5:16 am

I’m trying to install a program using winetricks, but I’m using a separate wine install and WINEPREFIX, I run any command as such —

WINEARCH=»win32″ WINE=’/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32′ WINEPREFIX=’/home/de/media_writeit!/temp(others)/walkthrough’ ./winetricks

/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32 cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Also in the winetricks wiki it has not been explained properly how to point out to a seperate wine install.

I tried exporting all the WINE, WINEPREFIX and WINEARCH variables, but it doesn’t workout.

On the other hand —

WINEPREFIX=’/home/de/media_writeit!/temp(others)/walkthrough’ ‘/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32/bin/wine’ cmd

C:>echo %ProgramFiles%
C:Program Files

Post by dimesio » Thu Nov 10, 2011 10:58 am

Post by dE_logics » Thu Nov 10, 2011 11:44 am

I tried that, it doesn’t matter —

WINEARCH=»win32″ WINE=’/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32/bin/wine’ WINEPREFIX=’/home/de/media_writeit!/temp(others)/walkthrough’ ./winetricks
——————————————————
/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32/bin/wine cmd.exe /c echo ‘%ProgramFiles%’ returned empty string
——————————————————

Post by dE_logics » Thu Nov 10, 2011 11:52 am

WINEPREFIX=/home/de/media_writeit!/temp(others)/walkthrough/ /home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32/bin/wine cmd.exe /c echo ‘%ProgramFiles%’

Post by dimesio » Thu Nov 10, 2011 2:40 pm

Post by dE_logics » Thu Nov 10, 2011 10:08 pm

Nothing will happen (and nothing happened), winetricks is only available in the current directory, so it says command not found.

WINEPREFIX=’/home/de/game/temp(game)/soundforge-10′ ./winetricks
——————————————————
wine cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Post by dimesio » Thu Nov 10, 2011 11:35 pm

Re: «cmd.exe /c echo ‘%ProgramFiles%’ returned empty st

Post by DanKegel » Fri Nov 11, 2011 12:13 am

dE_logics wrote: WINEARCH=»win32″ WINE=’/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32′ WINEPREFIX=’/home/de/media_writeit!/temp(others)/walkthrough’ ./winetricks

/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32 cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Also in the winetricks wiki it has not been explained properly how to point out to a seperate wine install.

I tried exporting all the WINE, WINEPREFIX and WINEARCH variables, but it doesn’t workout.

WINE is how you tell winetricks which wine to run.

WINEPREFIX is how you tell wine (and winetricks) where the fake C drive and
registry live.

Do you really have two versions of wine? What program are you trying to install?

(Dimesio: The ./ in front of winetricks is for when you’ve downloaded winetricks yourself
and not installed it, but have marked it executable.
If you haven’t marked it executable, you have to use ‘sh winetricks’.
If you use the winetricks installed by your distro, you don’t want the ./ or the sh.
This is all about how the shell searches for commands in the directories
listed in the PATH environment variable.)

Post by dE_logics » Fri Nov 11, 2011 1:40 am

dE_logics wrote: WINEARCH=»win32″ WINE=’/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32′ WINEPREFIX=’/home/de/media_writeit!/temp(others)/walkthrough’ ./winetricks

/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32 cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Also in the winetricks wiki it has not been explained properly how to point out to a seperate wine install.

I tried exporting all the WINE, WINEPREFIX and WINEARCH variables, but it doesn’t workout.

WINE is how you tell winetricks which wine to run.

WINEPREFIX is how you tell wine (and winetricks) where the fake C drive and
registry live.

Do you really have two versions of wine? What program are you trying to install?

Yes, this system is 64 bit and this problem exists when you try running a 64 bit wine prefix on a 32 bit wine installation. But in my case, every prefix is 32bit.

This time around, since the WINE variable doesn’t appear to be working, I had to drop it and use the prefix of wine-1.3.32 (static build) with wine-1.3.29 (system install). I installed a few packages using winetricks, after which it suddenly stopped working and started giving this error.

Later on (now) I noticed that some wine processes where still running in background which were causing this problem.

However, the main issue now is, the WINE variable doesn’t appear to be working.

I’m trying to make soundforge 10 work. Currently there analyzer graph is bank.

«cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Post by Martin Gregorie » Fri Nov 11, 2011 6:48 am

Some distros (the RedHat ones and probably others) don’t include ‘.’ or
$HOME in $PATH by default. The first thing I do when I set up a new
login users is to make sure ‘.’, $HOME and $HOME/bin are added to $PATH,
preferably at the right end. Its such an automatic action that its easy
to forget you did it years ago.

It sounds like your $HOME directory isn’t in your search path. Post the
output from this:

So we can see what your search path looks like.

Re: «cmd.exe /c echo ‘%ProgramFiles%’ returned empty st

Post by Usurp » Fri Nov 11, 2011 8:33 am

Some distros (the RedHat ones and probably others) don’t include ‘.’ or
$HOME in $PATH by default. The first thing I do when I set up a new
login users is to make sure ‘.’, $HOME and $HOME/bin are added to $PATH,
preferably at the right end. Its such an automatic action that its easy
to forget you did it years ago.

It sounds like your $HOME directory isn’t in your search path. Post the
output from this:

So we can see what your search path looks like.

Having ‘.’ and $HOME in $PATH can lead to subtle failures,
if you create a file that has the same name as an existing command.

Simple example: the updatedb command from mlocate

«cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Post by Martin Gregorie » Fri Nov 11, 2011 9:42 am

Having ‘.’ and $HOME in $PATH can lead to subtle failures,
if you create a file that has the same name as an existing command.

Simple example: the updatedb command from mlocate

That is why, if you’re wise, you always run ‘which’ to check check
whether the script/program name you just thought up is going to clash
with anything else. Its also why I said «add them to the right hand
end», as in:

$PATH is searched left to right, so doing it this way guarantees that
pre-existing stuff takes precedence over anything you wrote without
first checking for name clashes.

«cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Post by perryh » Fri Nov 11, 2011 9:15 pm

Re: «cmd.exe /c echo ‘%ProgramFiles%’ returned empty st

Post by dE_logics » Sat Nov 12, 2011 7:45 am

Some distros (the RedHat ones and probably others) don’t include ‘.’ or
$HOME in $PATH by default. The first thing I do when I set up a new
login users is to make sure ‘.’, $HOME and $HOME/bin are added to $PATH,
preferably at the right end. Its such an automatic action that its easy
to forget you did it years ago.

It sounds like your $HOME directory isn’t in your search path. Post the
output from this:

So we can see what your search path looks like.

I’ve not seen any distro which sets ‘.’ in it’s PATH.

Also why will I need $HOME in $PATH?

PATH for user is —
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3:/usr/games/bin

Also ‘.’ in $HOME doesn’t make sense.

Having ‘.’ and $HOME in $PATH can lead to subtle failures,
if you create a file that has the same name as an existing command.

Simple example: the updatedb command from mlocate

That is why, if you’re wise, you always run ‘which’ to check check
whether the script/program name you just thought up is going to clash
with anything else. Its also why I said «add them to the right hand
end», as in:

$PATH is searched left to right, so doing it this way guarantees that
pre-existing stuff takes precedence over anything you wrote without
first checking for name clashes.

«cmd.exe /c echo ‘%ProgramFiles%’ returned empty string

Post by Martin Gregorie » Sat Nov 12, 2011 8:55 am

I suggested adding $HOME/bin to your search path, not $HOME.

If you write small shell scripts, e.g. as wrappers for Wine applications
or as a short-hand for common actions and they are intended to only be
used from one login, then a convenient place to keep them is in a
$HOME/bin directory because this keeps clutter out of your login
directory. If you do this you’ll want to include $HOME/bin in the search
path for that login by editing .bash_profile

If such scripts are for more general use they should be put in
«/usr/local/bin» and any associated configuration files should be in
«/usr/local/etc». Make sure that the «/usr/local» structure is backed up
along with «/home».

You should reserve «/bin» and «/usr/bin» for programs and scripts that
are part of your distro. Apart from anything else, if you upgrade your
distro or do a clean install you may loose anything you put in those
directories while, if you backed up the contents of /usr/local then its
easy to drop it back in place after the upgrade or install.

Источник

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1]   Вверх

I’m new to linux and I’m trying to install wine so I can play Hearthstone.
I following this tutorial: https://linuxconfig.org/how-to-install-battle-net-on-ubuntu-22-04-linux-desktop

I run winetricks and everything is OK until Step 3. Then, I get some errors that even if I press OK, they keep reappering and nothing else happens — until I stop the terminal.

Below you can see both images that show up (somewhere between Step 3 and 4)

image1

image2

And here a paste of the terminal while the errors are happening:

guin0x@guin0x-server:~$ winetricks
Executing mkdir -p /home/guin0x
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Using winetricks 20210206 - sha256sum: 0f21da98811e0bfda16a7d6d6b8e860a9cedbd4e836c7dd9b02f068d3092ee2e with wine-6.0.3 (Ubuntu 6.0.3~repack-1) and WINEARCH=win64
winetricks GUI enabled, using zenity 3.42.1
Executing w_do_call corefonts
Executing mkdir -p /home/guin0x
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Executing load_corefonts 
Executing w_do_call andale
Executing mkdir -p /home/guin0x
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Executing load_andale 
Executing cabextract -q -d /home/guin0x/.wine/dosdevices/c:/windows/temp /home/guin0x/.cache/winetricks/corefonts/andale32.exe
------------------------------------------------------
warning: Running /usr/bin/wineserver -w. This will hang until all wine processes in prefix=/home/guin0x/.wine terminate
------------------------------------------------------
Executing wine regedit C:windowsTemp_register-font.reg
Executing wine64 regedit C:windowsTemp_register-font.reg
0100:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0100:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
00f8:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
00f8:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
Executing cp /home/guin0x/.wine/dosdevices/c:/windows/temp/_register-font.reg /tmp/winetricks.WeeZhyWc/_reg_90ad6a9f_10400.reg
Executing wine regedit C:windowsTemp_register-font.reg
Executing wine64 regedit C:windowsTemp_register-font.reg
0120:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0120:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0118:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0118:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
Executing cp /home/guin0x/.wine/dosdevices/c:/windows/temp/_register-font.reg /tmp/winetricks.WeeZhyWc/_reg_f6204652_10400.reg
Executing w_do_call arial
Executing mkdir -p /home/guin0x
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.

Thanks a lot in advance!