Hello, and a slight problem with WINE

linux-addict · 04-16-2003, 09:37 PM

Hello everyone....been hanging around this board for some time, decided to register finally

I had a question related to Red Hat 8.0 and WINE.

Tried installing the new version of WINE, but it failed to make a registry? I'm trying to get Warcraft 3 to work in Linux. Anyone know what went wrong? I've asked several people, but nobody seems to know what to do. And yes, already went through the WINE setup documentation and tried google.

Quote:

Searching for an existing Windows installation... not found. (no matching /etc/fstab mount entry found)

Windows was not found on your system, so I assume you want
a Wine-only installation. Am I correct?
(yes/no) yes

Configuring Wine without Windows.
Some fake Windows directories must be created, to hold any .ini files, DLLs,
start menu entries, and other things your applications may need to install.
Where would you like your fake C drive to be placed?
(default is /home/netracer/c)
Configuring Wine for a no-windows install in /home/netracer/c...

Created /home/netracer/.wine/config using default Wine configuration.
You probably want to review the file, though.

Compiling regedit...
make: Nothing to be done for `all'.

Preparing to install default Wine registry entries...
Installing default Wine registry entries...

Could not stat /mnt/fd0 (No such file or directory), ignoring drive A:
Could not stat /cdrom (No such file or directory), ignoring drive D:
Warning: could not find wine config [Drive x] entry for current working directory /usr/installed-programs/wine-20030408; starting in windows directory.
/usr/installed-programs/wine-20030408/miscemu/wine: cannot find 'programs/regedit/regedit.exe.so'
Registry install failed.

Did winecheck and got this:

Quote:

This script verifies the configuration of the whole Wine environment.
Note that this is an ALPHA version, and thus it doesn't catch all problems !
The results of the checks are printed on the right side:
OK - test passed without problems.
NOTICE - Not a problem but something for the user to be aware of.
SUSPICIOUS - potentially problematic. You might want to look into that.
BAD - This is a problem, and it leads to configuration score penalty.
CRITICAL - A critical problem which can easily lead to malfunction.
FAILED - This problem leads to Wine failure almost certainly.

The result will be printed as a percentage score indicating config completeness.

------------------------- checking miscellaneous stuff -------------------------
001. Checking for root user... OK.

--------------------------- checking Wine base files ---------------------------
002. Checking for file "wine"... OK.
003. Checking for correct .so lib config (please wait)... SUSPICIOUS (libwine.so found 2 times: /usr/lib/wine/libwine.so /usr/local/lib/libwine.so).
- ADVICE: check whether this is really ok.

----------------------------- checking config file -----------------------------
004. Checking config file access... OK.

>>> Checking drive A settings:
005. Checking Path option... OK.
006. Checking Type option... OK.
007. Checking device /dev/fd0... OK.
008. Checking Filesystem option... OK.
--> OK.

>>> Checking drive C settings:
009. Checking Path option... OK.
010. Checking Type option... OK.
011. Checking Filesystem option... OK.
--> OK.

>>> Checking drive D settings:
012. Checking Path option... OK.
013. Checking Type option... OK.
014. Checking device /dev/cdrom... OK.
015. Checking Filesystem option... OK.
--> OK.

>>> Checking drive E settings:
016. Checking Path option... SUSPICIOUS (directory /tmp/ksocket-root is not accessible for you).
- ADVICE: If your user account is supposed to be able to access
it properly, use chmod as root to fix it ("man chmod"). If that doesn't help, change mount options in case of VFAT ("umask" option).
017. Checking Type option... OK.
018. Checking Filesystem option... OK.
--> PROBLEM.

>>> Checking drive F settings:
019. Checking Path option... OK.
020. Checking Type option... OK.
021. Checking Filesystem option... OK.
--> OK.

--------------------- checking system devices used by Wine ---------------------
022. Checking sound device /dev/dsp... OK.
023. Checking audio mixer device /dev/mixer... OK.
024. Checking MIDI sequencer device /dev/sequencer... BAD (no kernel driver for /dev/sequenceror used by other program?).
- ADVICE: module loading problems ? Read /usr/src/linux/Documentation/modules.txt.

----------------------- checking registry configuration ------------------------
025. Checking availability of winedefault.reg entries... CRITICAL (entry "SHAREDMEMLOCATION" not found in system.reg registry file).
- ADVICE: file winedefault.reg, the most basic wine registry environment, doesn't seem to have been applied using regedit.
026. Checking availability of windows registry entries... NOTICE (entry "Default Taskbar" not found).
- ADVICE: A Windows registry does not seem to have been added to Wine as this typical Windows registry entry does not exist in Wine's registry. A complete original Windows registry entry set will *not* be available with a no-windows install. Usually this will present no problem in running applications although this can affect newer programs. Feel free to ignore this message in case you do use a Windows registry, but have the SaveOnlyUpdatedKeys config setting set to N..

26 tests. 2 suspicious, 1 bad, 1 critical, 0 failed.
Wine configuration correctness score: 79.94%

ALSO- I told it to do a "no windows install". Was that the right thing to do? I don't want to mount my windows directory, it is Windows 2000 -> NTFS.

yowwww · 04-16-2003, 11:27 PM

why not try winex?

linux-addict · 04-16-2003, 11:48 PM

What's the difference? It looks like Winex is mostly for a few specialized games. While that is good, I'd like to wine other stuff as well.

I'll also have that nagging feeling that I can't get something on my box to work...

linux-addict · 04-16-2003, 11:58 PM

There is also the little problem that I need to subscribe to use WineX, as I have just noticed

wr3ck3d · 04-17-2003, 01:19 AM

dont worry about the registry, thats what it does EVERY time. Go into the config and fix all this

Code:

Could not stat /mnt/fd0 (No such file or directory), ignoring drive A:
Could not stat /cdrom (No such file or directory), ignoring drive D:
Warning: could not find wine config [Drive x] entry for current working directory /usr/installed-programs/wine-20030408; starting in windows directory.
/usr/installed-programs/wine-20030408/miscemu/wine: cannot find 'programs/regedit/regedit.exe.so'
Registry install failed.

Then run 'wine' Then it will install the registry. How can it install the registry when it has no clue where the drives/directories are??

btw, you probably will need winex for warcraft. If it wc3 uses a installshield installer just go ahead and buy winex, if not get it from cvs for free.

linux-addict · 04-17-2003, 06:55 PM

K, I think I got the config like I should have. I have everything posinting towards the proper directories, but I still cannot get this to go. Tried running notepad.exe as "wine notepad.exe" and here is what happened..

Quote:

wine notepad.exe
wine: Symbol `Dosvm' has different size in shared object, consider re-linking
err:module:BUILTIN32_dlopen failed to load .so lib for builtin kernel32.dll: /usr/local/lib/wine/kernel32.dll.so: undefined symbol: BeginUpdateResourceA
err:module:PE_fixup_imports Module (file) kernel32.dll (which is needed by advapi32.dll) not found
err:module:load_library can't load advapi32.dll
err:module:BUILTIN32_LoadLibraryExA loaded .so but dll advapi32.dll still not found - library environment problem or version conflict, check your setup.
err:module:MODULE_LoadLibraryExA Loading of builtin DLL C:\WINDOWS\SYSTEM\advapi32.dll failed (error 14), check this file.
err:module:PE_fixup_imports Module (file) advapi32.dll (which is needed by ole32.dll) not found
err:module:load_library can't load ole32.dll
wine: Unhandled exception, starting debugger...
Warning: /usr/bin/winedbg.exe not accessible from a configured DOS drive
fixme:console:SetConsoleCtrlHandler (0x4052f0f0,1) - no error checking or testing yet
err:wineconsole:WCUSER_SetFont wrong font
err:wineconsole:WCUSER_SetFont wrong font
Terminated

looks like some linking errors, but I have no clue how to correct them. Any ideas?

*also, my default c:\ directory is /wine, and I copied the structure from /usr/share/wine-c to there. Could I be missing DLLs?

wr3ck3d · 04-18-2003, 11:35 AM

ok, when you just run 'wine' by itself what happens? does it give errors?? if so that is a config problem, if it says the version and options then config is good.

mhearn · 04-18-2003, 01:29 PM

You need WineHQ latest release for updated redhat 8 systems, try with that and see if it helps (CVS or the very latest release, nothing else is good enough)

linux-addict · 04-21-2003, 10:12 AM

Quote:

Originally posted by wr3ck3d
ok, when you just run 'wine' by itself what happens? does it give errors?? if so that is a config problem, if it says the version and options then config is good.

Sorry for the dealy- college studnet, lots of work to do

Quote:

wine: Symbol `Dosvm' has different size in shared object, consider re-linking
Wine 20020605

Usage: wine [options] [--] program_name [arguments]
The -- has to be used if you specify arguments (of the program)

Options:
--debugmsg name Turn debugging-messages on or off
--dll name Enable or disable built-in DLLs
--help,-h Show this help message
--version,-v Display the Wine versio

Looking back I think that it failed to uninstall the previous version of wine, thus the old version number.

linux-addict · 04-21-2003, 10:38 AM

Woohoo! Got it to work with notepad and sol.exe. Had to remove the old RPM's first- I though wineinstall did this, but I noticed that it kept screwing up along the way. It's all good now though. Now on to getting WC3 to work properly. Should it work if I copy all of the necessary DLL's into the c:\windows\system or \system32 folders from my windows install (2000) and then try to install off of the CD-ROM?

Thanks for all the help, and TIA for this question.

mhearn · 04-21-2003, 01:23 PM

Check the apps db, I have no idea if WarCraft 3 works with wine at all, if not then you'll either need to find a combination of native/builtin DLLs that works (there may not be any such combo), debug it yourself or get a wine developer to debug it for you. I recommend option 2.

Don't try and install DirectX into Wine, that won't work, you need to use Wines built in directx

mhearn · 04-21-2003, 01:44 PM

WarCraft 3 does not work with WineHQ. You'd need to check with TransGaming.

linux-addict · 04-21-2003, 02:38 PM

Quote:

Originally posted by mhearn
WarCraft 3 does not work with WineHQ. You'd need to check with TransGaming.

K, cool. I'll look into it. Thanks!!!

looper · 04-21-2003, 03:08 PM

did you check http://appdb.codeweavers.com to verify if warcraft works on wine ? or if it has been tested ?

linux-addict · 04-22-2003, 02:43 AM

Quote:

Originally posted by looper
did you check http://appdb.codeweavers.com to verify if warcraft works on wine ? or if it has been tested ?

Yup, it works on wine.
http://appdb.codeweavers.com/appview...versionId=1177