05-29-2015
Should I get the file and run it under Wine? Would you recommend doing it in a certain way.
Thanks.
10 More Discussions You Might Find Interesting
1. IP Networking
We run Compaq UNIX Tru64 5.1.
After a switch got replaced our ethernet-card was magically set to
half duplex!
We saw, that the card was set to Autonegotiate:
vmunix: ee1: Autonegotiated, 100 Mbps full duplex
So we set the card with ifconfig to 100 Mbps full duplex with the
following... (3 Replies)
Discussion started by: arn_ch
3 Replies
2. UNIX for Dummies Questions & Answers
We are using ZIX 4.3.3 and we need to configure the NIC for ful duplexing and we also need to configure it for a TCP/IP default gateway and DNS server to acccess the Interent.
Can you please tell me the commands and procedures for configuring this?
Thanks
Marc (2 Replies)
Discussion started by: marc3483
2 Replies
3. UNIX for Dummies Questions & Answers
Ok at the moment I have a hub whit 5 computers connected to it. It's a 10/100 NetGear hub.
Ok I heard that there is some command I can run or a file I edit or something like that. But what the command/file/script/whatever does is tells you what connect speed it's connecting to the hub to.
... (4 Replies)
Discussion started by: merlin
4 Replies
4. UNIX for Dummies Questions & Answers
Dear Members,
I was reading a few posts and saw something about installing two Nics so one could use Full Duplex. I remember back in the day of dial up, you could have two modems and use one for upstream and one for downstream. This was called shotgunning. It seems that you can now do the same... (4 Replies)
Discussion started by: Phobos
4 Replies
5. Programming
what is meant by full duplex and half duplex?
b'coz in differences b\w hub and switch ,i heard lot this duplex word
so please help me (1 Reply)
Discussion started by: parvathy
1 Replies
6. Solaris
I need to change some Ip addresses for my servers to reflect in the NIS map.
I also need to force full duplex on the 10/100 cards & 1/2 duplex in the 10 cards.
I can change the IP by doing ifconfig <NIC card > plumb up <newip>.
Not quite sure on how to force the full / half duplex & how to... (2 Replies)
Discussion started by: Remi
2 Replies
7. SuSE
How do I configure full duplex on suse 8.2
I tried
ethtool -s eth0 speed 100 duplex full autoneg off
the above works but when I reboot the machine the configure was lost.
How do I configure full duplex so that when the machine get rebooted the configuration will stay.
My interface... (4 Replies)
Discussion started by: hassan2
4 Replies
8. UNIX for Advanced & Expert Users
I would like to change half duplex to full duplex on solaris 5.5. I tried with below commands but they didnt work on solaris 5.5.
#ndd -set /dev/le adv_100fdx_cap 1 (6 Replies)
Discussion started by: csreenivas
6 Replies
9. Solaris
Hi,
How to find whether the server is running with half duplex or full duplex. I tried with the following command ndd -get /dev/ but am not getting any output,. Is the command correct?
Also let me know how to change from half to full duplex. (1 Reply)
Discussion started by: rogerben
1 Replies
10. Programming
Hello,
here's my situation: I have a C++ server running on a well known machine and a number of Java clients running on other machines (assumed as unknown) on the same LAN. What I want to achieve is full duplex communication between those applications, in order to exchange complex objects and data... (3 Replies)
Discussion started by: demerzel3
3 Replies
LEARN ABOUT OSX
wineserver
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)