Thu, 10 Jan 2008 16:00:00 GMT Wine allows users to run Windows programs natively under Linux without paying a dime. However, there's a tiny problem: programs running in Wine don't look so great. They don't even try to fit into your native GNOME or KDE color scheme or use your preferred fonts. You could use a Windows theme, but themes make Wine run extremely slowly. Luckily, with a little configuration editing, it's easy to make Wine applications look at lot more like the rest of the apps on your desktop.
ok, here's the scoop, google has similar, but nothing that quite fits the bill. here is what I'm up against:
i have a linux system that is running both kde 3.x and gnome 2.x, selectable via gdm.
the kde 3.x app menu is heavily modified and i'm looking for a way to import that over to the... (0 Replies)
I've just done a brand new full clean install of OPenSUSE 10 and thought I'd take a look at Gnome. Having spent a day playing with it I've decided I prefer the familiarity I have with KDE.
How do I now install KDE? I've tried logging off to log back on with a different envionnment but KDE... (1 Reply)
i have been reading some atticles but i still do not understand the diferrence btw KDE & Gnome. Someone once told me he prefers Gnome to KDE 'coz of it's audio support & Redhat says ver 7.3 has KDE 3.0 & Gnome 1.4. So could someone explain? (2 Replies)
Hey all :)
I finally got around to installing FreeBSD 4.4, which considering it's my first attempt with *nix, didn't go too badly. I've managed to configure X and everything else, but I've got a bit of a problem, lol.
I installed KDE and GNOME. I had a rough idea as to what they were, but I... (5 Replies)
WINESERVER(1) Windows on Unix WINESERVER(1)NAME
wineserver - the Wine server
SYNOPSIS
wineserver [options]
DESCRIPTION
wineserver is a daemon process that provides to Wine roughly the same services that the Windows kernel provides on Windows.
wineserver is normally launched automatically when starting wine(1), so you shouldn't have to worry about it. In some cases however, it can
be useful to start wineserver explicitly with different options, as explained below.
OPTIONS
-d[n], --debug[=n]
Set the debug level to n. 0 means no debugging information, 1 is the normal level, and 2 is for extra verbose debugging. If n is
not specified, the default is 1. The debug output will be sent to stderr. wine(1) will automatically set the debug level when start-
ing wineserver if the +server option is set in the WINEDEBUG variable.
-f, --foreground
Make the server remain in the foreground for easier debugging, for instance when running it under a debugger.
-h, --help
Display a help message.
-k[n], --kill[=n]
Kill the currently running wineserver, optionally by sending signal n. If no signal is specified, sends a SIGINT first and then a
SIGKILL. The instance of wineserver that is killed is selected based on the WINEPREFIX environment variable.
-p[n], --persistent[=n]
Specify the wineserver persistence delay, i.e. the amount of time that the server will keep running when all client processes have
terminated. This avoids the cost of shutting down and starting again when programs are launched in quick succession. The timeout n
is in seconds, the default value is 3 seconds. If n is not specified, the server stays around forever.
-v, --version
Display version information and exit.
-w, --wait
Wait until the currently running wineserver terminates.
ENVIRONMENT VARIABLES
WINEPREFIX
If set, the content of this variable is taken as the name of the directory where wineserver stores its data (the default is
$HOME/.wine). All wine processes using the same wineserver (i.e.: same user) share certain things like registry, shared memory and
kernel objects. By setting WINEPREFIX to different values for different Wine processes, it is possible to run a number of truly
independent Wine sessions.
WINESERVER
Specifies the path and name of the wineserver binary that will be launched automatically by wine. If not set, wine will try to load
/usr/bin/wineserver, and if this doesn't exist it will then look for a file named wineserver in the path and in a few other likely
locations.
FILES
~/.wine
Directory containing user specific data managed by wine.
/tmp/.wine-uid
The directory containing the server Unix socket and the lock file. These files are created in a subdirectory generated from the
WINEPREFIX directory device and inode numbers.
AUTHORS
The original author of wineserver is Alexandre Julliard. Many other people have contributed new features and bug fixes. Please check the
file Changelog in the Wine distribution for the complete details.
BUGS
If you find a bug, please submit a bug report at http://bugs.winehq.org. <http://bugs.winehq.org>
AVAILABILITY
wineserver is part of the Wine distribution, which is available through WineHQ, the Wine development headquarters, at
http://www.winehq.org/. <http://www.winehq.org/>
SEE ALSO wine(1).
Wine 1.2-rc6 October 2005 WINESERVER(1)